IBM Z Decision Support

Version 1.9

Administration Guide and Reference

IBM

SC27-9055-03
 Note
Before using this information and the product it supports, read the information in “Notices” on page
307.

This edition applies to Version 1 Release 9 of IBM Z Decision Support (5698-B06) and to all subsequent releases and
modifications until otherwise indicated in new editions.
Last updated: December 2024
© Copyright International Business Machines Corporation 1993, 2017.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.
© Teracloud ApS 2018, 2024.
Contents

Figures................................................................................................................ vii

Preface...............................................................................................................xiii
Who should read this book........................................................................................................................xiii
Publications............................................................................................................................................... xiii
Accessing publications online............................................................................................................. xiii
Accessibility............................................................................................................................................... xiii
Support information.................................................................................................................................. xiv
Conventions used in this book.................................................................................................................. xiv
Typeface conventions.......................................................................................................................... xiv
What's new in this edition (December 2024)............................................................................................ xv

Chapter 1. Introduction to IBM Z Decision Support................................................. 1

Introduction to IBM Z Decision Support performance features.................................................................2
Introduction to the log collector..................................................................................................................3
Log definitions........................................................................................................................................ 3
Record definitions...................................................................................................................................3
Update definitions.................................................................................................................................. 3
Table definitions..................................................................................................................................... 4
Log and record procedures.....................................................................................................................4
Collect process....................................................................................................................................... 4
Introduction to the IBM Z Decision Support database............................................................................... 6
Introduction to the administration dialog................................................................................................... 7
Introduction to the reporting dialog............................................................................................................ 7
Introduction to the Key Performance Metrics components....................................................................... 8
Introduction to the DataSplitter and the SMF Extractor............................................................................. 9
The SMF Extractor.................................................................................................................................. 9
Receiving raw SMF records from the SMF Extractor........................................................................... 10
Introduction to the Usage and Accounting Collector................................................................................11

Chapter 2. Installing IBM Z Decision Support .......................................................13

Installation prerequisites.......................................................................................................................... 13
Hardware prerequisites........................................................................................................................13
Software prerequisites......................................................................................................................... 13
Step 1: Reviewing the results of the SMP/E installation........................................................................... 15
Step 2: Automatic processing of SMF data using Hub and Spoke topology............................................ 17
Step 3: Setting up the Hub or stand-alone system................................................................................... 17
Step 3.1: Setting up security................................................................................................................17
Step 3.2: Initializing the Db2 database............................................................................................... 20
Step 3.3: Preparing the dialog and updating the dialog profile.......................................................... 21
Step 3.4: Setting personal dialog parameters.....................................................................................23
Step 3.5: Setting up QMF..................................................................................................................... 24
Step 3.6: Defining the log stream to communicate between the DataMover and the Continuous
Collector (Optional)......................................................................................................................... 25
Step 3.7: Defining the coupling facility structures attributes in the CFRM function couple data
set.................................................................................................................................................... 25
Step 3.8: Creating system tables......................................................................................................... 26
Step 3.9: Customizing JCL................................................................................................................... 27
Step 3.10: Testing the installation of the IBM Z Decision Support base............................................ 28
Step 3.11: Reviewing Db2 parameters................................................................................................ 30

iii
 Step 3.12: Determining partitioning mode and keys...........................................................................31
Step 3.13: Installing components....................................................................................................... 31
Step 4: Installing automated data gathering on the hub system or on a stand-alone system................32
Step 4.1: Defining the log stream to feed the Continuous Collector.................................................. 32
Step 4.2: Customizing the Continuous Collector JCL..........................................................................33
Step 4.3: Starting the Continuous Collector........................................................................................ 33
Step 4.4: Installing the SMF Extractor.................................................................................................33
Step 4.5: Configuring the SMF Extractor............................................................................................. 34
Step 4.6: Unpacking the DataMover.................................................................................................... 37
Step 4.7: Tailoring the DataMover on the Hub system........................................................................37
Step 4.8: Configuring the DataMover...................................................................................................37
Step 4.9: Testing the DataMover..........................................................................................................37
Step 4.10: Creating a vehicle for running the DataMover on the Hub system....................................37
Step 5: Installing automated data gathering on each Spoke system.......................................................38
Step 5.1: Defining the log stream to communicate between the SMF Extractor and the
DataMover....................................................................................................................................... 38
Step 5.2: Defining the coupling facility structures attributes in the CFRM function couple data
set.................................................................................................................................................... 40
Step 5.3: Installing the SMF Extractor.................................................................................................40
Step 5.4: Configuring the SMF Extractor............................................................................................. 40
Step 5.5: Unpacking the DataMover.................................................................................................... 43
Step 5.6: Tailoring the DataMover on the Spoke system.................................................................... 43
Step 5.7: Configuring the DataMover...................................................................................................43
Step 5.8: Clearing the log stream........................................................................................................ 43
Step 5.9: Start the SMF Extractor........................................................................................................ 44
Step 5.10: Testing the DataMover....................................................................................................... 44
Step 5.11: Creating a vehicle for running the DataMover on a Spoke system....................................44
Step 5.12: Activate automated data gathering on the Spoke systems...............................................45
Installing the Usage and Accounting Collector.........................................................................................46
Step 1: Customizing the Usage and Accounting Collector.................................................................. 46
Step 2: Allocating and initializing Usage and Accounting files........................................................... 48
Step 3: Processing SMF data using DRLNJOB2 (DRLCDATA and DRLCACCT).................................... 49
Step 4: Running DRLNJOB3 (DRLCMONY) to create invoices and reports.........................................51
Step 5: Processing Usage and Accounting Collector subsystems...................................................... 53
Installing multiple IBM Z Decision Support systems................................................................................53
Installing IBM Z Decision Support features separately............................................................................54

Chapter 3. Installation reference......................................................................... 57

SMF Configuration......................................................................................................................................57
Review the SID parameter................................................................................................................... 57
Review your SYS settings..................................................................................................................... 57
Review each of your SUBSYS settings................................................................................................. 57
Sample configuration members................................................................................................................ 58
DRLJSMFO - SMF Extractor control file............................................................................................... 58
DRLJSMFX - SMF Extractor startup procedure................................................................................... 58
Defining a DASD-only log stream.........................................................................................................60
Dialog parameters......................................................................................................................................60
Modifying the DRLFPROF data set....................................................................................................... 61
Overview of the Dialog Parameters window........................................................................................61
Dialog parameters - variables and fields............................................................................................. 63
Allocation overview.............................................................................................................................. 72
Defining objects......................................................................................................................................... 73
IBM Z Decision Support component installation.................................................................................73
Naming convention for IBM Z Decision Support definition members......................................................80
Naming convention for members of DRLvrm.SDRLDEFS.................................................................... 80
Naming convention for members of DRLVRM.SDRLRENU.................................................................. 80

iv
Chapter 4. Administering IBM Z Decision Support.................................................83
Extending the SMF extractor..................................................................................................................... 83
Configuration parameters..........................................................................................................................83
SMF Extractor console commands...................................................................................................... 85
Setting up operating routines.................................................................................................................... 86
Collecting log data................................................................................................................................86
Improving collect performance........................................................................................................... 95
Administering the IBM Z Decision Support database......................................................................... 96
Administering lookup and control tables.......................................................................................... 110
Administering reports........................................................................................................................ 111
Administering problem records......................................................................................................... 117
Working with components.......................................................................................................................119
Installing and uninstalling a component........................................................................................... 120
Working with table space profiles..................................................................................................... 128
Reviewing table space profiles prior to installation.......................................................................... 128
Reviewing the GENERATE statements for table spaces, tables, and indexes..................................129
Working with a component definition................................................................................................129
Working with definitions.......................................................................................................................... 134
Working with the contents of logs..................................................................................................... 135
Working with log definitions.............................................................................................................. 142
Working with record definitions in a log............................................................................................ 145
Working with tables and definitions........................................................................................................153
Working with data in tables............................................................................................................... 154
Working with tables and update definitions......................................................................................165
Working with the log data manager option............................................................................................. 186
Summary of how the log data manager is used................................................................................ 186
Invoking the log data manager.......................................................................................................... 187
Job step for recording a log data set for collection...........................................................................187
Modifying log collector statements................................................................................................... 189
Listing and modifying the list of log data sets to be collected..........................................................192
The DRLJLDMC collect job and the parameters it uses.................................................................... 195
Modifying the list of successfully collected log data sets................................................................. 198
Modifying the list of unsuccessfully collected log data sets.............................................................200
Working with the Continuous Collector...................................................................................................201
DataSplitter..............................................................................................................................................203
Configuring the SMF Extractor........................................................................................................... 203
Installing the DataSplitter..................................................................................................................203
Configuring the DataSplitter.............................................................................................................. 204
Direct streaming.................................................................................................................................204

Chapter 5. Administration reference...................................................................205

System tables and views......................................................................................................................... 205
Log collector system tables............................................................................................................... 205
Dialog system tables.......................................................................................................................... 215
Views on Db2 and QMF tables........................................................................................................... 221
Views on IBM Z Decision Support system tables..............................................................................221
Control tables and common tables......................................................................................................... 222
Control tables..................................................................................................................................... 222
CICS control tables............................................................................................................................ 224
Common data tables.......................................................................................................................... 225
Common lookup tables...................................................................................................................... 228
Sample component..................................................................................................................................230
Sample component............................................................................................................................ 231
SAMPLE_H, _M data tables................................................................................................................231
SAMPLE_USER lookup table.............................................................................................................. 232
Sample component reports............................................................................................................... 232

v
 Record definitions....................................................................................................................................235
SMF records........................................................................................................................................236
DFSMS/RMM records......................................................................................................................... 241
IMS SLDS records...............................................................................................................................242
DCOLLECT records............................................................................................................................. 244
EREP records...................................................................................................................................... 245
Linux on zSeries records.................................................................................................................... 245
RACF records......................................................................................................................................246
IBM Z Workload Scheduler................................................................................................................ 246
VM accounting records.......................................................................................................................246
VMPRF records................................................................................................................................... 247
z/VM Performance Toolkit records.................................................................................................... 247
Administration dialog options and commands....................................................................................... 248
IBM Z Decision Support dialog options............................................................................................. 248
IBM Z Decision Support commands.................................................................................................. 254
Administration reports............................................................................................................................ 255
3270 reports...................................................................................................................................... 256
Cognos reports................................................................................................................................... 271
Using the REXX-SQL interface................................................................................................................. 290
Calling the DRL1SQLX module...........................................................................................................290
Using the IBM Db2 Analytics Accelerator............................................................................................... 293
Relationship of Analytics Components to non-Analytics Components............................................ 294
Configuring Analytics Components for use with IBM Db2 Analytics Accelerator............................ 299
Collecting data for direct load to the Accelerator............................................................................. 301
Loading data into the Accelerator......................................................................................................301
Uninstalling components used with an IBM Db2 Analytics Accelerator.......................................... 302

Appendix A. Support information....................................................................... 305

Contacting IBM Support.......................................................................................................................... 305

Notices..............................................................................................................307
Trademarks.............................................................................................................................................. 308

Bibliography...................................................................................................... 309
IBM Z Decision Support publications......................................................................................................309
Glossary............................................................................................................ 311

Index................................................................................................................ 315

vi
Figures

1. Overview of IBM Z Decision Support............................................................................................................ 1

2. Overview of IBM Z Decision Support batch collection................................................................................. 2

3. Overview of IBM Z Decision Support automated data gathering and continuous collection......................2

4. Overview of the data collection and processing steps................................................................................. 5

5. Overview of the setup for data collection and reporting.............................................................................. 6

6. Administration window................................................................................................................................. 7

7. Introducing the Reporting dialog.................................................................................................................. 8

8. SMF Extractor.............................................................................................................................................. 10

9. Using the CDPz Data Streamer:.................................................................................................................. 11

10. IBM Z Decision Support Administration Dialog........................................................................................23

11. Dialog Parameters window....................................................................................................................... 24

12. System Tables (not created) window....................................................................................................... 26

13. Logs window..............................................................................................................................................28

14. Collect window.......................................................................................................................................... 29

15. Reports window........................................................................................................................................ 29

16. Data Selection window............................................................................................................................. 30

17. System Tables (created) window..............................................................................................................55

18. DRLJSMFO: Parameters for the SMF Extractor control file......................................................................58

19. DRLJSMFX: JCL for the SMF Extractor startup procedure....................................................................... 59

20. JCL to define a DASD-only log stream......................................................................................................60

21. Dialog Parameters window, when QMF is used....................................................................................... 62

22. Dialog Parameters window, when QMF is not used................................................................................. 63

23. IBM Z Decision Support definition member DRLISAMP, setting component definitions....................... 74

vii
 24. IBM Z Decision Support definition member DRLLSAMP, defining a log type.......................................... 76

25. IBM Z Decision Support definition member DRLRSAMP, defining a record type.................................... 76

26. Using SQL to define a table space (see definition member DRLSSAMP).................................................76

27. Using GENERATE to define a table space (see definition member DRLSKZJB)......................................77

28. IBM Z Decision Support definition member DRLOSAMP, defining reports and report groups............... 79

29. IBM Z Decision Support definition member DRLQSA01, report query....................................................80

30. Invoking the log collector in batch to collect data................................................................................... 87

31. Sample collect messages......................................................................................................................... 91

32. Collect Statistics window..........................................................................................................................94

33. Db2 environment for the IBM Z Decision Support database................................................................... 97

34. Tablespace list window.............................................................................................................................97

35. Tables window - Option 12..................................................................................................................... 101

36. Tablespace list window...........................................................................................................................102

37. DRLJPURG job that uses all purge conditions........................................................................................104

38. Tables window -Option 10......................................................................................................................105

39. DRLJCOPY job for backing up IBM Z Decision Support table spaces................................................... 106

40. DRLJRUNS job for generating Db2 statistics..........................................................................................108

41. DB2I Primary Option Menu.....................................................................................................................110

42. Using QMF to report in batch..................................................................................................................117

43. Space pull-down..................................................................................................................................... 121

44. Installation Options window...................................................................................................................122

45. Sample log collector messages.............................................................................................................. 123

46. Lookup Tables window............................................................................................................................124

47. Editing an installation job....................................................................................................................... 125

48. Select Table window............................................................................................................................... 126

viii
49. Tables window - showing component's lookup tables.......................................................................... 126

50. Component window................................................................................................................................ 130

51. Data Sets window................................................................................................................................... 136

52. Collect Statistics window........................................................................................................................136

53. Collect window........................................................................................................................................137

54. Sample log statistics output................................................................................................................... 139

55. Record Data window............................................................................................................................... 140

56. List Record window.................................................................................................................................141

57. Output from List record function............................................................................................................ 141

58. Log Definition window.............................................................................................................................143

59. Record Definitions window..................................................................................................................... 145

60. Record Definition window.......................................................................................................................146

61. Field Definition window.......................................................................................................................... 147

62. Section Definition window...................................................................................................................... 148

63. Record Procedure Definition window.....................................................................................................151

64. Tables window........................................................................................................................................ 154

65. Using QMF to display an IBM Z Decision Support table........................................................................ 155

66. Table Size window...................................................................................................................................157

67. Recalculate window................................................................................................................................158

68. Condition window................................................................................................................................... 158

69. Column Values window...........................................................................................................................159

70. Selecting tables to unload...................................................................................................................... 161

71. Unload Utility window.............................................................................................................................161

72. Db2 High Performance Unload utility.....................................................................................................164

73. Table window.......................................................................................................................................... 166

ix
 74. Column Definition window......................................................................................................................166

75. Add Column window............................................................................................................................... 167

76. Indexes window...................................................................................................................................... 168

77. Index window..........................................................................................................................................168

78. Add Index window.................................................................................................................................. 169

79. Update Definitions window.....................................................................................................................170

80. Update Definition window...................................................................................................................... 170

81. Abbreviations window............................................................................................................................ 172

82. Distribution window................................................................................................................................ 173

83. Apply Schedule window..........................................................................................................................174

84. Retention Period window........................................................................................................................175

85. Purge Condition window......................................................................................................................... 175

86. Tablespaces window...............................................................................................................................176

87. Tablespace DRLxxx................................................................................................................................. 177

88. Indexes window...................................................................................................................................... 178

89. Index window..........................................................................................................................................178

90. Tablespace window................................................................................................................................ 179

91. View window........................................................................................................................................... 180

92. New Table window.................................................................................................................................. 182

93. Grant Privilege window........................................................................................................................... 185

94. Revoke Privilege window........................................................................................................................ 186

95. Log Data Manager Main Selection window.............................................................................................187

96. Collect Statements window....................................................................................................................190

97. Edit collect statements window............................................................................................................. 191

98. Add Collect Statements Definition window........................................................................................... 192

x
99. Modify Collect Statements Definition window....................................................................................... 192

100. SMF Log Data Sets To Be Collected window........................................................................................ 193

101. Modify Log ID For a Log Data Set window............................................................................................194

102. Add a Data Set To Be Collected window.............................................................................................. 195

103. Log Data Sets Collected Successfully window.....................................................................................198

104. Retention Period window..................................................................................................................... 199

105. Log Data Sets Collected with Failure window...................................................................................... 200

106. Sample data flow.................................................................................................................................. 231

107. Sample Report 1................................................................................................................................... 233

108. Sample Report 2................................................................................................................................... 234

109. Sample Report 3................................................................................................................................... 235

110. Indexspace Cross-Reference report.................................................................................................... 257

111. Actual Tablespace Space Allocation report......................................................................................... 258

112. Table Purge Condition report................................................................................................................259

113. Table Structure with Comments report................................................................................................260

114. Table Names with Comments report................................................................................................... 261

115. Object Change Level report.................................................................................................................. 262

116. Collected Log Data Sets report.............................................................................................................263

117. Components and Subcomponents report............................................................................................264

118. Tablespace Allocation report............................................................................................................... 265

119. Update Definitions report..................................................................................................................... 266

120. Update Details report........................................................................................................................... 267

121. Table Name to Tablespace Cross-Reference report............................................................................ 268

122. Tablespace to Table Name Cross-Reference report............................................................................ 269

123. System Tables report............................................................................................................................270

xi
 124. Non-System Tables Installed report.................................................................................................... 271

125. Indexspace Cross-Reference report.................................................................................................... 272

126. Actual Tablespace Space Allocation report......................................................................................... 273

127. Table Purge Condition report................................................................................................................274

128. Table Structure with Comments report................................................................................................275

129. Table Names with Comments report................................................................................................... 276

130. Object Change Level report.................................................................................................................. 277

131. Collected Log Data Sets report.............................................................................................................278

132. Components and Subcomponents report............................................................................................279

133. Tablespace Allocation report............................................................................................................... 281

134. Update Definitions report..................................................................................................................... 282

135. Update Details report........................................................................................................................... 283

136. Table Name to Tablespace Cross-Reference report............................................................................ 284

137. Tablespace to Table Name Cross-Reference report............................................................................ 286

138. System Tables report............................................................................................................................287

139. Non-System Tables Installed report.................................................................................................... 289

140. Example of REXX-SQL interface call.................................................................................................... 293

xii
Preface
This book provides an introduction to IBM Z Decision Support, the administration dialog and the reporting
dialog. It describes procedures for installing the base product and its features and for administering IBM
Z Decision Support through routine batch jobs and the administration dialog.
It also describes how to setup and configure for extended reporting capability through interfacing
analytics tools, both on and off-platform.
The terms listed are used interchangeably throughout the guide:
• MVS, OS/390®, and z/OS.
• VM and z/VM®.

Who should read this book

The Administration Guide and Reference is for the IBM Z Decision Support administrator, the person who
initializes the IBM Z Decision Support database, and customizes and administers IBM Z Decision Support.
Readers should be familiar with the following:
• Db2® and its utilities
• Query Management Facility (QMF), if QMF is used with IBM Z Decision Support
• Time Sharing Option Extensions (TSO/E)
• Restructured Extended Executor (REXX) language
• Job control language (JCL)
• Interactive System Productivity Facility/Program Development Facility (ISPF/PDF) and its dialog
manager functions

Publications
This section describes how to access the IBM Z Decision Support publications online.
For a list of publications and related documents, refer to “IBM Z Decision Support publications” on page
309.

Accessing publications online

Publications for this and all other IBM products, as they become available and whenever they are
updated, can be viewed in IBM Documentation from where you can also download the associated PDF.
IBM Z Decision Support 1.9.0
https://www.ibm.com/docs/en/z-decision-support
IBM Documentation
https://www.ibm.com/docs

Accessibility
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to
use software products successfully.
With this product, you can use assistive technologies to hear and navigate the interface. You can also use
the keyboard instead of the mouse to operate all features of the graphical user interface.
For additional information, refer to the IBM Accessibility website:
https://www.ibm.com/accessibility

© Copyright IBM Corp. 1993, 2017 xiii

Support information
If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following
ways for you to obtain the support you need:
• Searching knowledge bases: You can search across a large collection of known problems and
workarounds, Technotes, and other information.
• Obtaining fixes: You can locate the latest fixes that are already available for your product.
• Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with
someone from IBM, you can use a variety of ways to contact IBM Software Support.
For more information about these three ways of resolving problems, see Appendix A, “Support
information,” on page 305.

Conventions used in this book

This guide uses several conventions for special terms and actions, operating system-dependent
commands and paths, and margin graphics.
The following terms are used interchangeably throughout this book:
• MVS, OS/390, and z/OS.
• VM and z/VM.

Typeface conventions
This guide uses the following typeface conventions:
Bold
• Lowercase commands and mixed case commands that are otherwise difficult to distinguish from
surrounding text
• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons,
list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs,
property sheets), labels (such as Tip, and Operating system considerations)
• Column headings in a table
• Keywords and parameters in text
Italic
• Citations (titles of books, diskettes, and CDs)
• Words defined in text
• Emphasis of words (words as words)
• Letters as letters
• New terms in text (except in a definition list)
• Variables and values you must provide
Monospace
• Examples and code examples
• File names, programming keywords, and other elements that are difficult to distinguish from
surrounding text
• Message text and prompts addressed to the user
• Text that the user must type
• Values for arguments or command options

xiv Preface
What's new in this edition (December 2024)
The changes in this edition relate to IBM Z Decision Support 1.9.0 new function and enhancements.
The changes apply to the PTFs for the following APARs and other documentation improvements.
• APAR PH61370 - DRLJCOLL job:
– “Using the DRLCHECKPOINT table” on page 89
Technical changes are marked in the PDF with a vertical bar in the margin to the left of the change.

Changes in previous editions

November 2024
• APAR PH52322 and PH56662 - DataMover:
– Added before you begin section: “Step 5.12: Activate automated data gathering on the Spoke
systems” on page 45
– Added recommendation to use a DASD-only log stream and updated JCL: “Defining a DASD-only
log stream” on page 60
• APAR PH49313 and PH60858 - SMF Extractor:
– Updated DRLJSMFX JCL for the SMF Extractor startup procedure, and added parameter
descriptions: Figure 19 on page 59
– Added DRLFPROF variables db2exit and def_lobbpool: “Dialog parameters - variables and fields”
on page 63
– Added console command STATUS MEMORY: “SMF Extractor console commands” on page 85
• Editorial change:
– Updated Reorg/Discard JCL: “Reorg/Discard utility” on page 101
December 2022
• APAR PH45558 - Db2 component:
– Added Db2 V13 toleration: “Step 3.2: Initializing the Db2 database” on page 20
• APAR PH45278 - Continuous Collector:
– Added new information: “Working with the Continuous Collector” on page 201
• Updated instructions to specify the maximum memory size for Java in the Shell script to run the
DataMover:
– “Step 4.7: Tailoring the DataMover on the Hub system” on page 37
– “Step 5.6: Tailoring the DataMover on the Spoke system” on page 43
May 2022
• APAR PH44198 - SMF Extractor:
– Changed TRACE(Y) to TRACE(N) on the PARM option in “DRLJSMFX - SMF Extractor startup
procedure” on page 58
– Updated the F smfext,STOP command in “SMF Extractor console commands” on page 85
November 2021
• APAR PH38154 - Db2 Admin Authority reporting enhancements:
– “Administration reports” on page 255
• Updated DataMover instructions:
– “Step 3.6: Defining the log stream to communicate between the DataMover and the Continuous
Collector (Optional)” on page 25

Preface xv
 • Added new information for “Step 3.2: Initializing the Db2 database” on page 20
• Included AGGR_VALUE as a common lookup table
September 2021
• APAR PH07965 - Db2 Delta Statistics:
– Added a new lookup table: “TIME_RES” on page 229
– “Example of table contents” on page 230
June 2021
• APAR PH33645 - z/OS Connect EE, added new information:
– “Dialog parameters - variables and fields” on page 63
– “SMF records” on page 236
• Updated DataSplitter description:
– “Introduction to the DataSplitter and the SMF Extractor” on page 9
– “Receiving raw SMF records from the SMF Extractor” on page 10
– “DataSplitter” on page 203
– “Configuring the DataSplitter” on page 204
March 2021
• Added new information for “Introduction to the DataSplitter and the SMF Extractor” on page 9
• Modified the structure and added new information to Chapter 3:
– “SMF Configuration” on page 57
– “Review the SID parameter” on page 57
– “Review your SYS settings” on page 57
– “Review each of your SUBSYS settings” on page 57
– Moved from Chapter 4: “Sample configuration members” on page 58
• Modified the structure and added new information to Chapter 4:
– “Extending the SMF extractor” on page 83
– “Configuration parameters” on page 83
– “SMF Extractor console commands” on page 85
– “DataSplitter” on page 203
– “Configuring the SMF Extractor” on page 203
– “Installing the DataSplitter” on page 203
– “Configuring the DataSplitter” on page 204
– “Direct streaming” on page 204
November 2020
• Clarified architecture considerations for installation prerequisites: “Software prerequisites” on page
13
• Updated migration instructions for moving to IBM Z Decision Support from an earlier version:
Chapter 2, “Installing IBM Z Decision Support ,” on page 13
• Improved instruction clarity for Secure Setup Procedure: “Step 3.1: Setting up security” on page
17
• Removed instructions for establishing separate storage groups: “Step 3.2: Initializing the Db2
database” on page 20
• Modified instructions for reviewing Db2 parameters: “Step 3.11: Reviewing Db2 parameters” on
page 30

xvi Preface
• Improved instruction for SMF Extractor installation
• Updated off-platform reporting instructions "Step 6: Setting up data streaming"
• Improved sample JCL for log streaming to coupling facility
• Updated DataMover parameters
• Clarified the description of modtenu field: “Dialog parameters - variables and fields” on page 63
• Updated STEPLIB instructions for sample DRLJCOLL job: “The DRLJCOLL job” on page 87
• Improved instruction for DRLDB database table space: “Understanding table spaces” on page 97
• APAR PH29556: Added new instruction for dynamically modifying Continuous Collector commit
interval

Preface xvii
xviii IBM Z Decision Support : Administration Guide and Reference
Chapter 1. Introduction to IBM Z Decision Support
IBM Z Decision Support enables you to effectively manage the performance of your system by collecting
performance data in a Db2 database and presenting the data in a variety of formats for use in systems
management.
After reading this topic, you should have a basic understanding of IBM Z Decision Support and be ready to
install it.
IBM Z Decision Support has two basic functions:
1. Collecting systems management data into a Db2 database.
2. Reporting on the data.
IBM Z Decision Support consists of a base product and several optional features.
The IBM Z Decision Support base can generate graphical and tabular reports using systems management
data it stores in its Db2 database. To display graphical reports, IBM Z Decision Support can use IBM
Graphical Data Display Manager (GDDM) or web reporting tools such as IBM Cognos Analytics. You can
also send the data to other platforms for further analysis and reporting using interfacing products such as
Splunk and ELK.
The IBM Z Decision Support Administration and Reporting dialogs enable you to specify your data
collection and reporting requirements. An overview of the setup for data collection and reporting is shown
in Figure 1 on page 1. Use the Administration dialog is to define to the Log Collector the type of log data
that you want to collect from SMF, IMS, and other systems to store in Db2 databases. Use the Reporting
dialog to define to the report generator the reports that you want produced.

Administration Reporting
dialog dialog

Tabular
reports

Report
generator
SMF Charts
log
Reporting
tools

Log Jobs and

IMS collector utilities
Db2
log

Other
logs

Figure 1. Overview of IBM Z Decision Support

You can use IBM Z Decision Support for batch data collection and periodic reporting. When familiar with
batch operation, you can implement more advanced configurations for automated data gathering and
continuous collection.

© Copyright IBM Corp. 1993, 2017 1

Introduction to IBM Z Decision Support performance features

Data transfer Aggregate data is

SYS1
SMF Extract SMF must be complete Batch job to run the
Log Collector
written to Db2
before each batch run during the batch run
Data

SMF
Data Batch Log Db2
Extract SMF
SYS2

SMF SMF Collector

SYSX
Data
Data

SMF Reports
Data

SMF
SYS3

SMF Extract
Data Updated reports, based
on the aggregated data,
become available at the
end of each batch run

Figure 2. Overview of IBM Z Decision Support batch collection

IBM Z Decision Support

agents to gather and
transmit the data

Data Aggregate data is

SYS1

Log Collector adapted

SMF IBM Z Decision Support
for continuous
written to Db2 as
Sender agent to read the
incoming data
operation
it becomes available

Continuous Db2
Data Data
SYS2

SMF Collector

SYSX
Sender Receiver

Reports

Data
SYS3

SMF Sender Current reports available

as soon as the aggregate
data behind them has
been updated

Figure 3. Overview of IBM Z Decision Support automated data gathering and continuous collection

Introduction to IBM Z Decision Support performance features

IBM Z Decision Support performance features provide Db2 table definitions and table update instructions
for collecting required systems management data. They also provide predefined queries, forms, and
reports for presenting that data.
Resource Accounting for z/OS is part of the IBM Z Decision Support base function.
The following performance features are additional to the base function:
• AS/400 System Performance feature
• Customer Information Control System (CICS) Performance feature
• Distributed Systems Performance feature
• Information Management System (IMS) Performance feature
• Network Performance feature
• System Performance feature

2 IBM Z Decision Support : Administration Guide and Reference

 Introduction to the log collector

These features are used to collect and report on systems management data, such as System Management
Facility (SMF) data or IMS log data.
Each IBM Z Decision Support performance feature has components, which are groups of related IBM
Z Decision Support definitions. For example, the z/OS Performance Management (MVSPM) component
consists of everything IBM Z Decision Support needs to collect log data and create reports showing z/OS
performance characteristics.

Introduction to the log collector

At the center of IBM Z Decision Support is the log collector program that reads and processes
performance data. Log collector tasks are controlled by log, record, update, and other definitions in IBM
Z Decision Support system tables. For more information, see “Log collector system tables” on page 205.
You can add or modify definitions with both the administration dialog (see “Introduction to the reporting
dialog” on page 7) and log collector language statements. For information on the administration dialog,
see “Introduction to the administration dialog” on page 7.
IBM Z Decision Support provides both batch and interactive processing of log collector language
statements. For a description of the log collector and the language, refer to the Language Guide and
Reference.
The key function of the log collector is to read data and store it in data tables in the IBM Z Decision
Support database. The log collector groups the data by hour, day, week, or month. It computes sums,
maximum or minimum values, averages, and percentiles, and calculates resource availability. The collect
process, also referred to as collecting data or as collect, includes gathering, processing, and storing the
data.

Log definitions
IBM Z Decision Support gathers performance data about systems from sequential data sets such as those
written by SMF under z/OS, or by the Information Management System (IMS). These data sets are called
log data sets or logs.
To collect log data, IBM Z Decision Support needs log descriptions. The log collector stores descriptions of
logs as log definitions in the IBM Z Decision Support database. All log definitions used by IBM Z Decision
Support features are provided with the base product.
The administration dialog enables you to create log definitions or modify existing ones. For more
information, see “Working with log and record definitions” on page 134.
The log collector language statement, DEFINE LOG, also enables you to define logs. For more information,
refer to the description of defining logs in the Language Guide and Reference.

Record definitions
Each record in a log belongs to one unique record type. Examples of record types include SMF record
type 30, generated by z/OS, and SMF record type 110, generated by CICS. For IBM Z Decision Support
to process a record, the record type must be defined. Detailed record layouts, field formats, and offsets
within a record, are described in IBM Z Decision Support record definitions. All record definitions used by
IBM Z Decision Support features are provided with the base product.
The administration dialog enables you to create and modify record definitions. For more information, see
“Working with log and record definitions” on page 134.
The log collector language statement, DEFINE RECORD, also enables you to define records. For more
information, refer to the description of defining records in the Language Guide and Reference.

Update definitions
Instructions for processing data and inserting it into tables in the IBM Z Decision Support database are
provided in update definitions. Each update definition describes how data from a source (either a specific
record type, or a row of a table) is manipulated and inserted into a target (a row in a table). The update

Chapter 1. Introduction to IBM Z Decision Support 3

Introduction to the log collector

definitions used by an IBM Z Decision Support component are provided with the feature that contains the
component.
The administration dialog enables you to create update definitions or modify them. For more information,
see “Displaying and modifying update definitions of a table” on page 169.
The log collector language statement, DEFINE UPDATE, also enables you to define updates. For more
information, refer to the description of defining updates in the Language Guide and Reference.

Table definitions
IBM Z Decision Support stores data collected from log data sets in its database tables. It also stores
IBM Z Decision Support system data in system tables and site-specific operating definitions in lookup
and control tables. A table definition identifies the database and table space in which a table resides, and
identifies columns in the table. The table definitions used exclusively by the feature components in IBM Z
Decision Support are provided with the feature.
The administration dialog enables you to create or modify lookup and data table definitions. For more
information, see “Working with tables and update definitions” on page 153.

Log and record procedures

Log procedures and record procedures are user exit programs for specific data collection scenarios.
Record procedures work on specific record types. Log procedures work on an entire log. The log and
record procedures used by IBM Z Decision Support features are provided with the base product.
For information about creating log and record procedure exits, refer to the Language Guide and Reference.
The administration dialog enables you to view and modify record procedure definitions, to identify
record definitions that require processing by record procedures, and to define record definitions that are
output from a record procedure. For more information, see “Viewing and modifying a record procedure
definition” on page 150.

Collect process
When definitions exist for a log, the log records, the log update instructions for record data, and target
data tables, you can collect data from that log. You start the collect process:
• From the administration dialog.
• With the log collector language statement COLLECT.
The log collector retrieves stored definitions and performs the data collection that they define.
Figure 4 on page 5 shows the collect process.

4 IBM Z Decision Support : Administration Guide and Reference

 Introduction to the log collector

1 Log data

IBM Z Decision Support

Collect

3a
2 Log definition Log procedure

3b

5a

4 Record definitions 5b Record procedures

7
6 Update definitions Lookup tables

9a

8 Data tables 9b Update definitions

11
10 SQL queries Lookup tables

12 Reports

Figure 4. Overview of the data collection and processing steps

IBM Z Decision Support processes data in these steps:

1. The operating system or other program writes data to a sequential log data set, which is the input to
IBM Z Decision Support.
2. You initiate the collect either through the dialog or by using an IBM Z Decision Support language
statement in a job, identifying a specific log type definition.
3. Optionally, the log definition might process the log data with a user exit program; a log procedure. If
the log definition calls a log procedure:
a. The log procedure receives each record in the log as input.
b. Output from a log procedure varies in format and is usually a record mapped by an IBM Z Decision
Support record definition.
4. IBM Z Decision Support looks for record definitions associated with the log definition in its system
tables. It applies those record definitions to specific record types from the log or log procedure.
5. Optionally, a record definition might require processing by a user exit program; a record procedure. If
a record definition requires processing by a record procedure:
a. The record procedure receives only a specific record type and is not called for other record types.
b. Output from a record procedure varies in format and is usually a record mapped by an IBM Z
Decision Support record definition.
6. IBM Z Decision Support applies a specific update definition to each known record type and performs
the data manipulations and database updates as specified.

Chapter 1. Introduction to IBM Z Decision Support 5

Introduction to the IBM Z Decision Support database

7. IBM Z Decision Support often selects data from lookup tables to fulfill the data manipulations that
update definitions require.
8. IBM Z Decision Support writes non-summarized and first-level summarized data to data tables
specified by the update definitions.
9. IBM Z Decision Support uses updated tables as input for updating other, similar tables that are for
higher summary levels. If update definitions specify data summarization:
a. IBM Z Decision Support selects data from a table as required by the update definitions and
performs required data summarization.
b. IBM Z Decision Support updates other data tables as required by update definitions.
c. IBM Z Decision Support might select data from lookup tables during this process (although that is
not shown in the diagram for this step).
10. After IBM Z Decision Support stores the data from a collect, you can display reports on the data. IBM
Z Decision Support uses a query to select the data for the report.
11. Optionally, IBM Z Decision Support might select data from lookup tables specified in the query.
12. IBM Z Decision Support creates report data, displaying, printing, and saving it as you requested.
For more information about collecting log data, see “Setting up operating routines” on page 86.

Introduction to the IBM Z Decision Support database

The IBM Z Decision Support database contains system tables, lookup tables, and collected data. Log
collector processing transforms large amounts of log data into useful information about your systems and
networks. The volume of this information in the data tables is less than the volume of data read from logs.
An overview of the architecture and data flow from collecting, filtering and storing in the IBM Z Decision
Support Db2 database through to analysis and reporting is shown in Figure 5 on page 6.

Lookup tables
Log data

Log Record Update

SQL queries
definition definitions definitions Data tables

Log procedure Record Update

Reports
procedures definitions

Architecture - Data Flow

Figure 5. Overview of the setup for data collection and reporting

IBM Z Decision Support stores data that it collects in hourly, daily, weekly, and monthly tables, and
in non-summarized tables. It maintains groups of tables that have identical definitions except for their
summarization levels. For example, the EREP component of the System Performance feature creates the
data tables EREP_DASD_D and EREP_DASD_M, which differ only because one contains daily data and the
other, monthly data.
Because the IBM Z Decision Support database is relational, you can:
• Combine information from any of your systems into a single report.
• Summarize by system within department, by department within system, or by whatever grouping is
required.

6 IBM Z Decision Support : Administration Guide and Reference

 Introduction to the administration dialog

You can keep data tables containing historical data for many years without using much space. The
database size depends mainly on the number of short-term details you keep in it and not on summarized
weekly or monthly data.
The IBM Z Decision Support database contains operating definitions in its system tables. These
definitions include those for logs, records, updates, and tables shipped with IBM Z Decision Support.
The database also contains lookup tables of parameters that you supply, such as performance objectives
or department and workload definitions for your site.

Introduction to the administration dialog

The administration dialog enables you to carry out the following tasks:
1. Install and customize IBM Z Decision Support and its features.
2. Install and customize IBM Z Decision Support components.
3. Work with log and record definitions.
4. Work with tables in the IBM Z Decision Support database.
5. Create and run reports.
All of these options are available from the Administration window (Figure 6 on page 7).

Options Other Utilities Help

------------------------------------------------------------------------------
IBM Z Decision Support Administration
Option ===> __________________________________________________________________

1 System Perform IZDS system tasks System ID . . : AUS1

2 Components Install IZDS components Db2 Subsystem : DEC1
3 Logs Show installed IZDS log objects IZDS plan name : DRLPLAN
4 Tables Show installed IZDS data tables System tables : DRLSYSYY
5 Reports Run IZDS reports Data tables . : DRLYY

F1=Help F2=Split F3=Exit F9=Swap F10=Actions F12=Cancel

Figure 6. Administration window

Introduction to the reporting dialog

The IBM Z Decision Support reporting dialog enables you to display reports that present the log data
stored in the product database. When you use the reporting dialog to display or print a report, IBM Z
Decision Support runs a query associated with the report to retrieve data from the database, and then
displays, or prints, the results according to an associated form. If your installation uses QMF with IBM Z
Decision Support, QMF is started up when you work with queries and reports. Otherwise, IBM Z Decision
Support uses its own report generator.
Figure 7 on page 8 shows the Reporting dialog.

Chapter 1. Introduction to IBM Z Decision Support 7

Introduction to the Key Performance Metrics Components

Reporting Dialog Defaults

Type information. Then press Enter to save defaults.

Entry to dialog . . . 2_ 1. Display of previous selection

2. Display of all reports
3. Display of a selected group of reports

Group ID . . . . . . . __________________ + (required if group selected)

Group owner . . . . . ________ (blank for public group)

Display of this window 1_ 1. No display

2. Display at exit from dialog
3. Display at entry to dialog

Confirmation of exit 1_ 1. Yes

2. No

F1=Help F2=Split F4=Prompt F9=Swap F12=Cancel

Figure 7. Introducing the Reporting dialog

When you produce a report, you can specify values for the query that is used to select specific rows of
data. You can display, print, or save, the retrieved data in either a tabular or a graphic report format.
Note: To generate and display graphic reports, IBM Z Decision Support uses Graphical Data Display
Manager (GDDM). If you are using IBM Z Decision Support without QMF, GDDM is not required. If GDDM is
not used, all reports are displayed in tabular form.
A report can consist of these items, which are identified in the report definition:
• A query for selecting data (required).
• A form that formats the data and specifies report headings and totals.
• Graphical Data Display Manager (GDDM) format for a graphic report.
• Report attributes (for creating logical groups of reports).
• Report groups to which the report belongs.
• Variables in the report.
When installing a component, you install a comprehensive set of predefined report queries, forms, and,
optionally, GDDM formats for the component. The reporting dialog enables you to:
• Define new report definitions or modify existing ones.
• Define new queries and forms or modify existing ones, using QMF or the IBM Z Decision Support built-in
report generator.
• Display reports.
• Define reports for batch execution.
The Guide to Reporting describes the host reporting dialog. For a description of using the Common User
Access (CUA) interface presented in IBM Z Decision Support windows and helps, refer to the "Getting
Started" section of that book.

Introduction to the Key Performance Metrics components

IBM Z Decision Support has four components called the Key Performance Metrics (also referred to as
KPM) components. Specifically, there is one KPM component for each of z/OS, Db2, CICS, and IMS.
Within the IBM Z Decision Support component list, you will see the components named as follows:
• Key Performance Metrics - z/OS
• Key Performance Metrics - CICS
• Key Performance Metrics - Db2
• Key Performance Metrics - IMS

8 IBM Z Decision Support : Administration Guide and Reference

 Introduction to the Key Performance Metrics Components

These components are designed to only collect data that is considered to be key metrics for the
monitoring of these subsystems. They can be installed stand alone, or they can be installed along with the
corresponding existing base component. For example, the Db2 KPM component could be installed with or
without the existing Db2 component being installed. Note that if you had both the Db2 KPM component
and the existing base Db2 component installed, at collect time you only need to collect the SMF log the
once to populate the data tables for both components.
The number of tables and columns within each of these tables will be significantly reduced in each
of the KPM components. For this reason, the performance of collecting data into these components
should be significantly improved when compared against their associated existing base components.
For users who only reference metrics from the KPM tables, collecting only the KPM components should
result in considerable CPU and elapsed time savings at collect time when compared to collecting the
corresponding base components.
For details on each of the individual KPM components, refer to the appropriate guide in the table below.

Table 1. KPM components

KPM Component Guide
Key Performance Metrics - z/OS System Performance Feature Reference Volume I
Key Performance Metrics - CICS CICS Performance Feature Guide and Reference
Key Performance Metrics - Db2 System Performance Feature Reference Volume I
Key Performance Metrics - IMS IMS Performance Feature Guide and Reference

Each KPM component uses table space profiles which allow the table, table space, and index settings
within each KPM component to be easily modified in one place. Before installing the KPM components,
refer to the topic “Working with table space profiles” on page 128.

Introduction to the DataSplitter and the SMF Extractor

The DataSplitter is used with the SMF Extractor to distribute raw SMF records to whatever receivers users
wish to set up and the records are delivered over TCPIP.

The SMF Extractor

The SMF Extractor is the component of IBM Z Decision Support that captures SMF records for processing
by IBM Z Decision Support. This is a common component with IBM Z Batch Resiliency (IZBR) and,
following APAR PH29065, a single SMF Extractor instance can feed both IBM Z Decision Support and IBM
Z Batch Resiliency (IZBR) when they are running on the same system. The SMF Extractor can produce
additional log stream outputs, one or more of which can be used to feed an IBM Z Decision Support
DataSplitter.

Chapter 1. Introduction to IBM Z Decision Support 9

Introduction to the DataSplitter and the SMF Extractor

IZDS

IZDS

Figure 8. SMF Extractor

Receiving raw SMF records from the SMF Extractor

The SMF Extractor supports the specification of multiple output streams – up to six sets of data sets and
up to six log streams.
• When data sets are used, they are rotated at a user specifiable interval (defaulting to 10 minutes). This
means that the currently open data sets will be closed and a new set of data sets will be opened. The
data from the closed data sets may then be read. Data set output is used by IBM Z Batch Resiliency, see
the IBM Z Batch Resiliency (IZBR) documentation for more details.
• When log streams are used, new SMF records are appended to the end of the log stream and the
consumer is expected to wipe records from the front of the log stream after they have been read (or
leave them to be automatically purged after the log stream retention period is reached).
While you may write an application to read raw SMF records from one of the log streams or a sequence of
data sets, you can also use a DataSplitter to read, subdivide and, optionally, clean up the stream before
transmitting the records over TCPIP.
The following diagram show how the SMF Extractor and a DataSplitter might be deployed in this scenario.

10 IBM Z Decision Support : Administration Guide and Reference

 Introduction to Usage and Accounting Collector

IZDS Collator

IZDS Collator

Figure 9. Using the CDPz Data Streamer:

The role of the DataSplitter in these scenarios is to:

• Read the records from the log stream.
• Sort them into separate 'streams' using a Collate stage to sort them.
• Send each stream to one or more remote receivers.

Introduction to the Usage and Accounting Collector

The CIMS Lab Mainframe collector is incorporated into IBM Z Decision Support and called the Usage and
Accounting Collector. This extracts z/OS accounting data which is used to populate IBM Tivoli Usage and
Accounting Manager databases on distributed platforms. The Usage and Accounting Collector does not
require Db2 as prerequisite software on z/OS.
For a description of the Usage and Accounting Collector, see “System Overview” in the Usage and
Accounting Collector User Guide.
For information on how to install the Usage and Accounting Collector, see “Installing the Usage and
Accounting Collector” on page 46.
Note: Spectrum Writer is not included with UAC. Former CIMS Lab customers have a perpetual license for
Spectrum Writer and should retain the CIMS Lab data sets so that they can make use of it. For support
of Spectrum Writer, contact Pacific Systems. Customers that require access to CIMS Mainframe 12.2.1
should contact IBM support.

Chapter 1. Introduction to IBM Z Decision Support 11

Introduction to Usage and Accounting Collector

12 IBM Z Decision Support : Administration Guide and Reference

Chapter 2. Installing IBM Z Decision Support
How to install IBM Z Decision Support.
Follow these instructions to install IBM Z Decision Support for the first time.
The initial installation process starts after a system programmer has performed the SMP/E installation.
The SMP/E installation of the IBM Z Decision Support base and its features is described in the IBM Z
Decision Support Program Directory.
You can also use this information to install IBM Z Decision Support on other systems, or to install features
that you did not install previously with the IBM Z Decision Support base.
This section describes the following installation tasks:
• “Installation prerequisites” on page 13
• “Step 1: Reviewing the results of the SMP/E installation” on page 15
• “Step 3.1: Setting up security” on page 17
• “Step 3.2: Initializing the Db2 database” on page 20
• “Step 3.3: Preparing the dialog and updating the dialog profile” on page 21
• “Step 3.4: Setting personal dialog parameters” on page 23
• “Step 3.5: Setting up QMF” on page 24
• “Step 3.12: Determining partitioning mode and keys” on page 31
• “Step 3.8: Creating system tables” on page 26
• “Step 3.9: Customizing JCL” on page 27
• “Step 3.10: Testing the installation of the IBM Z Decision Support base” on page 28
• “Step 3.11: Reviewing Db2 parameters” on page 30
• “Step 3.13: Installing components” on page 31
• “Installing multiple IBM Z Decision Support systems” on page 53
• “Installing IBM Z Decision Support features separately” on page 54

Installation prerequisites
This section lists the hardware and software prerequisites.

Hardware prerequisites
IBM Z Decision Support can run in any hardware environment that supports the required software.

Software prerequisites
This section lists the software requirements to install and use IBM Z Decision Support basic functions
and optional component features. Refer to the IBM Z Decision Support Program Directory for further
information about mandatory and conditional requirements.

Architecture considerations
IBM Z Decision Support can run on a stand-alone system, or can be configured for multiple systems
with hub and spoke architecture. For more information, refer to “Step 3.6: Defining the log stream to
communicate between the DataMover and the Continuous Collector (Optional)” on page 25.
Most of the prerequisites apply to the hub or stand-alone system, and do not need to be installed on every
system that you want IBM Z Decision Support to collect data from.

© Copyright IBM Corp. 1993, 2017 13

 It is highly recommended that IBM Z Decision Support be installed in to its own Db2 subsystem. This will
avoid contention with other applications.
Data gathering
IBM Z Decision Support is installed on one or more hub systems, where data from multiple spoke
systems is analyzed and archived. A system can be both a spoke and a hub.
A hub system requires:
• z/OS V2.2.0 or later
• Db2 V11 or later
While you can manually transfer data from the spoke systems to the hub, there is an automated data
gathering agent that can be installed on the spoke systems running z/OS to gather SMF data.
A spoke system running the automated data gathering agent requires:
• z/OS V2.2.0 or later
• IBM 64-bit Java 8
To enable automated data gathering by spokes, the hub needs:
• IBM 64-bit Java 8
Data can be gathered from the following applications on spoke systems:
z/OS systems
• z/OS V2.2.0 or later
– DFSMS/OAM
– DFSMS/RMM
– DFSMS/MVS
– JES2 and JES3
– EREP
– Communications Server
– IBM Z Workload Scheduler
– IBM Tivoli Information Management for z/OS
– MVS
• Db2 for z/OS V11.0.0 or later
• CICS Transaction Server V5.2 or later
• IMS V13 or later
• IBM Security zSecure Manager for RACF z/VM V1.11.1 or later
• IBM Tivoli NetView for z/OS – V5.4.0 or later
• IBM Tivoli Storage Manager for z/OS (ADSM) V7.1.6 or later
• WebSphere MQ for z/OS V7.1.0 or later
• IBM HTTP Server V6.1.0 or later
z/Linux systems
• Red Hat Enterprise Linux V7.3
• SUSE Linux Enterprise Server V11+
Power Systems running IBM i
• Power Systems running IBM i V7.2 or V7.3
AIX systems
• AIX V7.1+

14 IBM Z Decision Support : Administration Guide and Reference

 HP-UX systems
• HP-UX 11i V3+
Solaris systems
• Solaris V11.1
Windows systems
• Windows Server 2008, 2012 or 2016
Reporting
Reports can be drawn directly from Db2 on the hub system or indirectly from Splunk or ELK
installations that are fed by one or more hub systems. Basic reporting on a hub producing tabular
textual reports requires no additional software. Other reporting options are:
3270 graphical reporting
• GDDM-PGF
Cognos
• Cognos Analytics V11.1.7 (license bundled with IBM Z Decision Support )
QMF reporting
• IBM QMF for IBM Z - to enable QMF reporting
• GDDM-REXX - this is required only if you are not using QMF for IBM Z
Remote QMF reporting
• QMF For Workstations V11
IBM Db2 Analytics Accelerator
To use IBM Db2 Analytics Accelerator to accelerate your queries:
• Db2 High Performance Unload for z/OS V5.1 – to enable high performance unloading
• High performance unload is not necessary to accelerate queries with the Db2 Analytics
Accelerator. The Accelerator is used when Db2 processes Accelerator Only Tables, which require
Acceleration, or when processing Shadow tables, which gain a performance benefit from the
Accelerator.
To feed data off-platform for web reporting by Splunk or ELK
• IBM 64-bit Java 8
• Optionally, the IBM Z Common Data Provider V1.2 or higher to distribute the feed. The
alternative is a direct feed from IBM Z Decision Support to Splunk or ELK

Step 1: Reviewing the results of the SMP/E installation

After SMP/E installation the following will be on your system. The locations and names listed here are
based on the defaults, and may have been changed during the SMP/E installation at your site.

IBM Z Decision Support data sets

The data set names and descriptions of the product data sets are:
DRLvrm.SDRLCNTL
Sample jobs and Db2 DBRM module
DRLvrm.SDRLDEFS
Definitions of records, tables, and other objects
DRLvrm.SDRLEXEC
REXX execs

Chapter 2. Installing IBM Z Decision Support 15

 DRLvrm.SDRLLOAD
Load modules
DRLvrm.SDRLSKEL
ISPF skeletons
DRLvrm.SDRLA400
OS/400
DRLvrm.SDRLWS
Content for distributed platforms as well as reports.
DRLvrm.SDRLEXTR
SMF extractor load modules
usr/lpp/IBM/IDSz/v1r9m0/IBM
The directory that contains the DataMover and other apps. This is the target of the SDRLIDM DDDEF.

Local data sets

The data set names and descriptions of the local operational data sets are:
&HLQ.LOCAL.ADMCFORM
Local GDDM-Presentation Graphics Facility (GDDM-PGF) interactive chart utility (GDDM/ICU) formats
&HLQ.LOCAL.CHARTS
Saved graphic reports (GDDM ADMGDF format)
&HLQ.LOCAL.CNTL
Local IBM Z Decision Support jobs
&HLQ.LOCAL.DEFS
Local IBM Z Decision Support definitions
&HLQ.LOCAL.EXEC
Local IBM Z Decision Support execs
&HLQ.LOCAL.MESSAGES
Messages sent through the dialog
&HLQ.LOCAL.REPORTS
Saved tabular reports
&HLQ.LOCAL.USER.DEFS
Local IBM Z Decision Support user/alter definitions

Language-dependent IBM Z Decision Support data sets

The last three letters in these data set names indicate the language version. xxx is ENU for English. For
example, SDRLRENU contains the English report definition files. The corresponding Japanese version is
SDRLRJPN.
DRLvrm.SDRLFxxx
GDDM/ICU formats
DRLvrm.SDRLMxxx
ISPF messages
DRLvrm.SDRLPxxx
ISPF windows
DRLvrm.SDRLRxxx
Definitions of reports
DRLvrm.SDRLTxxx
ISPF tables

16 IBM Z Decision Support : Administration Guide and Reference

Step 2: Automatic processing of SMF data using Hub and Spoke
topology
You can setup IBM Z Decision Support in a Hub and Spoke configuration for processing SMF records,
where data is brought from the source systems (the Spoke systems) to a central system (the Hub system)
where the data is collected, stored and analyzed. The data is transported by a data gathering agent (the
IBM Z Decision Support Agent) and is processed as it arrives. You can configure IBM Z Decision Support to
automatically gather SMF data on the Spoke systems and transport it to the Hub to be processed.
Note: You can continue to collect SMF data and transmit it manually rather than using automatic data
gathering. Also you can collect some data using the IBM Z Decision Support Agent and other data using
the manual approach.

Step 3: Setting up the Hub or stand-alone system

The initial steps for configuring a single IBM Z Decision Support system, or the Hub system (if you are
using IBM Z Decision Support in a Hub and Spoke configuration with SMF data) are the same.
To setup the Hub system or stand-alone system you must setup security, initialize the Db2 database,
prepare the dialog, optionally setup QMF, define the log stream, define coupling facility structures, and
create system tables.

Step 3.1: Setting up security

About this task

This topic describes how you can protect IBM Z Decision Support data sets and the database.
Use RACF® or a similar product to protect the IBM Z Decision Support data sets. Administrators and users
must have read access to the DRL190 data sets and update access to the local data sets.
The data in the database is protected by Db2. Administrators and users must be granted Db2 privileges to
be able to access the data, as follows:
• Administrators need SYSADM (system Db2 administrator authority for the IBM Z Decision Support
database. They also need the ability to use the prefixes of IBM Z Decision Support tables (DRLSYS and
DRL) as authorization IDs in Db2.
• Users need read access to the tables they use to produce reports, and update access to some of the
IBM Z Decision Support system tables (to be able to create their own reports).
• The user IDs that you use for IBM Z Decision Support production jobs, such as collect, need DBADM
authority.
This step describes two ways you can define authorities for IBM Z Decision Support administrators and
users:
• Using secondary authorization IDs.
• Without secondary authorization IDs.
Find out through the Db2 system administrator whether secondary authorization IDs are used on your
Db2 system.
Note: If you are defining authorities without using secondary user IDs, the installation process is
slightly different. See “Step 3.1.2: Security without secondary authorization IDs” on page 19 for more
information.

Chapter 2. Installing IBM Z Decision Support 17

 Step 3.1.1: Security using secondary authorization IDs

About this task

The most efficient way to give users privileges is to use secondary authorization IDs in Db2. With this
method, privileges are granted to group IDs rather than user IDs, and all users who can use these
secondary authorization IDs get the privileges.
The secondary authorization IDs a user has access to can be controlled in different ways. If you
have RACF installed, users can usually use the RACF groups that they are connected to as secondary
authorization IDs. If RACF is not installed, secondary authorization IDs can be assigned by the Db2
authorization exit.
This topic describes how to define the secondary authorization IDs using RACF. If you assign secondary
authorization IDs in another way, consult your Db2 system administrator.

Procedure
1. Create three RACF groups. The default RACF group IDs are DRL, DRLSYS, and DRLUSER

ADDGROUP DRL DATA ('IBM Z Decision Support TABLES')

ADDGROUP DRLSYS DATA (’IBM Z Decision Support SYSTEM TABLES')
ADDGROUP DRLUSER DATA ('IBM Z Decision Support USERS')

The IDs DRL and DRLSYS are also prefixes for the IBM Z Decision Support Db2 tables. If you plan to
change the prefixes for IBM Z Decision Support system tables and views (DRLSYS) or for other IBM Z
Decision Support tables and views (DRL) in “Step 3.2: Initializing the Db2 database” on page 20, use
your values as RACF group IDs.
If all users on your system need access to the IBM Z Decision Support data, you do not need the
DRLUSER group. If different users need access to different sets of tables, you can define several RACF
group IDs, such as DRLMVS and DRLCICS, instead of the DRLUSER group.
You can use either RACF commands or RACF dialogs to specify security controls. These commands
are samples. You may have to specify additional operands to comply with the standards of your
organization.
2. Connect IBM Z Decision Support administrators to all three groups.
Use RACF commands or RACF dialogs to connect user IDs to a group. This command is a sample.

CONNECT (user_ID1 user_ID2 ...) GROUP(DRLUSER)

3. Connect IBM Z Decision Support (not VIEWER) users to the DRLUSER group only.
Use RACF commands or RACF dialogs to connect user IDs to a group. This command is a sample.

CONNECT (user_ID1 user_ID2 ...) GROUP(DRLUSER)

4. If you use different RACF group IDs, be sure to use them throughout all the steps listed .
5. If you use other group IDs than DRLUSER, you must modify the following fields in the Dialog
Parameters window (see Figure 11 on page 24):
Users to grant access to
Users to grant access to must be specified when you create the system tables and when you install
components. When you create the system tables it should contain all group IDs that should have
access to IBM Z Decision Support. To grant access to all users, specify PUBLIC.
When you install components, Users to grant access to should contain the group IDs that should
have access to the component.
SQL ID to use (in QMF)
If QMF is used with IBM Z Decision Support in your installation, the SQL ID to use in QMF must be
specified by each user. It should be one of the groups the user is connected to or the user's own
user ID.

18 IBM Z Decision Support : Administration Guide and Reference

6. If you use different RACF group IDs, you can make your RACF group IDs the default for all IBM Z
Decision Support users. Edit the IBM Z Decision Support initialization exec DRLFPROF, described in
“Step 3.3: Preparing the dialog and updating the dialog profile” on page 21. Variables def_syspref,
def_othtbpfx, def_iduser1, and def_idsqluser may need to be changed, depending on the changes you
made to the IDs.

Step 3.1.2: Security without secondary authorization IDs

About this task

If you are not using secondary authorization IDs in Db2, the installation process is slightly different. See
“Example: Installation steps when secondary user IDs are not used” on page 19 for more information.
If you are not using secondary authorization IDs in Db2, all privileges must be granted to individual users.

Procedure
1. Grant authority to the administrators:
a) Create all tables and views with the administrator user ID as prefix. That is, replace DRLSYS and
DRL with a user ID. Only one administrator is possible.
b) Grant SYSADM authority to all administrators.
2. Give authority to the users in one of two ways. This is done in “Step 3.4: Setting personal dialog
parameters” on page 23.
• Specify a list of up to 8 user IDs in the field Users to grant access to in the Dialog Parameters
window (Figure 11 on page 24).
• Specify PUBLIC in the field Users to grant access to. This gives all users access to IBM Z Decision
Support data. This is easier to maintain than a list of user IDs.
For both cases, each user must specify his own user ID in the SQL ID to use (in QMF) field in the
Dialog Parameters window, if QMF is used with IBM Z Decision Support in your installation.
You must specify user IDs in the field Users to grant access to before you create the system tables. It
is also used when you install components.

Example: Installation steps when secondary user IDs are not used
Follow this example if you have several administrators. In the example, we assume that there are three
administrators:
• ADMIN1 is the user who creates system tables.
• ADMIN2 and ADMIN3 are the other administrators.
When performing the installation, note these items:
• “Step 3.2: Initializing the Db2 database” on page 20 : Change DRL and DRLSYS in the DRLJDBIN job to
ADMIN1, ADMIN2, and ADMIN3.
• “Step 3.3: Preparing the dialog and updating the dialog profile” on page 21: No changes.
• “Step 3.4: Setting personal dialog parameters” on page 23: Use ADMIN1 as prefix for system tables,
ADMIN2 and ADMIN3 as prefix for other tables. For Users to grant access to, specify ADMIN1, ADMIN2,
ADMIN3, and all user IDs for the end users. For SQL ID to use (in QMF), specify ADMIN1 (if QMF is used
with IBM Z Decision Support in your installation).
• “Step 3.5: Setting up QMF” on page 24: No changes.
• “Step 3.8: Creating system tables” on page 26: The system tables should be created with the prefix
ADMIN1. Otherwise, there are no changes compared with the information in this step.
• “Step 3.9: Customizing JCL” on page 27: No changes.
• “Step 3.10: Testing the installation of the IBM Z Decision Support base” on page 28 and “Step 3.13:
Installing components” on page 31: If one of the secondary administrators, for example ADMIN2,

Chapter 2. Installing IBM Z Decision Support 19

 wants to install the Sample component or any other component, that administrator has to change the
dialog parameters before the installation to use these settings:
Prefix for system tables
ADMIN1
Prefix for other tables
ADMIN2
SQL ID to use (in QMF)
ADMIN2
When the component is installed by ADMIN2, the installed Db2 objects are created with the prefix
ADMIN2.
All Db2 objects can be read by all administrators, but an object can be created only with the current
administrator's primary user ID.
To make your changes the default for all IBM Z Decision Support users, you must change the initialization
exec DRLFPROF as described in “Step 3.3: Preparing the dialog and updating the dialog profile” on page
21.

Step 3.2: Initializing the Db2 database

Follow these instructions to run the DRLJDBIN job to initialize the Db2 database when you are installing
IBM Z Decision Support for the first time.

About this task

You must use IBM Z Decision Support to perform several Db2-related installation tasks, which are
described below.
Note: IBM Z Decision Support is an update/insert intensive Db2 application. This means that during a
collect, IBM Z Decision Support adds and updates many rows in the Db2 tables. Normal Db2 processing
logs these changes. Your Db2 administrator should verify that the capacity of the Db2 logs is sufficient to
cope with the increase in logging activity.
If your operational Db2 system is constrained, consider implementing another (analytical) Db2 system for
the IBM Z Decision Support environment.

Procedure
1. Copy member DRLJDBIN in the DRLvrm.SDRLCNTL library to the &HLQ.LOCAL.CNTL library.
DRLJDBIN needs to be customized to refer to one of the following samples: DRLJDCVB, DRLJDCVC,
or DRLJDCVD depending on your version of Db2. The required sample must also be copied to the
&HLQ.LOCAL.CNTL library and customized for your environment if you are not using the default
database name and table prefixes. Refer to the instructions in the comments in DRLJDBIN job and
the selected DRLJDCVx member for more information about using these samples.
2. Modify the job card statement to run your job.
3. Customize the job for your site.
Follow the instructions in the job prolog to customize it for your site.
Note:
a. A person with Db2 SYSADM authority (or someone with the authority to create plans, storage
groups, and databases, and who has access to the Db2 catalog) must submit the job.
b. Do not delete steps from DRLJDBIN. Even if you have DBADM authorization, you must grant DRL
and DRLSYS authority for the IBM Z Decision Support database.
4. Submit the job to:
• Bind the Db2 plan used by IBM Z Decision Support.

20 IBM Z Decision Support : Administration Guide and Reference

 The plan does not give privileges (it contains only dynamic SQL statements) thereby making it safe to
grant access to all users (PUBLIC).
If you change the name of the plan from the default (DRLPLAN) then you must update the
def_db2plan variable in DRLFPROF to specify the new plan name. You also need to modify any
sample jobs that execute DRLPLC, DRL1PRE or DRLPLOGM to specify the PLAN parameter with the
new plan name. Changing the plan name allows you to run versions of the IBM Z Decision Support
environment with incompatible DBRMs in the same Db2 subsystem.
• Create the Db2 storage group and database used by IBM Z Decision Support.
• Grant Db2 DBADM authority as database administrators of DRLDB to DRL and DRLSYS.
• Create views on the Db2 catalog for IBM Z Decision Support dialog functions for users who do not
have access to the Db2 catalog.

Step 3.3: Preparing the dialog and updating the dialog profile

About this task

The load library and the exec library must be allocated at the startup of your TSO logon procedure. IBM
Z Decision Support dynamically allocates other libraries and data sets as it starts, and allocates others
as certain functions are performed. This step describes how to set up procedures for startup and for
allocating the libraries and data sets that IBM Z Decision Support needs.
Ensure that the load library, exec library, Db2 load library, QMF load library (optional), GDDM libraries, and
load libraries, are accessible to your TSO session

Procedure
1. Make the load library (DRLvrm.SDRLLOAD), Db2 load library, QMF load library, and the GDDM load
library accessible by performing one of these tasks:
a) Allocate the SDRLLOAD library, Db2 load library (SDSNLOAD), QMF load library (SDSQLOAD), and
the GDDM load library (SADMMOD) to STEPLIB in the generic logon procedure.

//STEPLIB DD DISP=SHR,DSN=DRLvrm.SDRLLOAD
// DD DISP=SHR,DSN=QMF.SDSQLOAD
// DD DISP=SHR,DSN=GDDM.SADMMOD
// DD DISP=SHR,DSN=DSN.SDSNLOAD

b) Add SDRLLOAD, SDSQLOAD, SADMMOD, and SDSNLOAD to the link list.

c) Copy SDRLLOAD, SDSQLOAD, SADMMOD, and SDSNLOAD members to a library already in the
link list. Make sure that the Db2 modules DSNALI, DSNHLI2, and DSNTIAR are linked in 31-bit
addressing mode
2. Make the local exec library and the IBM Z Decision Support exec library (DRLvrm.SDRLEXEC)
accessible by performing one of these tasks:
a) Allocate the libraries to SYSPROC in the logon procedure. For example:

//SYSPROC DD DISP=SHR,DSN=&HLQ.LOCAL.EXEC
// DD DISP=SHR,DSN=DRLvrm.SDRLEXEC

b) Allocate the libraries to SYSEXEC in the logon procedure. For example:

//SYSEXEC DD DISP=SHR,DSN=&HLQ.LOCAL.EXEC
// DD DISP=SHR,DSN=DRLvrm.SDRLEXEC

c) Use the ALTLIB function to allocate the libraries.

Chapter 2. Installing IBM Z Decision Support 21

 If IBM Z Decision Support is invoked by using the ALTLIB function on the application level, make
sure that only the IBM Z Decision Support exec library is included. Allocate other exec libraries to
user level by using the ALTLIB ACT USER(EXEC) command.
3. Make the ADMPC data set accessible by allocating it in the logon procedure. For example:

//ADMPC DD DISP=SHR,DSN=GDDM.SADMPCF

IBM Z Decision Support dynamically allocates other libraries and data sets, such as the GDDM symbols
data set GDDM.SADMSYM, when a user starts a dialog. “Allocation overview” on page 72 describes
the libraries that IBM Z Decision Support allocates and when it allocates them.
4. If you have used any values other than default values for DRLJDBIN or for IBM Z Decision Support data
set names, you must modify the userid .DRLFPROF file (allocated copying the DRLFPROF member of
DRLvrm.SDRLCNTL).
DRLEINI1 sets dialog defaults for all users. IBM Z Decision Support stores defaults for each
user in member DRLPROF in the library allocated to the ISPPROF ddname, which is usually
tsoprefix.ISPF.PROFILE. Edit DRLFPROF to include default values so users do not need to change
dialog parameter fields.
5. Allocate a sequential data set with name user.DRLFPROF, LRECL=80 BLKSIZE=32720 RECFM=FB and
copy the DRLFPROF member of the SDRLCNTL library.
6. Locate and change any variable values that you have changed during installation.
Note:
• Change values for data set names that identify Db2 and, optionally, QMF and GDDM libraries.
• If you do not use QMF with IBM Z Decision Support, change the value for qmfuse to NO.
• If you do not use GDDM with IBM Z Decision Support, change the value for gddmuse to NO. (If QMF
is used, GDDM must be used.)
“Modifying the DRLFPROF data set” on page 61 shows the DRLFPROF file containing the parameters
to be modified.
“Overview of the Dialog Parameters window” on page 61 shows the administration dialog window
and the default initialization values that DRLFPROF sets.
“Dialog parameters - variables and fields” on page 63 describes parameters and shows the
interrelationship of DRLEINI1 and the Dialog Parameters.
7. You can add IBM Z Decision Support to an ISPF menu by using this ISPF statement:

CMD(%DRLEINIT) [DEBUG] [RESET] [DBRES] [REPORTS | R] [ADMINISTRATION | A]

To access a dialog from the command line of an ISPF window, any authorized user can issue the
command TSO %DRLEINIT from the command line of an ISPF window.
The optional DEBUG parameter sets on a REXX trace for the initialization execs. This helps you solve
problems with data set and library allocation.
The optional RESET parameter sets the ISPF profile variables to their default value. It has the same
effect as deleting the DRLPROF member from the local (ISPPROF) profile library.
The optional DBRES parameter sets the ISPF profile variables for IBM Z Decision Support to their
default value (like Db2 Subsystem, Db2 Database, Db2 Storage Group). Only these values are deleted
from the DRLPROF member of the local (ISPPROF) profile library. All the other values set and already
stored in the profile are preserved.
The optional REPORTS parameter takes you directly to the reporting dialog. You can abbreviate this to
R. This is the default for non-administrator users.
The optional ADMINISTRATION parameter takes you directly to the administration dialog. You can
abbreviate this to A. This option is only available for administrators, and is the default for these users.

22 IBM Z Decision Support : Administration Guide and Reference

Step 3.4: Setting personal dialog parameters

About this task

If you have edited the dialog parameters profile file DRLFPROF from the DRLvrm.SDRLCNTL library, and
copied it into the sequential data set userid.DRLFPROF in “Step 3.3: Preparing the dialog and updating the
dialog profile” on page 21 to match your installation values, you do not need to follow the instructions in
this step to change the parameters unless you want to use the reporting dialog in administrator mode.
Authorized administrators can use the reporting dialog in administrator mode to view or modify all
reports. Otherwise, a reporting dialog user uses the dialog in end-user mode, the default. In this mode, a
user can view only public and privately-owned reports. In end-user mode, a user can modify only reports
he or she created.
IBM Z Decision Support stores parameters for each user in member DRLPROF in the library allocated to
the ISPPROF ddname, which is usually tsoprefix.ISPF.PROFILE.
This topic describes the procedure for the IBM Z Decision Support dialogs if you did not edit the
DRLFPROF file. Perform this step if necessary.

Procedure
1. From the command line of an ISPF/PDF window, type TSO %DRLEINIT to display the IBM Z Decision
Support Administration Dialog.
Reporting dialog users can access the Dialog Parameters window from the Options pull-down.

Options Other Utilities Help

------------------------------------------------------------------------------
IBM Z Decision Support Administration
Option ===>

1 System Perform IZDS system tasks System ID . . : SYS1

2 Components Install IZDS components Db2 Subsystem : SUB1
3 Logs Show installed IZDS log objects IZDS plan name : PLNPLAN
4 Tables Show installed IZDS data tables System tables : SYTSYSSY
5 Reports Run IZDS reports Data tables . : DATBL

Figure 10. IBM Z Decision Support Administration Dialog

2. From the Administration Dialog, select 1 System, to display the System window.
Note: If your installation does not use QMF, Import QMF initialization query is not selectable, and
indicated by an asterisk (*).
3. From the System window, select 1 Dialog parameters.

System

Select one of the following. Then press Enter.

1. Dialog parameters
2. System tables
3. Import QMF initialization query

F1=Help F2=Split F9=Swap F12=Cancel

Note: If your installation does not use QMF with IBM Z Decision Support, the contents of this window
is slightly different from what you see here. Both versions of the Dialog Parameters window are shown
in “Overview of the Dialog Parameters window” on page 61.

Chapter 2. Installing IBM Z Decision Support 23

 Dialog Parameters

Type information. Then press Enter to save and return.

More: +
DB2 subsystem name . . . . . DEC1
Database name . . . . . . . . DRLDBYY_
Storage group default . . . . SYSDEFLT
Prefix for system tables . . DRLSYSYY
Prefix for all other tables DRLYY___
Show panel IDs (yes/no) . . . YES

Buffer pool for data . . . . BP0___

Buffer pool for indexes . . . BP0___

Users to grant access to . . DRLUSRYY ________ ________ ________

________ ________ ________ ________

Batch print SYSOUT class . . A

Printer line count per page 60_
SQLMAX value . . . . . . . . 5000____
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 11. Dialog Parameters window

Note: When you see a plus sign indicator (More: +) in the upper-right corner of an IBM Z Decision
Support window, press F8 to scroll down.
If it shows a minus sign indicator (More: -), press F7 to scroll up. For more information about using
IBM Z Decision Support dialog windows, refer to the description in the Guide to Reporting.
You must scroll through the window to display all its fields. “Overview of the Dialog Parameters
window” on page 61 shows the entire Dialog Parameters window, both the version shown if QMF is
used with IBM Z Decision Support and the version shown if QMF is not used with it. “Dialog parameters
- variables and fields” on page 63 has a description of the fields in the window.
4. Make modifications and press Enter.
Changes for administration dialog users and for end users are the same. You must identify the correct
names of any data sets (including prefixes and suffixes) that you changed from default values during
installation.
IBM Z Decision Support saves the changes and returns to the System window. Although some changes
become effective immediately, all changes become effective in your next session when IBM Z Decision
Support can allocate any new data sets you may have selected.

Step 3.5: Setting up QMF

About this task

Note: IBM Z Decision Support can use QMF, for example, to display and work with reports. If your
installation does not use QMF, the information in this topic does not apply, and option 3, Import QMF
initialization query, is not selectable in the System window.
When IBM Z Decision Support starts QMF, it runs a query, (DRLQINIT), to set the current SQL ID (by
default, DRLUSER) that gives users required authority in QMF and lets them access objects in the QMF
lists.
To import the QMF query from member DRLQINIT (in the DRLvrm.SDRLDEFS library) and save it in QMF as
DRLSYS.DRLQINIT, from the System window, select 3, Import QMF initialization query, and press Enter.

24 IBM Z Decision Support : Administration Guide and Reference

 System

Select one of the following. Then press Enter.

1. Dialog parameters
2. System tables
3. Import QMF initialization query

F1=Help F2=Split F9=Swap F12=Cancel

IBM Z Decision Support imports the query into QMF and then returns to the System window.

Step 3.6: Defining the log stream to communicate between the DataMover
and the Continuous Collector (Optional)

About this task

This is required only if using the continuous collector. When you define log streams to system logger, you
must put information into the LOGR and CFRM couple data sets. Do the following:
Ensure that you have a formatted LOGR couple data set available. If you use other system logger
applications, such as OPERLOG or Logrec, the LOGR couple data set will already be available. See Format
the LOGR couple data set and make it available to the sysplex in z/OS MVS Setting Up a Sysplex.
Define the log streams and coupling facility structures (for coupling facility log streams) in the LOGR
policy couple data set using the administrative data utility (IXCMIAPU). See Add information about log
streams and coupling facility structures to the LOGR policy and LOGR keywords and parameters for the
administrative data utility in z/OS MVS Setting Up a Sysplex.
Define the log stream on the coupling facility (CF) if one exists in the sysplex, however it is recommended
to only use DASD. For JCL to do this, refer to sample configuration members:
• “Defining a DASD-only log stream” on page 60
Define the coupling facility structures in the CFRM policy couple data set using the IXCMIAPU utility. See
Define the coupling facility structures attributes in the CFRM function couple data set and CFRM parameters
for administrative data utility in z/OS MVS Setting Up a Sysplex.

Step 3.7: Defining the coupling facility structures attributes in the CFRM
function couple data set

About this task

This step applies to coupling facility log streams only. DASD-only log streams can omit this step.

Procedure
1. Determine the attributes needed to define coupling facility structures used by IBM Z Decision Support
2. Specify ALLOWAUTOALT(YES) on the list structure definition in the CFRM policy. The system may
automatically alter the size and ratio attributes of the structure as needed. Specify a minimum size for
the logger list structure with the MINSIZE parameter, to ensure that logger always has enough space
to do its work.
3. Allow the FULLTHRESHOLD parameter to take the default value.
4. Add information to the CFRM function couple data set about the desired attributes of the coupling
facility list structures for system logger applications. Note that each coupling facility structure that you
define in the LOGR policy must match those defined in the CFRM policy.
5. Activate the CFRM function couple data set using the SETXCF command

Chapter 2. Installing IBM Z Decision Support 25

Step 3.8: Creating system tables

About this task

Before you can use all dialog functions, you must create the Db2 tables. These Db2 tables are used by
IBM Z Decision Support to store its definitions and are known as system tables.
To create system tables follow these steps:

Procedure
1. From the System window, select 2, System tables.
The System Tables window is displayed. (Figure 12 on page 26).

Other Utilities Help

Administration

Select System

System Tables

Press Enter to list all system tables.

Prefix : DRLSYS
Status : Not created
Creator :
Database name : DRLDB

F1=Help F2=Split F5=Create F6=Update

F9=Swap F11=Delete F12=Cancel

Command ===>
F1=Help F2=Split F3=Exit F9=Swap F10=Actions F12=Cancel

Figure 12. System Tables (not created) window

2. Press F5 (Create).
IBM Z Decision Support creates system tables and fills in information about feature components by
searching DRLvrm.SDRLDEFS to see which features you have installed with SMP/E.
IBM Z Decision Support displays messages in a browse window, if a problem has occurred. In this
case, look for errors at the beginning of the listing. Resolve any errors such as this:

DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN

UNAVAILABLE RESOURCE. REASON 00D70025, TYPE OF RESOURCE
AND RESOURCE NAME DB2A.DSNDBC.DRLDB.A.I0001.A001

For information about specific Db2 messages, refer to the Messages and Problem Determination.
System messages should be error free, with a Db2 return code of zero. After creating the system
tables, IBM Z Decision Support returns to the System Tables window where you must press F12 to
return to the System window.
During the process of creating system tables, these administrative reports are also created:
• PRA001 - INDEXSPACE cross-reference.
• PRA002 - ACTUAL TABLESPACE allocation.
• PRA003 - TABLE PURGE condition.
• PRA004 - LIST COLUMNS for a requested table with comments.
• PRA005 - LIST ALL TABLES with comments.

26 IBM Z Decision Support : Administration Guide and Reference

 • PRA006 - LIST USER MODIFIED objects.

Creating and updating system tables with a batch job

About this task

You can also create, update, and delete IBM Z Decision Support system tables by running TSO/ISPF in
batch mode. Sample job DRLJCSTB shows an example of how to submit a request to program DRLEAPST
to create system tables. You can update or delete system tables by passing a different request to
DRLEAPST, as described in the comments in DRLJCSTB.
The TSO/ISPF batch job step must include:
• DRLFPROF DD referring to your DRLFPROF data set
• ISPPROF DD referring to a PDS with RECFM=F and LRECL=80. If you have made changes to the IBM Z
Decision Support dialog parameters and have not also made those changes in your DRLFPROF data set,
then the ISPPROF DD should refer to your ISPF profile data set and you should not specify the RESET
parameter to DRLEINIT.
• ISPPLIB, ISPMLIB, ISPSLIB, and ISPTLIB DDs referring to your IBM Z Decision Support and ISPF panel,
message, skeleton, and table data sets.
• ISPLOG DD referring to a data set with RECFM=VA and LRECL=125.
• SYSTSIN DD referring to instream data, or a data set, containing a command to invoke DRLEINIT, for
example:

IPSTART CMD(%DRLEINIT RESET)

• DRLBIN (batch input) DD referring to instream data or a data set containing a command to invoke
DRLEAPST with a request to perform the required function, for example:

DRLEAPST CREATE

DRLEAPST is the only program that can be invoked in this way.

Step 3.9: Customizing JCL

About this task

The DRLvrm.SDRLCNTL library contains several batch jobs that you can copy to &HLQ.LOCAL.CNTL and
customize. Customization includes inserting correct data set names and the correct Db2 subsystem ID.
These jobs, described in “Setting up operating routines” on page 86, are:
DRLJBATR
A sample job for printing and saving all (or a selected subset) of the batch reports. See “Using job
DRLJBATR to run reports in batch” on page 112 for more information.
DRLJCOLL and DRLJCOxx
A sample job for collecting log data. See “Collecting log data” on page 86 for more information.
DRLJCOPY
A sample job for backing up an IBM Z Decision Support table space with the Db2 COPY utility. See
“Backing up the IBM Z Decision Support database” on page 105 for more information.
DRLJDICT
A sample job for partitioning the CICS_DICTIONARY table, if the CICS Partitioning feature is going to
be used. See the CICS Partitioning feature chapter in CICS Performance Feature Guide and Reference
for more information.
DRLJEXCE
A sample job for producing IBM Tivoli Information Management for z/OS problem records. See
“Administering problem records” on page 117 for more information.

Chapter 2. Installing IBM Z Decision Support 27

 DRLJEXCP
A sample job for partitioning the EXCEPTION_T table, if the CICS Partitioning feature is going to be
used. See the CICS Partitioning feature chapter in CICS Performance Feature Guide and Reference for
more information.
DRLJPURG
A sample job for purging data from the database. See “Purge utility” on page 103 for more
information.
DRLJREOR
A sample job for reorganizing the IBM Z Decision Support database with the Db2 REORG utility. See
“Purge utility” on page 103 for more information.
DRLJRUNS
A sample job for updating statistics on IBM Z Decision Support table spaces with the Db2 RUNSTATS
utility. See “Monitoring the size of the IBM Z Decision Support database” on page 108 for more
information.
DRLJTBSR
A sample job for producing a detailed report about the space required for all, or a subset of, a selected
component’s tables. See “Understanding table spaces” on page 97 for more information.
If you already have jobs for maintaining Db2, for example, COPY, REORG or RUNSTATS, you can continue
to use them for this purpose, instead of using the IBM Z Decision Support jobs.

Step 3.10: Testing the installation of the IBM Z Decision Support base

About this task

Before you install IBM Z Decision Support feature components, ensure that the installation has been
successful:

Procedure
1. Install the Sample component using the information in “Installing a component” on page 120.
Although editing lookup tables is a usual part of online component installation, you need not edit the
sample lookup table to successfully complete this test. For a description of what is provided with the
sample component, see “Sample component” on page 230
2. After you install the Sample component, select 3, Logs, from the Administration window and press
Enter.
The Logs window is displayed (Figure 13 on page 28).

Log Utilities View Other Help

--------------------------------------------------------------------------
Logs ROW 1 TO 1 OF 1

Select a log. Then press Enter to display record definitions.

/ Logs Description
/ SAMPLE Sample log definition
******************************* BOTTOM OF DATA ********************************

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F5=Log def F6=Datasets F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=Collect F12=Cancel

Figure 13. Logs window

3. From the Logs window, select the SAMPLE log and press F11.
The Collect window is displayed.

28 IBM Z Decision Support : Administration Guide and Reference

 Collect

Type information. Then press Enter to edit the collect JCL.

Data set DRLxxx.SDRLDEFS(DRLSAMPL)_____________________________ (reqd)

Volume . . ______ (If not cataloged)
Unit . . . __________________ (Required for batch if Volume defined)

Reprocess . . . . . . 2 1. Yes
2. No
Commit after . . . . . 1 1. Buffer full
2. End of file
3. Specify number of records
Number of records . . ________
Buffer size . . . . . . 10
Extention . . . . . . . 2 1. K
2. M
Condition . . . . . . ________________________________________ >
F1=Help F2=Split F4=Online F5=Include F6=Exclude
F9=Swap F10=Show fld F11=Save def F12=Cancel

Figure 14. Collect window

4. Type DRLxxx.SDRLDEFS(DRLSAMPL) in the Data set field and press F4.
The online collect is started. When it finishes, it displays statistics about the data it collected.
5. Press F3 to return to the Logs window after you finish looking at the messages.
6. Press F3 to return to the Administration window
7. From the Administration window, select 5, Reports, and press Enter.
The Reporting Dialog Defaults window is displayed. (Refer to Guide to Reporting for more
information.)
8. Press Enter to display the Reports window.

Report Batch Group Search Options Other Help

Reports Row 1 to 9 of 9

Select a report. Then press Enter to display.

Group . . . . . : All reports

/ Report ID
ACTUAL TABLESPACE SPACE allocation PRA002
INDEXSPACE cross-reference PRA001
List all tables with comments PRA005
List columns for a requested table with comments PRA004
List User Modified Objects PRA006
/ Sample Report 1 SAMPLE01
Sample Report 2 SAMPLE02
Sample Report 3 SAMPLE03
TABLE PURGE Condition PRA003
******************************* Bottom of data ******************************

Command ===>
F1=Help F2=Split F3=Exit F4=Groups F5=Search F6=Listsrch
F7=Bkwd F8=Fwd F9=Swap F10=Actions F11=Showtype F12=Cancel

Figure 15. Reports window

9. From the Reports window, select Sample Report 1. Type a character other than a question mark in
the selection field and press Enter.
The Data Selection window is displayed.

Chapter 2. Installing IBM Z Decision Support 29

 Data Selection ROW 1 TO 1 OF 1

Type values. Then press Enter to generate the report.

Report ID : Sample Report 1

Variable Value Oper Req

SYSTEM_ID > + = No
**************************** BOTTOM OF DATA ****************************

Command ===>
F1=Help F2=Split F4=Prompt F5=Table F6=Chart F7=Bkwd
F8=Fwd F9=Swap F10=Showfld F11=Hdrval F12=Cancel

Figure 16. Data Selection window

10. Press Enter to generate the report.
The query associated with the report is run and the report is displayed through GDDM/ICU. If your
installation does not have GDDM, the report is displayed in tabular format. (Figure 107 on page 233
shows the report.)
11. When you finish viewing the report, press F9 to exit from GDDM/ICU, and press F3 (Exit) to return to
the Reports window.
12. From the Reports window, press F3 to return to the Administration window.

Step 3.11: Reviewing Db2 parameters

About this task

Before you install components, you can review Db2 table and index space parameters such as:
• Buffer pool.
• Compression.
• Erase on deletion.
• Free space.
• Lock size.
• Number of partitions, for a partitioned space.
• Number of subpages, for an index space.
• Primary and secondary space.
• Segment size.
• Type of space.
• VSAM data set password.
These parameters can affect the performance of your system.
Note: Before you assign a buffer pool to a component index or table space, activate the buffer pool and
add the USE privilege to the privilege set for the buffer pool.
To alter the Tablespace or Index definitions, the GENERATE_PROFILES table should be reviewed.

30 IBM Z Decision Support : Administration Guide and Reference

 What to do next
If you are unsure about the meaning of a field, press F1 to get help. For more information, refer to the
CREATE INDEX and CREATE TABLESPACE command descriptions in the Db2 for z/OS: SQL Reference
IBM Z Decision Support saves the changed definitions in your local definitions library. When you save a
changed definition, it tells you where it is saving it, and prompts you for a confirmation before overwriting
a member with the same name.

Step 3.12: Determining partitioning mode and keys

About this task

Some component definitions use the GENERATE statement to create the tables paces, partitioning,
and indexes. The table space, partitioning, and index attributes can easily be changed by updating the
appropriate profile in the GENERATE_PROFILES and GENERATE_KEYS system tables.

Procedure
1. Consult the guide for the component you are installing.
Many will have a job which must be run to set up Store groups, partition ranges or keys. Follow the
instructions for that component before proceeding. If the component does not support Generated
Table spaces and Indexes, you may skip this step.
2. When using GENERATE TABLESPACE the type of table space created is determined by the
TABLESPACE_TYPE field in the GENERATE_PROFILES system table.
3. If you decide to use Range Partitioned table spaces TABLESPACE_TYPE=RANGE, you will need to
adjust the range values in the GENERATE_KEYS system table.

What to do next
The supplied values for these tables are in the member DRLTKEYS in the SDRLDEFS data set, and the
tables are created and loaded during the creation of the IBM Z Decision Support System Tables. These
values may be reviewed prior to creating the IBM Z Decision Support system tables. If changes are
required, you may make a copy in your userid.LOCAL.DEFS data set and make the required changes prior
to System Table creation.
Alternatively, once loaded into the System Tables these values may be changed by various methods:
• Using the IBM Z Decision Support table edit facility.
• Using SQL UPDATE statements. For example, to change the TABLESPACE_TYPE from the supplied value
of RANGE to GROWTH for IMS the statement would look like the following example:

SQL UPDATE <sysprefix>.GENERATE_PROFILES

SET TABLESPACE_TYPE='GROWTH'
WHERE PROFILE='IMS';

Step 3.13: Installing components

About this task

You can now install IBM Z Decision Support features. To install components, use the information in
“Installing a component” on page 120, and in these books:
Feature name
Book name
AS⁄400 Performance
AS/400 System Performance Feature Guide and Reference
CICS Performance
CICS Performance Feature Guide and Reference

Chapter 2. Installing IBM Z Decision Support 31

 Distributed Systems Performance
Distributed Systems Performance Feature Guide and Reference
IMS Performance
IMS Performance Feature Guide and Reference
System Performance
System Performance Feature Reference Volume I and II
To install Resource Accounting for z/OS (part of the base function), see the Resource Accounting for z/OS
book.

Step 4: Installing automated data gathering on the hub system or

on a stand-alone system
To use automated data gathering you need to configure your hub system and spoke systems when using
the hub and spoke configuration, or on your stand-alone system when using a single system.
On the hub or stand-alone system you must do the following:
• Define the log stream to feed the Continuous Collector
• Create the Continuous Collector task
• Install and configure the SMF Extractor
• Set up a DataMover with an appropriate configuration (hub and spoke configuration only)

Step 4.1: Defining the log stream to feed the Continuous Collector

About this task

You must define the log stream to feed the Continuous Collector.
When you define log streams to system logger, you must put information into the LOGR and CFRM couple
data sets.

Procedure
1. Choose a high-level qualifier that is defined to SMS. Use the system name or SMF ID of the system as a
second qualifier, with a third qualifier of IZDSSEND (to identify the function of the logstream).
The offload data sets will use the log stream name to determine the offload data set names. For more
information on naming the log stream and DASD data sets, see: Naming conventions for the log stream
and DASD data sets.
The DataMover supports symbolic substitution, in the following parameters:
Log stream Input
stream_name and sourcename
Log stream Output
stream_name
File Output
file_name and directory
If you want to use symbolic substitution, ensure that you use consistent naming conventions on all
systems. This will allow you to use a single spoke configuration file for all spoke systems.
2. Ensure that you have a formatted LOGR couple data set as available.
If you use other system logger applications, such as OPERLOG or Logrec, the LOGR couple data set will
already be available. See Format the LOGR couple data set and make it available to the sysplex in z/OS
MVS Setting Up a Sysplex for more information.
3. Define the log streams and coupling facility structures (for coupling facility log streams) in the LOGR
policy couple data set using the administrative data utility (IXCMIAPU) utility. See Add information

32 IBM Z Decision Support : Administration Guide and Reference

 about log streams and coupling facility structures to the LOGR policy and LOGR keywords and
parameters for the administrative data utility in z/OS MVS Setting Up a Sysplex for more information.
We recommend that you use Coupling Facility log streams for performance reasons.
• For a DASD-only log stream, specify the LOGR policy MAXBUFSIZE parameter to define the
maximum log block size, in bytes, that the system can write to the DASD-only log stream. We suggest
a MAXBUFSIZE for a DASD-only log stream of 65532. The MAXBUFSIZE must be at least 33024.
• For a coupling facility log stream, specify the LOGR policy MAXBUFSIZE parameter to define the
maximum log block size, in bytes, that the system can write to the log stream assigned to the
structure you are defining. We suggest that you define a MAXBUFSIZE value between 33024 and
65532.

4. Define the coupling facility structures in the CFRM policy couple data set using the IXCMIAPU utility.
See Define the coupling facility structures attributes in the CFRM function couple data set and CFRM
parameters for administrative data utility in z/OS MVS Setting Up a Sysplex for more information.

Step 4.2: Customizing the Continuous Collector JCL

Procedure
1. Start with sample DRLJCCOL and modify the JCL by follow the instructions in the sample job. Ensure
that you specify the name of the log stream that you created in “Step 4.1: Defining the log stream to
feed the Continuous Collector” on page 32 for the SMF Extractor.
2. Install the Continuous Collector as a Started Task.

Step 4.3: Starting the Continuous Collector

Procedure
Start the Continuous Collector to validate your JCL by using an MVS start command.
It will come up and connect to Db2 and its log stream. It will not be processing any data yet as there’s
nothing in the log stream and you will receive a RC=8 because the log stream is empty. This is expected
behavior.

Step 4.4: Installing the SMF Extractor

About this task

You must install the SMF Extractor on your Hub or stand-alone system.

Procedure
1. Copy the hlq.vrm.SDRLEXTR data set to the Hub system.
2. Ensure that this library is APF authorized.

SMF Extractor Parameters

The SMF Extractor parameters options are distributed in member DRLJSMFO in the DRLvrm.SDRLCNTL
library.
During installation, this member must be copied to one or more members as SMFPssss, where ssss is
the SMF system ID of the system or systems that will run an SMF Extractor. All options can start in any
column; only one option is permitted per statement. The format of all options is:
• option=value
• Any characters beyond the value field are treated as comments and are ignored.

Chapter 2. Installing IBM Z Decision Support 33

 • There are no spaces between the option keyword, the equal sign and the value of the parameter.
The supported options are described below.

Parameter Default Range Description

OUTLGR=base_name None Specifies the log stream data set that is used when
(required) the extractor is configured to write to log stream
continuously.
This name must be a valid MVS data set name from 1
to 28 characters in length, and must not be a GDG base
name.

SMFREC=n,x,y...,z 14, 15, 0 to Specifies the SMF record types to be collected by the
30, 60, 255 SMF Extractor
61, 64,
65 Each value must be a valid numeric from 0 to 255,
separated by a comma with no intervening blanks
Alternatively, a range of values can be specified as
nnn:ppp, where nnn denotes the start of the range, and
ppp denotes the end of the range (for example, 60:64
specifies SMF record types 60 through 64, inclusive)
An SMF record type of * (asterisk) resets all prior
specified types (for example, SMFREC=24,28,*,32,80:84
would result in SMF record types 32, 80, 81, 82, 83, and
84 collection)
If you wish to specify more SMF types than can fit
on a single statement, specify multiple SMFREC option
statements (as many as necessary)

Step 4.5: Configuring the SMF Extractor

About this task

The SMF Extractor gathers SMF records from the IEFU8x SMF exits and writes them into the log stream
that you defined in “Step 4.1: Defining the log stream to feed the Continuous Collector” on page 32.
JCL procedure hlq.SDRLCNTL(DRLJSMFX) and the job hlq.SDRLCNTL(DRLJVFIX) are used to
execute the SMF Extractor. This procedure sets up a STEPLIB to hlq.SDRLEXTR. This library must be
APF authorized in order for the SMF Extractor to run successfully.
The configuration member, DRLJSMFO, in the hlq.SDRLCNTL data set describes the name of the
log stream that is used for the extracted records and which SMF records are to be extracted. The
configuration member is selected through specification of the SYSTEM parameter on the DRLJVFIX JCL.
The SMF Extractor can run as either a started task or a batch job. An operator interface is provided
to control execution. SMFEXT SMF configuration is performed with PARMLIB member SMFPRMxx. The
SMFPRMxx parameters SYS and SUBSYS define the SMF recording options.

Procedure
1. Determine what SMF records need to be extracted based on the needs of your downstream
applications.
2. If you have SUBSYS statements, in your existing SMFPRM member, in the SUBSYS statement, you must
ensure the following is updated in each SUBSYS statement.
• In the EXITS statements, you include IEFU83, IEFU84, IEFU85.

34 IBM Z Decision Support : Administration Guide and Reference

 • If you are using the TYPE statement, ensure that the SMF records that are in your SMFREC statement
in SMFPxxxx are included.
• If you are using the NOTYPE statement, ensure that the SMF records that are in your SMFREC
statement in SMFPxxxx are not included.
SUBSYS
Specifies subsystem specific recording options. The SUBSYS parameter options override the
equivalent options specified on the SYS parameter. Any SUBSYS parameter option not specified
will default to the SYS parameter option for the specified subsystem.
3. In your existing SMFPRMxx member, in the SYS statement, you must ensure the following.
• In the EXITS parameter, include IEFU83, IEFU84, IEFU85.
• If you are using the TYPE statement, ensure that the SMF records that are in your SMFREC statement
in SMFPxxxx are included.
• If you are using the NOTYPE statement, ensure that the SMF records that are in your SMFREC
statement in SMFPxxxx are not included.
SYS
Specifies system wide recording options for all subsystems (JES2, TSO, STC)
4. Copy the JCL sample from hlq.SDRLCNTL(DRLJVFIX) to a data set containing production JCL and
update it to match your environment.
Update the following parameters.
• System SMFID (the SMF system name for the system is the SID value that you will find in SMFPRMxx)
• The data set for the JCL library to the production procedure library where you will copy
hlq.SDRLCNTL(DRLJSMFX) and hlq.SDRLCNTL(DRLJSMFO)
5. Ensure that the executable library (STEPLIB) is APF authorized.
6. Copy the PROC sample from hlq.SDRLCNTL(DRLJSMFX) to a data set containing production
procedures and update the JCLLIB in the JCL to point to the procedure in the PROC library.
7. Copy the sample data set from hlq.SDRLCNTL(DRLJSMFO) to a data set containing production
procedures and update it to match your environment.
Update the values of the following parameters in hlq.SDRLCNTL(SMFPxxxx) to match your
environment. Where xxxx is the SMF system ID.
OUTLGR
Specifies the log stream data set that is used when the extractor is configured to write to log
stream continuously.
SMFREC
Specifies the SMF record types to be collected by the SMF Extractor

Results
This is the end of the configuration steps when configuring a stand-alone system.

Example configuration – one CNTL member per system

In the following example, the product has been installed into the DRL HLQ.
DRL.SDRLCNTL(DRLJVFIX)

Chapter 2. Installing IBM Z Decision Support 35

 //DRLJVFIX JOB (ACCT#),'EXTRACT'
/*JOBPARM BYTES=999999,CARDS=999999,LINES=9999,PAGES=99999
/*JOBPARM SYSAFF=SYSA
//******************************************************************
//* NAME: DRLJVFIX *
//* *
//* FUNCTION: *
//* SMF EXTRACTOR JCL *
//* *
//******************************************************************
//VFIPROC JCLLIB ORDER=(DRL.SDRLCNTL)
//SMFEXT EXEC DRLJSMFX,
// SYSTEM=SYSA /* SMF SYSTEM ID */

DRL.SDRLCNTL(DRLJSMFX)

//*==================================================================*/
//* */
//* THIS JCL IS THE SMF EXTRACTOR STARTUP PROC. */
//* */
//* THE SMFXPARM DATA SET SHOULD CONTAIN THE CONTROL FILES FOR */
//* EACH SYSTEM ON WHICH THE EXTRACTOR IS RUN. */
//* Change CNTL and the member to the name of your data set */
//* name and member name for the SMFXPARM for your system. */
//* */
//* Set the following parameters for maximum utilization: */
//* 1. Extractor parm MAXQD(150000) */
//* 2. MAX64(25) */
//* */
//* MAX64 parm is used to limit above the bar memory (in GB). */
//* The default value is 25, but can range between 3 and 99. */
//* */
//* To run more than one SMF Extractor in an LPAR, */
//* run the first with a parm without the MULT option. */
//* For a second (or more) SMF Extractor(s) add the MULT option */
//* as per this example: */
//* */
//* PARM=('TRACE(N),MSGLVL(9),SDUMP(Y),MAXSD(2),MAXQD(150000)', */
//* 'MAX64(25),MULT(n)') */
//* */
//* where n is a value 1 to 9 (up to 9 additional SMF Extractors) */
//* */
//*==================================================================*/
//SMFEXTP PROC SYSTEM=SYSA /* SMF SYSTEM ID */
//CKKXMAI EXEC PGM=CKKXMAI,REGION=0M,
// PARM=('TRACE(N),MSGLVL(9),SDUMP(Y),MAXSD(2),MAXQD(150000)',
// 'MAX64(25)')
//*
//STEPLIB DD DISP=SHR,DSN=DRL.SDRLEXTR
//SYSPRINT DD SYSOUT=*
//SMFXPARM DD DISP=SHR,DSN=CNTL(SMFP&SYSTEM.)
//SYSUDUMP DD SYSOUT=*
//SMFXPRNT DD SYSOUT=*
//*------------------------------

DRL.SDRLCNTL(DRLJSMFO)

***********************************************************************
* NAME: DRLJSMFO *
* *
* FUNCTION: *
* SMF EXTRACTOR CONTROL FILE. *
* *
*=====================================================================*
* COPY THIS MEMBER TO A DATA SET AS SMFPsysi WHERE sysi IS THE *
* SMF ID OF THE SYSTEM WHERE THE MEMBER WILL BE USED. *
* *
* THESE PARAMETERS MUST BE CUSTOMIZED TO MATCH YOUR INSTALLATION *
* REQUIREMENTS PRIOR TO THE FIRST STARTUP OF THE SMF EXTRACTOR. *
* *
* SET OUTLGR TO THE NAME OF THE OUTPUT LOG STREAM *
* SET SMFREC TO A COMMA SEPARATED LIST OF SMF RECORDS TO BE RECORDED *
*=====================================================================*
OUTLGR=logstreamname
SMFREC=14,15,30,42,60,61,64,65,70,71,72,73,74,85,90,94,99,100,101,113

36 IBM Z Decision Support : Administration Guide and Reference

Step 4.6: Unpacking the DataMover

About this task

This step is only required when you are working using the Hub and Spoke configuration.

Procedure
Extract the TAR file by using the following command.

tar -xvof /usr/lpp/IDSz/v1r9m0/IBM/DRLPJDM -C /destination

Where destination is the location where you want the contents of TAR file to reside and the path name
specified is the default path name.
This creates the following subdirectories:

IDSz
IDSz/DataMover
IDSz/DataMover/config
IDSz/DataMover/java
IDSz/DataMover/mappings

Step 4.7: Tailoring the DataMover on the Hub system

Procedure
Edit IDSz/DataMover/DataMover.sh and make the following changes.
a) Update the rundir and JAVA_HOME environment variables to point to the correct directories by
following the instructions in the file.
b) Ensure the -Xmx16G parameter is present in the Java statement to specify the maximum memory size
for Java.

Step 4.8: Configuring the DataMover

Procedure
Edit config/hub.properties and to ensure that the following properties accurately reflect your site.
• The TCPIP port you want the DataMover to accept connections on.
• The name of the log stream you set up to feed data into the Continuous Collector.
The remainder of the config file does not require modification.

Step 4.9: Testing the DataMover

Procedure
1. Under OMVS change into the DataMover directory.
2. Issue the command DataMover.sh hub. To start the DataMover, running under your account.
To stop the DataMover, type stop and click enter.

Step 4.10: Creating a vehicle for running the DataMover on the Hub system

About this task

You can run the DataMover as a started task or as a batch job .

Chapter 2. Installing IBM Z Decision Support 37

 Procedure
1. Determine whether you will run as a started task or a batch job.
2. Configure the provided samples to match your environment.
• To run as a started task
a. Modify the JCL sample DRLJDMP to point to the DataMover you just installed and the IBM Z
Decision Support Hub system.
b. Put DRLJDMP in your PROCLIB concatenation.
c. Start the DataMover to test it.
d. Stop the DataMover by using the following command.

/f stcname1,appl=stop

Where stcname is the PROC name you used for the DataMover started task.
• To run as a batch job
a. Modify the JCL sample DRLJDMJ to create a batch job to run DataMover. It is easier to operate
the DataMover if it has a jobname that is no more than 7 characters long. This is because the
OMVS task that is created to actually run the DataMover will have the same jobname with a 1
appended to it.
b. Start the DataMover to test it.
c. Stop the DataMover by using the following command.

/f jobname1,appl=stop

Where jobname is the name you used for the DataMover job.
For example, if the jobname is TUESDAY, then to stop it, the command is:

/f TUESDAY1,appl=stop

Step 5: Installing automated data gathering on each Spoke system

On each Spoke System you must set up an IBM Z Decision Support agent.
• Deploy the necessary libraries and configure them
• Set up a log stream for it to use
• Install and configure the SMF extractor
• Set up a DataMover with an appropriate configuration
When this is done, data will start flowing from the spoke system to the Continuous Collector and into Db2.
Note that the DataMover can wipe data from a log stream. It should not have access to any log streams
other than those created expressly for IBM Z Decision Support to use.

Step 5.1: Defining the log stream to communicate between the SMF
Extractor and the DataMover

About this task

You must define a log stream to communicate between the SMF Extractor and the DataMover. When you
define log streams to system logger, you must put information into the LOGR and CFRM couple data sets.

38 IBM Z Decision Support : Administration Guide and Reference

Procedure
1. Choose a high-level qualifier that is defined to SMS. Use the system name or SMF ID of the system as a
second qualifier, with a third qualifier of IZDSEXDM (to identify the function of the log stream).
The offload data sets will use the log stream name to determine the offload data set names. For more
information on naming the log stream and DASD data sets, see: Naming conventions for the log stream
and DASD data sets.
The DataMover supports symbolic substitution, in the following parameters:
Logstream Input
stream_name and sourcename
Logstream Output
stream_name
File Output
file_name and directory
If you want to use symbolic substitution, ensure that you use consistent naming conventions on all
systems. This will allow you to use a single Spoke configuration file for all Spoke systems.
2. Ensure that you have a formatted LOGR couple data set available.
If you use other system logger applications, such as OPERLOG or Logrec, the LOGR couple data set will
already be available. See Format the LOGR couple data set and make it available to the sysplex in z/OS
MVS Setting Up a Sysplex for more information.
3. Define the log streams and coupling facility structures (for coupling facility log streams) in the LOGR
policy couple data set using the administrative data utility (IXCMIAPU) utility. See Add information
about log streams and coupling facility structures to the LOGR policy and LOGR keywords and
parameters for the administrative data utility in z/OS MVS Setting Up a Sysplex for more information.
We recommend that you use Coupling Facility log streams for performance reasons.
• For a coupling facility log stream, specify the LOGR policy MAXBUFSIZE parameter to define the
maximum log block size, in bytes, that the system can write to the log stream assigned to the
structure you are defining. We suggest that you define a MAXBUFSIZE value between 33024 and
65532.
• For a DASD-only log stream, specify the LOGR policy MAXBUFSIZE parameter to define the
maximum log block size, in bytes, that the system can write to the DASD-only log stream. We suggest
a MAXBUFSIZE for a DASD-only log stream of 65532. The MAXBUFSIZE must be at least 33024.

4. Define the coupling facility structures in the CFRM policy couple data set using the IXCMIAPU utility.
See Define the coupling facility structures attributes in the CFRM function couple data set and CFRM
parameters for administrative data utility in z/OS MVS Setting Up a Sysplex for more information.

Example

//*********************************************************
//* SAMPLE JOB TO DELETE AND REDEFINE A LOGSTREAM *
//* CHECK WITH YOUR SYSTEM PROGRAMMER TO REVIEW *
//*********************************************************
//LGDELDEF EXEC PGM=IXCMIAPU
//SYSPRINT DD SYSOUT=*,DCB=RECFM=FBA
//SYSIN DD *
DATA TYPE(LOGR) REPORT(YES)
DELETE LOGSTREAM NAME(your.logstream.dataset)

DEFINE LOGSTREAM NAME(your.logstream.dataset)

DESCRIPTION(SMF_LOGSTREAM)
MODEL(NO)
DASDONLY(YES) /* NO DASD LOG */
STG_SIZE(65532)
LS_SIZE(15000)
HLQ(IXGLOGR)
HIGHOFFLOAD(80)
LOWOFFLOAD(0)
AUTODELETE(NO) /* DELETE OPTION */
OFFLOADRECALL(YES)

Chapter 2. Installing IBM Z Decision Support 39

 MAXBUFSIZE(65532)
DIAG(NO)
RETPD(1) /* DELETE 1 DAYS */
//

Step 5.2: Defining the coupling facility structures attributes in the CFRM
function couple data set

About this task

This step applies to coupling facility log streams only. DASD-only log streams can omit this step.

Procedure
1. Determine the attributes needed to define coupling facility structures used by IBM Z Decision Support
2. Specify ALLOWAUTOALT(YES) on the list structure definition in the CFRM policy. The system may
automatically alter the size and ratio attributes of the structure as needed. Specify a minimum size for
the logger list structure with the MINSIZE parameter, to ensure that logger always has enough space
to do its work.
3. Allow the FULLTHRESHOLD parameter to take the default value.
4. Add information to the CFRM function couple data set about the desired attributes of the coupling
facility list structures for system logger applications. Note that each coupling facility structure that you
define in the LOGR policy must match those defined in the CFRM policy.
5. Activate the CFRM function couple data set using the SETXCF command

Step 5.3: Installing the SMF Extractor

Procedure
1. Copy the hlq.vrm.SDRLEXTR data set to all of the systems where you want automated collection of
SMF data.
2. Ensure that this library is APF authorized.

Step 5.4: Configuring the SMF Extractor

About this task

The SMF Extractor gathers SMF records from the IEFU8x SMF exits and writes them into the log stream
that you defined in “Step 5.1: Defining the log stream to communicate between the SMF Extractor and the
DataMover” on page 38.
JCL procedure hlq.vrm.SDRLCNTL(DRLJSMFX) and the job hlq.vrm.SDRLCNTL(DRLJVFIX) are
used to execute the SMF Extractor. This procedure sets up a STEPLIB to hlq.vrm.SDRLEXTR. This library
must be APF authorized in order for the SMF Extractor to run successfully.
The configuration member, DRLJSMFO, in the hlq.vrm.SDRLCNTL data set describes the name of the
log stream that is used for the extracted records and which SMF records are to be extracted. The
configuration member is selected through specification of the SYSTEM parameter on the DRLJSMFX
procedure.
The SMF Extractor can run as either a started task or a batch job. An operator interface is provided
to control execution. SMFEXT SMF configuration is performed with PARMLIB member SMFPRMxx. The
SMFPRMxx parameters SYS and SUBSYS define the SMF recording options.

40 IBM Z Decision Support : Administration Guide and Reference

Procedure
1. Determine what SMF records need to be extracted based on the needs of your downstream
applications.
2. If you have SUBSYS statements, in your existing SMFPRM member, in the SUBSYS statement, you must
ensure the following is updated in each SUBSYS statement.
• In the EXITS statements, you include IEFU83, IEFU84, IEFU85.
• If you are using the TYPE statement, ensure that the SMF records that are in your SMFREC statement
in SMFPxxxx are included.
• If you are using the NOTYPE statement, ensure that the SMF records that are in your SMFREC
statement in SMFPxxxx are not included.
SUBSYS
Specifies subsystem specific recording options. The SUBSYS parameter options override the
equivalent options specified on the SYS parameter. Any SUBSYS parameter option not specified
will default to the SYS parameter option for the specified subsystem.
3. In your existing SMFPRMxx member, in the SYS statement, you must ensure the following.
• In the EXITS parameter, include IEFU83, IEFU84, IEFU85.
• If you are using the TYPE statement, ensure that the SMF records that are in your SMFREC statement
in SMFPxxxx are included.
• If you are using the NOTYPE statement, ensure that the SMF records that are in your SMFREC
statement in SMFPxxxx are not included.
SYS
Specifies system wide recording options for all subsystems (JES2, TSO, STC)
4. Copy the JCL sample from hlq.SDRLCNTL(DRLJVFIX) to a data set containing production JCL and
update it to match your environment.
Update the following parameters.
• System SMFID (the SMF system name for the system is the SID value that you will find in SMFPRMxx)
• The data set for the JCL library to the production procedure library where you will copy
hlq.SDRLCNTL(DRLJSMFX) and hlq.SDRLCNTL(DRLJSMFO)
5. Ensure that the executable library (STEPLIB) is APF authorized.
6. Copy the PROC sample from hlq.SDRLCNTL(DRLJSMFX) to a data set containing production
procedures and update the JCLLIB in the JCL to point to the procedure in the PROC library.
7. Copy the sample data set from hlq.SDRLCNTL(DRLJSMFO) to a data set containing production
procedures and update it to match your environment.
Update the values of the following parameters in hlq.SDRLCNTL(SMFPxxxx) to match your
environment. Where xxxx is the SMF system ID.
OUTLGR
Specifies the log stream data set that is used when the extractor is configured to write to log
stream continuously.
SMFREC
Specifies the SMF record types to be collected by the SMF Extractor

Example configuration - one CNTL member per system

In the following example, the product has been installed into the product library with high level qualifier
DRL.
DRL.SDRLCNTL(DRLJVFIX)

Chapter 2. Installing IBM Z Decision Support 41

 //DRLJVFIX JOB (ACCT#),'EXTRACT'
/*JOBPARM BYTES=999999,CARDS=999999,LINES=9999,PAGES=99999
/*JOBPARM SYSAFF=SYSA
//******************************************************************
//* *
//* NAME: DRLJVFIX *
//* *
//* FUNCTION: *
//* SMF EXTRACTOR JCL *
//* *
//VFIPROC JCLLIB ORDER=(DRL.SDRLCNTL)
//SMFEXT EXEC DRLJSMFX,
// SYSTEM=SYSA /* SMF SYSTEM ID */

DRL.SDRLCNTL(DRLJSMFX)

//*==================================================================*/
//* */
//* THIS JCL IS THE SMF EXTRACTOR STARTUP PROC. */
//* */
//* THE SMFXPARM DATA SET SHOULD CONTAIN THE CONTROL FILES FOR */
//* EACH SYSTEM ON WHICH THE EXTRACTOR IS RUN. */
//* Change CNTL and the member to the name of your data set */
//* name and member name for the SMFXPARM for your system. */
//* */
//* Set the following parameters for maximum utilization: */
//* 1. Extractor parm MAXQD(150000) */
//* 2. MAX64(25) */
//* */
//* MAX64 parm is used to limit above the bar memory (in GB). */
//* The default value is 25, but can range between 3 and 99. */
//* */
//* To run more than one SMF Extractor in an LPAR, */
//* run the first with a parm without the MULT option. */
//* For a second (or more) SMF Extractor(s) add the MULT option */
//* as per this example: */
//* */
//* PARM=('TRACE(N),MSGLVL(9),SDUMP(Y),MAXSD(2),MAXQD(150000)', */
//* 'MAX64(25),MULT(n)') */
//* */
//* where n is a value 1 to 9 (up to 9 additional SMF Extractors) */
//* */
//*==================================================================*/
//SMFEXTP PROC SYSTEM=SYSA /* SMF SYSTEM ID */
//CKKXMAI EXEC PGM=CKKXMAI,REGION=0M,
// PARM=('TRACE(N),MSGLVL(9),SDUMP(Y),MAXSD(2),MAXQD(150000)',
// 'MAX64(25)')
//*
//STEPLIB DD DISP=SHR,DSN=DRL.SDRLEXTR
//SYSPRINT DD SYSOUT=*
//SMFXPARM DD DISP=SHR,DSN=CNTL(SMFP&SYSTEM.)
//SYSUDUMP DD SYSOUT=*
//SMFXPRNT DD SYSOUT=*
//*------------------------------

DRL.SDRLCNTL(DRLJSMFO)

******************************************************************** *
* *
* NAME: DRLJSMFO *
* *
* FUNCTION: *
* SMF EXTRACTOR CONTROL FILE. *
* *
*=====================================================================*
* COPY THIS MEMBER TO A DATA SET AS SMFPsysi WHERE sysi IS THE *
* SMF ID OF THE SYSTEM WHERE THE MEMBER WILL BE USED. *
* *
* THESE PARAMETERS MUST BE CUSTOMIZED TO MATCH YOUR INSTALLATION *
* REQUIREMENTS PRIOR TO THE FIRST STARTUP OF THE SMF EXTRACTOR. *
* *
* SET OUTLGR TO THE NAME OF THE OUTPUT LOG STREAM *
* SET SMFREC TO A COMMA SEPARATED LIST OF SMF RECORDS TO BE RECORDED *
*=====================================================================*
OUTLGR=logstreamname
SMFREC=14,15,30,42,60,61,64,65,70,71,72,73,74,85,90,94,99,100,101,113

42 IBM Z Decision Support : Administration Guide and Reference

Step 5.5: Unpacking the DataMover

Procedure
Extract the TAR file by using the following command.

tar -xvof /usr/lpp/IDSz/v1r9m0/IBM/DRLPJDM -C /destination

Where destination is the location where you want the contents of TAR file to reside and the path name
specified is the default path name.
This creates the following subdirectories:

IDSz
IDSz/DataMover
IDSz/DataMover/config
IDSz/DataMover/java

Step 5.6: Tailoring the DataMover on the Spoke system

About this task

The DataMover supports encrypted communications across the TCP/IP connection between the Agent
and the Receiver.

Procedure
1. Edit IDSz/DataMover/DataMover.sh and make the following changes.
a) Update the rundir and JAVA_HOME environment variables to point to the correct directories by
following the instructions in the file.
b) Ensure the -Xmx16G parameter is specified in the Java statement to specify the maximum memory
size for Java.
2. Duplicate the procedure for the DataMover started task and change the working directory specification
in the new copy.
3. Update the Spoke config file in the new IDSz/DataMover/config directory to specify the TCP/IP
port your new DataMover is to use for output and ensure it has the correct log stream for input from
the SMF Extractor.

Step 5.7: Configuring the DataMover

Procedure
Edit config/spoke.properties and to ensure that the following properties accurately reflect your
site.
• The TCPIP port you want the DataMover to accept connections on.
• The name of the log stream you set up to feed data into the Continuous Collector.
The remainder of the config file does not require modification.

Step 5.8: Clearing the log stream

About this task

If you have data in the log stream that is either already committed or not SMF data, you must clear the log
stream so that you do not record duplicate data. If your log stream contains uncommitted SMF data, and
you clear the log stream by following this procedure, you will lose the data.

Chapter 2. Installing IBM Z Decision Support 43

 Procedure
1. Under OMVS change into the DataMover directory.
2. Update the config/clear.properties configuration file with the correct log stream name. The log
stream you list in the file will be cleared with no verification step.
3. Issue the command DataMover.sh clear to start the DataMover, running under your account.
The DataMover will start up and erase all the data in the log stream that the SMF Extractor is writing to.
It is important to stage the cutover to Automated Data Gathering properly. Stray SMF records in the log
stream can cause inaccurate results in the curated data.
The DataMover will automatically shut down after the log stream has been cleared.

Step 5.9: Start the SMF Extractor

Procedure
Start the hlq.SDRLCNTL(DRLJSMFX) procedure.

Step 5.10: Testing the DataMover

Procedure
1. Under OMVS change into the DataMover directory.
2. Issue the command DataMover.sh spoke. To start the DataMover, running under your account.
The DataMover will start up and connect to the DataMover on the hub. If the DataMover on the hub
is not running it will issue an error message and retry. When it makes a connection, it will be ready to
send data.
To stop the DataMover, type stop and click Enter.
If the DataMover terminates with an exception about the log stream, check that the SMF Extractor is
running. If it is, wait for a full SMF interval (usually about 15 minutes) before you try again to allow it to
capture some SMF data.

Step 5.11: Creating a vehicle for running the DataMover on a Spoke system

About this task

You can run the DataMover as a started task or as a batch job .

Procedure
1. Determine whether you will run as a started task or a batch job.
2. Configure the provided samples to match your environment.
• To run as a started task
a. Modify the JCL sample DRLJDMP to point to the DataMover you just installed and the IBM Z
Decision Support Hub system.
b. Put DRLJDMP in your PROCLIB concatenation.
c. Start the DataMover to test it.
d. Stop the DataMover by using the following command.

/f stcname1,appl=stop

Where stcname is the PROC name you used for the DataMover started task.

44 IBM Z Decision Support : Administration Guide and Reference

 • To run as a batch job
a. Modify the JCL sample DRLJDMJ to create a job to run DataMover. It is easier to operate the
DataMover if it has a jobname that is no more than 7 characters long. This is because the OMVS
task that is created to run the DataMover will have the same jobname with a 1 appended to it.
b. Start DataMover to test it.
c. Stop the DataMover by using the following command.

/f jobname1,appl=stop

Where jobname is the name you used for the DataMover job.
For example, if the jobname is TUESDAY, then to stop it, the command is:

/f TUESDAY1,appl=stop

Step 5.12: Activate automated data gathering on the Spoke systems

Before you begin

Set parameter values for your SSL communications in the SSL.properties file.

About this task

You must start data gathering on each Spoke system. When you have started data gathering, the data that
is gathered on each Spoke system is sent to the Hub system.

Procedure
1. Optional: Configure SSL to protect your TCPIP links. In the previous step, you setup your
communications. By default, these communications use unencrypted TCPIP links. You can configure
your communications to encrypt your TCPIP links.
a) On each Spoke system, create a keystore for each DataMover and produce a .cert file that holds a
certificate for it.
On each Spoke system, in the DataMover Directory, issue the following commands:

Datamover.sh SSL GEN

DataMover.sh SSL EXPORT

b) The certificate for the hub must be exported to each Spoke system
c) The certificates for each Spoke must be transported to the Hub
d) Import each certificate into the system's trust store. Ensure that each certificate is imported with a
unique name.
When the certificates arrive, issue the following command:

DataMover.sh SSL IMPORT name.cert

e) Modify the hub and spoke configurations by changing the use_ssl=no setting on each TCPIP stage
to use_ssl=yes. The SSL implementation that is used is that of the underlying Java installation.
2. Start automated data gathering the Spoke system. If you have not previously collected data on this
system, you can start collecting data at any time. If you have previously been gathering data for the
system, wait until the cutoff point for its data collection before you start collecting data.
• Start the DataMover on each spoke system.
– Ensure that the DataMover on the Hub system is running.
– Under OMVS change into the DataMover directory.
– Issue the command DataMover.sh Spoke.

Chapter 2. Installing IBM Z Decision Support 45

 • Start the SMF Extractor by running the SDRLCNTL(DRLJSMFX) customized job setup in “The SMF
Extractor” on page 9.

Installing the Usage and Accounting Collector

The CIMS Lab Mainframe collector is incorporated into IBM Z Decision Support and called the Usage and
Accounting Collector.
For a description of the Usage and Accounting Collector, see the System Overview section in the Usage
and Accounting Collector User Guide.
To install the Usage and Accounting Collector, follow these steps:
• “Step 1: Customizing the Usage and Accounting Collector” on page 46
• “Step 2: Allocating and initializing Usage and Accounting files” on page 48
• To verify your installation, follow these steps:
– “Step 3: Processing SMF data using DRLNJOB2 (DRLCDATA and DRLCACCT)” on page 49
– “Step 4: Running DRLNJOB3 (DRLCMONY) to create invoices and reports” on page 51
– “Step 5: Processing Usage and Accounting Collector subsystems” on page 53
To support programs such as CICS, Db2, IDMS, IMS, VM/CMS, VSE, DASD Space Chargeback, and Tape
Storage Accounting, edit and run the appropriate jobs. Examples of member names are DRLNCICS,
DRLNDB2, DRLNDISK.

Step 1: Customizing the Usage and Accounting Collector

About this task

Installation job DRLNINIT invokes the REXX program DRLCINIT. This program is a utility that customizes
Usage and Accounting Collector jobs to your specifications. DRLCINIT inserts job cards, adds high level
nodes to all Usage and Accounting Collector data sets, changes VOLSER numbers, and specifies DSCB
model names.
Run job DRLNINIT and follow these steps:

Procedure
1. Replace sample job card with user job card.
2. Insert or replace data set name high-level qualifiers.
3. Insert serial numbers on the VOLUME parameter.
4. Insert DSCB model names.
Note: If you do not run DRLCINIT, you must change each job member manually as you use it.

DRLNINIT

About this task

To execute job DRLNINIT, follow these instructions:

Procedure
1. DRL.SDRLCNTL (DRLMFLST) contains the list of Usage and Accounting Collector jobs that are used in
this utility.
2. The SMP/E process allocates &HLQ.LOCAL.CNTL. This DSN stores the customized jobs. The Usage and
Accounting Collector JCL is copied to this library and changes are made in this library. The first step in

46 IBM Z Decision Support : Administration Guide and Reference

 DRLNINIT performs the copy. This makes it possible to execute DRLNINIT repeatedly until the desired
result is achieved.
Replace the two occurrences of &HLQ.LOCAL.CNTL in DRLNINIT with the filename that was allocated
during the SMP/E install.
3. Job card replacement.
A standard job card can be inserted with a unique jobname. The following parameters in STEP020
control the job card replacement:
JCDSN=
Specifies the file containing the standard job card.
For example: JCDSN=DRL.SDRLCNTL(JBCARD)
The contents in member JBCARD is used as the job card.
JCLINES=
The number of lines to use from JCDSN.
For example: JCLINES=2
The first two lines in the JCDSN member are used as a job card.
JCMASK=
A unique job name can be generated for the execution jobs. The JCMASK is used to specify the
common part of the jobname and the position of a sequential number. After the first character,
you must enter a sequence of '*' (asterisk) characters to indicate where to insert the job sequence
number. The sequence mask is from 2 to 6 characters in length:
Examples:
JCMASK
Jobnames generated
DRL****
DRL0001, DRL0002, DRL0003...
P******Q
P000001Q, P000002Q, P000003Q...
DRL**DRL
DRL01DRL, DRL02DRL, DRL03DRL...
JCSKIP=
Specify any non-blank character and the Job card replacement process will be skipped.
For example: JCSKIP=Y
No job card customization of the Usage and Accounting Collector execution jobs is done.
4. Insert or replace data set name high level qualifiers. The default filenames used for the Usage and
Accounting Collector files start with the high-level qualifier of 'DRL'. The HLQ process in the DRLCINIT
utility allows this default to be replaced or an additional high-level qualifier to be inserted. The
following parameters in STEP020 control the HLQ processing:
HLQACT=
Specifies the action to perform: R=Replace, I=Insert.
For example: HLQACT=R
Every occurrence of a filename with the high-level qualifier of 'DRL.', will be replaced with the value
in HLQDSN.
HLQDSN=
The new value to use for the high-level qualifier.
For example: HLQDSN=DRL.TDSZUAC
The default filenames are changed to start with 'DRL.TDSZUAC'.

Chapter 2. Installing IBM Z Decision Support 47

 HLQSKIP=
Specify any non-blank character and the HLQ processing is skipped.
For example: HLQSKIP=Y
No customization of the Usage and Accounting Collector data set names is done.
5. Insert VOLSER numbers. At various places within the Usage and Accounting Collector jobs, volume
serial numbers are needed. The DRLCINIT job allows you to replace them all globally. The default
volume serial numbers are “??????” throughout the JCL. The default volume serial appears in IDCAMS
processing as VOL(??????) and VOL=SER=?????? and is used for VSAM file allocation. The JCL also uses
VOL=SER=?????? for temporary space allocations. The following parameters in STEP020 control the
VOLSER processing:
VOL=
The replacement volume serial to use instead of “??????”
VSSKIP=
Specify any non-blank character and the VOLSER processing is skipped.
For example: VSSKIP=Y
No customization of the Usage and Accounting Collector VOL or VOL=SER parameters is done.
6. Insert DSCB model names.
A model DSCB parameter is used for the proper functioning of Generation Data Groups (GDGs). The
Usage and Accounting Collector JCL is distributed with all model DSCBreferences set to 'MODELDCB'.
If your installation does not require the use of this parameter, you can delete it manually from the
JCL. The DSCB processing can be used to change the default to a value used at your installation. The
following parameters in STEP020 control the DSCB processing:
MDDSCB=
The replacement model DSCB to use instead of MODELDSCB.
MDSKIP=
Specify any non-blank character and the model DSCB processing will be skipped.
For example: MDSKIP=Y
No customization of the Usage and Accounting Collector model DSCB will be done.
The DRLCINIT utility produces statistics for the execution. If any exceptions are noted, they can be
found listed in the DRLMXCEP member of &HLQ.LOCAL.CNTL. These exceptions might or might not be
severe enough to cause a JCL error; check DRLMXCEP if exceptions are reported.

Statistic report DDNAME SYSTSPRT

Processing......

Completed SYSTSIN

69 Files
0 Exceptions

JobCard : 68 Replacements
HLQ : 1389 Replacements
Volume : 30 Replacements
ModelDSCB: 207 Replacements

Normal completion

Step 2: Allocating and initializing Usage and Accounting files

About this task

DRLNJOB1 is a member in DRL190.SDRLCNTL. This job creates four permanent files and four Generation
Data Groups (GDGs). The permanent files are:

48 IBM Z Decision Support : Administration Guide and Reference

 Usage and Accounting Collector client
Member DRLMCLNT contains sample client records. For information about client records, see “Client
Identification and Budget Reporting - DRLCCLNT and DRLCBDGT” in the Usage and Accounting
Collector User Guide.
Rate
Members DRLMRATE, DRLMRT01, and DRLMRT02 contain sample Rate records. For information about
rate records, see “Computer Center Chargeback Program - DRLCMONY” in the Usage and Accounting
Collector User Guide.
Dictionary
Members DRLKxxxx contain the default record definitions for the Usage and Accounting Collector
Dictionary. For more information about the Usage and Accounting Collector Dictionary, see “Dictionary
- CIMSDTVS” in the Usage and Accounting Collector User Guide.
Status and Statistics VSAM
The Status and Statistics file is a VSAM file that should be allocated so that checkpoint and statistical
information can be recorded for program DRLCEXTR. Use the default values to create the VSAM files.
Note: You do not need to set rates or identify clients at this time.
For the JCL, see member DRLNJOB1 in DRL190.SDRLCNTL.

Step 3: Processing SMF data using DRLNJOB2 (DRLCDATA and DRLCACCT)

About this task

This job, which is divided into two steps, runs programs DRLCDATA and DRLCACCT. These programs
interface with the z/OS-SMF data set and create the DRL.DRLCACCT.DAILY batch chargeback file.
DRLNJOB2 job is the basis for daily processing and is the only job required on a daily basis for
batch chargeback. Logically, it is run immediately after the SMF data set is unloaded to disk or tape.
After DRLNJOB2 processing is finished, data set DRL.DRLCACCT.DAILY contains z/OS batch and TSO
accounting records, and data set DRL.SMF.HISTORY contains reformatted SMF records.
Note: It is recommended that you read “SMF Interface Program - DRLCDATA” and “Accounting File
Creation Program - DRLCACCT” in the Usage and Accounting Collector User Guide before you start
changing the default control statements.

Procedure
1. OB STEP DRLC2A
This executes program DRLCDATA. For more information, see “SMF Interface Program - DRLCDATA” in
the Usage and Accounting Collector User Guide.

Table 2. Explanation of Program DRLCDATA

Input/output DDNAME Description
INPUT SMFIN This is the SMF DUMP data set.
INPUT CIMSCNTL Data set DRL190.SDRLCNTL (DATAINPT)
Contains input control statements. For more
information, see the Control Statement Table in
Chapter 2. “SMF Interface Program - DRLCDATA”
in the Usage and Accounting Collector User Guide.

Chapter 2. Installing IBM Z Decision Support 49

 Table 2. Explanation of Program DRLCDATA (continued)
Input/output DDNAME Description
OUTPUT CIMSSMF Usage and Accounting Collector reformatted
SMF data set. Contains each SMF record from
the input data set unless limited by a records
statement. This data set is designed as a backup
data set of reformatted SMF Records. Depending
on installation requirements, you might choose
to DD DUMMY this data set, or to COMMENT the
statement.
OUTPUT CIMSACCT This data set contains selected SMF chargeback
records (6, 30, 101, 110). This data set is used as
input in step DRLC2B.
OUTPUT CIMSCICS This data set contains CICS records (SMF Type
110). This record is used by the Usage and
Accounting Collector CICS interface programs.
OUTPUT CIMSDb2 This data set contains Db2 records (SMF Type
101). This record is used by the Usage and
Accounting Collector Db2 interface programs.
2. SMF Merge
It is recommended that you insert a merge between steps DRLC2A and DRLC2B to create a history of
data set DRL.SMF.HISTORY (see member DRLNSMFM in DRL190.SDRLCNTL). The merge field is 7 for
one character. Use a cartridge tape and block the output data set to 32K (BLKSIZE = 32760).
The Usage and Accounting Collector Merge is a sample SORT/MERGE set of JCL that creates a sorted
history data set of Usage and Accounting Collector accounting records can be found in data set
DRL190.SDRLCNTL member DRLNMERG. This job should be run daily after the batch and online Usage
and Accounting Collector jobs have been executed.
If DRLNMERG is done on a daily basis, at the end of the month, the Usage and Accounting Collector
master file is in account code sort sequence.
You should maintain the history data sets on tape. Leave the daily files on disk for daily reports and set
up generation data sets to tape for the history file.
3. JOB STEP DRLC2B
This executes program DRLCACCT, which processes the data set created by program DRLCDATA
(DDNAME CIMSACCT) and generates the Usage and Accounting Collector batch chargeback data set.
For details, see “Accounting File Creation Program - DRLCACCT” in the Usage and Accounting Collector
User Guide.

Table 3. Explanation of Program DRLCACCT

Input/output DDNAME Description
INPUT CIMSDATA Reformatted SMF records. These records are
created by DDNAME CIMSACCT in program
DRLCDATA. The Usage and Accounting Collector
Suspense file for unmatched job step and print
records is appended to DDNAME CIMSDATA.
INPUT CIMSCNTL Control statements.

50 IBM Z Decision Support : Administration Guide and Reference

 Table 3. Explanation of Program DRLCACCT (continued)
Input/output DDNAME Description
INPUT CIMSTABL Optional user-supplied table to convert job
names and/or job card account codes to a new
format.
For more information, see Chapter 3. “Accounting
File Creation Program - DRLCACCT” in the Usage
and Accounting Collector User Guide.

INPUT CIMSDTVS Usage and Accounting Collector Dictionary VSAM

file.
INPUT CIMSPDS Control statements.
This data set is used by DRLCACCT when
PROCESS CIMS SERVER RESOURCE RECORDS
control statement is specified. A member,
DRLMALSA, in this data set contains the control
members for the different records.

OUTPUT IMSACT2 Usage and Accounting Collector batch

chargeback file containing the 79x accounting
records. This data set is used by DRLCEXTR and
DRLCMONY.
OUTPUT CIMSUSPN Suspense file. This data set contains Step and
Print records that have not been matched with a
Job Start or Job Stop record.
OUTPUT CIMSEXCP This data set contains records that have not been
matched with entries in the CIMSTABL data set.
OUTPUT CIMSPRNT This data set contains the runtime parameters
and the results of the run.
OUTPUT CIMSMSG This data set contains informational messages.
OUTPUT CIMSSEL Usage and Accounting Collector accounting
records. This data set contains the records
that failed date selection when the PROCESS
CIMS MAINTENANCE and NON-SELECTED
FILE PROCESSING ON control statements are
specified.
OUTPUT CIMSUNSP Unsupported CSR records. This data set contains
all CSR records that did not have a definition
within CIMSDTVS.

Note: For JCL information, see member DRLNJOB2 in DRL190.SDRLCNTL.

Step 4: Running DRLNJOB3 (DRLCMONY) to create invoices and reports

About this task

DRLNJOB3 contains the JCL to run program DRLCMONY, which creates invoices and zero-cost invoices
(rate determination).
Billing control statements are contained in member DRLMMNY. Edit these statements to customize Usage
and Accounting Collector for your installation.

Chapter 2. Installing IBM Z Decision Support 51

 You can use the Usage and Accounting Collector defaults as distributed until you decide on client
information, billing rates, and control information.
To run DRLNJOB3, follow these steps:

Procedure
1. Run DRLN3A.
This step converts the 79x accounting records into CSR+ records. DRLCMONY supports only CSR+
records.
2. Run DRLC3B.
This step sorts the data set created by step DRLC3A into account code, job name, and job log number
sequence.
3. Run DRLC3C.
This step is for the Computer Center Billing System - DRLCMONY.

Input/output DDNAME Description

INPUT CIMSACCT Integrated chargeback data set.
INPUT CIMSCLVS Client records.
INPUT CIMSCNTL Control statements.
INPUT CIMSRTVS Billing rates.
INPUT CIMSCLDR Usage and Accounting Collector calendar file.
INPUT CIMSNCPU CPU normalization statements.
INPUT CIMSSCPU CPU job class and priority surcharge statements.
OUTPUT SYSOUT Messages
OUTPUT CIMSPRNT Processing results.
OUTPUT CIMSINVC Invoices.
OUTPUT CIMSMSG Informational messages.
OUTPUT CIMSSUM Summary records by account. One record per
account and billable item - (Rate Code).
OUTPUT CIMSIDNT Identifier data that can be loaded into an IBM
Tivoli Usage and Accounting Manager database.
This file is produced by DRLCMONY in Server
mode.
OUTPUT CIMSDETL Detail data that can be loaded into an IBM Tivoli
Usage and Accounting Manager database. This
file is produced by DRLCMONY in server mode.
OUTPUT CIMSUMRY Summary data that can be loaded into an IBM
Tivoli Usage and Accounting Manager database.
This file is produced by DRLCMONY in server
mode.

For record descriptions, refer to “Accounting File Record Descriptions” in the Usage and Accounting
Collector User Guide.
For JCL information, see member DRLNJOB3 in DRL190.SDRLCNTL.

52 IBM Z Decision Support : Administration Guide and Reference

Step 5: Processing Usage and Accounting Collector subsystems

About this task

Note: This step is optional.
Usage and Accounting Collector is now installed and ready to be customized for batch chargeback.
After you are comfortable with the results you are receiving from the Usage and Accounting Collector
z/OS batch system, you can start integrating data from the wide range of subsystems that Usage and
Accounting Collector supports.
To integrate a Usage and Accounting Collector subsystem, perform the following steps:

Procedure
1. Edit the appropriate JCL member. For example, DRLNCICS.
2. Create an account code conversion table.
3. Process the job.
4. Merge the output with the input to program DRLCMONY (DRLNJOB3).
5. Run DRLNJOB3 to generate the integrated invoices.

Results
The following list provides a list of member names for some of the most commonly-used Usage and
Accounting Collector subsystems.

Table 4. Usage and Accounting Collector Subsystem Member Names (Partial List)
Subsystem Member name Description
DRLNCICS CICS Support
DRLNDB2 Db2
DRLNMQSR MQSeries®
DRLNDISK DASD Space
DRLNTAPE Tape Storage
DRLNIMS IMS
DRLNUNIV ROSCOE, ADABAS/SMF, IDMS/SMF, RJE, WYLBUR,
Oracle, MEMO, Control-T, BETA

Installing multiple IBM Z Decision Support systems

About this task
You can install more than one IBM Z Decision Support system on the same Db2 subsystem. This is useful
if you want to develop and test newIBM Z Decision Support applications.
Note: You cannot use Db2 Copy to copy the objects from the first installation to the new one. If you do,
QMF definitions may be lost.
To install another IBM Z Decision Support system, repeat the installation from “Step 3.1: Setting up
security” on page 17 to “Step 3.13: Installing components” on page 31 and specify different values for:
• Db2 subsystem
• Database
• System table prefix

Chapter 2. Installing IBM Z Decision Support 53

 • Other tables prefix
• RACF groups (if necessary)
• Local data sets
For example, assume your user ID is BILL, and you want a private IBM Z Decision Support system.
Dialog parameter
Value
Db2 subsystem
DB2T
Database
BILLDB
System table prefix
BILL
Other table prefix
BILL
Users to grant access to
BILL
Local data sets
BILL.DEFS....and so on
Other users cannot use this system because BILL is not a Db2 secondary authorization ID nor a RACF
group ID. If you want to share this new IBM Z Decision Support system, establish a valid RACF group ID
and use the group ID as the prefix instead of BILL.

Installing IBM Z Decision Support features separately

About this task
Use this information if you are installing IBM Z Decision Support features separately; that is, not at the
same time as you installed the IBM Z Decision Support base and any features. To install features follow
these steps.

Procedure
1. Follow the instructions in the IBM Z Decision Support Program Directory to use SMP/E to install all the
performance features required. If you have already installed a feature with SMP/E, you need not install
it again unless you are reinstalling to correct a previous installation error.
2. Update IBM Z Decision Support system tables with information about the features you are installing
a) From the IBM Z Decision Support Administration window, select 1,System, to display the System
window.
b) Select 2, System Tables, to display the System Tables window (Figure 17 on page 55).

54 IBM Z Decision Support : Administration Guide and Reference

 Other Utilities Help

Administration

Select System

System Tables

Press Enter to list all system tables.

Prefix : DRLSYS
Status : Created
Creator : JUDIT
Database name : DRLDB

F1=Help F2=Split F5=Create F6=Update

F9=Swap F11=Delete F12=Cancel

Command ===>
F1=Help F2=Split F3=Exit F9=Swap F10=Actions F12=Cancel

Figure 17. System Tables (created) window

c) Press F6 (Update) to update the system tables with information about the newly installed features.
d) Resolve any Db2 errors that appear at the top of the browse window. The successful installation
of a component that is a part of the feature (described in “Installing a component” on page 120)
verifies the feature's installation

Chapter 2. Installing IBM Z Decision Support 55

56 IBM Z Decision Support : Administration Guide and Reference
Chapter 3. Installation reference

SMF Configuration
In order to ensure that messages reach the SMF Extractor, it is necessary to review your SMFPRMxx
member, to ensure that the necessary exits are going to be driven.
• If you are running z/OS 2.3 or later, you must use the IEFU86 exit active.
• If you are running z/OS 2.2 or earlier, you must use the IEFU83, IEFU84 and IEFU85 exits active.
Under z/OS 2.3 you may run either the IEFU83/4/5 exits or the IEFU86 exits. This is to allow for
migration. It is strongly recommended that you move to using the IEFU86 exit as soon as possible.

Review the SID parameter

The SID parameter identifies the systems SMF ID. Users probably do not want to change it, but there are
some aspects of how IBM Z Decision Support process that they need to be aware of.
• The value turns up in the IBM Z Decision Support database in a column usually called MVS_SYSTEM_ID.
– The system name is not recorded and is not present in most SMF records.
– Neither is the SYSPLEX name.
• Each system feeding data into the same IBM Z Decision Support database should have a unique SMF ID.
• If a system is re-IPL’d on a different LPAR and ends up with a different SMF ID, then IBM Z Decision
Support will see it as a separate system in its reports.
– This may reduce the value of some of the reports because there will be ‘holes’ in the data while it was
running with a different SMF ID.
– If there is a significant difference in the capacities of the two LPARs such separation may be desirable
so the reports reflect the actual execution of the system in each LPAR it can run in.
While it is possible to change the SMF ID in the data as it is being ingested, it is better not to have to do it.

Review your SYS settings

The SYS setting specifies overall SMF recording options for the whole system.
• The TYPE field should contain each type of SMF record that the user want to collect from the system.
• The EXITS field must contain the names of the exit(s) that the user want the SMF Extractor to use.
If either of these are wrong, then IBM Z Decision Support will not receive the data that it requires.

Review each of your SUBSYS settings

Each SUBSYS setting specifies SMF recording options for SMF records coming from a particular
subsystem.
• The TYPE field should contain each type of SMF record that the user want to collect from the
subsystem.
• The EXITS field must contain the names of the exit(s) that the user want the SMF Extractor to use.
– If the SUBSYS settings contain any active exit points other than IEFU83, IEFU84, IEFU85 (z/OS
2.2 or earlier) or IEFU86 (z/OS2.3 or higher) then the relevant IEFU** exit points need to be
explicitly included for the SUBSYS. The SUBSYS EXITS specification is used in place of the SYS EXITS
specification if it is present for a SUBSYS.
If either of these are wrong, then IBM Z Decision Support will not receive the data that it requires.

© Copyright IBM Corp. 1993, 2017 57

Sample configuration members
Sample JCL and associated members are provided to help with your configuration and installation tasks.
Before running for the first time, tailor the members to suit the specific requirements of the user
installation.

DRLJSMFO - SMF Extractor control file

Sample member DRLJSMFO is provided in the SDRLCNTL library. It contains parameters and instructions
for configuring the SMF Extractor control file.
Before the first startup of the SMF Extractor, customize the parameters by following the instructions in the
comments.

***********************************************************************
* NAME: DRLJSMFO *
* *
* FUNCTION: SMF EXTRACTOR CONTROL FILE. *
* *
* COPY THIS MEMBER TO A DATA SET AS SMFPxxxx WHERE xxxx IS THE *
* 4 CHARACTER SMF ID OF THE SYSTEM WHERE THE MEMBER WILL BE USED. *
* *
* THESE PARAMETERS MUST BE CUSTOMIZED TO MATCH YOUR INSTALLATION *
* REQUIREMENTS PRIOR TO THE FIRST STARTUP OF THE SMF EXTRACTOR. *
* *
* SET OUTLGR TO THE NAME OF THE OUTPUT LOG STREAM *
* SET SMFREC TO A COMMA SEPARATED LIST OF SMF RECORDS TO BE RECORDED *
*=====================================================================*
OUTLGR=log.stream.name
SMFREC=14,15,30,42,60,61,64,65,70,71,72,73,74,85,90,94,99,100,101,113

Figure 18. DRLJSMFO: Parameters for the SMF Extractor control file

For example:

OUTLGR=&SYSNAME.DRL.LOGSTRM
SMFREC=14,15,30,42,60,61,64,65,70,71,72,73,74,85,90,94,99,100,101,113

DRLJSMFX - SMF Extractor startup procedure

Sample member DRLJSMFX is provided in the SDRLCNTL library. It contains the JCL for the SMF Extractor
startup procedure.
Before the first startup of the SMF Extractor, customize the parameters by following the instructions in the
comments.

58 IBM Z Decision Support : Administration Guide and Reference

 //*==================================================================*/
//* */
//* THIS JCL IS THE SMF EXTRACTOR STARTUP PROC. */
//* */
//* THE SMFXPARM DATA SET SHOULD CONTAIN THE CONTROL FILES FOR */
//* EACH SYSTEM ON WHICH THE EXTRACTOR IS RUN. */
//* Change CNTL and the member to the name of your data set */
//* name and member name for the SMFXPARM for your system. */
//* */
//* Set the following parameters for maximum utilization: */
//* 1. Extractor parm MAXQD(150000) */
//* 2. MAX64(25) */
//* */
//* MAX64 parm is used to limit above the bar memory (in GB). */
//* The default value is 25, but can range between 3 and 99. */
//* */
//* To run more than one SMF Extractor in an LPAR, */
//* run the first with a parm without the MULT option. */
//* For a second (or more) SMF Extractor(s) add the MULT option */
//* as per this example: */
//* */
//* PARM=('TRACE(N),MSGLVL(9),SDUMP(Y),MAXSD(2),MAXQD(150000)', */
//* 'MAX64(25),MULT(n)') */
//* */
//* where n is a value 1 to 9 (up to 9 additional SMF Extractors) */
//* */
//*==================================================================*/
//SMFEXTP PROC SYSTEM=SYSA /* SMF SYSTEM ID */
//CKKXMAI EXEC PGM=CKKXMAI,REGION=0M,
// PARM=('TRACE(N),MSGLVL(9),SDUMP(Y),MAXSD(2),MAXQD(150000)',
// 'MAX64(25)')
//*
//STEPLIB DD DISP=SHR,DSN=DRL.SDRLEXTR
//SYSPRINT DD SYSOUT=*
//SMFXPARM DD DISP=SHR,DSN=CNTL(SMFP&SYSTEM.)
//SYSUDUMP DD SYSOUT=*
//SMFXPRNT DD SYSOUT=*
//*------------------------------

Figure 19. DRLJSMFX: JCL for the SMF Extractor startup procedure

The SMF Extractor startup procedure parameters are as follows:

TRACE
Include the diagnostic trace in the output. Value can be Y or N.
MSGLVL
Defines the message level. Values are 0-9.
SDUMP
SVC Dump. Value is Y or N.
MAXSD
Maximum number of SVC dumps. Default is 2.
MAXQD
Maximum queue depth for SMF records. MAXQD (in the parameters for the CKKXMAI) can be updated
to a maximum of 9999, if necessary, when the SMF Extractor runs out of queue space. The value
should be increased incrementally to balance functionality with available resources. A value of 5000
is usually enough for a very busy LPAR. Default is 2000.
MAX64
Maximum 64-bit virtual storage the SMF Extractor may use, in gigabytes. Values are 3-99. Default is
25.
Note: 64-bit virtual storage obtained by the extractor with the MAX64 parameter, for the purpose of
buffering SMF data, is separate from system or job specific MEMLIMIT storage.

Chapter 3. Installation reference 59

Defining a DASD-only log stream
This is an example of the JCL for defining a DASD-only log stream.
Note: It is recommended to use a DASD-only log stream with IBM Z Decision Support due to the data
volume involved.
Customize the JCL before running the job by following the instructions in the comments.
Note: RETPD must be greater than zero.

//CRLOGRDS JOB (IZDS)

//******************************************************************
//* DEFINE IZDS LOG STREAM ON DASD *
//******************************************************************
//* Change the following: *
//* <LOG_STRM> - Log stream name. Name must be unique by *
//* SYSID. Recommended name is *
//* <SYSID>.DRL.LOGSTRM *
//****************************************************************** //*
//IXCMIAPU EXEC PGM=IXCMIAPU
//STEPLIB DD DISP=SHR,DSN=SYS1.MIGLIB
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DATA TYPE(LOGR)

DEFINE LOGSTREAM NAME(<LOG_STRM>)

DESCRIPTION(IDSZ_LOGSTREAM)
DASDONLY(YES)
MAXBUFSIZE(65532)
LS_SIZE(1000000)
LS_ALLOCAHEAD(3)
STG_SIZE(5000)
AUTODELETE(YES)
RETPD(1)
HLQ(DRL)
HIGHOFFLOAD(40)
LOWOFFLOAD(0)
DIAG(YES)
/*
//

Figure 20. JCL to define a DASD-only log stream

Dialog parameters
This topic describes dialog parameters that are set initially by member DRLEINI1 in the
DRLxxx.SDRLEXEC library and read from the userid.DRLFPROF data set. IBM Z Decision Support initializes
a new user's first dialog session with parameter settings from userid.DRLFPROF. From that point forward,
a user's dialog parameters are in personal storage in member DRLPROF in the library allocated to
the ISPPROF ddname, which is usually tsoprefix.ISPF.PROFILE. If DRLFPROF exists, a user changes
parameter values through the Dialog Parameters window. DRLEINI1 continues to set parameters that do
not appear in the Dialog Parameters window. It does this when a user starts IBM Z Decision Support.
“Step 3.3: Preparing the dialog and updating the dialog profile” on page 21 describes the installation step
where userid.DRLFPROF is customized for your site. It refers to this section for descriptions of:
• “Modifying the DRLFPROF data set” on page 61
• “Overview of the Dialog Parameters window” on page 61
• “Dialog parameters - variables and fields” on page 63
• “Allocation overview” on page 72

60 IBM Z Decision Support : Administration Guide and Reference

 Modifying the DRLFPROF data set

Modifying the DRLFPROF data set

About this task

The DRLFPROF data set contains user modifiable parameters. A sample of the DRLFPROF data set is
provided in member DRLFPROF in library SDRLCNTL. To customize DRLFPROF with your site specific
values, allocate a data set with the name userid.DRLFPROF and copy in the sample DRLFPROF member
from the SDRLCNTL library.
For a description of the fields that can be modified in the userid.DRLFPROF data set, see “Dialog
parameters - variables and fields” on page 63.
When editing the userid.DRLFPROF data set, note that:
• IBM Z Decision Support regards any characters after the /* characters as comments. This means that //*
JCL comments cannot be used. A closing */ is recommended but not required.
• The format for field assignment is: field-name = value [/* comment [*/]] except as noted below. No other
tokens may be present. Tokens are case insensitive.
• Each field assignment must be completed on one line. Continuation is not supported.
• Any value (even integer values) can be given as a REXX-style string, delimited by the single (') or double
(") quotation marks. Escaping of delimiter characters works in the same way as a REXX string.
• If a value does not begin with a ' or " character, only the first blank-separated word present after the =
character is taken.
• Though sequence numbering in DRLFPROF may not cause errors, it is not supported and should be
turned off.
• For the fields DEF_JCLSTA1, DEF_JCLSTA2, DEF_JCLSTA3 and DEF_JCLSTA4, the value is taken as any
characters between the = and the '/*, or end of the line if no comment is present. Delimiting this value
with double quotation marks (") is highly recommended but not required.
• If the above recommendations are adhered to, the DRLFPROF file syntax is a subset of REXX syntax and
so syntax highlighting can be used for easier editing.

Overview of the Dialog Parameters window

The parameters displayed in the Dialog Parameters window depend on whether your installation uses
QMF. This section shows the parameters used when QMF is used. For an overview of the parameters used
when QMF is not installed on your system, refer to Figure 22 on page 63.

Dialog Parameters when QMF is used

Figure 21 on page 62 is a logical view of the Dialog Parameters window, which is available from the
System window of the administration dialog and from the Other pull-down of the reporting dialog. You can
change the personal settings that control their your dialog sessions. For a description of the fields in this
window, see “Dialog parameters - variables and fields” on page 63.

Chapter 3. Installation reference 61

Overview of the Dialog Parameters window

Dialog Parameters

Type information. Then press Enter to save and return.

More: +

Db2 subsystem name . . . . . DSN

Db2 plan name for TDS . . . . DRLPLAN
Database name . . . . . . . . DRLDB
Storage group default . . . . DRLSG
Prefix for system tables . . DRLSYS
Prefix for all other tables . DRL
Show TDS environment data . . NO (YES or NO)

Buffer pool for data . . . . BP0

Buffer pool for indexes . . . BP0

Users to grant access to . . DRLUSER ________ ________ ________

________ ________ ________ ________

SQL ID to use (in QMF) . . . DRLUSER

QMF language . . . . . . . . PROMPTED (SQL or PROMPTED)
SYSOUT class (in QMF) . . . Q
Default printer . . . . . . . ________ (for graphic reports)
SQLMAX value . . . . . . . . 5000

Reporting dialog mode . . . . 1 1. End-user mode

2. Administrator mode

Dialog language . . . . . . . 1 1. English

3. Japanese
Db2 data sets
Prefix . . . . . . . . . . DSN810
Suffix . . . . . . . . . . ___________________________________
QMF data sets prefix . . . . QMF810

IBM Z Decision Support data sets prefix . . . . DRL190

Temporary data sets prefix . (user_ID substituted)

Local definitions data set DRL.LOCAL.DEFS

Local GDDM formats data set DRL.LOCAL.ADMCFORM
Local messages data set . . . DRL.LOCAL.MESSAGES
Saved reports data set . . . DRL.LOCAL.REPORTS
Saved charts data set . . . . DRL.LOCAL.CHARTS

Job statement information (required for batch jobs):

//(user_ID substituted) JOB (000000,XXXX),'USER1',MSGLEVEL=(1,1),
// NOTIFY=(user_ID substituted),MSGCLASS=Q,CLASS=E,REGION=4096K
//*

F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 21. Dialog Parameters window, when QMF is used

Dialog Parameters when QMF is not used

Figure 22 on page 63 is a logical view of the Dialog Parameters window, which is available from the
System window of the administration dialog and from the Other pull-down of the reporting dialog. IBM Z
Decision Support users can change personal settings that control their dialog sessions. For a description
of the fields in this window, see “Dialog parameters - variables and fields” on page 63.

62 IBM Z Decision Support : Administration Guide and Reference

 Dialog parameters - variables and fields

Dialog Parameters

Type information. Then press Enter to save and return.

More: +

Db2 subsystem name . . . . . DSN

Db2 plan name for TDS . . . . DRLPLAN
Database name . . . . . . . . DRLDB
Storage group default . . . . DRLSG
Prefix for system tables . . DRLSYS
Prefix for all other tables . DRL
Show TDS environment data . . NO (YES or NO)

Buffer pool for data . . . . BP0

Buffer pool for indexes . . . BP0

Users to grant access to . . DRLUSER ________ ________ ________

________ ________ ________ ________

Batch print SYSOUT class . . A

Printer line count per page 60
SQLMAX value . . . . . . . . 5000

Reporting dialog mode . . . . 1 1. End-user mode

2. Administrator mode

Dialog language . . . . . . . 1 1. English

2. Japanese

Db2 data sets

Prefix . . . . . . . . . . DB2.V820
Suffix . . . . . . . . . .

TDS for zOS data

sets prefix . . . . . . . . . TDS182
Temporary data sets prefix (user_ID substituted)

Local defs data set . . . . . DRL.LOCAL.DEFS

Local User defs data set . . DRL.LOCAL.USER.DEFS
Local GDDM formats data set DRL.LOCAL.ADMCFORM
Local messages data set . . . DRL.LOCAL.MESSAGES
Saved reports data set . . . DRL.LOCAL.REPORTS
Saved charts data set . . . . DRL.LOCAL.CHARTS

Job statement information (required for batch jobs):

//(user_ID substituted) JOB (000000,XXXX),'USER1',MSGLEVEL(1,1),

// NOTIFY=&SYSUID,MSGCLASS=Q,CLASS=E,REGION=4096K
//*
//*
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 22. Dialog Parameters window, when QMF is not used

Dialog parameters - variables and fields

Most variable names in userid.DRLFPROF and field names in the Dialog Parameters window are directly
related. The following table describes the relationship between the variables and fields and describes
how IBM Z Decision Support uses the values to allocate libraries or control other dialog functions. It also
describes variables and fields that do not have exact equivalents.
“Modifying the DRLFPROF data set” on page 61 shows the user-modifiable area of the file that is
processed at the product startup. The “Overview of the Dialog Parameters window” on page 61 shows the
Dialog Parameters window. “Allocation overview” on page 72 describes the data sets allocated by IBM Z
Decision Support.
userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

modtenu N/A None

The fully qualified name of the user ISPF table library, if any.

db2plib2 N/A SDSNPFP

Chapter 3. Installation reference 63

Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

The Db2 panel library, which, depending on the value of db2def, is either a fully qualified name or a value that IBM Z Decision Support
appends to def_db2dspfx before appending def_db2dssfx.

db2plibe N/A SDSNPFPE

The English Db2 panel library, which, depending on the value of db2def, is either a fully qualified name or a value that IBM Z Decision
Support appends to def_db2dspfx before appending def_db2dssfx.

db2plibk N/A SDSNPFPK

The Japanese Db2 panel library, which, depending on the value of db2def, is either a fully qualified name or a value that IBM Z Decision
Support appends to def_db2dspfx before appending def_db2dssfx.

qmfprint N/A YES

Specifies whether the QMF output is saved in the DSQPRINT data set (YES) or in the SYSOUT class (NO).

def_db2subs Db2 subsystem name DSN

The Db2 subsystem where IBM Z Decision Support resides.

This required field can be 4 alphanumeric characters. The first character must be alphabetic.
The default value is DSN. If the value in this field is something other than DSN, it was changed during installation to name the correct Db2
subsystem.
Do not change the value to name another Db2 subsystem to which you might have access. IBM Z Decision Support must use the Db2
subsystem that contains its system, control, and data tables.

def_db2plan Db2 plan name for TDS DRLPLAN

The Db2 plan name to which the distributed IBM Z Decision Support for z/OS DBRM has been bound.
This required field can be 8 alphanumeric characters. The first character must be alphabetic.
The default value for this field is DRLPLAN. If the value in this field is something other than DRLPLAN, it may have been changed during
installation to refer to a customized plan name forIBM Z Decision Support .
Only change the plan name shown here if instructed to do so by your IBM Z Decision Support system administrator.

def_dbname Database name DRLDB

The Db2 database that contains all IBM Z Decision Support system, control, and data tables. The value of this field is set during
installation.
This required field can be up to 8 alphanumeric characters. The first character must be alphabetic. The value of this field depends on the
naming conventions at your site.
The default database is DRLDB. If this value is something other than DRLDB, it is likely the default value for your site.
Do not change this name to identify another Db2 database to which you have access. You must use the Db2 database that contains IBM Z
Decision Support.

def_storgrp Storage group default DRLSG

The storage group that IBM Z Decision Support uses for the Db2 database identified in the Database name field.
This required field can be 8 alphanumeric characters. The first character must be alphabetic.
The default is DRLSG. If the value of the field is something other than DRLSG, it was changed during installation.
Do not change the value of this field to another storage group to which you might have access; IBM Z Decision Support uses the value of
this field to create new tables.

def_syspref Prefix for system tables DRLSYS

The prefix of all IBM Z Decision Support system and control Db2 tables. The value of this field depends upon your naming conventions and
is determined during installation.
This required field can be 8 alphanumeric characters. The first character must be alphabetic.
The default is DRLSYS. If the value is something other than DRLSYS, it was changed during installation.
Do not change the value; IBM Z Decision Support uses this value to access its system tables.

def_othtbpfx Prefix for all other tables DRL

64 IBM Z Decision Support : Administration Guide and Reference

 Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

The prefix of IBM Z Decision Support data tables in the Db2 database.
Valid values are determined at installation.
This required field can be 8 alphanumeric characters. The first character must be alphabetic.
The default is DRL. If the value is something other than DRL, it was changed during installation.

def_drlshwid Show TDS environment data NO

Specifies whether or not to display the IBM Z Decision Support environment data in the main panels.
This required field can have a value of YES or NO.
The default value for this field is NO.

def_tsbpool Buffer pool for data BP0

The default buffer pool for IBM Z Decision Support table spaces. This field can have values from BP0 to BP49, from BP8K0 to BP8K9,
from BP16K0 to BP16K9, from BP32K to BP32K9. The buffer pool implicitly determines the page size. The buffer pools BP0, BP1, ..., BP49
hold 4-KB pages. The buffer pools BP8K0, BP8K1, ..., BP8K9 hold 8-KB pages. The buffer pools BP16K0, BP16K1, ..., BP16K9 hold 16-KB
pages. The buffer pools BP32K, BP32K1, ..., BP32K9 hold 32-KB pages.

def_ixbpool Buffer pool for indexes BP0

The default buffer pool for IBM Z Decision Support indexes. This field can have values from BP0 to BP49 (The buffer pool for indexes must
identify a 4-KB buffer pool).

def_lobbpool Buffer pool for LOBB tables BP32K

The default buffer pool for IBM Z Decision Support LOBB data sets. The default is a 32K buffer pool.

def_iduser1 Users to grant access to DRLUSER

The user IDs or group IDs of users who are granted Db2 access to the next component you install. Users or user groups with Db2 access to
a component have access to the tables and views of the component. You can specify up to 8 users or group IDs in these fields.
You must specify a value for at least one of the fields.
Each user ID or group ID can be 8 alphanumeric characters. The first character must not be numeric.
The default is DRLUSER, as shipped by IBM. You can use any user group ID that is valid for your Db2 system. You should use one such
group ID to define a list of core IBM Z Decision Support users (who might include yourself). It is a good idea to leave such a core group as
the value in one of the fields, regardless of whether you control user access to various components by adding other group IDs.
You can grant users access to the tables and views of a component by listing them here before you install the component.
Consider using RACF group IDs or Db2 secondary authorization IDs and specifying them in these fields before installing a component. It is
easier to connect individual user IDs to an authorized group than it is to grant each individual access to each table or view that they need.

def_idsqlusr SQL ID to use (in QMF) DRLUSER

This field is used only if your installation uses QMF.

The Db2 primary or secondary authorization ID to which you are connected. IBM Z Decision Support uses the value of this field in the SET
CURRENT SQLID as it starts QMF. The ID must have Db2 authorization to IBM Z Decision Support tables and views.
This required field can be up to 8 alphanumeric characters. The first character must be alphabetic.
The default is DRLUSER. If the value is something other than DRLUSER, it was changed during installation.
You can change this value to your user ID if you have Db2 authorization to IBM Z Decision Support tables and views.

def_qmflng QMF language PROMPTED

The QMF language for creating reports and queries, either SQL (structured query language) or PROMPTED QUERY.
PROMPTED QUERY is the default QMF language for IBM Z Decision Support.
This is a required field, if your installation uses QMF.

def_qmfprt SYSOUT class (in QMF) Q

The SYSOUT class for report data sets that QMF generates, or for output that QMF routes to a printer. The default value is Q.
This is a required field, if your installation uses QMF.

def_printer Default printer blank

Chapter 3. Installation reference 65

Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

The GDDM nickname of a printer to use for printing graphic reports. The printer should be one capable of printing GDDM-based graphics.
The printer name must be defined in the GDDM nicknames file, allocated to the ADMDEFS ddname. Refer to QMF: Reference and GDDM
User's Guide for more information about defining GDDM nicknames.

def_drlprt Batch print SYSOUT class A

This field is used only if your installation does not use QMF.
A valid SYSOUT class for printing tabular reports in batch. Valid values are A-Z, 0-9, and *.

def_pagelen Printer line count per page 60

This field is used only if your installation does not use QMF.
The number of report lines that should be printed on each page when you print tabular reports online and in batch.

def_drlmax SQLMAX value 5000

The maximum number of rows for any single retrieval from an IBM Z Decision Support table when using an IBM Z Decision Support-Db2
interface for such functions as listing tables, reports, or log definitions.
The value of this required field is the maximum allowed size of the IBM Z Decision Support Db2 table to be retrieved. The default value is
5000 rows of data.

def_rptdialg Reporting dialog mode 1

The dialog mode for using the reporting dialog. Any option you save applies to future sessions.
You can choose administrator mode to access reports belonging to all users if you have an IBM Z Decision Support administrator authority.
You can choose end-user mode to access reports that you have created or that have been created for you (including public reports).
Type 1 to use end-user mode or 2 to specify administrator mode. If you leave the field blank, the default is end-user mode.

N/A Dialog language 1

The language in which IBM Z Decision Support displays all its windows.
IBM Z Decision Support supports those languages listed in the window. Choose the language your site has installed.
If you leave this field blank, IBM Z Decision Support displays its windows in English.
Any changes you make to this field become effective in your next dialog session, when IBM Z Decision Support allocates its libraries.

def_db2dspfx Db2 data sets-prefix DSN710

The prefix to which IBM Z Decision Support appends Db2 data set names as it performs tasks.
This field is required if db2def is SUFFIX. If db2def is DATASET, this field is ignored.
This field can be 35 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
The default is DB2.V810. If the value of this field is something other than DB2.V810, it was changed during installation.
Any changes you make to this field become effective in your next session, when IBM Z Decision Support allocates Db2 libraries and data
sets.

Db2 data sets-suffix def_db2dssfx blank

The suffix that IBM Z Decision Support appends as the low-level qualifier for Db2 data sets that IBM Z Decision Supportuses. Most sites do
not use a Db2 data set suffix, but this depends on your Db2 naming conventions.
This field can be used if db2def is SUFFIX. If db2def is DATASET, this field is ignored.
This field can be 35 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
Your IBM Z Decision Support administrator can set a default value for this field if it is in use at your site. If the field is blank, it is very likely
not in use.
Do not use this field to qualify data sets that you create; this is not its purpose. Use it to identify Db2 modules only.
Any changes you make to this field are not effective until your next invocation of the dialog, when IBM Z Decision Support has a chance to
reallocate Db2 libraries and data.

66 IBM Z Decision Support : Administration Guide and Reference

 Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

def_qmfdspfx QMF data sets prefix QMF710

This field is used only if your installation uses QMF. The prefix to which IBM Z Decision Support appends all QMF data set names. This
includes all QMF libraries allocated by the dialog during invocation. It also includes all QMF queries and forms.
If qmfdef is SUFFIX, this field is required. If qmfdef is DATASET, this field is ignored.
This field can be up to 35 alphanumeric characters. Names longer than 8 characters must be in groups of not more than 8 characters,
separated by periods. The first character of each group must be alphabetic.
The default is DB2.V810. If the value is something other than DB2.V810, it was changed during installation.
Do not use this value to identify your personal QMF data sets. IBM Z Decision Support uses this value for all QMF data sets.
Any changes you make to this field become effective in your next session, whenIBM Z Decision Support allocates its libraries.

def_dsnpref IBM Z Decision Support data DRL190

sets prefix

The prefix of IBM Z Decision Support libraries.

This required field can be up to 35 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
The default is DRL190. If the value of this field is something other than DRL190, it was changed during installation.
Any changes you make to this field become effective in your next session, when IBM Z Decision Support allocates its libraries.

No equivalent Temporary data sets prefix user_ID

The prefix for any temporary data sets you create while using IBM Z Decision Support.
This required field can be up to 35 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
The default value is your user_ID or the TSO_prefix.user_ID.

def_dsnlocdn Local definitions data set DRL.LOCAL.DEFS

The partitioned data set (PDS) that contains definitions of IBM Z Decision Support objects you have created. The value of this field depends
on naming conventions that apply to IBM Z Decision Support.
The members of this PDS contain definition statements that define new objects to IBM Z Decision Support. IBM Z Decision Support uses
the value of this field to locate local definition members.
This optional field can be 44 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
The default PDS is DRL.LOCAL.DEFS. Your administrator can set a different default for this field during installation. Do not change the value
that your IBM Z Decision Support administrator sets.
Any changes you make to this field are not effective until you start the dialog again, when IBM Z Decision Support reallocates local
definition data sets.

def_usrlocdn Local User alter/definitions data DRL.LOCAL.USER.DEFS

set

The partitioned data set (PDS) that contains definitions of IBM Z Decision Support objects you have modified. The value of this field
depends on naming conventions that apply to IBM Z Decision Support.
The members of this PDS contain definition statements that define user modified objects to IBM Z Decision Support. This PDS also
contains members with alter statements built by the update processor on the definitions contained in the same PDS. IBM Z Decision
Support uses the value of this field to locate local user definition members.
This optional field can be 44 alphanumeric characters. Names longer than 8 characters must be in groups of not more than 8 characters,
separated by periods. The first character of each group must be alphabetic.
The default PDS is DRL.LOCAL.USER.DEFS. Your administrator can set a different default for this field during installation. Do not change the
value that your IBM Z Decision Support administrator sets.
Any changes you make to this field are not effective until you start the dialog again, when IBM Z Decision Support reallocates local
definition data sets.

def_modform The local GDDM formats data set DRL.LOCAL. ADMCFORM

Chapter 3. Installation reference 67

Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

The data set where you keep your GDDM formats for graphic reports.

def_drlmsgs Local messages data set DRL.LOCAL.MESSAGES

Use this field to identify a PDS that contains messages generated by users during communication with IBM Z Decision Support
administrators.
The value of this field depends on naming conventions that your IBM Z Decision Support administrator has established.
This required field can be up to 44 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
Any changes you make to this field are not effective until you start the dialog again, when IBM Z Decision Support reallocates the message
data set.

def_dsnreprt Saved reports data set DRL.LOCAL.REPORTS

The PDS where IBM Z Decision Support saves your tabular reports.
This optional field can be up to 44 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
The default PDS is DRL.LOCAL.REPORTS.

def_dsnchrts Saved charts data set DRL.LOCAL.CHARTS

The PDS where IBM Z Decision Support saves the graphic reports you choose to save.
This optional field can be up to 44 alphanumeric characters.
Names longer than 8 characters must be in groups of not more than 8 characters, separated by periods. The first character of each group
must be alphabetic.
The default PDS is DRL.LOCAL.ADMGDF.

def_jclsta1, def_jclsta2, Job statement information Sample job card in which IBM
def_jclsta3, def_jclsta4 (required for batch jobs) Z Decision Support dynamically
substitutes the user ID.

The job statement information to be used for batch jobs that the dialogs create for you.
You must use correct JCL in the job statement. IBM Z Decision Support does not validate job statement information.
Do not use JCL comments in these JCL statements.
You can specify up to four card images in these job statement fields.
The first "//" card image should contain the job name. Press Enter to save any job statements for all future sessions.

drl1sh00 N/A IBMBK.DRL1SH00. BKSHELF

dsnsufx N/A SDRLDEFS

The IBM Z Decision Support definitions data set suffix.

execsfx N/A SDRLEXEC

The IBM Z Decision Support exec data set suffix.

loadsfx N/A SDRLLOAD

The IBM Z Decision Support load library suffix.

skelsfx N/A SDRLSKEL

The IBM Z Decision Support skeleton data set suffix.

eng_lib_sfx N/A ENU

The English library suffix.

jpn_lib_sfx N/A JPN

The Japanese library suffix.

68 IBM Z Decision Support : Administration Guide and Reference

 Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

def_nlslang N/A eng_lib_sfx

The national language library suffix.

repsufx N/A "SDRLR"+def_nlslang

The IBM Z Decision Support report definitions library suffix.

plibsfx N/A "SDRLP"+def_nlslang

The IBM Z Decision Support panel library suffix.

messsfx N/A "SDRLM"+def_nlslang

The IBM Z Decision Support message library suffix.

formsfx N/A "SDRLF"+def_nlslang

The IBM Z Decision Support GDDM formats library suffix.

eng_qmf_sfx N/A E

The English library suffix.

jpn_qmf_sfx N/A K

The Kanji-Japanese library suffix.

def_qmflang N/A eng_qmf_sfx

The national language default library suffix.

qmfdef N/A SUFFIX

The method of describing QMF library names to IBM Z Decision Support, either SUFFIX or DATASET.
If qmfdef is SUFFIX (the default), IBM Z Decision Support implements the QMF library naming standard, requiring a prefix for QMF data
sets (def_qmfdspfx) and a suffix (described below). IBM Z Decision Support appends each suffix to the QMF prefix to identify QMF libraries,
which it then allocates.
If qmfdef is DATASET, IBM Z Decision Support does not use a prefix or suffix and you must specify fully-qualified data set names for the
QMF library variables described below.
In either case, IBM Z Decision Support uses the next several variables to allocate QMF libraries.

qmfclib N/A SDSQCLST+def_qmflang

The QMF CLIST library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfclibe N/A SDSQCLST+eng_qmf_sfx

The English QMF CLIST library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision
Supportappends to def_qmfdspfx. IBM Z Decision Support requires this library even though you might be using another language.

qmfelib N/A SDSQEXEC+def_qmflang

The QMF EXEC library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfelibe N/A SDSQEXEC+eng_qmf_sfx

The English QMF EXEC library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision
Support appends to def_qmfdspfx. IBM Z Decision Support requires this library even though you might be using another language.

qmfplib N/A SDSQPLIB+def_qmflang

The QMF panel library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfmlib N/A SDSQMLIB+def_qmflang

The QMF message library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfslib N/A SDSQSLIB+def_qmflang

Chapter 3. Installation reference 69

Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

The QMF skeleton library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfmap N/A SDSQMAP+def_qmflang

The ADMGGMAP library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfpnl N/A DSQPNL+def_qmflang

The QMF panel library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

dsqpnl N/A DSQPNL+def_qmflang

The ddname of QMF DSQPNLx library. Even if you use fully-qualified data set names to identify QMF data sets, you must specify the
ddname of your DSQPNLx library as the value of this variable.

qmfload N/A SDSQLOAD

The QMF load library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfchart N/A DSQCHART

The ADMCFORM library, which (depending on the value of qmfdef), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_qmfdspfx.

qmfdsdum N/A DUMMY

The fully-qualified name of the data set to be allocated to ddname DSQUDUMP, or DUMMY.

qmfdebug N/A DUMMY

The fully-qualified name of the data set to be allocated to ddname DSQDEBUG, or DUMMY.

dsunit N/A SYSDA

The disk unit.

db2ver N/A 10

The version of Db2. Must be a decimal number 1-99.

db2rel N/A 1

The release of Db2.

db2def N/A SUFFIX

The method of describing Db2 library names to IBM Z Decision Support, either SUFFIX or DATASET.
If db2def is SUFFIX (the default), IBM Z Decision Support implements the Db2 library naming standard, requiring a prefix for Db2 data sets
(def_db2dspfx), a library name, and an optional suffix (def_db2dssfx).
If db2def is DATASET, IBM Z Decision Support does not use a prefix or a suffix and you must specify fully-qualified data set names for the
Db2 library variables described below.
In either case, IBM Z Decision Support uses the next several variables to allocate Db2 libraries.

db2llib N/A RUNLIB.LOAD

The Db2 runlib load library name, which (depending on the value of db2def), is the fully-qualified name or is a value that IBM Z Decision
Support appends to def_db2dspfx before appending def_db2dssfx.

db2load N/A SDSNLOAD

The Db2 load library, which (depending on the value of db2def), is the fully-qualified name or is a value that IBM Z Decision
Supportappends to def_db2dspfx before appending def_db2dssfx.

db2exit N/A SDSNEXIT

The customized Db2 load library for your Db2 system. The parameter must be the fully qualified name of your SDSNEXIT data set.

db2clst N/A SDSNCLIST

The Db2 CLIST library, which (depending on the value of db2def), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_db2dspfx before appending def_db2dssfx.

70 IBM Z Decision Support : Administration Guide and Reference

 Dialog parameters - variables and fields

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

db2mlib N/A SDSNSPFM

The Db2 message library, which (depending on the value of db2def), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_db2dspfx before appending def_db2dssfx.

db2plib N/A SDSNSPFP

The Db2 panel library, which (depending on the value of db2def), is the fully-qualified name or is a value that IBM Z Decision Support
appends to def_db2dspfx before appending def_db2dssfx.

gddmload N/A GDDM.SADMMOD

The GDDM load library.

admsymbl N/A GDDM.SADMSYM

The GDDM symbols library.

admdefs N/A SYS1.GDDMNICK

The GDDM nicknames library.

admprntq N/A None

The data set name of the GDDM master print queue, if any. This overrides any value specified for TSOPRNT in the GDDM external defaults
file. If you supply a value, IBM Z Decision Support adds an ADMPRNTQ DD statement to the batch JCL for graphic reports.

def_geapplid N/A zuser

The application ID (usually sent as a TSO user ID) that has an assigned Information/Management privilege class. The default is the user ID
of the IBM Z Decision Support user.

def_gesessn N/A BLGSES00

The session member (module) used to start an Information/Management session.

def_geprivcl N/A MASTER

qmfuse N/A YES

Specifies if QMF is used with IBM Z Decision Support in your installation. Any other value than YES or NO causes IBM Z Decision Support to
use YES.

gddmuse N/A YES

Specifies if GDDM is used with IBM Z Decision Support in your installation. (If QMF is used, GDDM must be used.) If GDDM is not used,
reports are always shown in tabular format. Any other value than YES or NO causes IBM Z Decision Support to use YES.

decsep N/A PERIOD

When generating tabular reports without QMF, IBM Z Decision Support uses period as decimal separator and comma as thousands
separator. You can exchange the decimal and thousands separators by specifying decsep="COMMA". In that case, period is used as
thousands separator. Any other value of decsep causes IBM Z Decision Support to use period as a decimal separator.

subhdrv N/A N

This value is used only for QMF (where qmfuse='YES'). Specify Y if you want IBM Z Decision Support to replace empty variables in the
report header with a text string. You specify the text string using F11 on the Data Selection panel, or when you get message DRLA171.
Note: Replacing empty variables increases the time taken to generate a report.
Specify N to leave the empty variable in the report.

def_useaot N/A NO

Specifies whether Analytics component tables are created as Accelerator Only Tables in IBM Db2 Analytics Accelerator or as tables in Db2.
"YES": Tables are created as Accelerator Only Tables.
"NO": Tables are created in Db2 and are applicable for use either as Db2 tables or as IDAA_ONLY table.
The default value is "NO".
This parameter is only applicable for Analytics components.

def_accelerator N/A

Chapter 3. Installation reference 71

Allocation overview

userid.DRLFPROF variable Dialog Parameters field name Default value Your value
name

The name of the Accelerator where the Analytics components tables reside. Required only if using Accelerator Only Tables, that is, if
def_useaot is set to "YES".
This parameter is only applicable for Analytics components.

def_timeint N/A T

Specifies the time interval granularity for records collected for Analytics components tables.
"H": The timestamp for records is rounded to hourly intervals, which is similar to non-Analytics tables with a suffix of "_H" in other
components.
"S": The timestamp for records is rounded to intervals of a second, which is similar to non-Analytics tables with time field instead of
timestamp in other components.
"T": The timestamp for tables is the actual timestamp in the SMF log record, which is similar to non-Analytics tables with suffix "_T".
The default value is "T".
This parameter is only applicable for Analytics components.

drl_grant N/A YES

When installing components, this variable specifies if SQL GRANTs are issued. When set to "NO" the pre-processor will replace the SQL
GRANT with a comment stating that the GRANT has been omitted.

Allocation overview
This section describes the data sets allocated by IBM Z Decision Support .

Library type or data set Library or data set Allocated by

ddname (EPDM exec)
IBM Z Decision Support allocates the following libraries as a user starts an IBM Z Decision Support dialog:
ISPPLIB • IBM Z Decision Support panel library DRLEINI1
• QMF panel library
• Db2 panel library

ISPTLIB • IBM Z Decision Support tables library DRLEINI1

• QMF tables library

ISPMLIB • IBM Z Decision Support message library DRLEINI1

• QMF message library
• Db2 message library

ISPLLIB • IBM Z Decision Support load library DRLEINI1

• QMF load library

ISPSLIB • IBM Z Decision Support skeleton library DRLEINI1

• QMF skeleton library

IBM Z Decision Support allocates the following data sets as a user starts an IBM Z Decision Support dialog:
DRLTABL Userprefix.DRLTABL (for values in query variables) DRLEINI1
ADMGDF Saved charts data set DRLEINI1
DRLMSGDD IBM Z Decision Support user message data set (drlmsgs) DRLEINI1
IBM Z Decision Support allocates the following libraries as a user starts an IBM Z Decision Support function that uses
QMF:
SYSPROC QMF CLIST library (def_qmfdspfx.qmfclib+E) DRLEQMF
SYSEXEC QMF exec library (def_qmfdspfx.qmfelib+E) DRLEQMF

72 IBM Z Decision Support : Administration Guide and Reference

 Allocation overview

Library type or data set Library or data set Allocated by

ddname (EPDM exec)
ADMGGMAP SDSQMAP library (def_qmfdspfx.qmfmap) DRLEQMF
ADMCFORM Saved forms data set + DSQCHART library (dsnpref.formsfx + DRLEQMF
def_qmfdspfx.qmfchart)
DSQUCFRM Saved forms data set DRLEQMF
DSQPNLE QMF panel library DRLEQMF
DSQPRINT QMF sysout class (qmfprt) DRLEQMF
DSQSPILL NEW DELETE (temporary file allocation) DRLEQMF
DSQEDIT NEW DELETE (temporary file allocation) DRLEQMF
DSQDEBUG (qmfdebug) DRLEQMF
DSQUDUMP (qmfdsdum) DRLEQMF
IBM Z Decision Support allocates the following library as a user starts an IBM Z Decision Support function that uses
GDDM:
ADMSYMBL GDDM symbols data set DRLEINI1
IBM Z Decision Support allocates the following libraries when a table or report is displayed without QMF:
DRLTAB Userprefix.DRLTAB (for table display) DRLEADIT
DRLREP Userprefix.DRLREP (for report display) DRLERDIR
IBM Z Decision Support allocates the following library as a user starts Db2 Interactive (DB2I) from IBM Z Decision
Support:
SYSPROC Db2 CLIST library (db2dspfx.db2clst) DRLEDB2I

Overview of IBM Z Decision Support objects

This section describes how a feature definition member is used to update system tables. It then describes
how IBM Z Decision Support uses the resulting component definitions to install a component's objects.
There is also a section on how to create and change definitions in both the dialog and log collector
language.
For more information about the log collector language and report definition language statements, see the
Language Guide and Reference.
This topic uses the Sample component as the basis of most of its examples. For more information, see
“Sample component” on page 230.
For information on the naming convention for IBM Z Decision Support definition members, see “Naming
convention for IBM Z Decision Support definition members” on page 80.

IBM Z Decision Support component installation

Component installation starts with the SMP/E installation of the definition members of a feature in the
DRL190.SDRLDEFS library. IBM Z Decision Support features provide definition members that update the
system tables with information about the definitions in a feature.

Defining definition library members with SQL

Before installing TDS for z/OS components, you must create or update the system tables. When you do
this from the dialog or in batch, the DRLIxxxx members, in the DRL190.SDRLDEFS library, contain SQL
statements that are executed.
Figure 23 on page 74 shows the DRLIxxxx definition member for the Sample component. These
members use the SQL log collector language statement to pass an SQL statement to Db2.

Chapter 3. Installation reference 73

Allocation overview

/**********************************************************************/
/* Sample Component */
/**********************************************************************/
SQL INSERT INTO &SYSPREFIX.DRLCOMPONENTS
(COMPONENT_NAME, DESCRIPTION, USER_ID)
VALUES('SAMPLE','Sample Component',USER);
/**********************************************************************/
/* Log and record definitions */
/**********************************************************************/
SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS
(COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME)
VALUES('SAMPLE','LOG ','SAMPLE','DRLLSAMP');
⋮
/**********************************************************************/
/* Table space, table, and update definitions */
/**********************************************************************/
SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS
(COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME)
VALUES('SAMPLE','TABSPACE','DRLSSAMP','DRLSSAMP');
⋮
/**********************************************************************/
/* Report and report group definitions */
/**********************************************************************/
SQL INSERT INTO &SYSPREFIX.DRLCOMP_OBJECTS
(COMPONENT_NAME, OBJECT_TYPE, OBJECT_NAME, MEMBER_NAME)
VALUES('SAMPLE','REPGROUP','SAMPLE','DRLOSAMP');
⋮

Figure 23. IBM Z Decision Support definition member DRLISAMP, setting component definitions

Executing these statements populates the IBM Z Decision Support system tables with component
definitions. These component definitions describe the installable components and the SDRLDEFS
members that can be used to install the component.

How IBM Z Decision Support controls object replacement

Once the system tables have been updated with the installation members, you must reinstall all affected
components in order to replace all objects. Each component installed is controlled by a variable VERSION
which is specified in the DEFINE statements and a corresponding column VERSION is included in the IBM
Z Decision Support system tables where objects are defined.
During the installation of the IBM Z Decision Support components, a preprocessor checks each definition
member to see if an object already exists (from the installation of an earlier level of the component).
If the object does not already exist, the DEFINE statement for this object is passed to the log collector.
If the object does already exist, and providing the variable VERSION is specified in the DEFINE statement
for the object, then the values of VERSION in the DEFINE statement and in the system table where
the object is defined, are compared. If the values of VERSION are the same, the log collector replaces
theDEFINE statement for the object with a comment, saying that the most recent version of the object
already exists in the system table. If the values of VERSION are different, the log collector inserts an
DROP statement. This DROP statement drops the object so that it can be redefined.
Note: IBM Z Decision Support only checks the VERSION variable when you install using option 2
Components.
All log, record, record procedure, and update objects shipped with the product contain the VERSION
variable, which takes the value: IBM.vrm
where vrm corresponds to the product version. For example, IBM.190 indicates objects created or
modified by IBM Z Decision Support 1.9.0. If an object is modified by an APAR, then the APAR number is
used as the VERSION variable, for example, VERSION 'PH10636'.

IBM Z Decision Support Version variable format

All IBM Z Decision Support log, record, record procedure, and update objects shipped with the product
contain the VERSION variable, which takes the value IBM.vrm, where vrm corresponds to the product
version. For example IBM.190 indicates objects created or modified by IBM Z Decision Support 1.9.0.

74 IBM Z Decision Support : Administration Guide and Reference

 Allocation overview

If an object is modified by an APAR, then the APAR number is used as the VERSION variable, for example,
VERSION 'PH10636.190'.
IBM Z Decision Support recognizes the following version variable patterns as being standard objects
shipped by the product:
• Version numbers beginning with 'IBM'.
• Version numbers with no text (the empty string or no version clause).
• Version numbers beginning with an APAR number, that is, two letters followed by any number of
digits up to an optional decimal point. For example, the version numbers PM123, PX123456.V190,
RW987654, and OK123.2014101, are all considered 'standard' version numbers, but PK1234A and
MXC1234 are not.

Custom Version numbers:

When customizing IBM Z Decision Support objects (see “Controlling objects that you have modified” on
page 129) you must choose a version number which does not conform to the standards above. A version
number might be 'ALTERED' or 'MODIFIED', or your own version system such as 'C.V2'.

How IBM Z Decision Support determines installation order

After IBM Z Decision Support stores the names of a feature's component objects and definition
members in the system tables, you can use the dialog to install the feature's components. The product
queries the system tables to determine the names of definition members in the DRL190.SDRLDEFS,
DRL190.SDRLRxxx, and DRL190.SDRLFxxx libraries. (xxx is ENU for the English language version of IBM Z
Decision Support.
IBM Z Decision Support requires some definitions to exist before it can install others. For example, if a
component contains a record procedure, The product must install the record definition that maps the
source record for the record procedure before installing the record procedure. Furthermore, it must install
the record procedure before installing the record definition that maps the record procedure's output. The
definition members that are supplied by the product supplies often combine several definitions in the
same member to ensure their order of installation.
Table 5 on page 75 shows the order in which IBM Z Decision Support installs a feature's definitions.

Table 5. Order of installation of feature definition members

Order Member naming Definition types
convention
1 DRLLxxxx Logs.
2 DRLRxxxx Records and record procedures. Record definitions mapping record procedure input
must appear before the associated record procedure definition. Record definitions
mapping record procedure output must appear after the associated record procedure
definition.
3 DRLSxxxx Table spaces.
4 DRLTxxxx Lookup tables, tables, updates, and views. Lookup tables and tables must be defined
before update definitions that refer to them. Tables must also be defined before views
that refer to them.
5 DRLUxxxx Updates (also found in DRLTxxxx members).
6 DRLVxxxx Views (also found in DRLTxxxx members).
7 DRLOxxxx Report groups and reports. Report groups must be defined before the report definitions
that reference them.

The order of installation within a definition type is determined by the sort sequence of the definition
member names. The examples that follow appear in the same order that IBM Z Decision Support would
install them.

Chapter 3. Installation reference 75

Allocation overview

Defining logs with log collector language

DRLLxxxx members of the DRL190.SDRLDEFS library define log types to IBM Z Decision Support. Figure
24 on page 76 shows the definition member for the SAMPLE log type.

DEFINE LOG SAMPLE VERSION 'IBM.110';

COMMENT ON LOG SAMPLE IS 'Sample log definition';

Figure 24. IBM Z Decision Support definition member DRLLSAMP, defining a log type

Defining records with log collector language

DRLRxxxx members of the DRL190.SDRLDEFS library define record types to IBM Z Decision Support.
Figure 25 on page 76 shows the definition for the SAMPLE_01 record type. (“Record definitions supplied
with IBM Z Decision Support” on page 235 describes IBM Z Decision Support record definitions.)

DEFINE RECORD SAMPLE_01

VERSION 'IBM.110'
IN LOG SAMPLE
IDENTIFIED BY S01TYPE = '01'
FIELDS
(S01TYPE OFFSET 4 LENGTH 2 CHAR,
S01DATE OFFSET 7 DATE(MMDDYY),
S01TIME OFFSET 14 TIME(HHMMSS),
S01SYST OFFSET 21 LENGTH 4 CHAR,
S01USER OFFSET 26 LENGTH 8 CHAR,
S01TRNS OFFSET 35 LENGTH 6 EXTERNAL INTEGER,
S01RESP OFFSET 42 LENGTH 6 EXTERNAL INTEGER,
S01CPU OFFSET 49 LENGTH 6 EXTERNAL INTEGER,
S01PRNT OFFSET 56 LENGTH 6 EXTERNAL INTEGER);

COMMENT ON RECORD SAMPLE_01 IS 'Sample record type 01';

Figure 25. IBM Z Decision Support definition member DRLRSAMP, defining a record type

Defining table spaces

DRLSxxxx members of the definition library SDRLDEFS define table spaces to IBM Z Decision Support.
At least one table space is defined per component to contain the tables in the component.
Table spaces can be defined explicitly using SQL statements. Alternatively, the Log Collector Language
statement GENERATE TABLESPACE may be used to create table spaces, which use values in the
GENERATE_PROFILES and GENERATE_KEYS system tables to determine the partitioning type. Using the
GENERATE statement eliminates the need to change the DRLSxxxx members, and allows multiple table
spaces to be configured in the same manner.
The following figure shows the definition for the DRLSSAMP table space of the IBM Z Decision Support
Sample component.

SQL CREATE TABLESPACE DRLSSAMP

IN &DATABASE
USING STOGROUP &STOGROUP
PRIQTY 60
SECQTY 30
SEGSIZE 8
BUFFERPOOL &TSBUFFERPOOL
LOCKSIZE TABLE;

Figure 26. Using SQL to define a table space (see definition member DRLSSAMP)

The following figure shows the definition for the DRLSKZJ1 table space of the z/OS Key Performance
Metrics component.

76 IBM Z Decision Support : Administration Guide and Reference

 Allocation overview

GENERATE TABLESPACE DRLSKZJ1

PROFILE 'SMF';

Figure 27. Using GENERATE to define a table space (see definition member DRLSKZJB)

Defining tables and updates

DRLTxxxx members of the DRL190.SDRLDEFS library define tables and updates to IBM Z Decision
Support.
These members use the SQL log collector language statement to create tables in the database, populate
lookup tables, and grant access to the tables. They also use the DEFINE UPDATE log collector language
statement to create update definitions in the system tables. The following example shows the definition
for tables (that includes the lookup table) and updates of the Sample component, DRLTSAMP. “Definition
member DRLTSAMP, defining tables and updates (using SQL)” on page 77 uses the SQL log collector
language statement and “Definition member DRLTSAMP, defining tables and updates (using DEFINE
UPDATE)” on page 78 uses the DEFINE UPDATE log collector language statement.
Definition member DRLTSAMP, defining tables and updates (using SQL)

/**********************************************************************/
/* Define table SAMPLE_USER */
/**********************************************************************/
SQL CREATE TABLE &PREFIX.SAMPLE_USER
(USER_ID CHAR(8) NOT NULL,
DEPARTMENT_NAME CHAR(8) NOT NULL,

PRIMARY KEY (USER_ID))

IN &DATABASE.DRLSSAMP;

SQL CREATE UNIQUE INDEX &PREFIX.SAMPUSER_IX

ON &PREFIX.SAMPLE_USER
(USER_ID)
USING STOGROUP &STOGROUP.
PRIQTY 12
SECQTY 4
CLUSTER
BUFFERPOOL &IXBUFFERPOOL;
/**********************************************************************/
/* Define comments for SAMPLE_USER */
/**********************************************************************/
SQL COMMENT ON TABLE &PREFIX.SAMPLE_USER
IS 'This lookup table assigns department names to users.';

SQL COMMENT ON &PREFIX.SAMPLE_USER

(USER_ID IS 'User ID.',
DEPARTMENT_NAME IS 'Department name.');
/**********************************************************************/
/* Grant users read access to SAMPLE_USER */
/**********************************************************************/
SQL GRANT SELECT ON &PREFIX.SAMPLE_USER TO &USERS.;
/**********************************************************************/
/* Insert data in SAMPLE_USER */
/**********************************************************************/
SQL INSERT INTO &PREFIX.SAMPLE_USER
VALUES('ADAMS ','Appl Dev');
⋮
/**********************************************************************/
/* Define table SAMPLE_H */
/**********************************************************************/
SQL CREATE TABLE &PREFIX.SAMPLE_H
(DATE DATE NOT NULL,
TIME TIME NOT NULL,
SYSTEM_ID CHAR(4) NOT NULL,
DEPARTMENT_NAME CHAR(8) NOT NULL,
USER_ID CHAR(8) NOT NULL,
TRANSACTIONS INTEGER,
RESPONSE_SECONDS INTEGER,
CPU_SECONDS FLOAT,
PAGES_PRINTED INTEGER,
PRIMARY KEY (DATE, TIME, SYSTEM_ID, DEPARTMENT_NAME, USER_ID))
IN &DATABASE.DRLSSAMP;

Definition member DRLTSAMP, defining tables and updates (using DEFINE UPDATE)

Chapter 3. Installation reference 77

Allocation overview

⋮
/**********************************************************************/
/* Define update from record SAMPLE_01 */
/**********************************************************************/
DEFINE UPDATE SAMPLE_01_H
VERSION 'IBM.110'
FROM SAMPLE_01
TO &PREFIX.SAMPLE_H
GROUP BY
(DATE = S01DATE,
TIME = ROUND(S01TIME,1 HOUR),
SYSTEM_ID = S01SYST,
DEPARTMENT_NAME = VALUE(LOOKUP DEPARTMENT_NAME
IN &PREFIX.SAMPLE_USER
WHERE S01USER = USER_ID,
'?'),
USER_ID = S01USER)
SET
(TRANSACTIONS = SUM(S01TRNS),
RESPONSE_SECONDS = SUM(S01RESP),
CPU_SECONDS = SUM(S01CPU/100.0),
PAGES_PRINTED = SUM(S01PRNT));
⋮
/**********************************************************************/
/* Define update from SAMPLE_H */
/**********************************************************************/
DEFINE UPDATE SAMPLE_H_M
VERSION 'IBM.110'
FROM &PREFIX.SAMPLE_H
TO &PREFIX.SAMPLE_M
GROUP BY
(DATE = SUBSTR(CHAR(DATE),1,8) || '01',
SYSTEM_ID = SYSTEM_ID,
DEPARTMENT_NAME = DEPARTMENT_NAME,
USER_ID = USER_ID)
SET
(TRANSACTIONS = SUM(TRANSACTIONS),
RESPONSE_SECONDS = SUM(RESPONSE_SECONDS),
CPU_SECONDS = SUM(CPU_SECONDS),
PAGES_PRINTED = SUM(PAGES_PRINTED));

Defining updates and views

DRLUxxxx members of the DRL190.SDRLDEFS library define updates not previously defined in DRLTxxxx
definition members. For example, member DRLUMVAV in the DRL190.SDRLDEFS library defines updates
from record types SMF_030 and SMF_070 to the AVAILABILITY_T table.
DRLVxxxx members of the DRL190.SDRLDEFS library define views not previously defined in DRLTxxxx
definition members. For example, member DRLVC901 in the DRL190.SDRLDEFS library defines views on
the CICS_T_TRAN_T table for CICS unit-of-work processing.

Defining table spaces and indexes using the GENERATE statement

The GENERATE statement may be used to create table spaces, partitioning on tables, and indexes
on tables. The GENERATE statement has a PROFILE parameter which is the major key to the
GENERATE_PROFILES and GENERATE_KEYS system tables. All customization for creating table spaces,
partitioning, and indexes may be performed using these system tables. The definition member DRLTKEYS
is used to create and load the default values into the GENERATE_PROFILES and GENERATE_KEYS tables
when the system tables are created.
These system tables provide default profiles referenced by GENERATE statements in the supplied
definition members. The defaults may be changed by updating the data in these system tables without
modifying the GENERATE statements in the definition members. The profiles may be made more granular
by using the COMPONENT_ID, SUBCOMPONENT_ID or TABLESPACE_NAME key fields, with no changes
required to the product definition members.
When RANGE is specified in the TABLESPACE_TYPE column of the GENERATE_PROFILES table,
GENERATE statements referring to the profile will create range-partitioned table spaces. In this case, the
number of partitions created is determined by the number of entries for the key in the GENERATE_KEYS
system table. For example, the supplied profile of IMS has PART_NUM 1-4 which will generate four

78 IBM Z Decision Support : Administration Guide and Reference

 Allocation overview

partitions. This number of key entries can be increased or decreased to generate the required number of
partitions. Changing the number of partitions does not require a change to the GENERATE statement in
the IBM Z Decision Support definition members.

Defining reports
DRLOxxxx members of the DRL190.SDRLRENU library use report definition language to define report
groups and reports in IBM Z Decision Support system tables. Report definition members are contained in
national language-specific definition libraries.
Figure 28 on page 79 shows the definition for the reports and report group of the Sample component.

DEFINE GROUP SAMPLE

VERSION 'IBM.110'
DESC 'Sample Reports';

DEFINE REPORT SAMPLE01

VERSION 'IBM.110'
DESC 'Sample Report 1'
QUERY DRLQSA01
FORM DRLFSA01
CHART DRLGSURF
ATTRIBUTES SAMPLE
GROUPS SAMPLE;

DEFINE REPORT SAMPLE02

VERSION 'IBM.110'
DESC 'Sample Report 2'
QUERY DRLQSA02
FORM DRLFSA02
ATTRIBUTES SAMPLE
GROUPS SAMPLE;

DEFINE REPORT SAMPLE03

VERSION 'IBM.110'
DESC 'Sample Report 3'
QUERY DRLQSA03
FORM DRLFSA03
CHART DRLGHORB
ATTRIBUTES SAMPLE
GROUPS SAMPLE;

Figure 28. IBM Z Decision Support definition member DRLOSAMP, defining reports and report groups

The IBM Z Decision Support report definition program uses the definitions in DRLOxxxx members to
locate these types of members for each report:
Member type
Description
DRLQxxxx
Report queries in DRL190.SDRLRxxx
DRLFxxxx
Report forms in DRL190.SDRLRxxx
DRLGxxxx
Report charts in DRL190.SDRLFxxx
where xxx refers to your national-language code (for example, ENU, JPN).
IBM Z Decision Support imports members in these data sets to QMF to provide queries and forms for
predefined reports. If QMF is not used, the contents of the report queries and forms are stored in IBM Z
Decision Support system tables.
DRLQxxxx members in the DRL190.SDRLRENU library are queries for predefined reports. Figure 29 on
page 80 shows the query for Sample Report 1.

Chapter 3. Installation reference 79

Naming convention for members of
DRL190.SDRLDEFS

SELECT TIME, DEPARTMENT_NAME, SUM(CPU_SECONDS)

FROM &PREFIX.SAMPLE_H
WHERE SYSTEM_ID = &SYSTEM_ID.
GROUP BY TIME, DEPARTMENT_NAME

Figure 29. IBM Z Decision Support definition member DRLQSA01, report query

DRLFxxxx members in the DRL190.SDRLRENU library are QMF forms for predefined English reports. For
example, DRLFSA01 is the QMF form for Sample Report 1.
DRLGxxxx members in the DRL190.SDRLFENU library are GDDM/ICU formats for predefined English
reports. For example, DRLGSURF is the GDDM/ICU format used for Sample Report 1.

Naming convention for IBM Z Decision Support definition members

This section describes the naming convention for members of the DRL190.SDRLDEFS and
DRL190.SDRLRENU libraries. For information on defining these libraries, see “Overview of IBM Z Decision
Support objects” on page 73.

Naming convention for members of DRLvrm.SDRLDEFS

The naming convention for the IBM Z Decision Support definitions library is:
Naming convention
Description
DRLBxxxx
Log data manager collect statements
DRLIxxxx
Component definitions (SQL statements that are executed when the system tables are created or
updated)
DRLLxxxx
Log definitions
DRLRxxxx
Record definitions “Record definitions supplied with IBM Z Decision Support” on page 235 describes
record definitions.
DRLSxxxx
Table space definitions
DRLTxxxx
Table and update definitions
DRLUxxxx
Update definitions (when separate from tables)
DRLVxxxx
View definitions
DRLWxxxx
Migration definitions

Naming convention for members of DRLVRM.SDRLRENU

The naming convention for the IBM Z Decision Support (predefined) reports definitions library, SDRLRENU
(or SDRLRJPN), is:
Naming convention
Description
DRLOxxxx
Report definitions

80 IBM Z Decision Support : Administration Guide and Reference

 Naming convention for members of
DRL190.SDRLRENU

DRLQxxxx
SQL queries
DRLFxxxx
QMF forms

Chapter 3. Installation reference 81

Naming convention for members of DRL190.SDRLRENU

82 IBM Z Decision Support : Administration Guide and Reference

Chapter 4. Administering IBM Z Decision Support

Extending the SMF extractor

The SMF Extractor can write multiple, concurrent streams of SMF records out to different log streams.
This section documents how to operate and configure the SMF Extractor from an IBM Z Decision Support
point of view. There are several parameters and concepts that are used with IBM Z Batch Resiliency
(IZBR) that are omitted from this documentation. Please review the IBM Z Batch Resiliency (IZBR)
documentation for information about these.

Configuration parameters
The following table lists the SMF Extractor Parameters that are relevant for IBM Z Decision Support users:

Parameter Default Range Description

OUTLGR= LSName None Valid log stream Name of the log stream files to write captured SMF
OUT1LGR= LSName1 name records to. Each OUT*LGR has its own SMF record
OUT2LGR= LSName2 filter, specified by the OUT*LREC parameters.
OUT3LGR= LSName3 At least one OUT*LGR parameter should be specified.
OUT4LGR= LSName4
OUT5LGR= LSName5
OUTLREC= n, x, y, z 14, 15, 30, 60, 0 to 255 or 0 to SMF Record types to be collected by each OUT*LGR.
OUT1LREC= n, x, y, z 61, 64, 65 2047 If not specified, then the values in the SMFREC
OUT2LREC= n, x, y, z parameter below are used.
OUT3LREC= n, x, y, z The syntax for the entries is the same as for the
OUT4LREC= n, x, y, z SMFREC parameter.
OUT5LREC= n, x, y, z
SMFREC= n, x, y, z 4, 15, 30, 60, 0 to 255 or 0 to SMF record types to be collected by the SMF
61, 63, 64 2047 Extractor.
• Each value must be a valid numeric from 0 to 255,
separated by a comma with no intervening blanks
– If the users are using the IEFU86 exit the
upper value is 2047 as it allows the capture of
extended SMF records.
• Alternatively, a range of values can be specified as
nnn:ppp, where nnn denotes the start of the range,
and ppp denotes the end of the range (for example,
60:64 specifies SMF record types 60 through 64,
inclusive).
• An SMF record type of asterisk (*) resets
all prior specified types (for example,
SMFREC=24,28,*,32,80:84 would result in only
SMF record types 32, 80, 81, 82, 83, and 84 being
captured).
If the user wants to specify more SMF types than can
fit on a single statement, specify multiple SMFREC
option statements (as many as necessary).

© Copyright IBM Corp. 1993, 2017 83

Parameter Default Range Description
LHDRS Y Y or N Specifying L1HDRS=N prevents LGRH headers from
L1HDRS being added to SMF records written to OUT1LGR log
L2HDRS stream.
L3HDRS
L4HDRS IBM Z Decision Support requires LGRH headers to be
L5HDRS written to the log streams for the Collector and the
DataSplitter.

Supported SMF record values

If the users are running with a traditional installation using the IEFU83, IEFU84 and IEFU85 exits, then
the SMF extractor supports capturing the traditional range of SMF records – 0 to 255.
If the users are running with IEFU86 enabled the SMF Extractor then Extended SMF records are also
available to be captured. The range of SMF values supported in these circumstances are from 0 thru
2047.

Default Configuration
If the users have followed the instructions in chapter 2, users will have configured the SMF Extractor
using only the SMFREC= and OUTLGR= parameters, with OUTLGR specifying the name of the log stream
to write the records to and SMFREC specify which SMF records to capture.

Configuring for multiple log stream output

If the users are going to make use of additional log stream outputs from the SMF Extractor to, for
example, stream some raw SMF records to an application, then the user needs to configure additional
output streams.
The example scenario we are going to use here is that the SMF extractor is currently capturing SMF 30
and 70 thru 79 for IBM Z Decision Support and we want to add a second log stream to capture SMF 80
thru 83 records.

The default configuration for this scenario would be:

*
* Output log stream for IZDS COLLECTOR
*
OUTLGR=MY.IZDS.LOG.STREAM
*
* IZDS wants SMF 30 and SMF 70 thru 79
SMFREC=30,70:79

To get the SMF Extractor to write output to multiple log streams the users need to first define the log
streams (as DASD log streams) and add an OUT*LGR statement for each of them. The SMF Extractor
supports writing to up to 5 additional log streams, numbered 1 thru 5. For example:

*
* Output log stream for IZDS COLLECTOR
*
OUTLGR=MY.IZDS.LOG.STREAM
*
* Output log stream for IZDS DataSplitter redistribution
*OUT1LGR=MY.RAW.LOG.STREAM

In order to capture additional SMF records the users need to ensure that the SMFREC statement will
capture the SMF records the users want write to the additional log streams. For example:

*
* IZDS wants SMF 30 and SMF 70 thru 79
*
SMFREC=30,70:79
*

84 IBM Z Decision Support : Administration Guide and Reference

 * Out security app wants SMF 80 thru 83
*
*SMFREC=80:83

Remember that all SMFREC statements are cumulative (unless one of them specifies an *).
If the users were to run the SMF Extractor at this point, user would get all of the records written to both
of the log streams. To be selective about which records get written to which log stream we must use
OUT*LREC statements. OUT*LREC statements are like SMFREC statements except that the serve to filter
the SMF records written to each output log stream.

*
* Write only the SMF records IZDS wants to its log streams
*
OUTLREC=30,70:79
*
* DataSplitter records
*
*80 thru 83 for our security app
*
OUT1LREC=80:83

The OUT1LREC is the OUTLREC parameter for the first additional output log stream (numbered 1).
OUT*LREC statements for the same output log stream are cumulative like the SMFREC statements.

Activating changes
If you need to change the SMF details being collected you are advised to:
1. Update the SMF Extractor configuration
2. Wait until the system is quite or in a maintenance window
3. Start the new SMF extractor job with the same name as the old one. It should simply queue up behind
it
4. Stop the old SMF Extractor instance
This will minimize the number of SMF messages that are missed during the change over.

SMF Extractor console commands

You can use these console commands to manage the SMF Extractor started task.
Change smfext to match the name of your SMF Extractor:
S smfextSMFID=smfid
Start the SMF Extractor on the system the command is issued on using the supplied SMF ID to pick
the SMFPxxxx member to get its parameters from.
F smfext,PTRACE
Prints out the last 100 trace records.
F smfext,RESUME
Resumes SMF recording after a SUSPEND had been used.
F smfext,STATUS
• Displays detailed information related to the performance of the SMF Extractor.
• Of note in the output is the CKKS141I message that shows current queue depths.
F smfext,STAT MEMORY|STATUS MEMORY
The output from this command displays the various 64-bit cellpools and how much memory is
allocated, specified in megabytes.
F smfext,STATUS|STATUS PROCESS
The PROCESS parameter display differs depending on the z/OS system version. On z/OS 2.3 or earlier,
only SMF record types 0 - 255 are displayed. On z/OS 2.3 or higher, SMF record types 0 - 2047 are
displayed.

Chapter 4. Administering IBM Z Decision Support 85

Collecting log data

F smfext,STATUS|STATUS PROCESS(ZERO)
The PROCESS(ZERO) parameter only displays SMF record types that have a zero count.
F smfext,STATUS|STATUS PROCESS(NZERO)
The PROCESS(NZERO) parameter only displays SMF record types that have a non-zero count.
F smfext,STOP
Terminate the SMF Extractor on the system the command is issued on.
F smfext,SUSPEND
Suspends SMF recording. SMF records issued while the extractor is suspended will not be captured or
processed by IBM Z Decision Support. Do not do this unless the user has to.
F smfext,VER
Display SMF Extractor version, release, and modification level.
There are a number of additional console commands that are only relevant to IBM Z Batch Resiliency. See
the IBM Z Batch Resiliency documentation for details of them.

Setting up operating routines

About this task
This section describes how to develop operating routines for:
• “Collecting log data” on page 86
• “Administering the IBM Z Decision Support database” on page 96
• “Administering reports” on page 111
The sample jobs described may not be identical to those shipped with IBM Z Decision Support. Before
using these jobs, refer to the samples in the DRL190.SDRLCNTL library.

Collecting log data

About this task

One of your primary responsibilities is to establish routines to collect data. To do this, you can use either
the IBM Z Decision Support administration dialog or log collector language statements that you execute
through either a job or the dialog. This section describes:
1. How to collect data from the SAMPLE log type. The Sample component contains a log definition, record
definitions, and update definitions for collecting SAMPLE log data sets.
2. How to collect data in batch without using the dialog. See “Collecting data from a log into Db2
tables” on page 137 for information about using the dialog to collect data. You can also automate the
collection of data using the log data manager option, described in “Working with the log data manager
option” on page 186.

Collecting data through the administration dialog

About this task

To collect log data from a SAMPLE log data set:

Procedure
1. From the Administration window, select 3, Logs, and press Enter.
The Logs window is displayed.
2. From the Logs window, select Sample and press F11.
The Collect window is displayed.

86 IBM Z Decision Support : Administration Guide and Reference

 Collecting log data

3. Type DRL190.SDRLDEFS(DRLSAMPL) in the Data set field.

This is the name of the data set that contains log data
4. Press F4 to start an online collect process.
After the data collection is complete, IBM Z Decision Support displays statistics about the collect. (See
“Sample collect messages” on page 90 for more information about the statistics.)
5. When the collect is complete, press F3.
The product returns to the Logs window.
6. From the Logs window, press F3.
The product returns to the Administration window.

Using log collector language to collect data

About this task

To collect log data using the SAMPLE log definition, create and submit the JCL (Figure 30 on page 87).

//jobname JOB parameters

//LC EXEC PGM=DRLPLC,PARM=('SYSPREFIX=DRLSYS SYSTEM=DSN')
//STEPLIB DD DISP=SHR,DSN=DRLxxx.SDRLLOAD
//DRLIN DD *
COLLECT SAMPLE;
//DRLLOG DD DISP=SHR,DSN=DRLxxx.SDRLDEFS(DRLSAMPL)
//DRLOUT DD SYSOUT=*
//DRLDUMP DD SYSOUT=*

Figure 30. Invoking the log collector in batch to collect data

IBM Z Decision Support uses the log collector program (DRLPLC) to collect the SAMPLE log type, using
these ddnames:
DD statement name
Description
DRLIN
Contains the log collector language statements. It can contain fixed-length or varying-length records
of any length, but the log collector reads a maximum of 72 bytes from each record.
DRLLOG
Identifies the log data set. The data set attributes are determined by the program creating the log.
DRLOUT
Identifies where collect messages are routed. It can have fixed-length or varying-length records of
any length, but the log collector assumes a length of at least 80 bytes for formatting. Lines that are
longer than the specified record length are wrapped to the next line. DRLOUT is allocated as RECFM=F
and LRECL=80 if no DCB attributes are specified.
DRLDUMP
Identifies where collect diagnostics are routed. It can have fixed-length or varying-length records
of any length, but the log collector assumes a length of at least 80 bytes for formatting. Lines that
are longer than the specified record length are wrapped to the next line. DRLDUMP is allocated as
RECFM=F and LRECL=80 if no DCB attributes are specified.

The DRLJCOLL job

The sample job DRLJCOLL is a generic collect job, adaptable for most logs.
“DRLJCOLL job for collecting data from an SMF data set” on page 88 shows sample job DRLJCOLL, used
to collect data from an SMF log data set.
Note: Ensure that the log data sets that are used as input for the collect (DRLLOG DD statement) are
sorted in chronological order.

Chapter 4. Administering IBM Z Decision Support 87

Collecting log data

DRLJCOLL job for collecting data from an SMF data set

//DRLJCOLL JOB (ACCT#),'COLLECT'

//******************************************************************
//* Name: DRLJCOLL *
//* *
//* Function: *
//* IBM Z Decision Support collect job *
//* *
//* Replace "COLLECT SMF" below with one of the following *
//* statements to collect other logs: *
//* *
//* COLLECT DCOLLECT *
//* WHERE DCUDATE > DATE(LOOKUP LAST_DCOLLECT_TIME *
//* IN DRL.DFSMS_LAST_RUN *
//* WHERE DCUSYSID = MVS_SYSTEM_ID *
//* AND DCURCTYP = RECORD_TYPE); *
//* (replace DRL with the table prefix you use) *
//* (the lookup table DFSMS_LAST_RUN must be initialized *
//* before the first collect as described in the DFSMS *
//* customization section of the SP Reference manual) *
//* *
//* COLLECT EREP; *
//* *
//* SET JES_COMPLEX = ' '; *
//* COLLECT SYSLOG_JES2; *
//* *
//* For operations log (OPERLOG) produced using the System *
//* Logger, use the COLLECT statement above and change the *
//* //DRLLOG statement as follows: *
//* //DRLLOG DD DSN=SYSPLEX.OPERLOG,DISP=SHR, *
//* DCB=(LRECL=32756, BLKSIZE=32760, RECFM=VB), *
//* SUBSYS=(LOGR,, *
//* 'FROM=(2015/152,00:00),TO=(2015/153,23:59)',) *
//* *
//* SET JES_COMPLEX = 'JES3COMP'; *
//* COLLECT SYSLOG_JES3; *
//* (replace JES3COMP with the name of the JES3 complex) *
//* *
//* SET MVS_SYSTEM_ID = 'MVS1'; *
//* COLLECT NETVIEW; *
//* (replace MVS1 with the name of the MVS system) *
//* *
//* COLLECT OPC; *
//* *
//* SET VMID = 'VM1'; *
//* COLLECT VMACCT; *
//* (replace VM1 with the name of the VM system) *
//* *
//* COLLECT VMPRF; *
//* COLLECT VMPERFT; *
//* *
//* COLLECT UNIX; *
//* *
//* COLLECT OS400_JOURNAL; *
//* COLLECT OS400_CONFIG; *
//* COLLECT OS400_HISTORY; *
//* COLLECT OS400_PM_DISK; *
//* COLLECT OS400_PM_POOL; *
//* COLLECT OS400_PM_SYS; *
//* *
//* SET UNLOAD_DATE = 'YYYY-MM-DD'; *
//* SET SYSTEM_ID = 'MVS1'; *
//* COLLECT RACFCONF REPROCESS; *
//* (Replace YYYY-MM-DD with the date when you run the *
//* RACF Database Unload utility. As default, the current *
//* date is used) *
//* (Replace MVS1 with the name of your system. As default, *
//* $UNK is used) *
//* *
//* COLLECT LINUX; *
//* COLLECT ZLINUX; *
//* *
//* For some logs, special collect jobs are required: *
//* DRLJCOIM IMS log *
//* DRLJCOVP Network configuration data *
//* DRLJCOIN IBM Tivoli Information Management for z/OS data *
//* *
//* Before you submit the job: *
//* - Check the IBM Z Decision Support *
//* and Db2 data set names. *

88 IBM Z Decision Support : Administration Guide and Reference

 Collecting log data

//* - Check the Db2 subsystem name (default is DSN) *

//* and IBM Z Decision Support *
//* system table *
//* prefix (default is DRLSYS). *
//* - Insert the correct collect statement in DRLIN *
//* (as described above). *
//* - Specify the name of the log data set in DRLLOG. *
//******************************************************************
//COLLECT EXEC PGM=DRLPLC,PARM=('SYSTEM=DSN SYSPREFIX=DRLSYS')
//STEPLIB DD DISP=SHR,DSN=DRL190.SDRLLOAD
// DD DISP=SHR,DSN=db2loadlibrary
//DRLIN DD *

COLLECT SMF;

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

Some logs require special collect procedures, which are supplied by the product. They are:
Collect job name
Description
DRLJCOIM
Collects IMS log data.
DRLJCOIN
Collects IBM Tivoli Information Management for z/OS data.
DRLJCOVP
Collects network configuration data.

Collecting data from IMS

About this task

DRLJCOIM is a sample job for collecting data from the IMS SLDS log. For information about collecting IMS
data and generating composite data records that combine various types of IMS log records, refer to the
IMS Performance Feature Guide and Reference.

Collecting data from IBM Tivoli Information Management for z/OS

About this task

The sample job, DRLJCOIN uses DRLJRFT2 to read data from the IBM Tivoli Information Management for
z/OS database. DRLJRFT2 is an IBM Tivoli Information Management for z/OS report format table (RFT)
in the DRLxxx.SDRLCNTL library. For information about collecting data from the IBM Tivoli Information
Management for z/OS database, refer to the System Performance Feature Reference Volume 1.

Collecting network configuration data

About this task

DRLJCOVP is a sample job for collecting network configuration data (vital product data). For information
about collecting network configuration data, refer to the Network Performance Feature Reference.

Using the DRLCHECKPOINT table

About this task

The DRLSYS.DRLCHECKPOINT system table contains data from record procedures that need to resume
from where a previous collect left off when it ended. This also allows record procedures to sync important
information with commits for restartability.

Chapter 4. Administering IBM Z Decision Support 89

Collecting log data

One of the keys in this table is the job name. When you run a collect job or STC, the job name is used to
link the executions together.

Performing routine data collection

About this task

When you set up your collect jobs, consider these guidelines:
• Collect data at off-peak hours.
Log data sets are generally available, online systems have been taken down, and there is less contention
for processing resources.
• Collect data daily, at least in the beginning (and especially from SMF and IMS logs).
• If you collect data from several systems, establish a procedure to get all the log data into the system
that contains the product database.
• Set up automatic procedures for submitting collect jobs. For example, use IBM Z Workload Scheduler to
initiate collect jobs. Refer to the IBM Z Workload Scheduler documentation for more information about
the product. You can also use the log data manager option to automate and obtain better control of the
submitting of collect jobs. This option is described in “Working with the log data manager option” on
page 186.

Monitoring collect activity

About this task

IBM Z Decision Support provides statistics about collect activity in messages called collect messages and
in the DRLSYS.DRLLOGDATASETS system table, described in the following sections.
Review collect activity to identify:
• Tables in high demand during collect processing. These tables are candidates for tuning to improve
performance.
• Errors that occur in user-defined IBM Z Decision Support objects.
• Any other errors that the log collector finds.

Sample collect messages

Figure 31 on page 91 shows a set of sample messages generated during a collect job.

90 IBM Z Decision Support : Administration Guide and Reference

 Collecting log data

DRL0300I Collect started at 2000-12-04-10.04.15

DRL0302I Processing SMF.DATA.SET on VOL001
DRL0341I The first record timestamp is 2000-06-03-07.00.01.730000.
DRL0308I A database update started after 2608 records due to a buffer-full condition
DRL0342I The last record timestamp is 2000-06-03-11.52.40.220000.
DRL0310I A database update started after 4582 records due to end of log
DRL0313I The collect buffer was filled 1 times. Consider increasing the
collect buffer size.
DRL0003I
DRL0315I Records read from the log or built by log procedure:
DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_000 | 0
DRL0319I SMF_006 | 6
DRL0319I SMF_007 | 0
DRL0319I SMF_021 | 0
DRL0319I SMF_025 | 0
DRL0319I SMF_026 | 476
DRL0319I SMF_030 | 3737
DRL0319I SMF_070 | 40
DRL0319I SMF_071 | 40
DRL0319I SMF_072_1 | 280
DRL0319I SMF_090 | 0
DRL0320I Unrecognized | 3
DRL0318I -------------------|----------
DRL0321I Total | 4582
DRL0003I
DRL0316I Records built by record procedures:
DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_030_X | 2012
DRL0319I SMF_070_X | 200
DRL0318I -------------------|----------
DRL0321I Total | 2212
DRL0003I
DRL0323I -------Buffer------ ------Database-----
DRL0324I Table name | Inserts Updates Inserts Updates
DRL0325I ----------------------------|----------------------------------------
DRL0326I DRL .AVAILABILITY_D | 3 23 2 1
DRL0326I DRL .AVAILABILITY_M | 3 1 2 1
DRL0326I DRL .AVAILABILITY_T | 9 76 9 0
⋮
DRL0326I DRL .MVS_WORKLOAD_H | 144 336 132 12
DRL0326I DRL .MVS_WORKLOAD_M | 60 12 48 12
DRL0325I ----------------------------|----------------------------------------
DRL0327I Total | 2643 99019 2148 495
DRL0003I
DRL0301I Collect ended at 2000-12-04-10.09.43
DRL0356I To update the database, the algorithm SCAN was most selected.

Figure 31. Sample collect messages

Using collect messages

About this task

To use collect messages effectively, follow this procedure:

Procedure
1. Identify which log was collected and when it started.
The first messages in a set of collect messages show when the collect starts and identify the data set.
The product then shows the timestamp of the first identified record in the log, which looks like this:

DRL0341I The first record timestamp is

2000-06-03-07.00.01.730000.

2. Look for database activity.

The product writes data to the database when:

Chapter 4. Administering IBM Z Decision Support 91

Collecting log data

• The buffer is full. See “Improving collect performance” on page 95 if the buffer fills often. An
example message is:

DRL0308I A database update started after 2608 records

due to a buffer-full condition

• All log data set records have been processed. An example message is:

DRL0310I A database update started after 4582 records

due to end of log

• A specific number of records have been read. The number is specified in the COMMIT AFTER
operand of the COLLECT statement. An example message (where 1000 was specified as the COMMIT
AFTER operand) is:

DRL0309I A database update started after 1000 records.

3. Determine the last record that the product identified in the log.

DRL0342I The last record timestamp is

2000-06-03-11.52.40.220000.

4. Review record-type statistical messages.

Collection statistics for record-type processing include:
• The type of each record processed
• The number of each record type found in the log data set
• The total number of records processed
IBM Z Decision Support does not process any log records whose record type is either not defined, or
defined but not used by collect. It issues a statistical message that labels the records unrecognized:

DRL0315I Records read from the log or built by log procedure:

DRL0317I Record name | Number
DRL0318I -------------------|----------
⋮
DRL0319I SMF_026 | 476
DRL0319I SMF_030 | 3737
⋮
DRL0320I Unrecognized | 3
DRL0318I -------------------|----------
DRL0321I Total | 4582

5. Verify that user-defined log, record, and update definitions are performing as expected. Check that
appropriate data is being collected and stored in the appropriate tables.
6. Examine the processing performed by log and record procedures.
When IBM Z Decision Support finds records that require handling by record procedures, it produces
temporary, intermediate records for further IBM Z Decision Support processing. Messages show the
names and numbers of intermediate records built by record procedures while IBM Z Decision Support
was processing the log data set.
The messages appear in a group; for example:

DRL0316I Records built by record procedures:

DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_030_X | 2012
DRL0319I SMF_070_X | 200
DRL0318I -------------------|----------
DRL0321I Total | 2212

7. Examine database activity to identify tables with the most activity during collect processing.
Database inserts and updates show the number of rows inserted or updated in Db2 tables. The
number of rows inserted in the database and the number of rows updated in the database equal the
number of buffer inserts. Statistical messages of this sort look like these:

92 IBM Z Decision Support : Administration Guide and Reference

 Collecting log data

DRL0323I -------Buffer------ ------Database-----

DRL0324I Table name | Inserts Updates Inserts Updates
DRL0325I ----------------------------|----------------------------------------
DRL0326I DRL .AVAILABILITY_D | 3 23 2 1
⋮
DRL0326I DRL .MVS_WORKLOAD_M | 60 12 48 12
DRL0325I ----------------------------|----------------------------------------
DRL0327I Total | 2643 99019 2148 495

8. You can use message DRL0356I to optimize the collect process by selecting the SCAN or DIRECT
parameter. For more details, refer to the Language Guide and Reference. Following is an example of
message DRL0356I

DRL0356I To update the database, the algorithm SCAN was most selected.

Reviewing log statistics

About this task

Use the administration dialog to create a log statistics file for any log data set, regardless of whether it has
been collected. See “Displaying log statistics” on page 138 for more information.
Note: There are no lookup tables in the table name list.

Using the DRLLOGDATASETS table

About this task

The DRLSYS.DRLLOGDATASETS system table contains one row of information for each log data set IBM
Z Decision Support collects. DRLLOGDATASETS contains collect statistics, such as elapsed time for a
collection, record types collected, and numbers of records processed.
The product uses the data set name, log type, and the first 80 bytes from the first recognized record, to
warn against attempts to collect a log data set already collected.
Data sets can contain identical records, but with different names. If you want to be notified when the
second data set is processed, redefine the DRLLOGDATASETS system table so that it does not use the
DATASET_NAME column as a key. Collection of the second data set fails with ABEND U0016 and an SQL
code -803 against the DRLLOGDATASETS system table.
To view collect statistics, select a log definition from the Logs window, press F6 to see the data sets
that have been collected for the log, choose a data set, and press Enter. The Collect Statistics window is
displayed (Figure 32 on page 94).
Note: First timestamp is the first record selected, Last timestamp is the last record selected. Last
timestamp might show an earlier date and time than the first timestamp.

Chapter 4. Administering IBM Z Decision Support 93

Collecting log data

DCOLLECT Collect Statistics

Press Enter to return.

Data set : IM3.DCOLLECT.SLOG14

Volume : TSOL06

Time collected : 2000-02-11-12.38.00 Collected by : LASZLOM

Elapsed time : 54 Return code : 4
Times collected : 3 Completed : Y

First record : 000000700000E540000ID5D9C4F10048D2740092

276F00000000D7D9C9F0F0F0E700000000280010
First timestamp : 2000-10-02-13.15.24
Last timestamp : 2000-10-02-13.15.24

Records read : 16458 Records selected : 16458

Database updates : 7 Inserts :4954 Deletes : 0

F1=Help F2=Split F9=Swap F12=Cancel

Figure 32. Collect Statistics window

IBM Z Decision Support can produce a report from DRLLOGDATASETS that shows statistics for every
collect job in the table.
The product does not update DRLLOGDATASETS until a collection results in a successful commit. If it
finds an error that terminates processing of a log data set, such as a locking error or an out of space error,
it does not update DRLLOGDATASETS. If it has already created a row for the log data set (which it does
at the first commit), it does not update such indicators of a successful conclusion to processing as the
Elapsed seconds column or the Complete column. See “Recovering from database errors” on page 107
for more information.
Refer to “DRLLOGDATASETS” on page 207 for a description of its columns.

Collecting multiple log data sets

About this task

To collect multiple log data sets, specify the log data set names in the DRLLOG job card of the collect job
as follows:

//DRLIN DD *
COLLECT log-name
...
//DRLLOG DD DISP=SHR,DSN=log-data-set-1
DD DISP=SHR,DSN=log-data-set-2
DD DISP=SHR,DSN=log-data-set-3
//DRLOUT DD SYSOUT=*

If the log collecting job stops prematurely, you can start it again. In this case, the log collector does not
collect the records of the data sets that were already completely processed and the following messages
are issued:

DRL0302I Processing log-data-set-1 on EPDM0F

DRL0303W The log data set has already been processed. Data set name: log-data-set-1

The COLLECT process completes with a return code of 4.

If a log data set was only partially processed, the log collector does not collect the records that were
already collected. In this way, the same data is not summarized twice.

94 IBM Z Decision Support : Administration Guide and Reference

 Improving collect performance

Note: If the IMS checkpoint mechanism (DRLICHKI, DRLICHKO) is used, you cannot resubmit the same
collect job when using multiple concatenated IMS data sets. If you resubmit the same collect job you
could encounter a problem of duplicate key, because the DRLICHKI of the previous job would be used.

Improving collect performance

About this task

Correct collect performance problems using these tuning tasks:

Procedure
1. Optimize the collect buffer size.
Optimizing the size of the collect buffer has the greatest impact on performance
a) Reduce the number of times IBM Z Decision Support stops reading a log data set to write data to
the database by increasing the buffer size.
Message DRL0313I shows the number of database updates because of a full buffer. Look for cases
where the number of updates could be reduced by increasing the size of the buffer.
The optimum is to reduce the number of updates to 0.
b) The default buffer size is 10 MB. Use the buffer size operand of the COLLECT statement to increase
the size to 20 MB to 30 MB, or more.
Refer to the Language Guide and Reference for more information about the COLLECT statement.
c) Do not use the COMMIT AFTERnn records operand on the COLLECT statement.
2. Reduce the amount of data committed to the database.
a) Remove unnecessary tables using the INCLUDE/EXCLUDE clauses of the COLLECT statement.
b) Examine collect messages to determine the most active tables.
c) Concentrate on tables with a lot of buffer and database inserts and updates shown in DRL0326I
messages.
d) Modify update definitions to eliminate needless rows in tables.
For example, set a key column to a constant (such as a blank) instead of to a value from a record if
the detail is unnecessary.
e) Reduce the number of columns collected
i) Delete unneeded columns from the update definition of the table.
ii) Remove the columns in the SQL CREATE TABLE statement of the table definition.
iii) Drop the table.
iv) Re-create the table.
Note: With Db2 multiple insert functionality, when data is collected to data tables, the insert
statements are issued in bulk. Multiple rows are inserted with a single Db2 multiple insert
statement. This results in significant performance improvements. However, this performance
improvement decreases as the number of columns inserted increases.
3. Improve update effectiveness.
a) Define an index on the primary key but no other indexes for tables you create.
b) Do not use a LOOKUP expression with the LIKE operand (especially for large lookup tables) in
update definitions you create. Use an = operand where possible.
c) Minimize the number of rows in lookup tables that allow global search characters and in the
PERIOD_PLAN control table.
d) Run collect when the processing load from other programs is low and when Db2 use is light.
e) Optionally, choose the appropriate algorithm to update the Db2 database by specifying the DIRECT
or SCAN parameter in the COLLECT statement.

Chapter 4. Administering IBM Z Decision Support 95

Administering the IBM Z Decision Support database

If you do not specify any parameter, the collect process automatically chooses an algorithm among
the DIRECT, SCAN, and INSERT algorithms. This automatic selection, however, can be very time
consuming. To improve the performance, you can force the collect process to use either the DIRECT
or SCAN algorithm only, by specifying the DIRECT or SCAN parameter in the COLLECT statement.
For details about these parameters, refer to the Language Guide and Reference manual.

Administering the IBM Z Decision Support database

About this task

Maintaining the IBM Z Decision Support database includes purging unneeded data, reorganizing the
database, updating Db2 statistics, backing up data, updating views on the Db2 catalog, and protecting the
integrity of data by controlling the access.
Regular maintenance tasks are as follows:
Besides regularly scheduled jobs, run the RUNSTATS utility periodically while the database is growing to:
• Provide the Db2 optimizer with information. (After the database stabilizes, RUNSTATS does not make a
significant contribution to the Db2 optimizer.)
• Provide table size statistics for IBM Z Decision Support.
See “Monitoring the size of the IBM Z Decision Support database” on page 108 for more information.
The remainder of this section introduces the use of Db2 as the product database manager and shows how
to use Db2 to maintain the database.

Understanding Db2 concepts

By default, IBM Z Decision Support names for Db2-related items are:
DSN
Names the Db2 subsystem.
DRLDB
Names the product database.
DRLSSYS1
Names the product table space that contains log collector system tables.
DRLSSYS2
Names the product table space that contains other system tables.
DRLSSAMP
Names the product table space that contains tables for the Sample component
DRLSCOM
Names the product table space that contains common tables that the product components use.
The names of other product table spaces depend on the components you install. There is at least one
table space for each component.
Figure 33 on page 97 shows the data areas in the Db2 subsystem.

96 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

DSN Db2 subsystem

DRLDB database Other

Db2
DRLSSAMP databases
DRLSSYS1
Other
System Sample IBM Z
tables tables
Decision
Support
DRLSSYS2 DRLSCOM
Analytics
table
System Common spaces
tables tables

Figure 33. Db2 environment for the IBM Z Decision Support database

Understanding how IBM Z Decision Support uses Db2

Figure 33 on page 97 shows an IBM Z Decision Support installation that uses one product database.
There can be more than one product database in the installation of IBM Z Decision Support , more than
one IBM Z Decision Support installation in one Db2 subsystem, more than one Db2 subsystem with an
installation of the product, and so on.

Understanding table spaces

Figure 33 on page 97 shows that the product uses several table spaces in the DRLDB database. A table
space contains one or more tables and is the logical unit addressed by Db2 utilities such as COPY and
REORGanize.
To list the table spaces belonging to the current database:
1. Select 4, Tables, from the Administration window.
2. Without selecting a table, select the Maintenance pull-down.
3. Select 1, Tablespace, from the options.
Figure 34 on page 97 shows the list of table spaces, with the Utilities pull-down.

Tablespace Utilities Other Help

1. Run DB2 REORG utility... Row 1 to 20 of 37

2. Run DB2 RUNSTATS utility..
Select a ta 3. Run DB2 REORG/DISCAD utility.. ablespace definition.

Quantity
/ Tablespace Primary Secondary Storage grp Type Locksize
DRLSAIX 6000 3000 SYSDEFLT SEGMENTED TABLE
DRLSCI08 100 52 STOEPDM SEGMENTED TABLE
DRLSCOM 20000 10000 SYSDEFLT SEGMENTED TABLE
DRLSCP 60 32 SYSDEFLT SEGMENTED TABLE
DRLSDB2 40000 20000 SYSDEFLT SEGMENTED TABLE
DRLSDFSM 60000 30000 SYSDEFLT SEGMENTED TABLE
DRLSDPAM 100 52 SYSDEFLT SIMPLE ANY

Figure 34. Tablespace list window

When you change table space or index space parameters, the product uses SQL commands to alter the
space directly, and creates a job to unload and load table data as necessary. IBM Z Decision Support does

Chapter 4. Administering IBM Z Decision Support 97

Administering the IBM Z Decision Support database

not change the definition of the table space. To do this, select the Space pull-down on the Components
window.
If you create a table in the product database, you must specify the database and table space in which Db2
is to create the table. Once created, a table can be addressed by its table name only. You do not need to
specify the table space name.
“Working with tables and update definitions” on page 165 describes how to use the administration dialog
to view, change, or create table spaces.

Calculating and monitoring table space requirements

About this task

To make effective use of the available space, you need to monitor the storage required for your data
tables. The sample job, DRLJTBSR (in the DRL190.SDRLCNTL library), produces a detailed report about
the space required for some or all of the selected component tables, based on the average record size and
estimated number of rows.
To customize the job to your requirements, you must change some parameters in DRLJTBSR. For a
description of these parameters, see “Parameters for table space reporting” on page 99.
DRLJTBSR job that reports table space requirements

//DRLJTBSR JOB (ACCT#),'SPACE'

//********************************************************************
//* Name: DRLJTBSR *
//* *
//* FUNCTION: Print a report of estimated total kilobytes based on *
//* estimated records number and average record length *
//* for each table on component. *
//* Average records length is calculated,if the table is *
//* not created, reading TDS for zOS definition *
//* library *
//* *
//* The exec DRLETBSR accepts the following parameters: *
//* *
//* LIBRARY= TDS for zOS definition library *
//* SYSPREFIX= TDS for zOS system table prefix *
//* DB2SUBSYS= Db2 subsystem name *
//* COMPONENT= Component name. To have a complete list of *
//* component short name read the DRLCOMPONENTS *
//* system table *
//* TABLENAME= Table name ('*' to select all table) *
//* RECNUMBER= Estimated record numbers *
//* PAGESIZE= Value of pagesize . Can be 4K or 32K. *
//* Optional parameter, default value when *
//* not specified is 4K *
//* MAXROWS= Maximum number of rows per pages. Maximum *
//* value allowed is 255. *
//* Optional parameter, default value when not *
//* specified is 255 *
//* PCTFREE= Percentage of free space on each page. *
//* Value allowed from 0 to 99. *
//* Optional parameter, default value when not *
//* specified is 5 *
//* FREEPAGE= Number of free space pages. Value allowed *
//* from 0 to 255. *
//* Optional parameter, default value when not *
//* specified is 0 *
//* COMPRESS= Compression ratio. Optional parameter. *
//* The value must be in range from 0 to a value *
//* less than 1 *
//* Default value when not specified is 0. *
//* *
//* Notes: *
//* Before you submit the job, do the following: *
//* 1. Check that the data set names are correct. *
//* 2. Change the parameters to DRLETBRS as required. *
//* 3. Change the Db2 load library name according to *
//* the naming convention of your installation. *
//* Default is 'db2loadlibrary'. *
//* *

98 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

//********************************************************************
//SPACE EXEC PGM=IKJEFT01,DYNAMNBR=25
//*
//STEPLIB DD DISP=SHR,DSN=DRLvrm.SDRLLOAD <== DATA SET NAME
//SYSPROC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC <== DATA SET NAME
//SYSEXEC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC <== DATA SET NAME
//***************************
//* START EXEC DRLETBSR
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLETBSR LIBRARY= DRLvrm.SDRLDEFS -
Db2SUBSYS= DSN -
SYSPREFIX= DRLSYS -
COMPONENT= xxxx -
TABLENAME= * -
RECNUMBER= xxxx -
PAGESIZE= 4K -
MAXROWS= 255 -
PCTFREE= 5 -
FREEPAGE= 0 -
COMPRESS= 0
/*

Following is sample output for job DRLJTBSR that shows the space required for all tables of the IMS
collect component.
Sample output for DRLJTBSR

Statistics for space required for a component:

---------------------------------------------:

Input library : DRL190.SDRLDEFS

Db2 subsystem : DSN7
PR system prefix : PRM3SYS
Component : IMSV710C
Table name : *
Estimated records number : 500000
Page size : 4096
Maxrows per page : 255
Percentage of free space : 5
Number of free pages : 0
Compression ratio : 0

Definition Avg record Record Estimated

Estimated
Table name New Tablespace member length per page total pages
kilobytes
------------------ --- ----------- ----------- ----------- ----------- -----------
-------

IMS_APPLICATION_H N DRLSIA01 DRLTIMSA 651 5 100002 400008

IMS_APPLICATION_W N DRLSIA02 DRLTIMSA 648 5 100002 400008
IMS_CHKPT_IOSAM_T N DRLSIS01 DRLTIMSS 169 22 22730 90920
IMS_CHKPT_POOLS_T N DRLSIS02 DRLTIMSS 99 39 12823 51292
IMS_CHKPT_REGION_T N DRLSIS03 DRLTIMSS 101 38 13160 52640
IMS_CHKPT_STATS_T N DRLSIS04 DRLTIMSS 518 7 71430 285720
IMS_CHKPT_VSAM_T N DRLSIS05 DRLTIMSS 194 19 26318 105272
IMS_SYSTEM_D N DRLSIY01 DRLTIMSY 642 6 83335 333340
IMS_SYSTEM_Q N DRLSIY02 DRLTIMSY 645 6 83335 333340
IMS_TRANSACTION_D N DRLSIT02 DRLTIMSR 646 5 100002 400008
IMS_TRANSACTION_H N DRLSIT01 DRLTIMSR 649 5 100002 400008
IMS_TRANSACTION_W N DRLSIT03 DRLTIMSR 646 5 100002 400008

Parameters for table space reporting

Table 6. Parameters for table space reporting

Parameter Value to set Explanation Default value Your value

LIBRARY IBM Z Decision The name of the partitioned data set that
Support definition library contains definitions of the product tables.
(UPPERCASE) This is a required parameter. It is used for
component tables that do not yet exist.

Chapter 4. Administering IBM Z Decision Support 99

Administering the IBM Z Decision Support database

Table 6. Parameters for table space reporting (continued)

Parameter Value to set Explanation Default value Your value

Db2SUBSYS Db2 subsystems name The Db2 subsystem where the product
(UPPERCASE) resides. This is a required parameter.

SYSPREFIX Prefix for system tables The prefix of all IBM Z Decision Support
(UPPERCASE) system and control Db2 tables. This
is a required parameter. The value of
this parameter depends on your naming
convention and is determined during
installation.

COMPONENT Component name The name of an IBM Z Decision Support

(UPPERCASE) component. This is a required parameter.

TABLENAME The name of the table The name of the IBM Z Decision Support
(UPPERCASE) table. This is a required parameter. To specify
all component tables, type an asterisk, *. To
specify all component tables whose names
start with a particular string, type the string.
For example, type CICS_S for all component
tables whose name starts with this string.

RECNUMBER Number of rows The estimated number of rows. This is a

required parameter and must be numeric.

PAGESIZE Db2 page size The Db2 page size. This is an optional 4096 (4K)
parameter; when specified, it must be either
4K or 32K.

MAXROWS Maximum number of rows The maximum number of rows per page. This 255
per page is an optional parameter; when specified, it
must be a numeric value between 1 and 255.

PCTFREE Percentage of free space on The percentage of free space per page. This is 5
each page an optional Db2 parameter; when specified, it
must be a numeric value between 1 and 255.

FREEPAGE Number of free space pages The number of free space pages. This is an 0
optional Db2 parameter; when specified, it
must be a numeric value between 1 and 255.

COMPRESS Compression ratio The compression ratio calculated as 0

PERCSAVE/100 (PERCSAVE is the percentage
of kilobytes saved by compression as reported
by Db2 utility DSN1COMP). This parameter is
optional; when specified, it must be a numeric
value.

For detailed information about the parameters, refer to the Db2 for z/OS: SQL Reference.
For information about Db2, refer to the Db2 for z/OS: Administration Guide and Reference.
For information about the algorithm used for calculating table space requirements, refer to the Db2 for
OS/390 Installation Guide.

Considerations when running DRLJTBSR

The sample job DRLSJTBSR invokes the DRLETBSR exec. Before you can use DRLETBSR, the IBM Z
Decision Support system tables must have already been created or updated. If a component is already
installed, DRLETBSR obtains the average record size of each component table directly from the product
system tables.
The column NEW in the report shows the table status (N for a table already created, Y for a table that does
not exist). The DRLETBSR exec calculates the average record size for each component table.
If a component is not installed, the DRLETBSR exec reads each partitioned data set member that defines
each component table (see the LIBRARY parameter). Use this exec only for standard IBM Z Decision
Support libraries. Using it for customized libraries can produce unpredictable results. For variable length
fields, the average record size is calculated using the maximum length. The average record size does
not include GRAPHIC, VARGRAPHIC and LONG VARGRAPHIC Db2 data-types. When you specify the

100 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

estimated number of records, remember that the product collects data from tables according to rules
specified in the update definitions. Tables containing the same data may therefore have different numbers
of rows. For example, an hourly table may contain a greater number of rows than a daily table.

Reorganizing the database

It is important to delete obsolete data from the tables as this updates the product database and improves
performance during the query activity. Also, it is important to reorganize table space after data deletion
to optimize the available space. You can use the utility Reorg/Discard to delete data and reorganize table
space.

Reorg/Discard utility
The Reorg/Discard utility enables you to delete the data included in the tables using the Purge condition
included in the DRLPURGECOND table. This table is provided in IBM Z Decision Support. At the same time,
the Reorg/Discard utility automatically reorganizes the table space where data has been deleted.
The records deleted by the Discard function are automatically saved in a specific data set, SYSPUNCH.
SYSPUNCH can be used at a later time to reload discarded data in the table, if required.
During the Discard step, the Reorg function reorganizes the table space to improve access performance
and reclaim fragmented space. Also, the keyword STATISTICS is automatically selected for the Reorg/
Discard, enabling you to collect online statistics during database reorganization.
See the Db2 for z/OS: Utility Guide and Reference, for more information about Reorg/Discard utility.
There are two ways to run the Reorg/Discard utility from the Administration window of IBM Z Decision
Support:
From the Tables window, select option 12 from the Utilities pull-down menu.

Table Maintenance Utilities Edit View Other Help

------------------------------------------------------------------------------
| 12 1. Display... F11 | Row 1 to 21 of 129
| 2. Show size... |
Select one or more | 3. *mport... | definition.
| 4. *xport... |
/ Tables | 5. Grant... |
_ CICS_DICTIONARY | 6. Revoke... |
_ CICS_FIELD | 7. Document... |
_ DAY_OF_WEEK | 8. Recalculate... |
_ EXCEPTION_T | 9. Purge... |
_ IMS_APPLICATION | 10. Unload... |
_ IMS_APPLICATION | 11. Load... |
_ IMS_APPLICATION | 12. Reorg/Discard... |
_ IMS_CHKPT_IOSAM | 13. DB2HP Unload... |
_ IMS_CHKPT_POOLS |____________________________________|

Figure 35. Tables window - Option 12

In this way, the data contained in the table or tables selected from the table list is discarded, and a
space reorganization is automatically performed in the table space where the selected tables reside. The
Discard operation is only performed on the selected tables, while the Reorg operation is performed on all
the tables contained in the table space. You cannot run the Discard utility on Views or Tables that have
any discard condition specified in the DRLPURGECOND table.
As an alternative, use option 1 from the Maintenance pull-down menu of the Tables window to open the
Tablespace window, then select option 3 from the Utilities pull-down menu.

Chapter 4. Administering IBM Z Decision Support 101

Administering the IBM Z Decision Support database

Tablespace Utilities Other Help

1. Run DB2 REORG utility... Row 1 to 20 of 37

2. Run DB2 RUNSTATS utility..
Select a ta 3. Run DB2 REORG/DISCAD utility.. ablespace definition.

Quantity
/ Tablespace Primary Secondary Storage grp Type Locksize
DRLSAIX 6000 3000 SYSDEFLT SEGMENTED TABLE
DRLSCI08 100 52 STOEPDM SEGMENTED TABLE
DRLSCOM 20000 10000 SYSDEFLT SEGMENTED TABLE
DRLSCP 60 32 SYSDEFLT SEGMENTED TABLE
DRLSDB2 40000 20000 SYSDEFLT SEGMENTED TABLE
DRLSDFSM 60000 30000 SYSDEFLT SEGMENTED TABLE
DRLSDPAM 100 52 SYSDEFLT SIMPLE ANY

Figure 36. Tablespace list window

In this second scenario, from the Tablespace window, you select the table spaces for the Reorg operation.
The Discard operation is automatically run on all the tables contained in the selected table spaces,
according to the conditions specified in the DRLPURGECOND table.
All the tables that have the Discard operation specified in the DRLPURGECOND table are included in the
processing. All the tables that do not have the Discard operation specified in the DRLPURGECOND table
are ignored.
When you run Reorg/Discard, whichever procedure you use, a JCL is created and saved in your library,
so that it can be used at a later time, if required. When the JCL is launched, the following data sets are
created:
SYSPUNCH
Used to reload the discarded data, if required, using the Load utility.
SYSDISC
Contains the records discarded by the utility.
In addition, SYSREC data set is available. It contains all the records in the table, and you can
specify whether you want it to be Temporary or Permanent. If you specify Temporary, the data set is
automatically erased at the end of the reorganization job. If you specify Permanent, it is permanently
allocated on your disk.
When using the Reorg/Discard utility, you can select one or more tables and table spaces at a time.
However, in the data sets SYSPUNCH and SYSDISC, data is overwritten, therefore each data set maintains
only the information contained in the last table you processed.
The following is an example of how the Reorg/Discard utility works on a table space that contains several
tables:

//REODIS JOB (ACCOUNT),'NAME'

//*
//***************************************************************
//* Run Db2 Utility
//*
//* WARNING (REORG/DISCARD):
//* If you want, you can specify the SORTKEYS option:
//* a subtask sorts the index keys. For this optional
//* operation you need enough space in your
//* default Storage Disk for this SORT operation.
//*
//***************************************************************
//DB2UTIL EXEC DSNUPROC,
// SYSTEM=DEC1,UID=MYUID
//*
//DSNUPROC.STEPLIB DD DISP=SHR,DSN=DB2VC10.DEC1.SDSNEXIT
// DD DISP=SHR,DSN=DB2.VC10.SDSNLOAD
//DSNUPROC.SYSREC DD DSN=MYUID.DRLUNLD,UNIT=SYSDA,
// SPACE=(4096,(1,1)),DISP=(MOD,DELETE,CATLG)
//DSNUPROC.SYSUT1 DD DSN=MYUID.DRLWORK,UNIT=SYSDA,

102 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

// SPACE=(4096,(1,1)),DISP=(MOD,DELETE,CATLG)
//DSNUPROC.SORTOUT DD DSN=MYUID.DRLSROUT,UNIT=SYSDA,
// SPACE=(4096,(1,1)),DISP=(MOD,DELETE,CATLG)
//DSNUPROC.WORK DD DSN=MYUID.WORK1,UNIT=SYSDA,
// SPACE=(4096,(1,1)),DISP=(MOD,DELETE,CATLG)
//DSNUPROC.SYSPUNCH DD DISP=(MOD,CATLG),
// DSN=MYUID.TAB.SYSPUNCH,
// SPACE=(4096,(1,1)),UNIT=SYSDA
//DSNUPROC.SYSDISC DD DISP=(MOD,CATLG),
// DSN=MYUID.TAB.DISCARDS,
// SPACE=(4096,(1,1)),UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=410,BLKSIZE=27880)
//DSNUPROC.SYSIN DD *
TEMPLATE MYDDN DSN MYUID.&DB..&TS..Z&DATE.
MODELDCB TDS.UTS.MODEL
REORG TABLESPACE DRLDBAC.DRLSCOM4 LOG NO SHRLEVEL CHANGE
COPYDDN(MYDDN)
STATISTICS INDEX(ALL) DISCARD
FROM TABLE DRLDB.AVAILABILITY_T
WHEN (
START_TIME < CURRENT TIMESTAMP - 10 DAYS
)
REORG TABLESPACE DRLDBAC.DRLSCOM5 LOG NO SHRLEVEL CHANGE
COPYDDN(MYDDN)
STATISTICS INDEX(ALL) DISCARD
FROM TABLE DRLDB.AVAILABILITY_D
WHEN (
DATE < CURRENT DATE - 90 DAYS
)
REORG TABLESPACE DRLDBAC.DRLSCOM7 LOG NO SHRLEVEL CHANGE
COPYDDN(MYDDN)
STATISTICS INDEX(ALL) DISCARD
FROM TABLE DRLDB.AVAILABILITY_M
WHEN (
DATE < CURRENT DATE - 800 DAYS
)
/*

In this example, the Reorg/Discard utility reorganizes the MYUID.DRLSCOM table space and discards
data from the MYDB.AVAILABILITY_D, MYDB.AVAILABILITY_M, and MYDB.AVAILABILITY_T tables. This
example shows that the DDNAME for the SYSPUNCH data set is SYSPUNCH, the DDNAME for the discard
results data set is SYSDISC, and the DDNAME for the sort output data set is defaulted to SORTOUT. The
SYSDISC and SYSPUNCH data sets are reused every time the utility is run for all tables.

Purge utility
As an alternative to the Reorg/Discard utility, you can delete data and reorganize table space using the
Purge utility.
Each data table in a component has a Purge condition that specifies which data is to be purged from that
table. When you use the Purge function, the data specified in the purge condition is deleted.
Purge the contents of your database at least weekly. The sample job, DRLJPURG (in the
DRL190.SDRLCNTL library), purges all product database tables with Purge conditions. Figure 37 on page
104 shows part of DRLJPURG.

Chapter 4. Administering IBM Z Decision Support 103

Administering the IBM Z Decision Support database

//DRLJPURG JOB (ACCT#),'PURGE'

//***************************************************************
//* NAME: DRLJPURG *
//* *
//* FUNCTION: *
//* PURGE DATA FROM ALL TDS for zOS TABLES *
//* ACCORDING TO THE PURGE CONDITIONS DEFINED FOR THE TABLES)*
//* IF YOU WANT TO PURGE ONLY SOME TABLES, SPECIFY THE *
//* INCLUDE OR EXCLUDE OPTIONS. EXAMPLE: *
//* *
//* PURGE INCLUDE LIKE 'DRL.CICS%' *
//* *
//* NOTES: *
//* 1.CHECK Db2 SUBSYSTEM AND DATA SET NAMES. *
//* 2.Change the Db2 load library name according to *
//* the naming convention of your installation. *
//* Default is 'db2loadlibrary'. *
//* *
//***************************************************************
//PURGE EXEC PGM=DRLPLC,PARM=('SYSTEM=DSN SYSPREFIX=DRLSYS')
//STEPLIB DD DISP=SHR,DSN=DRLvrm.SDRLLOAD
// DD DISP=SHR,DSN=db2loadlibrary
//DRLIN DD *

PURGE;

//DRLOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//DRLDUMP DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
/*

Figure 37. DRLJPURG job that uses all purge conditions

The Purge utility generates messages that show if the job ran as expected:

DRL0300I Purge started at 2000-05-24-15.12.30.

DRL0404I Table name | Deletes
DRL0405I ---------------------------|---------
DRL0406I DRL .RACF_RESOURCE_T | 12376
DRL0406I DRL .RACF_LOGON_T | 98
DRL0406I DRL .RACF_OPERATION_T | 457
DRL0406I DRL .RACF_COMMAND_T | 17
DRL0301I Purge ended at 2000-05-24-15.12.44.

After purging the database, use the Db2 REORG utility to free the purged space for future use. There are
three methods of reorganizing your database:
1. Use option 1, Run Db2 REORG utility, from the Utilities menu on the Tablespace list window, shown in
Figure 34 on page 97. This reorganizes a whole table space.
2. Use option 10, Unload, from the Utilities menu on the Tables window, after having selected one or
more tables. When you Unload and then Load a table, it reorganizes it without affecting the other
tables in the table space.
Figure 38 on page 105 shows the list of tables, with the Utilities pull-down.

104 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

Table Maintenance Utilities Edit View Other Help

10 1. Display... F11 Row 28 to 48 of 427

2. Show size...
Select one or more 3. Import... definition.
4. Export...
/ Tables 5. Grant...
CICS_S_FILE_D 6. Revoke...
CICS_S_FILE_T 7. Document...
CICS_S_GLOBAL_D 8. Recalculate...
CICS_S_GLOBAL_T 9. Purge...
CICS_S_INTERCOM 10. Unload...
CICS_S_INTERCOM 11. Load...
CICS_S_JOURNAL_ 12. Rorg/Discard...
CICS_S_JOURNAL_T 13. DB2HP Unload...
s CICS_S_LSR_POOL_D DRL TABLE
CICS_S_LSR_POOL_T DRL TABLE
CICS_S_LSRP_FILE_D DRL TABLE
CICS_S_LSRP_FILE_T DRL TABLE
.
.
.

Figure 38. Tables window -Option 10

3. Use the sample job DRLJREOR (in the DRL190.SDRLCNTL library) to build your own job.
Refer to the description of the REORG utility in the Db2 for z/OS: Administration Guide and Reference for
more information.

Backing up the IBM Z Decision Support database

Back up the IBM Z Decision Support database regularly.

About this task

Ask your Db2 administrator to add your requirements to their site Db2 procedures for backing up the data.
If you cannot do this, copy and modify the sample job DRLJCOPY (in the DRL190.SDRLCNTL library), to
back up all product tables.
Determine:
• How often to back up the product database
• Whether to back up all data or just changed data
• The names of table spaces in the database
Figure 39 on page 106 shows job DRLJCOPY, used to back up the DRLSSYS1 and DRLSSYS2 table spaces.

Chapter 4. Administering IBM Z Decision Support 105

Administering the IBM Z Decision Support database

//DRLJCOPY JOB (ACCT#),'IMAGE COPY'

//***************************************************************
//* NAME: DRLJCOPY *
//* *
//* FUNCTION: *
//* RUN THE DB2 IMAGE COPY UTILITY TO MAKE BACKUP COPIES *
//* OF TDSzOS TABLE SPACES. THIS JOB COPIES *
//* TABLE SPACES DRLSSYS1 AND DRLSSYS2. YOU MUST ADD A COPY *
//* STATEMENT AND DATA SET FOR EACH TABLE SPACE THAT YOU *
//* WANT TO BACK UP. *
//* *
//* NOTES: *
//* CHECK THE FOLLOWING: *
//* LIB='db2loadlibrary' DB2 LOAD LIBRARY *
//* SYSTEM=DSN DB2 SUBSYSTEM NAME *
//* DSN=COPYDSN NAME OF BACKUP DATASET *
//* SPACE= SPACE REQUIRED *
//* COPY TABLESPACE DB.TS DATABASE.TABLESPACE NAME *
//* FULL YES/NO FULL OR INCREMENTAL COPY *
//* *
//***************************************************************
//UTIL EXEC DSNUPROC,LIB='db2loadlibrary',
// SYSTEM=DSN,UID='TEMP',UTPROC=''
//*
//COPY01 DD DSN=COPYDSN1,
// DISP=(MOD,CATLG,CATLG),
// SPACE=(16384,(50,50),,,ROUND),
// UNIT=SYSDA
//COPY02 DD DSN=COPYDSN2,
// DISP=(MOD,CATLG,CATLG),
// SPACE=(16384,(50,50),,,ROUND),
// UNIT=SYSDA
//SYSIN DD *
COPY TABLESPACE DRLDB.DRLSSYS1
COPYDDN COPY01
FULL YES
COPY TABLESPACE DRLDB.DRLSSYS2
COPYDDN COPY02
FULL YES
/*

Figure 39. DRLJCOPY job for backing up IBM Z Decision Support table spaces

Determining when to back up the IBM Z Decision Support database

About this task

Back up the database at least weekly to make it easier to recover from errors.

Determining a level of backup

About this task

Db2 provides two methods for backing up data, full-image copy (copy all data), and incremental-image
copy (copy only changed data). You can combine the two copies.

Determining which table spaces to back up

About this task

The Db2 COPY utility operates on table spaces. Ensure that all table spaces are part of the backup
procedures. For more information about backing up a Db2 database, refer to the discussion of backing up
and recovering databases in the Db2 for z/OS: Administration Guide and Reference.

106 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

Recovering from database errors

About this task

These errors might occur in an IBM Z Decision Support database that sees significant activity:
• Out of space in one of the table spaces or index spaces
• Corrupted data in the database
The following sections contain descriptions of each condition, how it might occur, and how to correct it.
A description of how to restore Db2 database backups appears in “Correcting corrupted data in the IBM Z
Decision Support database” on page 107.

Correcting out-of-space condition in an IBM Z Decision Support table space or index

space

About this task

A table space or index space can be out of space if:
• Volumes in the IBM Z Decision Support storage group are full.
If DASD is not constrained, the database continues to grow and performance can be an issue. If
performance is not an issue, ask the Db2 administrator to add volumes to the IBM Z Decision Support
storage group.
If you cannot add more volumes to your storage group, purge the database before continuing.
After purging data, reorganize the affected table spaces. See “Purge utility” on page 103 for more
information.
• The table space or index space uses its maximum number of extents.
This scenario can occur if the primary quantity and all secondary quantity (PRIQTY and SECQTY) extents
have been exhausted. IBM Z Decision Support table spaces and index spaces have a default size
specification based on an estimated number of rows in tables in the table space. These default values
may be too small for a very large site.
To recover from an out-of-space condition:

Procedure
1. Increase the primary and secondary quantities using the IBM Z Decision Support administration dialog
(Figure 90 on page 179), or by using the Db2 SQL statements, ALTER TABLESPACE or ALTER INDEX.
2. Reorganize the table space using the Db2 REORG utility as described in “Purge utility” on page 103 or
drop the index and recreate it as described in “Displaying and adding a table index” on page 167.

DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION

CAUSED BY AN UNAVAILABLE RESOURCE. REASON
00D70025, TYPE OF RESOURCE 00000220 AND RESOURCE
NAME DB2A.DSNDBC.DRLDB.A.I0001.A001

Correcting corrupted data in the IBM Z Decision Support database

About this task

Corrupted data can occur because of:
• Db2 errors
• Erroneously collecting the same log data set more than once
If the database has been incorrectly updated (for example, accidentally collecting the same log data
set twice or deleting required data), restore a previous backup copy with the Db2 RECOVER utility. For

Chapter 4. Administering IBM Z Decision Support 107

Administering the IBM Z Decision Support database

information about backing up and recovering Db2 databases, refer to the Db2 for z/OS: Administration
Guide and Reference.
You need not restore product data after a collect job terminates from locking or out of space. After
correcting the error, run the job again. If the database has been updated, the collect resumes from the
last checkpoint recorded in the DRLSYS.DRLLOGDATASETS system table. If it had not committed data to
the database before the error, IBM Z Decision Support recovers the data by collecting from the first record
in the log.

Monitoring the size of the IBM Z Decision Support database

Monitor the size of the database regularly.

About this task

Use the Db2 RUNSTATS utility to generate current statistics in the Db2 catalog about any Db2 table space,
including those in the IBM Z Decision Support database.
The sample job, DRLJRUNS (in the DRL190.SDRLCNTL library), calls the Db2 RUNSTATS utility. Figure 40
on page 108 shows the RUNSTATS statements used to generate statistics for table spaces DRLSSYS1 and
DRLSSYS2.

//DRLJRUNS JOB (ACCT#),'RUNSTATS'

//******************************************************************
//* Name: DRLJRUNS *
//* *
//* Function: *
//* Run the Db2 RUNSTATS utility to update the Db2 catalog *
//* information about Performance Reporter tables. *
//* This job only runs RUNSTATS for the table spaces *
//* DRLSSYS1 and DRLSSYS2. You must add a statement for *
//* each Performance Reporter table space. *
//* *
//* Notes: *
//* Check the following: *
//* LIB='db2loadlibrary' Db2 load library *
//* SYSTEM=DSN Db2 subsystem name *
//* *
//******************************************************************
//UTIL EXEC DSNUPROC,LIB='db2loadlibrary',
// SYSTEM=DSN,UID='TEMP',UTPROC=''
//*
//DSNUPROC.SYSIN DD *
RUNSTATS TABLESPACE DRLDB.DRLSSYS1 TABLE INDEX
RUNSTATS TABLESPACE DRLDB.DRLSSYS2 TABLE INDEX
/*

Figure 40. DRLJRUNS job for generating Db2 statistics

Learn more about the Db2 RUNSTATS utility from the description of its use in the Db2 for z/OS:
Administration Guide and Reference.
Start the RUNSTATS utility from the administration dialog by choosing it from the Utilities menu in the
Tables window. After using the RUNSTATS utility, use the administration dialog to see the number of bytes
used for data in the product database (described in “Showing the size of a table” on page 156).

Understanding how IBM Z Decision Support uses Db2 locking and

concurrency
Db2 provides locking and dynamic recovery for the databases it controls. The IBM Z Decision Support
database is under Db2 control and uses these Db2 mechanisms.
More than one IBM Z Decision Support user or function can request access to the data at the same time.
The way Db2 maintains data integrity during such times is by locking out data to all processes but one.
Learn more about Db2 locking and how it allows more than one process to work with data concurrently
from the discussion of improving concurrency in the Guide to Reporting.

108 IBM Z Decision Support : Administration Guide and Reference

 Administering the IBM Z Decision Support database

Deadlock or timeout conditions can occur when more than one user works with IBM Z Decision Support
tables, which causes Db2 to generate messages; for example:

DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS BEEN
ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON 00C90088,
TYPE OF RESOURCE 00000100, AND RESOURCE NAME DRLDB

Consider the following potential locking scenarios:

• If running more than one collect job at a time, ensure the jobs do not update the same tables.
Although concurrent collects might not update the same data tables, locking can occur for the
DRLSYS.DRLLOGDATASETS system table, updated by all collect runs.
• Generating reports while a collect job runs does not usually cause lockouts.
Report queries do not update table information; their access is read-only. However, QMF can hold locks
while you display large reports.
• You cannot collect while Db2 utilities such as COPY and REORG are running. Also, you cannot collect
and purge simultaneously.
COPY and REORG lock all tables in the table space on which they operate. Purge locks the table on
which it operates.
• Creating tables (or installing components) locks the entire database.
If some users create many tables, give them a private database. See “Installing multiple IBM Z Decision
Support systems” on page 53 for more information.
To find out who is locking a resource, use the DB2 COMMANDS option in Db2 to issue this command:

-DISPLAY DATABASE(DRLDB) LOCKS LIMIT(100)

For more information, refer to the description of monitoring Db2 locking in the Db2 for z/OS:
Administration Guide and Reference.

Maintaining database security

About this task

You control user access to database tables. Although IBM Z Decision Support grants read access to
the DRLUSER group ID for any components you install, you can grant or revoke authority to tables in
the IBM Z Decision Support database. See “Administering user access to tables” on page 185 for more
information.

Monitoring database access

About this task

To see which end users access which database tables (for example, if you are considering removing
tables), use the Db2 trace facility for tracing table accesses. Analyze the trace outside Db2 with another
product. IBM Db2 Performance Monitor (DB2PM) can format, print, and interpret Db2 trace data.
Tracing involves a significant amount of overhead and is not something you should do regularly.
For information about Db2 trace facilities, refer to the description of using tools to monitor performance in
the Db2 for z/OS: Administration Guide and Reference.
For information about DB2PM, refer to the Db2 for z/OS: Administration Guide and Reference and to the
IBM Db2 Performance Monitor: User's Guide.

Chapter 4. Administering IBM Z Decision Support 109

Administering lookup and control tables

Using available tools to work with the IBM Z Decision Support database

About this task

IBM and other software suppliers provide a variety of database maintenance tools. Because you have
database administrator authority for the IBM Z Decision Support database, you can use tools such as
DB2I, a part of Db2. With DB2I you can:
• Run SQL statements
• Issue authorized Db2 commands
• Run Db2 utilities
• Work with Db2 objects in your database
Select DB2I from the Other menu of any IBM Z Decision Support primary window. You can also type DB2I
on the command line of a window.
Figure 41 on page 110 shows the DB2I Primary Option Menu.

DB2I PRIMARY OPTION MENU

COMMAND ===>

Select one of the following Db2 functions and press ENTER.

1 SPUFI (Process SQL statements)

2 DCLGEN (Generate SQL and source language declarations)
3 PROGRAM PREPARATION (Prepare a Db2 application program to run)
4 PRECOMPILE (Invoke Db2 precompiler)
5 BIND/REBIND/FREE (BIND, REBIND, or FREE plans or packages)
6 RUN (RUN an SQL program)
7 DB2 COMMANDS (Issue Db2 commands)
8 UTILITIES (Invoke Db2 utilities)
9 CATALOG VISIBILITY (Invoke catalog dialogs)
D DB2I DEFAULTS (Set global parameters)
X EXIT (Leave DB2I)

F13=HELP F14=SPLIT F15=END F16=RETURN F17=RFIND F18=RCHANGE

F19=UP F20=DOWN F21=SWAP F22=LEFT F23=RIGHT F24=RETRIEVE

Figure 41. DB2I Primary Option Menu

For more information about DB2I, refer to the description of utility jobs in the Db2 for z/OS: Administration
Guide and Reference.

Administering lookup and control tables

Periodically review the contents of IBM Z Decision Support lookup and control tables. See “Control tables
and common tables” on page 222 for a description of the columns in lookup and control tables that many
product feature components use. Lookup tables used exclusively by an IBM Z Decision Support feature
are described in the documentation for each feature.
Edit each lookup table and control table to implement standards and definitions at your site. “Working
with data in tables” on page 154 describes how to edit tables.
Lookup and control tables are particularly important for reporting availability of resources. Discuss
availability reporting with your users to determine necessary changes to these tables.

110 IBM Z Decision Support : Administration Guide and Reference

 Administering reports

Administering reports

About this task

As an IBM Z Decision Support administrator, you have authority to run all frequently requested reports in
batch mode and distribute them regularly. You can also create report groups that suit your organization.

Running reports in batch

About this task

You can generate reports using the reporting dialog. For more information, refer to the Guide to Reporting.
However, for frequently requested reports, you should set up jobs that produce the reports regularly.
The steps to do this are as follows:

Procedure
1. Specify batch settings for the reports.
2. Define queries and forms suitable for batch reports.
3. Print reports or save them in data sets, using a batch job or the reporting dialog.
4. Optionally, save the reports for reporting dialog users and regularly replace the saved report data with
new data.

Specifying batch settings

Use the Set batch option in the Batch pull-down in the reporting dialog to specify the batch settings for a
report. Batch settings include output options and other options.

Understanding output options for batch reports

There are two output options for batch reports:
• Print the report:
– If your installation uses QMF, tabular reports are printed to the DSQPRINT file. Otherwise they are
printed to the DRLPRINT file.
– Graphic reports are printed to the printer specified in the job (or to the default printer defined in the
QMF profile, if no printer is specified).
The printer name must be defined in the GDDM nicknames file, allocated to the ADMDEFS ddname.
Refer to the QMF: Planning and Administration Guide for MVS and the GDDM User's Guide for more
information about defining GDDM nicknames.
If you do not use QMF, all reports are printed in tabular format. If you require graphic reports, you can
print a saved report with GDDM-PGF or other tools.
• Save the report in a data set:
– Tabular reports are saved in the data set defined by the DRLREP ddname, usually
DRL.LOCAL.REPORTS.
– Graphic reports are saved in the data set defined by the ADMGDF ddname, usually
DRL.LOCAL.CHARTS.
Saved reports serve different purposes:
– Set up the reporting dialog to use it to look at saved reports.
– Display the reports in other ways, such as from user-written applications.

Chapter 4. Administering IBM Z Decision Support 111

Administering reports

Defining report queries and forms for batch execution

Although all IBM Z Decision Support reports can be run in batch, most of them are not suited for batch
because you must supply values for all the variables in the queries and forms.
For example, a typical query looks like this:

SELECT column1, column2, ...

FROM table
WHERE DATE >= &FROM_DATE.
AND DATE <= &TO_DATE.
AND SYSTEM_ID = &SYSTEM_ID.

When displayed from the dialog, IBM Z Decision Support prompts you for values for FROM_DATE,
TO_DATE, and SYSTEM_ID. To run the report in batch, you must supply the values in the job and you
must change them when you want the reports to cover a different period.
You can change the query to require no variables and always cover the last week:

SELECT SYSTEM_ID, column1, column2, ...

FROM table
WHERE DATE >= CURRENT DATE - 7 DAYS

Refer to the Guide to Reporting for a description of how to create a query.

If the form used contains variables other than the standard variables REPORT_TITLE, PRODUCT_NAME,
and REPORT_ID, you must make sure that these variables are set in the batch reporting job, or modify the
form. Refer to the Guide to Reporting for a description of how to create and modify forms.

Using job DRLJBATR to run reports in batch

The sample job DRLJBATR in the SDRLCNTL library produces all, or a subset, of the reports that have
batch settings specified.
“DRLJBATR job for printing or saving reports in batch” on page 112 shows DRLJBATR.
You need to change some parameters in DRLJBATR to your requirements. For a description of those
parameters, see Table 7 on page 115.
DRLJBATR job for printing or saving reports in batch

//DRLJBATR JOB (ACCT#),'REPORTS'

//* *
//* Function: *
//* IBM Z Decision Support batch reporting sample job. *
//* *
//* This job is used to print and/or save all (or a selected *
//* subset of) the batch reports. *
//* *
//* Reports printed to : DSQPRINT with QMF (tables) *
//* DRLPRINT w/o QMF (tables) *
//* printer specified (charts) *
//* Reports saved in : DRLREP (tables) *
//* ADMGDF (charts) *
//* Messages written to: DRLOUT *
//* *
//* The exec DRLEBATR accepts the following parameters: *
//* *
//* SYSTEM=DB2_system Db2 subsystem name. The default is DSN *
//* SYSPREFIX=sysprefix Prefix for TDSzOS system *
//* tables. The default is DRLSYS. *
//* PREFIX=prefix Prefix for all other tables. The default *
//* is DRL. *
//* SHOWSQL=YES/NO Show SQL statements (for debugging). *
//* YES or NO. The default is NO. *
//* CYCLE=run_cycle Run cycle: DAILY, WEEKLY or MONTHLY. *
//* If not specified, all reports are printed.*
//* GROUP=report_group Report group. If not specified, all *
//* reports are printed. *
//* REPORT=rpt1,rpt2.. Lists the reports to print. If not speci- *
//* fied, all reports are printed. *
//* PRINTER=prt_name Printer to be used for graphic reports. *
//* The default printer is defined in the QMF *
//* profile. *

112 IBM Z Decision Support : Administration Guide and Reference

 Administering reports

//* DIALLANG=n Define the application language. *

//* n=1 for English (default) *
//* n=2 for German *
//* n=3 for Japanese *
//* QMF=YES/NO Report generation with or *
//* w/o QMF. YES or NO. Default is YES. *
//* GDDM=YES/NO GDDM available for graphic *
//* reports. YES or NO. Default is YES. *
//* DRLMAX=nnnn Max number of result rows from *
//* a query w/o QMF. Default is 5000. *
//* PAGELEN=nn Page length used when printing *
//* tabular reports w/o QMF. Default is 60. *
//* PAGE=PAGE This word is used in the report *
//* footing for page numbering tabular *
//* reports w/o QMF. Default is PAGE *
//* TOTAL=TOTAL This word is used for an across *
//* summary column header in tabular *
//* reports w/o QMF. Default is TOTAL *
//* DECSEP=PERIOD PERIOD/COMMA. Decimal separator *
//* setting for tabular reports without QMF. *
//* DUALSAVE=xxx Allow graphic reports to be saved *
//* as tabular reports simultaneously. *
//* YES/NO (default=NO) *
//* &variable=value Give a value to a variable used in a *
//* query or a form. All variables used in *
//* queries or forms MUST be given a value. *
//* '' = all values for that variable *
//* '''''' means the null value. *
//* NB: for variables used with IN operator *
//* '(''x'') OR (1=1)' = all values *
//* PRODNAME=IBM Z Decision Suppo *
//* This text is used in the report footing. *
//* The default is TDSzOS *
//* Note: If specified, PRODNAME must be the *
//* last parameter. *
//* *
//* Notes: *
//* Before you submit the job, do the following: *
//* 1. Check that the data set names are correct. Update 'DRLvrm' *
//* to match your HLQ for IZDS data sets. *
//* 2. Change the parameters to DRLEBATR as required. *
//* 3. Remove QMF DD-statements if you are not using QMF. *
//* Search on 'DSQ' to find such occurrences. *
//* The exception is DSQUCFRM, which should be changed *
//* to DRLUFORM. The data set name should point to the *
//* user defined forms library. *
//* 4. Change the Db2 load library name according to *
//* the naming convention of your installation. *
//* Default is 'db2loadlibrary'. *
//* *
//********************************************************************
//REPORT EXEC PGM=IKJEFT01
//*
//STEPLIB DD DISP=SHR,DSN=DRLvrm.SDRLLOAD
// DD DISP=SHR,DSN=qmfloadlibrary
// DD DISP=SHR,DSN=db2loadlibrary
//SYSPROC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC
// DD DISP=SHR,DSN=qmfclistlibrary
//SYSEXEC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC
// DD DISP=SHR,DSN=qmfexeclibrary
//*********************
//* MESSAGES
//*
//DRLOUT DD SYSOUT=*
//*********************
//* PRINT REPORTS TO EITHER DSQPRINT OR DRLPRINT
//*
//DSQPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)
//DRLPRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)
//*********************
//* SAVE REPORTS IN
//*
//DRLREP DD DISP=SHR,DSN=DRL.LOCAL.REPORTS
//ADMGDF DD DISP=SHR,DSN=DRL.LOCAL.CHARTS
//*********************
//* GDDM LIBRARIES
//*
//ADMGGMAP DD DISP=SHR,DSN=ADMGGMAPlibrary
//ADMCFORM DD DISP=SHR,DSN=ADMCFORMlibrary
// DD DISP=SHR,DSN=DRLvrm.SDRLFENU
//ADMSYMBL DD DISP=SHR,DSN=SYS1.GDDMSYM
//ADMDEFS DD DISP=SHR,DSN=SYS1.GDDMNICK

Chapter 4. Administering IBM Z Decision Support 113

Administering reports

//*ADMPRNTQ DD DISP=SHR,DSN=ADMPRINT.REQUEST.QUEUE
//DSQUCFRM DD DISP=SHR,DSN=DRLvrm.SDRLFENU
//*********************
//* QMF LIBRARIES
//*
//DSQDEBUG DD DUMMY
//DSQUDUMP DD DUMMY
//DSQPNL DD DISP=SHR,DSN=QMFDSQPNLxlibrary
//DSQSPILL DD DSN=&&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096)
//DSQEDIT DD DSN=&&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE),
// DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029)
//DRLFORM DD DSN=&&FORMDS,UNIT=SYSDA,SPACE=(TRK,(5,5),RLSE),
// DCB=(RECFM=VB,LRECL=255,BLKSIZE=2600),DISP=(NEW,DELETE)
//**********************
//* START EXEC DRLEBATR
//*
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLEBATR SYSTEM=DSN SYSPREFIX=DRLSYS PREFIX=DRL -
PRINTER=XXX -
REPORT=XXXXXXXX,YYYYYYYY -
&SYSTEM_ID='SYS1' -
&FROM_DATE='1993-01-01' -
&TO_DATE='1993-04-01' -
DIALLANG=1 -
PRODNAME=IBM Z Decision Suppo
/*
//*********************
//* GDDM LIBRARIES
//*
//ADMGGMAP DD DISP=SHR,DSN=ADMGGMAPlibrary
//ADMCFORM DD DISP=SHR,DSN=ADMCFORMlibrary
// DD DISP=SHR,DSN=DRLvrm.SDRLFENU
//ADMSYMBL DD DISP=SHR,DSN=SYS1.GDDMSYM
//ADMDEFS DD DISP=SHR,DSN=SYS1.GDDMNICK
//*ADMPRNTQ DD DISP=SHR,DSN=ADMPRINT.REQUEST.QUEUE
//DSQUCFRM DD DISP=SHR,DSN=DRLvrm.SDRLFENU
//*********************
//* QMF LIBRARIES
//*
//DSQDEBUG DD DUMMY
//DSQUDUMP DD DUMMY
//DSQPNL DD DISP=SHR,DSN=QMFDSQPNLxlibrary
//DSQSPILL DD DSN=&&SPILL,DISP=(NEW,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(1,1),RLSE),DCB=(RECFM=F,LRECL=4096,BLKSIZE=4096)
//DSQEDIT DD DSN=&&EDIT,UNIT=SYSDA,SPACE=(CYL,(1,1),RLSE),
// DCB=(RECFM=FBA,LRECL=79,BLKSIZE=4029)
//DRLFORM DD DSN=&&FORMDS,UNIT=SYSDA,SPACE=(TRK,(5,5),RLSE),
// DCB=(RECFM=VB,LRECL=255,BLKSIZE=2600),DISP=(NEW,DELETE)
//**********************
//* START EXEC DRLEBATR
//*
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLEBATR SYSTEM=DSN SYSPREFIX=DRLSYS PREFIX=DRL -
PRINTER=XXX -
REPORT=XXXXXXXX,YYYYYYYY -
&SYSTEM_ID='SYS1' -
&FROM_DATE='1993-01-01' -
&TO_DATE='1993-04-01' -
DIALLANG=1 -
PRODNAME=IBM Z Decision Suppo
/*

Using the reporting dialog to run reports in batch

To create reports in batch from the reporting dialog:
1. From the IBM Z Decision Support Administration window, select 5, Reports, and press Enter to display
the Reports window.
2. Without selecting any reports in the IBM Z Decision Support Reports window, select the Invoke batch
option from the Batch pull-down. The Batch Reports Selection window is displayed.
3. Type required information, such as whether to run daily, weekly, or monthly reports, and press Enter. If
any of the reports contain variables, the Batch Reports Data Selection window is displayed.

114 IBM Z Decision Support : Administration Guide and Reference

 Administering reports

4. Specify values to select the data to be reported, and press Enter to display the job.
5. Edit the job, specifying the parameters described in “Parameters for batch reporting” on page 115.
Then type SUBMIT on the command line, and press Enter.
IBM Z Decision Support submits your job to run in background.
6. Press F3 to return to the Reports window.
Refer to the Guide to Reporting for more information about running reports in batch.

Parameters for batch reporting

Table 7. Parameters for batch reporting

Parameter Value to set Explanation Default value Your value

SYSTEM Db2 subsystem name The Db2 subsystem where IBM Z Decision Support DSN
(UPPERCASE) resides.
This required parameter can be 4 alphanumeric
characters. The first character must be alphabetic.
The default value is DSN. If the value in this field is
something other than DSN, it was changed during
installation to name the correct Db2 subsystem.
Do not change the value to name another Db2
subsystem to which you might have access. IBM
Z Decision Support must use the Db2 subsystem
that contains its system, control, and data tables.

SYSPREFIX Prefix for system The prefix of all IBM Z Decision Support system DRLSYS
tables (UPPERCASE) and control Db2 tables. The value of this field
depends upon your naming conventions and is
determined during installation.
This required parameter can be 8 alphanumeric
characters. The first character must be alphabetic.
The default is DRLSYS. If the value is something
other than DRLSYS, it was changed during
installation.
Do not change the value; IBM Z Decision Support
uses this value to access its system tables.

PREFIX Prefix for all other The prefix of IBM Z Decision Support data tables in DRL
tables (UPPERCASE) the Db2 database.
Valid values are determined at installation.
This required parameter can be 8 alphanumeric
characters. The first character must be alphabetic.
The default is DRL. If the value is something other
than DRL, it was changed during installation.

SHOWSQL YES or NO Here you specify if SQL statements should be NO

(UPPERCASE) shown (for debugging purposes).

CYCLE DAILY, WEEKLY The run cycle for reports. If you do not specify All reports
or MONTHLY daily, weekly, or monthly, all reports are printed.
(UPPERCASE)

GROUP A report group ID Here you can specify the ID of a report group. If All reports
(UPPERCASE) you do not specify a group, all reports are printed.

REPORT One or more report Here you can specify one or more reports to be All reports
IDs (UPPERCASE) printed. If you do not specify any reports, all
reports are printed.

Chapter 4. Administering IBM Z Decision Support 115

Administering reports

Table 7. Parameters for batch reporting (continued)

Parameter Value to set Explanation Default value Your value

PRINTER Default printer name The GDDM nickname of a printer to use for printing As defined in the
(UPPERCASE) graphic reports. The printer should be capable of QMF profile
printing GDDM-based graphics.
The printer name must be defined in the GDDM
nicknames file, allocated to the ADMDEFS ddname.
Refer to the QMF: Reference and GDDM User's
Guide for more information about defining GDDM
nicknames.
This parameter cannot be used if QMF=NO.

DIALLANG 1. English With this parameter, you specify the language to be 1=English
used.
2. Japanese

QMF YES or NO With this parameter, you specify whether your YES
(UPPERCASE) installation uses QMF or not.

GDDM YES or NO With this parameter, you specify if your installation YES
(UPPERCASE) uses GDDM.

DRLMAX nnnn If your installation does not use QMF, you use 5000
this parameter to specify the maximum number of
result rows from a query.

PAGELEN nn If your installation does not use QMF, you use this 60
parameter to specify the page length when printing
tabular reports.

PAGE The word for page If your installation does not use QMF, the word you PAGE
(Mixed case) specify here is inserted before the page number for
tabular reports.
You can type the word in mixed case, for example,
Page.

TOTAL The word for total If your installation does not use QMF, the word you TOTAL
(Mixed case) specify here is used as column heading for across
summary columns in tabular reports.
You can type the word in mixed case, for example,
Total.

DECSEP Period or comma If your installation does not use QMF, you use this PERIOD
parameter to specify the decimal separator to be
used in tabular reports. If you use a comma as a
decimal separator, a period is used as thousands
separator, if applicable.

DUALSAVE YES or NO Allow graphic reports to be saved as tabular NO

(UPPERCASE) reports simultaneously.

&variable A value This parameter gives a value to a variable used in

a query or form. All variables used in queries or
forms must be given a value.

PRODNAME IBM Z Decision This text is used in the report footer. If specified, IBM Z Decision
Support Report PRODNAME must be the last parameter. Support Report
(Mixed case)

Saving reports for reporting dialog users

You can save report data from a reporting job like DRLJBATR. Creating reports for batch preprocessing
and then saving them for end users means:
• Users need not access the IBM Z Decision Support database if they have access to current reports
instead.
• Users need not take the time to run reports.
• Users have the data they need to begin analysis immediately.

116 IBM Z Decision Support : Administration Guide and Reference

 Administering problem records

To preprocess reports for dialog users:

1. Define the batch report as described in “Specifying batch settings” on page 111.
2. Select the batch report and select 4, Save report data, from the Reports pull-down. The Saved Report
Definition window is displayed. Refer to the Guide to Reporting for information about defining saved
reports in the Saved Report Definition window.
3. After completing all fields in the Saved Report Definition window, press Enter.
The report is run and saved in the specified member.
4. Add the saved report to a report group, such as Monthly Management Reports, to let users display
relevant reports easily.
Refer to the Guide to Reporting for information about adding a report to a report group.
After you complete the steps above, you can run the batch report periodically (using the DRLJBATR job) to
replace the saved report member with up-to-date information.

QMF batch reporting

Batch reporting can also be performed with QMF only, without using IBM Z Decision Support functions. A
QMF job can simply execute a QMF procedure that contains QMF commands (Figure 42 on page 117).

RUN QUERY1 (FORM=FORM1

PRINT REPORT
RUN QUERY2 (FORM=FORM2
PRINT REPORT (PRINTER=LOCAL1

Figure 42. Using QMF to report in batch

These books contain more information about using QMF in this way:
• QMF Advanced User's Guide
• QMF Reference

Creating report groups

About this task

IBM Z Decision Support reports are grouped by component within each feature. Placing more commonly
requested reports in new report groups can make retrieving them easier. Creating report groups for users
with special requirements, such as managers, also makes reporting more effective.
Refer to the Guide to Reporting for information about creating report groups.

Administering problem records

About this task

The update definitions of some IBM Z Decision Support components update the common table,
EXCEPTION_T, with data about system exceptions that require attention. Review this information and
use the product interface for adding selected exceptions to the IBM Tivoli Information Management for
z/OS database.
You can review exceptions only through the administration dialog. You can generate problem records with
either the dialog or a job.

Reviewing exceptions and generating problem records

About this task

To review exceptions and generate problem records:

Chapter 4. Administering IBM Z Decision Support 117

Administering problem records

Procedure
1. Select 2, Generate problem records, from the Utilities pull-down of the IBM Z Decision Support
Administration window and press Enter.
The Exception Selection window is displayed.
2. Type 2, No, in the Problems only field to list all exception records.
Note: The default update definitions do not classify exceptions as problems. You can modify them to
set the problem flag (column PROBLEM_FLAG='Y' in the EXCEPTION_T table).
3. Type 1, Yes, in the Not generated only field to select exception records that have not yet been
generated as problem records in the IBM Tivoli Information Management for z/OS database.
4. Select values for other required fields in the window.
Use the fields to restrict the number of exceptions in the list of exceptions.
Use F4 (Prompt) to see a selection list for any field in the Exception Selection window.
5. Press Enter to see the list of exceptions.
The Exception List window is displayed.
6. Select an exception and press Enter
The Generate Record window is displayed, showing the exception record in detail.
7. If the exception record is one you want to add to the IBM Tivoli Information Management for z/OS
database, press Enter.
IBM Z Decision Support generates the problem record.

Generating problem records in batch

About this task

Although the sample job, DRLJEXCE (in the hlq.SDRLCNTL library) does not let you review exception
records, it generates problem records in the IBM Z Decision Support database only from EXCEPTION_T
records defined as problems.
Note: You must customize the product update definitions that add records to EXCEPTION_T to set the
problem flag column.
DRLJEXCE job for generating problem records

//DRLJEXCE JOB (ACCT#),'EXCEPTION REPORTING'

//*********************************************************************
//* *
//* FUNCTION: EXCEPTION REPORTING. *
//* PROBLEM RECORDS ARE GENERATED BY TIVOLI SERVICE DESK *
//* FOR ALL RECORDS IN THE EXCEPTION TABLE (EXCEPTION_T), *
//* WHERE *
//* A) THE PROBLEM_FLAG COLUMN INDICATES THAT THIS RECORD *
//* IS A PROBLEM RECORD (PROBLEM_FLAG='Y') *
//* B) AND THE DATE_GENERATED COLUMN INDICATES THAT THE *
//* TIVOLI SERVICE DESK DATABASE HAS NOT BEEN UPDATED *
//* WITH THIS RECORD (DATE_GENERATED IS NULL). *
//* *
//* INPUT PARAMETERS: *
//* SYSTEM=Db2-SUBSYSTEM Db2 SUBSYSTEM (DEFAULT=DSN) *
//* PREFIX=PREFIX TABLE PREFIX (DEFAULT=DRL) *
//* MODE=BATCH BATCH/ONLINE (DEFAULT=BATCH) *
//* APPLID=XXXXXXX APPLICATION ID (DEFAULT=SYSUID) *
//* SESSMBR=XXXXXXX SESSION MEMBER (DEFAULT=BLGSES00) *
//* PRIVCLASS=XXXXXXX PRIVILEGE CLASS (DEFAULT=MASTER) *
//* *
//* OUTPUT: - PROBLEM RECORD(S) CREATED IN TIVOLI SERVICE DESK. *
//* - TABLE EXCEPTION_T UPDATED WITH PROBLEM NUMBER *
//* AND DATE GENERATED. *
//* - RESULT FILE WRITTEN TO FILE DEFINED BY DRLOUT DD. *
//* *
//* NOTES: BEFORE YOU SUBMIT THIS JOB, DO THE FOLLOWING: *
//* 1. ENSURE THAT YOU (OR THE VALUE SPECIFIED BY APPLID) ARE *

118 IBM Z Decision Support : Administration Guide and Reference

 Administering problem records

//* REGISTERED AS A VALID APPLICATION ID IN TIVOLI SERVICE DESK.*

//* 2. CHECK THAT THE DATASET NAMES ARE CORRECT. *
//* 3. CHANGE THE PARAMETERS TO DRLEREGE AS REQUIRED. *
//* 4. Change the Db2 load library name according to *
//* the naming convention of your installation. *
//* Default is 'db2loadlibrary'. *
//* *
//*********************************************************************
//*
//EPDMEXCE EXEC PGM=IKJEFT01,DYNAMNBR=25
//STEPLIB DD DISP=SHR,DSN=TSD.SBLMMOD1
// DD DISP=SHR,DSN=DRLvrm.SDRLLOAD
// DD DISP=SHR,DSN=db2loadlibrary
//SYSPROC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC
//*------------------------------------------------------------------*
//* TIVOLI SERVICE DESK LIBRARIES *
//*------------------------------------------------------------------*
//BLGSD DD DISP=SHR,DSN=TSD.SDDS
//BLGSI DD DISP=SHR,DSN=TSD.SDIDS
//BLGSL DD DISP=SHR,DSN=TSD.SDLDS
//BLGPNL0 DD DISP=SHR,DSN=TSD.IBMPNLS
//BLGPNL1 DD DISP=SHR,DSN=TSD.RPANEL1
//BLMFMT DD DISP=SHR,DSN=TSD.BLMFMT
//ISPLLIB DD DISP=SHR,DSN=TSD.SBLMMOD1
//*------------------------------------------------------------------*
//DRLOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLEREGE SYSTEM=DSN PREFIX=DRL MODE=BATCH
/*

Working with components

This section describes how to use the administration dialog to work with components. After reading this
section, you should be familiar with these tasks:
• “Installing a component” on page 120
• “Uninstalling a component” on page 127
• “Working with a component definition” on page 129
In IBM Z Decision Support, a component refers to a logical group of objects used to collect log data from
a specific source, to update the product database using that data, and to create reports from data in the
database. Grouping objects into a component enables you to:
• Install or remove (uninstall) a set of related objects as a package
• View and work with a set of related objects
Each IBM Z Decision Support component can include:
• Log collector definitions for:
– Log types
– Log procedures
– Record types in log data sets
– Record procedures
– Update definitions
• SQL statements that define these Db2 objects for the component:
– Table spaces
– Tables
– Lookup tables
– Views
• Report definitions for the component:
– Report groups

Chapter 4. Administering IBM Z Decision Support 119

Installing and uninstalling a component

– Reports
Each IBM Z Decision Support Key Performance Metrics (KPM) component also includes table space
profiles. Refer to the following section on working with table space profiles before installing any of the Key
Performance Metrics components.
Definition members in product libraries contain component object definitions. You can use the
administration dialog to examine statements in these definitions. For an explanation of the statements,
see the Language Guide and Reference.
You can use the administration dialog to work with components. From the Administration window (see
Figure 6 on page 7), select 2, Components, and press Enter.
The Components window is displayed.

Installing and uninstalling a component

The Components window lists the components available for IBM Z Decision Support installation on your
system. When you install a component, IBM Z Decision Support executes definitions in the component to
define all its objects. Then you can use the component to collect, store, and create reports on log data
that it supports.
If you no longer need a component, you can use the administration dialog to uninstall it. When you
uninstall a component, the product deletes from its system tables all objects in that component that are
not used by any other installed component. It also deletes all of the component's Db2 objects, including
tables and table spaces. The data sets that contain object definition statements are still available, so
you can reinstall the component if necessary. The component still appears in the list in the Components
window. “Uninstalling a component” on page 127 describes this procedure.

Installing a component

Procedure
1. Refer to these books to plan the tasks you must perform to complete the installation:
Feature
Book name
AS⁄400 Performance
AS/400 System Performance Feature Guide and Reference
CICS Performance
CICS Performance Feature Guide and Reference
Distributed Systems Performance
Distributed Systems Performance Feature Guide and Reference
IMS Performance
IMS CSQ Feature Guide and Reference
System Performance
System Performance Feature Guide
Resource Accounting
Resource Accounting for z/OS
2. If you want to review Db2 parameters before installing a component, select the component in the
Components window, and select Space, as shown in Figure 43 on page 121.

120 IBM Z Decision Support : Administration Guide and Reference

 Installing and uninstalling a component

Component Space Other Help

1. Tablespaces omponents Row 1 to 21 of 49

2. Indexes
Select one en press Enter to Open component.

/ Components Status Date

Sample Component Installed 02-04-26
CICS Monitoring Component
s CICS Statistics Component
. CICS Transaction and UOW Analysis Component
.
.

Figure 43. Space pull-down

You can use this pull-down to review and change Db2 space parameters such as:
• Buffer pool
• Compression
• Erase on deletion
• Free space
• Lock size
• Number of partitions, for a partitioned space
• Number of subpages, for an index space
• Primary and secondary space
• Segment size
• Type of space
• VSAM data set password
These parameters can affect the performance of your system. If you are unsure how these parameters
affect your system, you are recommended to use the defaults provided with the product. If you are
unsure about the meaning of a field, press F1 to get help. You should also refer to the CREATE INDEX
and CREATE TABLESPACE command descriptions in the Db2 documentation.
IBM Z Decision Support saves the changed definitions in your local definitions library. When you save
a changed definition, it tells you where it is saving it, and prompts you for a confirmation before
overwriting a member with the same name.
3. From the Components window, select the component to install and press F6 (Install).
If the component you selected contains subcomponents, the Component Parts window is displayed.
Either select the subcomponents to install or press F12 to install only those objects that are not in
a subcomponent. (IBM Z Decision Support might install some common definitions for the component
even though you do not select any of the parts to install.)
The Installation Options window is displayed.

Chapter 4. Administering IBM Z Decision Support 121

Installing and uninstalling a component

Component Space Other Help

Installation Options TO 30 OF 48

S Select one of the following. Then press Enter.

/ 1. Online Date
/ 2. Batch
– F1=Help F2=Split F6=Objects F9=Swap F12=Cancel
–
/ RACF Component
– Sample Component
– Storage Management Component
– VM Accounting Component
– VM Performance Component
******************************** BOTTOM OF DATA **********************************

Command ===>
F1=Help F2=Split F3=Exit F5=New F6=Install F7=Bkwd
F8=Fwd F9=Swap F10=Actions F12=Cancel

Figure 44. Installation Options window

4. From the Installation Options window, decide whether to install the component online or in batch
mode.
From the Installation Options window, you can press F6 (Objects) to see a list of objects in the
component. This gives you some idea of its size.
Batch installation leaves an audit trail of what it has done in its spooled output.
Installing a component locks write access to the database, whether you choose online or batch
installation. While batch installation occurs, you can use IBM Z Decision Support to do anything but
update a table in the IBM Z Decision Support database. You can also use your terminal to perform any
ISPF or TSO task.
5. Select 1 (online) or 2 (batch) and press Enter.
If installing the component online, see the next section, “Installing the component online” on page
122.
If installing the component in batch mode, see “Installing the component in batch mode” on page 124.

Installing the component online

About this task

IBM Z Decision Support runs the SQL, log collector, and report definition statements to create the objects
in the component. The resulting messages are displayed in a browse window:

Procedure
1. If the return code is greater than 0, investigate the messages. For example, the following message
indicates a problem accessing the database. Db2 messages are described in Db2 for z/OS: Messages. If
you get this message, you must reinstall the component:

DSNT408I SQLCODE = -911, ERROR: THE CURRENT UNIT OF WORK HAS

BEEN ROLLED BACK DUE TO DEADLOCK OR TIMEOUT. REASON
00C9008E, TYPE OF RESOURCE 00000100, AND RESOURCE
NAME DRLDB

Correct any error conditions that the product discovers, and install the component again. If the return
code is 8 or lower, the status of the component status is Installed.

122 IBM Z Decision Support : Administration Guide and Reference

 Installing and uninstalling a component

If there are no Db2 messages, userid.DRLOUT can look like Figure 45 on page 123.

Db2 Messages
SQL statements executed successfully
--------------------------------------------------------------------------

Line Log Collector Messages

--------------------------------------------------------------------------
93
DRL0125I The record SMF_080 is defined.
96
DRL0130I The comment is stored for the record SMF_080.
1007
DRL0201I The update RACFCOMMAND_80 is defined.
1014
DRL0403I The purge condition for DRL .RACF_COMMAND_T is added.
1138
DRL0201I The update RACFLOGON_80 is defined.
1145
DRL0403I The purge condition for DRL .RACF_LOGON_T is added.
1293
DRL0201I The update RACFOPERATION_80 is defined.
1300
DRL0403I The purge condition for DRL .RACF_OPERATION_T is added.
1466
DRL0201I The update RACFRESOURCE_80 is defined.
1473
DRL0403I The purge condition for DRL .RACF_RESOURCE_T is added.

Line Report Definition Messages

--------------------------------------------------------------------------
1503
DRL3001I The group RACF is defined.
1511
DRL3001I The report RACF01 is defined.
1519
DRL3001I The report RACF02 is defined.
1527
DRL3001I The report RACF03 is defined.
1535
DRL3001I The report RACF04 is defined.
1543
DRL3001I The report RACF05 is defined.
1551
DRL3001I The report RACF06 is defined.
1559
DRL3001I The report RACF07 is defined.
--------------------------------------------------------------------------

Figure 45. Sample log collector messages

2. When you finish browsing the output data set, press F3 (Exit).
If the component has lookup tables, the Lookup Tables window is displayed (“Installing the
component online” on page 122).

Chapter 4. Administering IBM Z Decision Support 123

Installing and uninstalling a component

Component Space Other Help

Lookup Tables ROW 1 TO 3 OF 3

Select a lookup table. Then press Enter to Edit the table in ISPF Edit
mode.

/ Lookup table
– RACF_EVENT_CODE
– RACF_RES_OWNER
– RACF_USER_OWNER
**************************** BOTTOM OF DATA *****************************

Command ===>
F1=Help F2=Split F5=QMF add F6=QMF chg F7=Bkwd F8=Fwd
F9=Swap F12=Cancel

– VM Accounting Component
– VM Performance Component

Command ===>
F1=Help F2=Split F3=Exit F5=New F6=Install F7=Bkwd
F8=Fwd F9=Swap F10=Actions F12=Cancel

Figure 46. Lookup Tables window

Refer to the appropriate feature book (shown in “Installing a component” on page 120) for a
description of its component lookup tables and how you must edit them.
3. To edit a lookup table using ISPF edit, select a table, and press Enter.
IBM Z Decision Support accesses the ISPF editor where you can edit the lookup table as described in
“Editing the contents of a table” on page 155.
If you have QMF installed, you can use the QMF table editor to edit tables wider than 255 characters.
If the table has more rows than the value you set for the SQLMAX value field in the Dialog Parameters
window, IBM Z Decision Support prompts you to temporarily override the default for this edit session.
To edit a lookup table using the QMF table editor in add mode, press F5 (QMF add). To edit a lookup
table using the QMF table editor in change mode, press F6 (QMF chg). “Editing the contents of a table”
on page 155 also describes using QMF to edit tables.
4. After you make any necessary changes to a lookup table, press F3 (Exit) to save your changes.
IBM Z Decision Support returns to the Lookup Tables window.
5. Edit any other lookup tables that the component requires.
When you finish, the installation is complete.
6. Press F12 (Cancel).
IBM Z Decision Support returns to the Components window.
The product has changed the Status field for the component to read Installed.
7. Press F3 (Exit).
The product returns to the Administration window.

Installing the component in batch mode

About this task

IBM Z Decision Support builds a batch job to run the SQL, log collector, and report definition statements
to create the objects in the component. It then initiates an ISPF edit session. You may have to edit the
JCL, for example, to change the job card. Figure 47 on page 125 shows a job in an ISPF edit session.

124 IBM Z Decision Support : Administration Guide and Reference

 Installing and uninstalling a component

EDIT ---- XLLOYDA.SPFTEMP2.CNTL -------------------------------COLUMNS 001 072

***************************** TOP OF DATA ******************************

//XLLOYDAA JOB (ACCOUNT),'NAME'
//*
//*
//*
//RUNLOG EXEC PGM=DRLPLC,
// PARM=('SYSTEM=DSN SYSPREFIX=DRLSYS &PREFIX=DRL',
// '&DATABASE=DRLDB &STOGROUP=DRLSG')
//STEPLIB DD DISP=SHR,DSN=DRLxxx.SDRLLOAD
// DD DISP=SHR,DSN=DSNxxx.SDSNLOAD
//DRLLOG DD DUMMY
//DRLOUT DD DSNAME=&TEMP,UNIT=SYSDA,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(CYL,(10,2)),DISP=(NEW,PASS)
//DRLDUMP DD SYSOUT=*,DCB=BLKSIZE=6160
//DRLIN DD *
SQL SET CURRENT SQLID='DRL';
SET USERS='DRLUSER';
// DD DSN=DRLxxx.SDRLDEFS(DRLRS080),DISP=SHR
COMMAND ===> submit SCROLL ===> 0020
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE

Figure 47. Editing an installation job

After editing the job:

Procedure
1. Type SUBMIT on the command line and press Enter.
2. Press F3 after submitting the job.
IBM Z Decision Support returns to the Components window. The Status field shows Batch which
does not mean that the job completed, or that it completed successfully. The installation job changes
the value to Installed at its successful completion.
3. When the job completes, use a tool such as the Spool Display and Search Facility (SDSF) to look at
the job spool.
4. Review messages for errors as described in step “1” on page 122.
5. Exit SDSF (or whatever tool you are using to review the job spool).
6. Exit the Components window.
7. Refer to the book for the appropriate feature for a description of the component lookup tables you
must edit.
8. Select 4, Tables, from the Administration window.
The Tables window is displayed.
9. Select 2, Some, from the View pull-down.
The Select Table window is displayed (Figure 48 on page 126).

Chapter 4. Administering IBM Z Decision Support 125

Installing and uninstalling a component

Table Maintenance Utilities Edit View Other Help

Tables ROW 1 TO 13 OF 393

S Select Table

/ Type in the selection criteria. Then press Enter to display.

–
–
– Component RACF Component +
* *
Name
Prefix
Type 2 1. Table
2. Lookup
3. View

F1=Help F2=Split F4=Prompt F9=Swap F12=Cancel

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

Figure 48. Select Table window

10. Type the values as shown in Figure 48 on page 126, and press Enter.
The Tables window is displayed (Figure 49 on page 126), showing the component's lookup tables
only.

Table Maintenance Utilities Edit View Other Help

Tables ROW 1 TO 3 OF 3

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

/ Tables Prefix Type

– RACF_EVENT_CODE DRL TABLE
– RACF_RES_OWNER DRL TABLE
/ RACF_USER_OWNER DRL TABLE
**************************** BOTTOM OF DATA *****************************

Objects of type Tables meeting the selection criteria are listed.

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

Figure 49. Tables window - showing component's lookup tables

11. Select a table to edit, but do not press Enter.
12. Select an edit option from the Edit pull-down and press Enter.
If you have QMF installed, you can use the QMF table editor to edit tables wider than 255 characters.
See “Editing the contents of a table” on page 155.
13. Press F3 (Exit) when you finish selecting and editing lookup tables.
IBM Z Decision Support returns to the Administration window.
When the installation of a component ends with an error or warning, and RC=4 or RC=8, this does not
necessarily indicate a problem. The following table shows when you can ignore these messages and
return codes.

126 IBM Z Decision Support : Administration Guide and Reference

 Installing and uninstalling a component

Message Return Code Explanation

SQLCODE=-204 name IS AN RC=8 You can ignore this message and return
UNDEFINED NAME code only if it is caused by an SQL ALTER
statement that attempts to add a column to
a table that has not yet been created.
SQLCODE=+562 A GRANT OF RC=4 You can always ignore this message and
A PRIVILEGE WAS IGNORED return code.
BECAUSE THE GRANTEE ALREADY
HAS THE PRIVILEGE FROM THE
GRANTOR
SQLCODE=-601 THE NAME OF RC=8 You can always ignore this message and
THE OBJECT TO BE CREATED IS return code.
IDENTICAL TO THE EXISTING
NAME name OF THE OBJECT
TYPE objecttype
SQLCODE=-612 column name IS RC=8 You can always ignore this message and
A DUPLICATE COLUMN NAME return code.

Testing the component to verify its proper installation

Procedure
1. Collect data from a log data set and review any messages, as described in “Using collect messages” on
page 91.
Note: Depending on the component you installed, you might not be able to collect its log data in an
online collect. Refer to “Collecting data from a log into Db2 tables” on page 137 for more information.
2. Display a table to ensure that it exists and that it contains the correct information as described in the
book for the appropriate feature:
Feature name
Book name
AS⁄400 Performance
AS/400 System Performance Feature Guide and Reference
CICS Performance
CICS Performance Feature Guide and Reference
Distributed Systems Performance
Distributed Systems Performance Feature Guide and Reference
IMS Performance
IMS CSQ Feature Guide and Reference
Network Performance
Network Performance Feature Reference
System Performance
System Performance Feature Reference
For Resource Accounting, see the Resource Accounting for z/OS book.
3. Display a report to ensure it is correctly installed.

Uninstalling a component

About this task

To uninstall a component:

Chapter 4. Administering IBM Z Decision Support 127

Installing and uninstalling a component

Procedure
1. From the Components window, select the component you want to uninstall. From the Component
pull-down, select the Uninstall option.
If the component you selected contains subcomponents, the Component Parts window is displayed.
Either select the parts to uninstall or press F12 to cancel.
A confirmation window is displayed.
2. Press Enter to confirm the uninstallation.
IBM Z Decision Support deletes from its system tables any component definitions not used by other
components. It also deletes all Db2 objects of the component or selected subcomponents, including
any tables and table spaces. The component remains in the list of components, but with its Status field
cleared. If the component contains subcomponents, they remain in the list of subcomponents but with
their Status field cleared.
Note: If a component (or subcomponent) including a common object is uninstalled, the common
object is not dropped, unless it is the only installed component (or subcomponent) that includes the
common object. When a component or subcomponent is uninstalled, all its data tables are dropped
and their contents lost.

Working with table space profiles

IBM Z Decision Support provides functionality to allow you to easily create table spaces, partitioning on
tables, and indexes on tables through the use of table space profiles.
These profiles are defined in the DRLTKEYS member in your SDRLDEFS library. Two system tables named
GENERATE_PROFILES and GENERATE_KEYS are created and loaded from the DRLTKEYS definition file
during system table creation.
Default profiles are provided that set default values for all table spaces, tables, and indexes associated
with the profile. Parameters that can be customized in a profile include the partitioning method (partition
by growth, partition by range, or non-partitioned), primary, and secondary quantities, storage group
names, lock sizes, maximum number of partitions, and most other Db2 table space parameters. You can
use the same parameters for the creation of a set of table spaces, tables, and indexes by using a single
shared profile.
For more detailed information on the GENERATE_PROFILES and GENERATE_KEYS system tables, refer to
“System tables and views” on page 205

Reviewing table space profiles prior to installation

When you have created your system tables, review the parameter values in the GENERATE_PROFILES and
GENERATE_KEYS system tables using the IBM Z Decision Support table edit facility.
Modify parameters such as PRIQTY and SECQTY accordingly. Note that the GENERATE_KEYS system
table only needs to be modified if you are using the partition by range partitioning method.
Refer to “System tables and views” on page 205 for information on each column within the
GENERATE_PROFILES and GENERATE_KEYS system tables.

Creating storage groups when partitioning by range

If you modify your table space profile to partition by range, you need to run the DRLJDBIP job. The
DRLJDBIP job creates additional storage groups that are used in the partitioned table spaces of the
components where partition by range was set. Be sure to create one storage group per partition that you
identified in the GENERATE_KEYS table.
To run DRLJDBIP:
1. Copy member DRLJDBIP in the DRL190.SDRLCNTL library to the &HLQ.CNTL library.
2. Modify the job statement to run your job.

128 IBM Z Decision Support : Administration Guide and Reference

 Working with a component definition

3. Customize the job for your site. Follow the instructions in the job prolog.
4. Submit the job.
Note: A person with Db2 SYSADMIN authority (or someone who has access to the Db2 catalog) must
submit the job.

Reviewing the GENERATE statements for table spaces, tables, and indexes
Components can make use of table space profiling by using GENERATE statements when creating table
spaces, tables, and indexes.
Each GENERATE statement will refer to a profile name in the GENERATE_PROFILES and GENERATE_KEYS
system tables. Default profiles are provided for use by the supplied components. For example, the
following GENERATE statement refers to the SMF table space profile:

GENERATE TABLESPACE DRLSKD01

PROFILE 'SMF';

If you install components that use these profiles, no customizations are required in the GENERATE
statements which create the table spaces, tables, and indexes for the components.
If you want to use a different profile name, you will need to customize all the GENERATE statements
by copying the definitions members into your LOCAL.DEFS data set, and modifying the profile names
accordingly.
If you want to use the default profile names but with a different set of table space parameters, you will
need to update the GENERATE_PROFILES and GENERATE_KEYS system tables with your new table space
settings for the default profiles.
Refer to the IBM Z Decision Support Language Guide and Reference for the syntax and additional
information on using the GENERATE statements.

Working with a component definition

About this task

This section describes these tasks:
• Controlling objects that you have modified
• Viewing objects in a component
• Viewing or editing an object definition
• Adding an object to a component
• Deleting an object from a component
• Excluding an object from a component installation
• Including an object in a component installation
• Deleting a component
• Creating a component

Controlling objects that you have modified

About this task

The variable VERSION, together with the VERSION column in the system tables, is used to:
• Ensure that unchanged IBM Z Decision Support objects are not replaced when a component is migrated
• Provide for the control of IBM Z Decision Support objects that you have changed

Chapter 4. Administering IBM Z Decision Support 129

Working with a component definition

The variable VERSION has the value IBM.nnnAPAR_number, where nnn is the version, release, and
modification level. For example, IBM.190 is an object supplied with IBM Z Decision Support version 1
release 9 modification level 0. The value of VERSION is set for all objects when the object is installed (see
“How IBM Z Decision Support controls object replacement” on page 74 for details).
Important:
If you change an object supplied by IBM Z Decision Support , you must set the variable VERSION to
a custom version number as defined in “IBM Z Decision Support Version variable format” on page 74.
During component installation, the product can then recognize an object as having been modified by you.
When you select the component you wish to install (from the Components window) and press F6=Install,
the User Modified Objects window is automatically displayed, listing the supplied objects that you have
later modified.

Viewing objects in a component

About this task

You can use the administration dialog to view a list of objects in a component. To view objects in a
component:

Procedure
1. From the Components window, select the component, and press Enter.
The Component window is displayed (Figure 50 on page 130) for the component. All IBM Z Decision
Support objects in the component are listed..

SAMPLE Component ROW 1 TO 11 OF 12

Select an object. Then press Enter to Edit definition.

Description . . . . . Sample Component

Installation time . :
Installed by . . . . :

/ Object Name Object Type Member Part

_ DRLSSAMP TABSPACE DRLSSAMP
_ SAMPLE LOG DRLLSAMP
_ SAMPLE REPGROUP DRLOSAMP
_ SAMPLE_H TABLE DRLTSAMP
_ SAMPLE_H_M UPDATE DRLTSAMP
_ SAMPLE_M TABLE DRLTSAMP
_ SAMPLE_USER LOOKUP DRLTSAMP
_ SAMPLE_01 RECORD DRLRSAMP
_ SAMPLE_01_H UPDATE DRLTSAMP
_ SAMPLE01 REPORT DRLOSAMP
_ SAMPLE02 REPORT DRLOSAMP

Command ===> ____________________________________________________________

F1=Help F2=Split F3=Exit F4=Exclude F5=Add obj F7=Bkwd
F8=Fwd F9=Swap F10=View F11=Delete F12=Cancel

Figure 50. Component window

2. Press F10 to limit the list of objects displayed in the window.
The View Objects window is displayed.
3. Type selection criteria in fields in the View Objects window and press Enter.
IBM Z Decision Support returns to the Component window and shows only those objects that meet the
criteria.
4. You can choose to edit objects, add objects, or delete objects. When you finish, press F3.
IBM Z Decision Support returns to the Components window.

130 IBM Z Decision Support : Administration Guide and Reference

 Working with a component definition

Viewing or editing an object definition

About this task

Before you modify any data set that contains IBM Z Decision Support definitions, copy the member to
avoid changing the shipped version. Copy any member you plan to change from the product definitions
or reports library to your local definitions library, DRL.LOCAL.DEFS. (The default names of the product
definitions and reports libraries are DRL190.SDRLDEFS and DRL190.SDRLRENU.)
You can use the administration dialog to view and edit an object definition. To edit an object in a
component:

Procedure
1. From the Component window, select an object to work with, and press Enter.
IBM Z Decision Support accesses the ISPF editor, where you can edit (or view) the object definition.
2. When you finish editing the object definition, press F3 to exit the ISPF edit session.
IBM Z Decision Support returns to the Component window.

Adding an object to a component

About this task

Components include object definitions necessary to collect log data, store it in the product database,
and generate reports. However, if you create customized objects, you can add the object definition to an
existing component.
Before using the administration dialog to add an object to a component, create the definition member that
defines the object. See “Overview of IBM Z Decision Support objects” on page 73 for more information
about definition members.
To add an object to a component:

Procedure
1. From the Component window, press F5.
The Add Object window is displayed.
2. Type information about the new object, and press Enter.
You must use the same name in the Object name field as the one that appears in the definition
member for the object. For example, if there is a definition member, DRLLSAMP, that contains the log
collector language statement DEFINE LOG SAMPLE;, you must specify SAMPLE as the name of the
log definition object.
IBM Z Decision Support saves the object specification (that includes the name of the member that
defines it) and returns to the Component window.
3. Repeat this procedure to add additional objects.

Deleting an object from a component

About this task

Components include object definitions necessary to collect log data, store it in the IBM Z Decision
Support database, and generate reports. If you do not need to collect, store, or report on certain types of
data, you can delete object definitions for those data types.

Chapter 4. Administering IBM Z Decision Support 131

Working with a component definition

Note: When you delete an object using the dialog, IBM Z Decision Support deletes references to the
object from the component. It does not delete the definition member that contains log collector language
statements that define the object. You can add the object again at a later time.
To delete an object from a component:

Procedure
1. From the Component window, select the object to delete, and press F11.
A Confirmation window is displayed.
2. From the Confirmation window, press Enter to confirm the deletion.
IBM Z Decision Support deletes from its system tables all references from the component to the object
and returns to the Component window.

Excluding an object from a component installation

About this task

This window User Modified Objects allows you to exclude product objects that have been modified by you,
from the installation of the component.
Objects that are listed here were previously included by you in the component installation, although they
contain your modifications to the IBM-supplied object.
For an explanation of the use of VERSION variable in controlling the excluding of user-modified objects
from component installation, see “How IBM Z Decision Support controls object replacement” on page 74.
To exclude an object from a component installation:>

Procedure
1. From the Components window, select the component. Then select the Show user objects option in the
Component pull-down.
2. From the User Modified Objects window, select the object to exclude, and press F4.
A Confirmation window is displayed.
3. From the Confirmation window, press Enter to confirm that the object should be excluded from the
installation.

Including an object in a component installation

About this task

After you have excluded an object from the installation of a component (see “Excluding an object from a
component installation” on page 132 for details), you have the option to re-include the object.
To include an object in a component installation:

Procedure
1. From the Components window, select the component. Then select the Show excluded option in the
Component pull-down.
2. From the Objects Excluded window, select the object to include, and press F4.
A Confirmation window is displayed.
3. From the Confirmation window, press Enter to confirm that the object should be included in the
installation.

132 IBM Z Decision Support : Administration Guide and Reference

 Working with a component definition

Deleting a component

About this task

To remove all references to a component from IBM Z Decision Support, you can use the administration
dialog to delete the component. Do not delete components shipped with the product unless you are sure
you are not going to use them.
To delete a component:

Procedure
1. Uninstall the component that you plan to delete. See “Uninstalling a component” on page 127 for
more information.
You must uninstall a component before deleting it. Uninstalling deletes all objects of the component.
2. From the Components window, select the component. Then select the Delete option in the Component
pull-down.
A confirmation window is displayed.
3. Press Enter to confirm the deletion.
IBM Z Decision Support deletes from its system tables all references to the component. The
component no longer appears in the list of components in the Components window. The feature
definition member (see “Overview of IBM Z Decision Support objects” on page 73) still exists,
however, and you can reinstall it at a later time. Before reinstalling deleted components, you must
update the system tables to refresh the list of components available for installation.

Creating a component

About this task

If you have created a set of definitions (for example, for records or tables) using log collector language
or report definition language, you can package them as a component. Creating a component can also be
useful when designing a component to use at other sites. You must also transfer members that define the
objects to the system at the other site.
You can define a component with SQL statements that directly update these system tables:
DRLCOMPONENTS, DRLCOMP_PARTS, and DRLCOMP_OBJECTS, described in “Dialog system tables” on
page 215. IBM Z Decision Support features define entries in these tables as you create or update
the system tables, using SQL statements in definition members. For examples of component definition
members, see “Overview of IBM Z Decision Support objects” on page 73.
Note: As you create your component, remember that the product requires that some definitions exist
before you can install others. For example, if your component contains record procedures, you must
install the record definition that maps the source record for the record procedure before installing
the record procedure. Furthermore, you must install the record procedure before installing the record
definition that maps the output of the record procedure. To do this, put both definitions in the same
member.
IBM Z Decision Support installs component definitions in the following order:
1. Log
2. Record
3. Record procedure
4. Table space
5. Lookup table
6. Table
7. Update

Chapter 4. Administering IBM Z Decision Support 133

Working with a component definition

8. View
9. Report group
10. Report
The order of installation within a definition type is determined by the sorting sequence of the definition
member names.
If you plan to use a component on the same IBM Z Decision Support system on which you are creating it,
you can use the administration dialog to create the component.

Procedure
1. Optionally, you can select an existing component for IBM Z Decision Support to use as a template for
the new component before performing the next step.
2. From the Components window, press F5.
The New Component window is displayed.
3. Type information about the new component in the fields.
4. Press F5 to add an object to the component.
The Add Object window is displayed. See “Adding an object to a component” on page 131 for more
information.
5. Select an object, and press Enter to edit its definition.
IBM Z Decision Support accesses the ISPF editor, where you can edit the object definition. See
“Viewing or editing an object definition” on page 131 for more information.
6. To delete an object that currently exists (either it existed in the template or you decided not to use an
object you added), select the object, and press F11.
A Confirmation window is displayed for you to confirm the deletion. See “Deleting an object from a
component” on page 131 for more information.
7. When you finish adding, editing, or deleting objects, press F3.
IBM Z Decision Support returns to the Components window and lists the new component.

Working with log and record definitions

IBM Z Decision Support uses log definitions to associate a series of processing definitions with a certain
type of log data set. An example is the SMF log definition that the product uses to process SMF log data
sets created by MVS. IBM Z Decision Support associates log, record, and update definitions with the SMF
log and uses these definitions to collect the data, manipulate it, and store it in appropriate tables.
This section describes how to use the administration dialog to work with log and record definitions. It
describes how to:
• Work with the contents of logs (page “Working with the contents of logs” on page 135):
– View a list of log data sets that IBM Z Decision Support has collected (page “Viewing a list of log data
sets collected” on page 135)
– Collect data from a log into Db2 tables (page “Collecting data from a log into Db2 tables” on page
137)
– Display statistics of log data sets (page “Displaying log statistics” on page 138)
– Display the contents of a log data set (page “Displaying the contents of a log” on page 139)
– Generate a report on a record in a log data set (page “Creating a report on a record” on page 140)
• Work with log definitions (page “Working with log definitions” on page 142):
– View and modify a log definition and its header fields (page “Viewing and modifying a log definition”
on page 142)
– Create a log definition (page “Creating a log definition” on page 144)

134 IBM Z Decision Support : Administration Guide and Reference

 Working with the contents of logs

– Delete a log definition (page “Deleting a log definition” on page 145)

• Work with record definitions (page “Working with record definitions in a log” on page 145):
– View and modify a record definition (page “Viewing and modifying a record definition” on page 146):
- Work with fields in a record definition (page “Working with fields in a record definition” on page
147)
- Work with sections in a record definition (page “Working with sections in a record definition” on
page 148)
– Create a record definition (page “Creating a record definition” on page 149)
– Display update definitions associated with a record (page “Displaying update definitions associated
with a record” on page 149)
– Delete a record definition (page “Deleting a record definition” on page 150)
– View and modify a record procedure definition (page “Viewing and modifying a record procedure
definition” on page 150)
– Create a record procedure definition (page “Creating a record procedure definition” on page 151)
– Delete a record procedure definition (page “Deleting a record procedure definition” on page 152)

Working with the contents of logs

About this task

To work with logs, first display a list of log definitions stored in the product system tables.

Procedure
1. From the IBM Z Decision Support Administration window, select 3, Logs.
2. Press Enter.
IBM Z Decision Support displays the Logs window.

Viewing a list of log data sets collected

About this task

The product Data Sets window shows you a list of data sets that have been collected. The window (Figure
51 on page 136) shows the name of each data set, when it was collected, and the status of the collect job.
The Status column reads OK if the collect job ran uninterrupted and without error. It shows Incomplete
if the job was interrupted before the entire log had been processed. For example, due to a locking or out
of space problem. Warning in the Status column means that the collect issued warning messages but the
job completed successfully.
You can display detailed collection statistics for each collected data set. This is the default action for the
window; you perform it by pressing Enter after selecting a data set.
You can also display the data in a log data set, record by record.
To view a list of collected log data sets:

Procedure
1. From the Logs window, select a log definition and press F6.
IBM Z Decision Support displays the Data Sets window for the log type you selected (see Figure 51 on
page 136). You can then display collect statistics for each data set.

Chapter 4. Administering IBM Z Decision Support 135

Working with the contents of logs

SMF Data Sets ROW 1 TO 15 OF 169

Select one data set. Then press Enter to view statistics.

/ Data Sets Time collected Status

_ SYST.SMFSYSA.D930131 2000-02-01-04.26.57 OK
_ SYST.SMFSYSA.D930130 2000-01-31-05.22.15 OK
_ SYST.SMFSYSB.D930129 2000-01-30-04.14.36 OK
_ SYST.SMFSYSA.D930129 2000-01-30-02.22.14 Incomplete
_ SYST.SMFSYSB.D930128 2000-01-29-02.59.20 OK
_ SYST.SMFSYSA.D930128 2000-01-29-01.38.50 OK
/ SYST.SMFSYSB.D930127 2000-01-28-08.30.02 Warning
_ SYST.SMFSYSA.D930127 2000-01-28-03.56.24 Warning
_ SYST.SMFSYSB.D930126 2000-01-27-03.23.27 OK
_ SYST.SMFSYSA.D930126 2000-01-27-03.26.17 OK
_ IVT.SMFCICS.TEST1 2000-01-26-14.23.23 OK
_ IVT.SMFCICS.DELTA 2000-01-26-10.42.26 OK
_ SYST.SMFSYSB.D930125 2000-01-26-04.18.48 OK
_ SYST.SMFSYSA.D930125 2000-01-26-02.56.26 OK
_ SYST.SMFSYSB.D930124 2000-01-26-04.18.48 OK

Command ===> _____________________________________________________________

F1=Help F2=Split F3=Exit F5=Display F7=Bkwd F8=Fwd
F9=Swap F11=Delete F12=Cancel

Figure 51. Data Sets window

2. From the Data Sets window, select a data set and press Enter.
The product displays the Collect Statistics window for the data set (Figure 52 on page 136).

SMF Collect Statistics

Press Enter to return.

Data set . . . . : SYST.SMFSYSB.D930127

Volume . . . . . : TSO007

Time collected . :2000-01-28-08.30.02 Collected by ... : STROMBK

Elapsed time . . : 462 Return code . . . : 4
Times collected. : 1 Completed . . . . : Y

First record . . : 00001E2900006EB60093104FD3C4C7F140404040

: 0003000500000000004400180001000000000000
Firsttimestamp . : 2000-01-27-00.04.43
Last timestamp . : 2000-01-27-22.17.23

Records read . . : 187714 Records selected. : 17701

Database updates : 0 Inserts: 13610 Deletes :0

F1=Help F2=Split F9=Swap F12=Cancel

Figure 52. Collect Statistics window

3. Press Enter to return to the Data Sets window after you finish viewing statistics.

What to do next
To display the contents of a data set record by record, select the data set and press F5.
IBM Z Decision Support displays the Record Selection window. Refer to “Displaying the contents of a log”
on page 139 for more information.

Deleting a log data set

About this task

To delete data set statistics from the product system tables:

136 IBM Z Decision Support : Administration Guide and Reference

 Working with the contents of logs

Procedure
1. From the Data Sets window, select the data set and press F11.
IBM Z Decision Support displays a confirmation window.
2. Press Enter to confirm the deletion.
The product deletes any references it has to the data set, which no longer appears in the list of
collected data sets.

Collecting data from a log into Db2 tables

About this task

IBM Z Decision Support stores data it collects in Db2 tables in the product database, following the
instructions in update definitions associated with records in the log.
Usually, you use a batch job to collect log data. (See “Collecting log data” on page 86 for more information
about sample collect jobs.) However, you can use the administration dialog to perform online collection.
For example, to correct problems or to test new log, record, or update definitions.
Note: Some logs require special processing or contain collect statements that can be initiated only from
batch jobs. Such logs include those for DCOLLECT, VMACCT, SMF_VPD, and IMS.
To collect data from a log into Db2 tables:

Procedure
1. From the Logs window, select a log and press F11.
The Collect window is displayed (see Figure 53 on page 137).

Log Utilities View Other Help

Collect

Type information. Then press Enter to edit the collect JCL.

Data set DRLxxx.SDRLDEFS(DRLSAMPL)

(reqd)
Volume (If not cataloged)
Unit (Required for batch if Volume defined)

Reprocess 2 1. Yes
2. No
Commit after 1 1. Buffer full
2. End of file
3. Specify number of records
Number of records
Buffer size 10
Extention 2 1.K
Condition 2.M >

F1=Help F2=Split F4=Online F5=Include F6=Exclude

F9=Swap F10=Show fld F11=Save def F12=Cancel

F8=Fwd F9=Swap F4=Action F11=Collect F12=Cancel

Figure 53. Collect window

2. Type the name of the log data set in the Data set field.
Note: The log data sets used as input for the collect (DRLLOG DD statement) are expected to be sorted
in chronological order).
3. Optionally, specify other collect options in fields in the window.
Note: Entry fields followed by a greater than (>) sign respond to the F10 (Show fld) function key, which
displays all of the data in the field or lets you type more data in the Show Field window.

Chapter 4. Administering IBM Z Decision Support 137

Working with the contents of logs

4. Press F5 to include only specific Db2 tables in the collect process.

The Include Tables window is displayed.
5. Select those tables to include in the collect process and press Enter.
You are returned to the Collect window.
You can exclude tables as well. You need exclude only tables that the product would normally update
during the collection.
6. Press F6 to exclude tables from the collect process.
The Exclude Tables window is displayed. Select tables to exclude from the collect process and press
Enter. You are returned to the Collect window.
7. Run the collect either in batch or online:
a) Press Enter to run the collect in batch mode.
IBM Z Decision Support builds a JCL job stream for the collect job and accesses the ISPF editor
where you can edit and submit the JCL.
b) Press F4 to perform an online collection.
IBM Z Decision Support starts the collect process online. When the collection is complete, collect
messages are displayed in an ISPF browse window.
8. Press F3 to return to the Logs window.

Displaying log statistics

About this task

You can create log statistics for any log data set, regardless of whether it has been collected. A log
statistics file shows the number of records of each type in a log data set. It also shows records built by log
and record procedures.
To view statistics for a log data set:

Procedure
1. From the Logs window, select a log definition.
2. Select 3, Show log statistics, from the Log pull-down.
You are prompted for the name of a log data set.
3. Type the name of the data set and press Enter.
The product displays statistics for the log (see Figure 14 on page 29).

138 IBM Z Decision Support : Administration Guide and Reference

 Working with the contents of logs

DRLnnnnI Logstat started at 2000-12-04-10.04.15

DRL0302I Processing SMF.DATA.SET on VOL001
DRL0341I The first record timestamp is 2000-06-03-07.00.01.730000.
DRL0342I The last record timestamp is 2000-06-03-11.52.40.220000.
DRL0003I
DRL0315I Records read from the log or built by log procedure:
DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_000 | 0
DRL0319I SMF_006 | 6
DRL0319I SMF_007 | 0
DRL0319I SMF_021 | 0
DRL0319I SMF_025 | 0
DRL0319I SMF_026 | 476
DRL0319I SMF_030 | 3737
DRL0319I SMF_070 | 40
DRL0319I SMF_071 | 40
DRL0319I SMF_072_1 | 280
DRL0319I SMF_090 | 0
DRL0320I Unrecognized | 3
DRL0318I -------------------|----------
DRL0321I Total | 4582
DRL0003I
DRL0316I Records built by record procedures:
DRL0317I Record name | Number
DRL0318I -------------------|----------
DRL0319I SMF_030_X | 2012
DRL0319I SMF_070_X | 200
DRL0318I -------------------|----------
DRL0321I Total | 2212
DRLnnnnI Logstat ended at 2000-12-04-10.09.43

Figure 54. Sample log statistics output

4. When you finish viewing statistics, press F3.
The Logs window is displayed.

Displaying the contents of a log

About this task

IBM Z Decision Support provides a facility for displaying the contents of a log, record by record. The
Record Data window describes each field in each record in the log data set you identify.
To view the contents of a log:

Procedure
1. From the Logs window, select the log.
2. From the Utilities pull-down, select 2, Display log, and press Enter.
Note: You can also display the contents of a log by selecting Display record from the Record Definition
window or by pressing F5 from the Data Sets window.
The Record Selection window is displayed.
3. Type the log data set name and, optionally, the name of a record type (to display only one record
definition), or a record sequence number (to start displaying records at that position in the log). Press
Enter.
The Record Data window is displayed.

Chapter 4. Administering IBM Z Decision Support 139

Working with the contents of logs

Record Data ROW 1 TO 13 OF 222

Press Enter to view the next record.

Record name . : SMF_030 Record number : 3

Data set . . : LDG.SMFSYSA.W20

Field Name Type Length Offset Value

SMF30LEN BINARY 2 0 628
SMF30SEG BINARY 2 2 0
SMF30FLG BIT 1 4
SMF30RTY BINARY 1 5 30
SMF30TME TIME 4 6 07.00.03.830000
SMF30DTE DATE 4 10 2000-06-03
SMF30SID CHAR 4 14 MVS1
SMF30WID CHAR 4 18 JES2
SMF30STP BINARY 2 22 3
------------------ -------- ---- ---- --------------------------
TRIPLETS SECTION 88 24 1 (1)
------------------ -------- ---- ---- --------------------------
SMF30SOF BINARY 4 0 112

Command ===> ______________________________________________________________

F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 55. Record Data window

4. Press Enter to step through records in the log.
Each time you press Enter, IBM Z Decision Support displays the next identified record in the log.
5. When you finish viewing record data, press F12.
You are returned to the Logs window.

Creating a report on a record

About this task

To produce a report of the data in a record type without performing a collect operation, you can use the
IBM Z Decision Support list function. For example, you may need very detailed data from a record, or
you may want to get information from a record one time, without creating product tables for it. The list
function creates a report of the data in a record either in QMF format or as a data set that can be browsed.
To create a report of the data in a record:

Procedure
1. From the Logs window, select the log and press Enter.
The Record Definitions window for the log is displayed (see Figure 59 on page 145).
2. Select a record and press F11.
The List Record window for the record is displayed (see Figure 56 on page 141).

140 IBM Z Decision Support : Administration Guide and Reference

 Working with the contents of logs

SMF_030 List Record ROW 61 TO 70 OF 176

Type information, select fields. Then press Enter to define option.

Condition >

/ Fields Type Sort Seq Condition

_ SMF30IOF BINARY
_ SMF30ION BINARY
_ SMF30ISB BINARY
_ SMF30IST TIME_001
_ SMF30IVA BINARY
_ SMF30IVU BINARY
/ SMF30JBN CHAR
_ SMF30JNM CHAR
_ SMF30JPT BINARY
_ SMF30JVA BINARY

Command===>
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap
F10=Show fld F12=Cancel

Figure 56. List Record window

3. From the List Record window, select fields to include in the report. Type information in the fields and
press Enter.
If your installation uses QMF, the Report Display Options window is displayed.
4. In the Report Display Options window, choose whether to display the report using QMF or as a data
set that can be browsed. Specify the name of the log data set from which IBM Z Decision Support is to
produce the report, then press Enter.
If your installation does not use QMF, the report is displayed using ISPF browse. Specify the name of
the log data set from which IBM Z Decision Support is to produce the report in the Input Log Data Set
Name window, then press Enter.
The report is displayed.

ISRBROBF STROMBK.DRLLST1 -------------------------- LINE 00000000 COL 001 080

********************************* TOP OF DATA ********************************
SMF30CPS SMF30CPT SMF30DTE SMF30JBN SMF30RST SMF30SIT
----------- ----------- ---------- -------- -------- --------
0 18 2000-06-03 LOGREFL1 07.00.00 07.00.01
1 19 2000-06-03 LOGREFL2 07.00.00 07.00.05
0 17 2000-06-03 LOGREES1 07.00.01 07.00.07
0 13 2000-06-03 LOGREES2 07.00.01 07.00.09
2 20 2000-06-03 LOGRSP4A 07.00.02 07.00.10
1 19 2000-06-03 LOGSP4B 07.00.02 07.00.22
0 16 2000-06-03 LOGRXAA 07.00.03 07.00.23
0 13 2000-06-03 LOGRXAB 07.00.03 07.00.26
4 73 2000-06-03 EID3D105 07.00.12 07.00.13
0 7 2000-06-03 EID3D105 07.00.12 07.01.21
9 79 2000-06-03 EID3D105 07.00.12 07.01.21
227 1108 2000-06-03 EID4 01.14.42 01.14.43
18 226 2000-06-03 EID4 07.12.42 07.12.44
1 12 2000-06-03 XGORANW 07.26.33 07.26.34
1 12 2000-06-03 XGORANW 07.26.50 07.26.51
7 215 2000-06-03 NORBACK 07.31.52 07.31.52
The list record action is executed successfully.
COMMAND ===> SCROLL ===> CSR
F1=Help F2= F3=End F4= F5=R Find F6=R Change
F7=Backward F8=Forward F9= F10=Left F11=Right F12=Cursor

Figure 57. Output from List record function

5. When you finish viewing the report, press F3 to exit QMF or the ISPF browse window.
You are returned to the List Record window.
6. From the List Record window, press F12 to return to the Record Definitions window.

Chapter 4. Administering IBM Z Decision Support 141

Working with log definitions

7. From the Record Definitions window, repeat this procedure for more records or press F3 to return to
the Logs window.

Working with log definitions

All the logs that you plan to process must be defined to IBM Z Decision Support. Log definitions included
with each component define the logs that the product uses to collect data.
A log definition can include these elements:
Header
Lists fields common to all records in the log.
Timestamp
Describes how to derive the timestamp of a record from fields in the header.
First record
Describes a condition that should be met for the first record in the log data set.
Last record
Describes a condition that should be met for the last record in the log data set.
Log procedure
Identifies a program that is invoked for each record read.
Log procedure parameters
Identifies the language of the log procedure and other information, such as information the log
procedure cannot retrieve from the record.
For more information about log procedures, refer to the Language Guide and Reference.

Viewing and modifying a log definition

About this task

You can use the administration dialog to view or modify log definitions. To view and modify a log
definition:

Procedure
1. From the Logs window, select the log and press F5.
The Log Definition window is displayed (see Figure 58 on page 143) for the log you specified.

142 IBM Z Decision Support : Administration Guide and Reference

 Working with log definitions

Log Utilities View Other Help

SMF Log Definition

Type information. Press Enter to save and return.

Description MVS Systems Management Facility >

Log procedure
Log procedure parameter >
Log procedure language 1. ASM
2. C

Record timestamp TIMESTAMP(SMFDTE,SMFTME) >

First record condition SMFRTY= 2 >
Last record condition SMFRTY= 3 >

F1=Help F2=Split F5=Header F9=Swap F10=Show fld

F12=Cancel

Command===>
F1=Help F2=Split F3=Exit F5=Log def F6=Datasets F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=Collect F12=Cancel

Figure 58. Log Definition window

2. Change the log definition.
3. Press F5 to display header fields for the log definition.
The Header Fields window is displayed for the log. See “Working with header fields” on page 143 for
more information.
4. When you finish modifying the log definition, press Enter.
The changes are saved and you are returned to the Logs window.

Working with header fields

About this task

To add header fields to a log definition:

Procedure
1. From the Header Fields window, press F5 to add a header field.
A blank Header Field Definition window is displayed.
2. Type the required information in the fields and press Enter.
The Header Field Definition window for the next field is displayed. IBM Z Decision Support carries
forward values for the Type and Length fields from the previous field and increments the Offset field by
the length of the previous field.
3. Press F12 when you finish adding fields.
You are returned to the Header Fields window.
4. Press F3 to return to the Log Definition window.

Modifying header fields for a log definition

About this task

To modify header fields for a log definition:

Chapter 4. Administering IBM Z Decision Support 143

Working with log definitions

Procedure
1. From the Header Fields window, select the header field and press Enter.
The Header Field Definition window for the header field you specified is displayed.
2. Type changes in the fields and press Enter.
You are returned to the Header Fields window.
3. Press F3 to return to the Log Definition window.

Deleting header fields for a log definition

About this task

To delete header fields for a log definition:

Procedure
1. To delete a header field, select the field and press F11.
A confirmation window is displayed.
2. Press Enter to confirm the deletion.
The header field is deleted from the list and you are returned to the Header Fields window.
3. Press F3 to return to the Log Definition window.

Creating a log definition

About this task

To collect data from a log that is not defined by an IBM Z Decision Support component, you must create
a log definition. You can use the administration dialog to create log definitions, or you can use the log
collector language. Refer to the Language Guide and Reference for more information about creating log
definitions with log collector language.
To create a log definition:

Procedure
1. To use an existing log definition as a template, select a log definition from the Logs window. Otherwise,
do not select a log definition before the next step.
2. Select 1, New, from the Log pull-down and press Enter.
The New Log Definition window is displayed.
3. Type information for the new log definition in the fields.
4. Press F5 to add header fields to the log definition.
The Header Fields window is displayed. See “Working with header fields” on page 143 for more
information on adding header fields.
5. After you add all the information, press Enter.
The new log definition is saved and you are returned to the Logs window.

144 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

Deleting a log definition

About this task

If you no longer need to collect data from a log, you can use the administration dialog to delete the log
definition. When you delete this log definition, you delete references to the log definition from IBM Z
Decision Support system tables, but you do not delete the member that defines the log type.
To delete a log definition:

Procedure
1. From the Logs window, select a log and then select the Delete option from the Log pull-down.
A confirmation window is displayed.
2. Press Enter to confirm the deletion.
The log definition is deleted and you are returned to the Logs window.

Working with record definitions in a log

About this task

Each record in a log belongs to a record type that must be defined to IBM Z Decision Support to be
collected. Otherwise, the product designates it as an unrecognized type of record and does not process it.
Record definitions are included with each predefined component.
To view a list of record definitions:

Procedure
1. From the product Administration window, select 3, Logs, and press Enter.
The Logs window is displayed.
2. From the Logs window, select the log that contains the record and press Enter.
The Record Definitions window for the log is displayed (see Figure 59 on page 145).

Record Utilities Other Help

--------------------------------------------------------------------------
SMF Record Definitions ROW 8 TO 20 OF 124

Select a record definition. Then press Enter to Open record definition.

/ Record Definitions Description

_ SMF_000 IPL
_ SMF_002 Dump header
_ SMF_003 Dump trailer
_ SMF_004 Step termination
_ SMF_005 Job termination
_ SMF_006 JES2/JES3/PSF/External writer
_ SMF_007 Data lost
_ SMF_008 I/O configuration
_ SMF_009 VARY device ONLINE
_ SMF_010 Allocation recovery
_ SMF_011 VARY device OFFLINE
_ SMF_014 INPUT or RDBACK data set activity
_ SMF_015 OUTPUT, UPDAT, INOUT, or OUTIN data set

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F5=Procs F6=Updates F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=List rec F12=Cancel

Figure 59. Record Definitions window

Chapter 4. Administering IBM Z Decision Support 145

Working with record definitions in a log

Viewing and modifying a record definition

About this task

Most of a record definition describes the layout of the record. Records are divided into fields and,
optionally, sections. A field is a named sequence of adjacent bytes. A section is a larger structure that
contains fields or other sections. For more information about defining records, sections, and fields, refer
to the Language Guide and Reference.
You can use the administration dialog to modify record definitions. To view and modify a record definition:

Procedure
1. From the Record Definitions window, select the record definition and press Enter.
The Record Definition window for the record definition is displayed (see Figure 60 on page 146).

SMF_030 Record Definition ROW 1 TO 9 OF 188

Type information. Select a field or a section. Then press Enter to

display.

Log name . . . SMF

Identified by . SMF30RTY= 30 > (condition)
Built by . . . ________ + (program name)
Description . . Common address space work >

/ Field Type Length Offset Section

_ SMF30LEN BINARY 2 0
_ SMF30SEG BINARY 2 2
_ SMF30FLG BIT 1 4
_ SMF30RTY BINARY 1 5
_ SMF30TME TIME_001 4 6
_ SMF30DTE DATE_001 4 10
_ SMF30SID CHAR 4 14
_ SMF30WID CHAR 4 18
_ SMF30STP BINARY 2 22

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F4=Prompt F5=Add fld F6=Add sec
F7=Bkwd F8=Fwd F9=Swap F10=Show fld F11=Delete F12=Cancel

Figure 60. Record Definition window

2. Type any changes to the record definition.
Note: By changing the value in the Log name field, you can move the record to another log definition.
3. To modify the definition of a field, select the field and press Enter.
The Field Definition window is displayed. See “Working with fields in a record definition” on page 147
for more information.
4. To modify a section, select the section and press Enter.
The Section Definition window is displayed. See “Working with sections in a record definition” on
page 148 for more information.
5. Press F5 to add fields to the record definition.
The Field Definition window is displayed. See “Working with fields in a record definition” on page 147
for more information.
6. Press F6 to add sections to the record definition.
The Section Definition window is displayed. See “Working with sections in a record definition” on
page 148 for more information.
7. To delete a section or field from the record definition, select the section or field and press F11.

146 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

If the section or field definition already existed in the record definition, a confirmation window is
displayed. Otherwise, you are deleting something you just added. IBM Z Decision Support does not ask
you to confirm this type of deletion and you can skip step 8.
8. Press Enter to confirm the deletion.
The section or field is deleted and you are returned to the Record Definition window.
9. Press F3 when you finish modifying the record definition.
Your changes are saved and you are returned to the Record Definitions window.
Note: If you have incorrectly modified the record definition, IBM Z Decision Support displays error
messages in an ISPF browse window. Examine the messages and press F3 to return to the Record
Definition window where you can correct the errors.

Working with fields in a record definition

About this task

You can use the administration dialog to modify existing field definitions or to add field definitions. You
can also use log collector language statements. Refer to the Language Guide and Reference for more
information about defining fields in a record.
To add a field definition to a record definition:

Procedure
1. From the Record Definition window, press F5.
A blank Field Definition window is displayed.
2. Type the required information in the fields and press Enter.
Another Field Definition window is displayed (see Figure 61 on page 147).

SMF_030 Record Definition ROW 1 TO 9 OF 188

T Field Definition
d
Type information.Then press Enter to save.
L
I Field name (required)
B Type + (required)
D Length
Offset
/
_ Section name +
_ Description >
_
_
_
_ F1=Help F2=Split F4=Prompt F9=Swap F10=Show fld
F12=Cancel
/
_
_ SMF30STP BINARY 2 22

Command===>
F1=Help F2=Split F3=Exit F4=Prompt F5=Add fld F6=Add sec
F7=Bkwd F8=Fwd F9=Swap F10=Show fld F11=Delete F12=Cancel

Figure 61. Field Definition window

3. Press F12 when you finish adding fields.
You are returned to the Record Definition window.

Chapter 4. Administering IBM Z Decision Support 147

Working with record definitions in a log

Modifying a field definition

About this task

To modify a field definition:

Procedure
1. From the Record Definition window, select the field and press Enter.
The Field Definition window is displayed.
2. Type changes in the fields and press Enter.
Your changes are saved and you are returned to the Record Definition window.

Working with sections in a record definition

About this task

You can use the administration dialog to modify existing section definitions or to add section definitions.
You can also use log collector language statements. Refer to the Language Guide and Reference for more
information about defining sections and repeated sections.
To modify a section definition:

Procedure
1. From the Record Definition window, select the section and press Enter.
The Section Definition window is displayed (see Figure 62 on page 148).

SMF_030 Record Definition ROW 42 to 50 OF 188

Section Definition

Type information. Press Enter to save and return.

Section name . . . . SUBSYSTEM (required)

In Section name . . . +

Offset . . . . . . . SMF30SDF >(required)

Length . . . . . . . SMF30SLN >
Number . . . . . . . SMF30SON >
Present if condition >

Repeated . . . . . . . 2 1. Yes
2. No

F1=Help F2=Split F4=Prompt F9=Swap F10=Show fld

F12=Cancel

Command ===>
F1=Help F2=Split F3=Exit F4=Prompt F5=Add fld F6=Addsec
F7=Bkwd F8=Fwd F9=Swap F10=Showfld F11=Delete F12=Cancel

Figure 62. Section Definition window

2. Type changes in the fields and press Enter.
Your changes are saved and you are returned to the Record Definition window.

148 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

Adding a section definition to a record definition

About this task

To add a section definition to a record definition:

Procedure
1. From the Record Definition window, press F5.
A blank Section Definition window is displayed.
2. Type the required information in the fields and press Enter.
Another Section Definition window is displayed.
3. Press F12 when you finish adding sections.
You are returned to the Record Definition window.

Creating a record definition

About this task

You can create record definitions by using:
• The administration dialog; or
• Log collector language statements.
For more information about defining records with the log collector language, refer to the Language Guide
and Reference.
To create a record definition:

Procedure
1. To use an existing record definition as a template, select a record definition from the Record
Definitions window. Otherwise, do not select a record definition.
2. From the Record Definitions window, select 1, New, from the Record pull-down.
The New Record Definition window is displayed.
3. Type information for the new record definition in fields of the window.
4. Press F5 to add fields to the record definition.
The Field Definition window is displayed. See “Working with fields in a record definition” on page 147
for more information.
5. Press F6 to add sections to the record definition.
The Section Definition window is displayed. See “Working with sections in a record definition” on page
148 for more information.
6. Press F3 when you finish adding fields and sections.
The new record definition is saved and you are returned to the Record Definitions window.

Displaying update definitions associated with a record

About this task

Update definitions contain instructions for summarizing log data into Db2 tables. The Record Definitions
window lets you view which update definitions IBM Z Decision Support uses to process data that a record
definition maps.

Chapter 4. Administering IBM Z Decision Support 149

Working with record definitions in a log

Each record is associated with one or more update definitions. To display update definitions associated
with a record:

Procedure
1. From the Record Definitions window, select the record with associated update definitions you plan to
view and press F6.
The Update Definitions window lists all the update definitions that use the selected record definition
as input. From this window, you can view, modify, or add update definitions. See “Displaying and
modifying update definitions of a table” on page 169 or “Creating an update definition” on page 183
for more information.
2. Press F3 when you finish viewing update definitions.
You are returned to the Record Definitions window.

Deleting a record definition

About this task

If you no longer require data from a certain record, you can use the administration dialog to delete the
record definition.
Note: IBM Z Decision Support prevents you from deleting record definitions that affect, or are affected by,
other IBM Z Decision Support objects. To delete a record definition, remove links from it to other IBM Z
Decision Support objects.
To delete a record definition:

Procedure
1. From the Record Definitions window, select the record definition to delete. Then select 5, Delete, from
the Record pull-down.
A confirmation window is displayed.
2. Press Enter to confirm the deletion.
The record definition is deleted and you are returned to the Record Definitions window.

Viewing and modifying a record procedure definition

About this task

Record procedures are programs that can modify, split, combine, sort, delete, or perform any function to
records during collection. Record procedures use existing records as input and produce other records,
which must be defined to IBM Z Decision Support. Some product components include record procedures
and their definitions.
Each record procedure definition defines record types that the procedure processes, identifies the
language of the procedure, and passes parameters to the procedure. For more information, refer to the
Language Guide and Reference.
You can use the administration dialog to modify record procedure definitions.
To view and modify a record procedure definition:

Procedure
1. From the Record Definitions window, select the record definition that is input to the record procedure
you plan to modify and press F5.

150 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

The Record Procedures window for the record definition is displayed. This window lists all record
procedure names that use the record as input.
2. From the Record Procedures window, select the record procedure whose definition you plan to modify
and press Enter.
The Record Procedure Definition window for the record procedure is displayed (see Figure 63 on page
151).

SMF_030 Record Procedures ROW 1 TO 1 OF 1

DRL2S030 Record Procedure Definition

Type in information. Then press Enter to save and return.

Description >

Language 1 1. ASM
2. C

Procedure parameter >

F1=Help F2=Split F5=Linkrec F9=Swap F10=Show fld

F12=Cancel

Command===>
F1=Help F2=Split F3=Exit F5=New F6=Delete F7=Bkwd
F8=Fwd F9=Swap F11=Save def F12=Cancel

Figure 63. Record Procedure Definition window

3. Type your changes in the fields.
4. Press F5 to link record definitions to the record procedure (to define them as input to the record
procedure).
The Record Definitions window is displayed.
5. From the Record Definitions window, select record definitions to link to the record procedure and press
Enter.
The record procedure is linked to the record definitions you selected and you are returned to the
Record Procedure Definition window.
6. When you finish modifying the record procedure definition, press Enter.
Your changes are saved and you are returned to the Record Procedures window.
7. Repeat this procedure for other record procedures or press F3 to return to the Record Definitions
window.

Creating a record procedure definition

About this task

If you must add a record procedure, you must first write a program according to the instructions in the
Language Guide and Reference. You can then use the administration dialog to define the record procedure
to IBM Z Decision Support.
To create a record procedure definition:

Procedure
1. From the Record Definitions window, select the record definition from which the new record procedure
derives its input and press F5.

Chapter 4. Administering IBM Z Decision Support 151

Working with record definitions in a log

The Record Procedures window for the record definition is displayed.

2. From the Record Procedures window, press F5.
The New Record Procedure Definition window is displayed.
3. Type information for the new record procedure in the fields.
4. Press F5 if you want to link the record procedure to additional record definitions that describe record
types on which the record procedure acts. The record procedure is automatically linked to the record
type selected in step 1 above.
The Record Definitions window is displayed.
5. From the Record Definitions window, select record definitions to link to the record procedure and press
Enter.
The record procedure is linked to the record definitions you selected and you are returned to the
Record Procedure Definition window.
6. When you finish entering information, press Enter.
The new record procedure is saved and returns to the Record Procedures window.
7. Repeat this procedure to add more record procedures or press F3 to return to the Record Definitions
window.

What to do next
In addition, you must define a record type as the record procedure's output. Do this in the Record
Definition window (Figure 60 on page 146). Type the record procedure name in the Built by field, to
identify a record type as one that is created by the record procedure.

Deleting a record procedure definition

About this task

If you no longer require a record procedure, you can use the administration dialog to delete the record
procedure definition.
Note: IBM Z Decision Support prevents you from deleting record procedure definitions that affect, or are
affected by, other product objects. To delete a record procedure definition, remove links from the record
procedure to other product objects.
To delete a record procedure definition:

Procedure
1. From the Record Definitions window, select the record definition that is associated with the record
procedure to delete and press F5.
The Record Procedures window for the record definition is displayed.
2. From the Record Procedures window, select the record procedure to delete and press F6.
A confirmation window is displayed.
3. Press Enter to confirm the deletion.
You are returned to the Record Procedures window.
4. Repeat this procedure to delete more record procedures or press F3 to return to the Record Definitions
window.

Results
The record procedure is deleted.

152 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

Working with tables and update definitions

This section describes how to use the administration dialog to work with tables, update definitions, and
other table-related objects such as purge conditions, indexes, views, and table spaces. After reading this
section, you should be familiar with these tasks:
• “Working with data in tables” on page 154
– “Displaying the contents of a table” on page 154
– “Editing the contents of a table” on page 155
– “Showing the size of a table” on page 156
– “Recalculating the contents of a table” on page 157
– “Importing the contents of an IXF file to a table” on page 159. (This option is available only if your
installation uses QMF with IBM Z Decision Support.)
– “Exporting table data to an IXF file” on page 159. (This option is available only if your installation
uses QMF with IBM Z Decision Support.)
– “Purging a table” on page 160
– “Unloading and loading tables” on page 160
• “Working with tables and update definitions” on page 165
– “Opening a table to display columns” on page 165
– “Displaying and modifying update definitions of a table” on page 169
– “Displaying and editing the purge condition of a table” on page 174
– “Displaying and modifying a table or index space” on page 176
– “Displaying a view definition” on page 180
– “Printing a list of IBM Z Decision Support tables” on page 180
– “Saving a table definition in a data set” on page 181
– “Listing a subset of tables in the Tables window” on page 181
– “Creating a table” on page 181
– “Deleting a table or view” on page 182
– “Creating a table space” on page 183
– “Creating an update definition” on page 183
– “Deleting an update definition” on page 184
– “Administering user access to tables” on page 185
When you use IBM Z Decision Support to collect log data, the product stores the data in Db2 tables in
its database. To view a list of the tables that are used to store collected data, from the Administration
window, select 4, Tables. TheTables window is displayed. The list in this window includes all the product
data tables, lookup tables, and control tables.

Chapter 4. Administering IBM Z Decision Support 153

Working with record definitions in a log

Table Maintenance Utilities Edit View Other Help

--------------------------------------------------------------------------
Tables ROW 1 TO 13 OF 212

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

/ Tables Prefix Type

_ AVAILABILITY_D DRL TABLE
_ AVAILABILITY_M DRL TABLE
_ AVAILABILITY_PARM DRL TABLE
_ AVAILABILITY_T DRL TABLE
_ AVAILABILITY_W DRL TABLE
_ CICS_A_BASIC_H DRL TABLE
_ CICS_A_BASIC_W DRL TABLE
_ CICS_A_DBCTL_H DRL TABLE
_ CICS_A_DBCTL_USR_H DRL TABLE
_ CICS_A_DBCTL_USR_W DRL TABLE
_ CICS_A_DBCTL_W DRL TABLE
_ CICS_A_DLI_H DRL TABLE
_ CICS_A_DLI_USR_H DRL TABLE

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F5=Updates F6=PurCond F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=Display F12=Cancel

Figure 64. Tables window

The name of each table is shown in the Tables column.

The prefix of each table is shown in the Prefix column. Data tables and lookup tables have a prefix of DRL,
the default value of the Prefix for all other tables field in the Dialog Parameters window. Control tables
have a prefix of DRLSYS, the default value of the Prefix for system tables field in the Dialog Parameters
window.
The Type column shows whether an object is a Db2 table or a view.

Working with data in tables

This section describes these tasks:
• Displaying the contents of a table
• Editing the contents of a table
• Showing the size of a table
• Recalculating the contents of a table
• Importing the contents of an IXF file to a table (This option is available only if your installation uses QMF
with IBM Z Decision Support.)
• Exporting table data to an IXF file (This option is available only if your installation uses QMF with IBM Z
Decision Support.)
• Purging a table
• Unloading and loading a table

Displaying the contents of a table

About this task

You can use the administration dialog to display the contents of a table.
Note: If QMF is not used with IBM Z Decision Support on your system, the following applies:
• Tables are displayed with ISPF browse.
• The Add rows and Change rows options on the Edit pull-down are not selectable.

154 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

• If you display a very large table, data table, or system table, you might run out of REXX storage. If this
happens, there are some actions you can take that enable you to display the table, or the part of the
table you want to see.
– Increase the region size.
– If you need to see only the first part of the table, you can decrease the SQLMAX parameter on the
Dialog Parameters window.
– Use F4 (Run) on the SQL Query pop-up in the reporting dialog. Write an SQL SELECT statement that
restricts the retrieved table information to the columns and rows you are interested in. This is a way
to create and run a query without having to save it.
To display the contents of a table:

Procedure
1. From the Tables window, select the name of the table that you plan to display.
2. Press F11, or select 1, Display, from the Utilities pull-down.
The product displays the contents of the table in rows and columns.
Note: The table is not necessarily sorted in key sequence.

REPORT DRL.SAMPLE_H LINE 1 POS 1 79

SYSTEM DEPARTMENT USER RESPONSE

DATE TIME ID NAME ID TRANSACTIONS SECONDS
---------- -------- ------ ---------- -------- ------------ -----------
2000-01-01 13.00.00 SYS1 Sys Supp PIANKA 40 267
2000-01-01 15.00.00 SYS1 Appl Dev ADAMS 72 198
2000-01-02 08.00.00 SYS1 Appl Dev JONES 28 131
2000-01-02 11.00.00 SYS1 Retail PEREZ 21 171
2000-01-03 10.00.00 SYS1 Marketng KWAN 74 220
2000-01-03 11.00.00 SYS1 Manufact LEE 22 234
2000-01-03 11.00.00 SYS1 Manufact LUTZ 2 95
2000-01-04 07.00.00 SYS1 Finance HAAS 26 109
2000-01-04 07.00.00 SYS1 Sys Supp THOMPSON 84 64
2000-01-04 08.00.00 SYS1 Marketng KWAN 63 290
2000-01-04 08.00.00 SYS1 Finance GEYER 94 131
2000-01-04 08.00.00 SYS1 Finance GEYER 94 131
2000-01-04 09.00.00 SYS1 Marketng STERN 51 162
2000-01-04 09.00.00 SYS1 Manufact PULASKI 69 76
1=Help 2= 3=End 4=Print 5=Chart 6=Query
7=Backward 8=Forward 9=Form 10=Left 11=Right 12=
OK, DRL.SAMPLE_H is displayed.
COMMAND ===> SCROLL ===> PAGE

Figure 65. Using QMF to display an IBM Z Decision Support table

3. Press F3 when you finish viewing the contents of the table,
You are returned to the Tables window.

Editing the contents of a table

About this task

You can use the administration dialog to edit the contents of a table, using either the QMF table editor (if
QMF is used with IBM Z Decision Support) or the ISPF editor.
The QMF table editor can be used in two modes, add and change. For a complete description, refer to the
Query Management Facility: Learner's Guide
To add rows to a table using the QMF table editor:

Chapter 4. Administering IBM Z Decision Support 155

Working with record definitions in a log

Procedure
1. From the Tables window (Figure 64 on page 154), select the table to edit.
2. Select 1, Add rows, from the Edit pull-down.
The product calls the QMF table editor in add mode.
3. Enter values for columns, and press F2.
4. Press F3 when you finish adding rows.
QMF prompts you for confirmation.
5. Press Enter.
You are returned to the Tables window.

Showing the size of a table

About this task

Monitor the size of tables periodically to ensure that they are not getting too large.
Use the Db2 RUNSTATS utility to get information about tables and store it in the Db2 catalog each time
you need current information about any Db2 database, including the IBM Z Decision Support database. As
described in “Monitoring the size of the IBM Z Decision Support database” on page 108, IBM Z Decision
Support provides a sample job, DRLJRUNS, as an example of how to run the RUNSTATS utility. You can
also run the RUNSTATS utility using these steps:

Procedure
1. From the list of tables, select the Maintenance pull-down without selecting a table.
2. Select option 1, Tablespace.
3. From the list of table spaces, select one or more table spaces (or make no selection to process all the
table spaces) and select the Utilities pull-down, as shown in Figure 34 on page 97.
4. Select option 2, Run Db2 RUNSTATS.

What to do next
To learn more about the Db2 RUNSTATS utility, refer to the Db2 for z/OS: Administration Guide and
Reference.
Use the administration dialog to check the size of tables in the product database:
1. From the Tables window (Figure 64 on page 154), select tables to display their sizes.
Note: If you do not select any tables, IBM Z Decision Support displays the size of all tables in the
product database.
2. Select 2, Show size, from the Utilities pull-down.
The Table Size window is displayed (Figure 66 on page 157).

156 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

Table Maintenance Utilities Edit View Other Help

Tables ROW 1 TO 13 OF 212

Table Size ROW 1 TO 10 OF 212

Press Enter to return

Name Prefix Row Row length Kbytes

MVSPM_DEVICE_H DRL 80927 240 18967
MVSPM_DEVICE_AP_H DRL 34821 102 3468
MVSPM_CHANNEL_H DRL 9338 140 1276
MVSPM_APPL_H DRL 2388 491 1145
MVSPM_WORKLOAD_H DRL 2727 308 820
MVSPM_STORAGE_H DRL 2567 199 498
MVSPM_PAGE_DS_H DRL 966 229 216
MVSPM_XCF_PATH_H DRL 1296 171 216
MVSPM_SWAP_H DRL 1771 114 197
MVSPM_ENQUEUE_H DRL 1642 100 160

Command===>
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

F8=Fwd F9=Swap F10=Actions F11=Display F12=Cancel

Figure 66. Table Size window

Note:
a. You can use the SORT command (for example, SORT KBYTES DESC) to find the largest tables.
b. If the information shown in the Table Size window is incomplete, run the Db2 RUNSTATS utility and
restart this procedure.
3. After you finish viewing this window, press Enter.
You are returned to the Tables window.

Recalculating the contents of a table

About this task

Sometimes tables get filled with incorrect data during the collect process. (This can be caused by a
situation such as a bad record in a log.) For a single, independent table, you can correct these problems
using one of the options on the Edit pull-down. IBM Z Decision Support provides a recalculate function for
the following special conditions:
• When tables are updated from other tables and corrections must be propagated to all dependent tables.
• When a key column is changed to a new value, and data already exists for the new key.
You can also use the recalculate function to populate a new table from another table, for example a
monthly table from a daily table.
You can use the administration dialog to recalculate the contents of tables. For more information about
the RECALCULATE log collector language statement, refer to the Language Guide and Reference.
To recalculate the contents of tables:

Procedure
1. From the Tables window (Figure 64 on page 154), select the source table (the table you plan to
modify)
2. Select 8, Recalculate, from the Utilities pull-down.
The Recalculate window is displayed (Figure 67 on page 158).

Chapter 4. Administering IBM Z Decision Support 157

Working with record definitions in a log

Table Maintenance Utilities Edit View Other Help

-
D Recalculate 12

S Select function. Then press Enter.

/ Source table : DRL.SAMPLE_H

S
_ Function 1 1. Update and recalculate
_ 2. Delete and recalculate
_ 3. Insert and recalculate
_ 4. Recalculate
_
_
_
_ F1=Help F2=Split F4=Target F9=Swap F11=Save def
_ F12=Cancel
_
_ VMACCT_SESSION_D DRL TABLE
_ VMACCT_SESSION_M DRL TABLE

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

Figure 67. Recalculate window

3. Optionally, press F4 to specify target tables (the tables that changes in the source table should be
propagated to). If you do not specify target tables, changes are propagated to all affected tables.
The Target Tables window is displayed.
4. Select one or more target tables from the list and press Enter.
You are returned to the Recalculate window.
5. Select the desired function from the list and press Enter. Options 1, 2, and 3 are used to modify the
source table. Option 4 propagates selected source table rows without changing the source table.
If you did not choose to insert and recalculate (option 3), the Condition window is displayed (Figure 68
on page 158).

Table Utilities Edit View Other Help

–
D Recalculate 12

S S Condition

/ S Type a select condition. Then press Enter to save and return.

s
– F
– DATE = '2000-06-06' AND TIME = '13.00.00' AND
– USER_ID = 'ADAMS'
–
–
–
–
–
– F
–
– F1=Help F2=Split F9=Swap F12=Cancel
V
V
Command ===>
F1=Help F2=Split F3=Exit F5=Updates F6=PurCond F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=Display F12=Cancel

Figure 68. Condition window

6. Specify a condition to restrict rows affected in the source table and press Enter.
If you choose to update and recalculate (option 1) or insert and recalculate (option 3), the Column
Values window is displayed (Figure 69 on page 159).

158 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

Table Utilities Edit View Other Help

–
D Recalculate 12

S S Condition

/ S Column Values ROW 2 TO 8 OF 9

s
– F Type column values. Then press Enter.
–
– Column Value
– TIME
– SYSTEM_ID
– DEPARTMENT_NAME
– USER_ID
– TRANSACTIONS
– F RESPONSE_SECONDS
– CPU_SECONDS 2.0
– V
V Command ===>
F1=Help F2=Split F7=Bwd F8=Fwd F9=Swap F12=Cancel
Comma
F1=Help F2=Split F3=Exit F5=Updates F6=PurCond F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=Display F12=Cancel

Figure 69. Column Values window

7. Type column values in the fields, and press Enter.
The recalculate function is performed and you are returned to the Recalculate window.
8. Press F12 to return to the Tables window.

Importing the contents of an IXF file to a table

About this task

You might want to import data from another source into an IBM Z Decision Support table. If QMF is used
with IBM Z Decision Support, you can use the administration dialog to import data in the Integration
Exchange Format (IXF). Refer to the QMF Application Development Guide for a description of the IXF
format.
Note: When you import the file, IBM Z Decision Support replaces the contents of the table.
To import data into a table:

Procedure
1. From the Tables window (Figure 64 on page 154), select the table.
2. Select 3, Import, from the Utilities pull-down.
The Import Data Set window is displayed.
3. Type the name of the data set that contains the data you want to import and press Enter.
The data is imported into the table and you are returned to the Tables window.

Exporting table data to an IXF file

About this task

You might want to export data from an IBM Z Decision Support table to an IXF data set. If QMF is used
with the product, you can use the administration dialog to do this.
To export data from a table:

Chapter 4. Administering IBM Z Decision Support 159

Working with record definitions in a log

Procedure
1. From the Tables window (Figure 64 on page 154), select the table.
2. Select 4, Export, from the Utilities pull-down
The Export Data Set window is displayed.
3. Type the name of the data set to export data into, and press Enter.
The data is exported into the data set you specified and you are returned to the Tables window.

Purging a table

About this task

Each table in the product database is associated with a purge condition that determines how long the
data in the table is kept. See “Displaying and editing the purge condition of a table” on page 174 for a
description of how to define the purge condition for a table.
Purging the database is normally a batch process. See “Purge utility” on page 103 for a description of how
to run purge in batch.
You can also use the administration dialog to delete the data specified by the purge condition:

Procedure
1. From the Tables window (Figure 64 on page 154), select tables to purge.
Note: If you do not select any tables, IBM Z Decision Support purges the contents of all data tables
with purge conditions.
2. Select 9, Purge, from the Utilities pull-down.
The Purge Confirmation window is displayed.
3. Press Enter to confirm the purge.
The purge conditions associated with the tables are run and the statistics on the number of rows
deleted from each table are displayed.

Unloading and loading tables

About this task

When you need to change a Db2 table, for example by adding a column, you can save the existing data by
using the Db2 Unload utility. After the change to the table, you then reload the table using the Load utility.
Using Unload and Load with no change reorganizes the data.
Moreover, the possibility of reading and writing a data set of data directly on tape improves possible
recovery and backup operations.
The Load utility is used to load data into a table of a table space. It enables you to load records into
the tables and builds or extends any indexes defined on them. If the table space already contains data,
you can either add the new data, or replace the existing data with the new data. Because the Load utility
operates at a table space level, to run it you must have the required authority for all the tables of the table
space. The data set used for the Load utility can be read from both disk and tape. The Unload utility is
used to unload data from a table to a sequential data set. To use the Unload utility, the definitions of the
table space and tables must be available on the system. The data set used for the unload operation can
be saved both on disk and tape.
Note: Load and Unload work only with tables, and cannot be used with views.
To unload the contents of a table:

160 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

Procedure
1. From the Tables window (Figure 64 on page 154), select the tables to unload, as shown in Figure 70 on
page 161.

Utilities Edit View Other Help

+------------------------------------+
| 10 1. Display... |
| 3. Import... |
| 4. Export... |
| 5. Grant... |
| 6. Revoke... |
| 7. Document... |
| 8. Recalculate... |
| 9. Purge... |
| 10. Unload... |
| 11. Load... |
| 12. Reorg/Discard... |
| 13. DB2HP Unload... |
+------------------------------------+

Figure 70. Selecting tables to unload

2. Select option 10 Unload, from the Utilities pull-down menu.
The Unload Utility window opens, as shown in the following figure:

UNLOAD Utility

The UNLOAD utility will unload table data to a data set. Type the fully
qualified data set name, without quotes. Then press Enter to create the
JCL.

Type of UNLOAD . . . . . . . 1_ 1. Disk

2. Tape
Table . . . . . . . . . . : AVAILABILITY_D
UNLOAD data set name . . . . SAMPLE.DAT__________________________________

Type information in the following fields. In case of Tape UNLOAD, VOLSER is

the Tape Label. In case of Disk UNLOAD, type information only if the data
set is not available.
UNIT . . . . . . . . . . . . ________
VOLSER . . . . . . . . . . . ________

F1=Help F2=Split F9=Swap F12=Cancel

Figure 71. Unload Utility window

3. From the Unload Utility window, specify the unload type by inserting 1 for disk unload or 2 for tape
unload. The default is Disk Unload.
4. Specify the name of the table and data set you want to unload.
5. If you selected Disk Unload:
Option Description
If the data set already Leave the fields UNIT and VOLSER blank. If you need to create a new
exists data set, enter the required information in both the fields.
If you selected Tape Specify the tape unit in the UNIT field, and the tape label in the VOLSER
Unload fiel.d
6. When you are finished, press Enter.
A JCL is created and saved in your library, so that it can be used later. When the JCL is launched two
data sets are automatically created. One is used to reload data (SYSPUNCH) and the other contains the
data unloaded by the utility.
Note: When using Load on a multiple table space, you must be careful because Load works on a
complete table space at a time (for information about replacing data with Load, refer to the Db2

Chapter 4. Administering IBM Z Decision Support 161

Working with record definitions in a log

for OS/390 V5 Utility Guide and Reference). This applies especially when tables are dropped and
recreated.
For this reason, when you apply PTFs involving tables that need to be dropped and recreated, you
should follow these steps:
a. Unload the tables, if you want to keep the previously collected data.
b. Use SMP/E to apply the PTF.
c. Execute the SQL drop table statement of the above tables using either of the following:
• Db2 SPUFI
• Option 5, Process IBM Z Decision Support statements, from the Other pull-down on any primary
window of the IBM Z Decision Support administration dialogs.
d. Execute the SQL create table statements for the same tables using either of the following methods:
• Reinstall the component.
• Select Option 5, Process IBM Z Decision Support statements, from the Other pull-down on any
primary window of the IBM Z Decision Support administration dialogs. Execute the definition
members of the local or the standard definition library, depending on whether or not the
definitions have been user-modified. Ignore the error messages issued for the existing objects
and make sure that the changed tables are correctly created.
e. Load your previously unloaded data.

What to do next
To generate a job that reloads the data, from the Tables window, select option 11, Load. Then enter the
required information, as explained above.
The following example shows control statements for the Unload utility. Data is unloaded from the
AVAILABILITY_D table onto tape. The DDNAME for SYSPUNCH data set is completed with the UNIT and
VOLSER information about the Tape Unit used. The data set input from panel is SYSREC00.

//UNLOAD JOB (ACCOUNT),'NAME'

//*
//* THIS JCL HAS BEEN REWRITTEN IN ORDER
//* TO PROPERLY UNLOAD THE DATA FROM Db2 TABLES.
//* DSNTIAUL IS USED FOR UNLOAD INSTEAD OF DSNUPROC
//* UTILITY.
//* THEREFORE, PLEASE, NOTE THAT THIS IS ONLY
//* A SAMPLE THAT NEEDS TO BE PROPERLY CUSTOMIZED.
//* WARNINGS :
//* PLEASE CHECK PLAN NAME (NORMALLY DSNTIBVR),
//* V=Db2 VERSION, AND R=Db2 RELEASE;
//* TWO NEW DATASETS ARE DEFINED (SYSREC00 AND SYSPUNCH).
//* SYSPUNCH DATASET, IS CREATED AT UNLOAD STEP,
//* as USERID.SYSPUNCH (USERID.SYSPUNCH).
//* SYSREC00 DATASET IS SELECTED FROM the PREVIOUS PANEL.
//*
//* I M P O R T A N T :
//* CHECK THE DATA SET PARAMETER IF YOU HAVE CHOSEN
//* THE UNLOAD ON TAPE.
//*
//UNLOAD EXEC PGM=IKJEFT01,DYNAMNBR=20
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DSN6)
RUN PROGRAM(DSNTIAUL) PLAN(DSNTIB71) -
PARMS('SQL') LIB('DSN710.RUNLIB.LOAD')
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSREC00 DD DSN=USERID.DAT.UNLOAD,
// UNIT=TAPE_UNIT,
// SPACE=(4096,(5040,504)),
// DISP=(,PASS),
// LABEL=(1,SL),
// DCB=(RECFM=FB,LRECL=410,BLKSIZE=27880),
// VOL=SER=TAPE_LABEL
//SYSPUNCH DD DSN=USERID.SYSPUNCH,
// UNIT=xxxx,

162 IBM Z Decision Support : Administration Guide and Reference

 Working with record definitions in a log

// VOL=SER=xxxxxx,
// SPACE=(4096,(5040,504)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920),
// DISP=(NEW,CATLG,CATLG)
//SYSIN DD *
SELECT * FROM USERDB.AVAILABILITY_D;

The following example shows control statements for the Load utility. Data is loaded from tape into the
AVAILABILITY_D table. The DDNAME for the SYSPUNCH data set is completed with the UNIT and VOLSER
information about the Tape Unit used. The data set input from panel is SYSREC00.

//LOAD JOB (ACCOUNT),'NAME'

//*
//* THIS JCL HAS BEEN REWRITTEN IN ORDER
//* TO PROPERLY LOAD THE DATA FROM Db2 TABLES.
//* DSNTIAUL IS PREVIOUSLY USED FOR UNLOAD
//* INSTEAD OF DSNUPROC UTILITY.
//* THEREFORE, PLEASE, NOTE THAT THIS IS ONLY
//* A SAMPLE THAT NEEDS TO BE PROPERLY CUSTOMIZED.
//* WARNINGS :
//* PLEASE CHECK PLAN NAME (NORMALLY DSNTIBVR),
//* V=Db2 VERSION, AND R=Db2 RELEASE;
//* TWO NEW DATASETS ARE DEFINED (SYSREC00 AND SYSPUNCH).
//* as USERID.SYSPUNCH (USERID.SYSPUNCH).
//* SYSREC00 DATASET IS SELECTED FROM the PREVIOUS PANEL
//*
//*
//* I M P O R T A N T :
//* SYSPUNCH DATASET NEEDS TO BE EDITED FROM USER
//* BEFORE EXECUTING LOAD,
//* INSERTING "RESUME YES LOG YES" OPTIONS,
//* IN ORDER TO CONTAIN COMMAND :
//* "LOAD DATA RESUME YES LOG YES INDDN
//* SYSREC00 INTO TABLE tablename"
//* CHECK THE DATA SET PARAMETER IF YOU HAVE CHOSEN
//* THE LOAD FROM TAPE.
//*
//LOAD EXEC DSNUPROC,PARM='DSN6,MYUID'
//DSNTRACE DD SYSOUT=*
//SORTLIB DD DSN=SYS1.SORTLIB,DISP=SHR
//SORTWK01 DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND)
//SORTWK02 DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND)
//SORTWK03 DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND)
//SORTWK04 DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND)
//SORTOUT DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND)
//SYSREC00 DD DSN=USERID.DAT.UNLOAD,
// UNIT=TAPE_UNIT,VOL=SER=TAPE_LABEL,
// LABEL=(1,SL),
// DISP=SHR
//SYSUT1 DD UNIT=SYSDA,SPACE=(4000,(20,20),,,ROUND)
//SYSIN DD DSN=USERID.SYSPUNCH,DISP=SHR

Integration with Db2 High Performance Unload

The Db2 High Performance Unload is a high-speed utility for unloading Db2 tables from either a table
space or an image copy. Tables are unloaded to one or more files based on a specified format. You can use
it to extract data for movement across enterprise systems or for reorganization in-place. Db2 HP Unload
can do the following:
• Rapidly unload table spaces
• Run parallel unloads accessing the same table space
• Unload against any image copy to eliminate interference with Db2 production databases
• Unload selected rows and columns
• Unload a maximum number of rows, unloading one row out of every n rows
• Generate load control statements for a subsequent reload.
The Db2 High Performance Unload can manage an UNLOAD command and an optional SELECT statement.
The syntax of the SELECT statement is compatible with the syntax of the Db2 SELECT statement. The
SELECT statement is used to define which table data must be extracted onto data set or tape (for
example, if in your table a DATE field is present, you can extract all the data with a date later than

Chapter 4. Administering IBM Z Decision Support 163

Working with record definitions in a log

2002-01-01, by writing the appropriate WHERE condition in the SELECT statement of the UNLOAD
command).

Running Db2 High Performance Unload utility

About this task

To run the Db2 High Performance Unload utility, you must have the product correctly installed and
configured on the system.
Note: The DB2HP Unload utility integration works in batch mode; it can run in interactive mode only if
you have Db2 Administration Tool, or Db2 Tools Launchpad, installed on your system. These products are
optional and not needed to run the DB2HP Unload utility.
To run the utility follow these steps:

Procedure
1. From the Tables window, select the table to unload, as shown in Figure 64 on page 154
2. From the Utilities pull-down menu, select option DB2HP Unload, as shown in Figure 70 on page 161.
Note: The Db2 High Performance Unload utility can only be run on tables. It cannot be run on views.
3. From the Db2 High Performance Unload Utility window, specify the unload type by inserting 1 for disk
unload or 2 for tape unload. The default value is disk unload. Then, specify the name of data set that
will be used to store the unloaded data, as shown in the following window.

DB2HP Unload Utility

The DB2HP Unload will unload table data to a data set. You can use the
utility only if the DB2HPU product is present on system. Type the fully
qualified data set name, without quotes. Then press Enter to create the
JCL.

Type of DB2HP Unload . . . . 1_ 1. Disk

2. Tape
Table . . . . . . . . . . : AVAILABILITY_D
Unload data set name . . . . SAMPLE.DAT__________________________________

Type information in the following fields. In case of Tape UNLOAD, VOLSER is

the Tape Label. In case of Disk UNLOAD, type information only if the data
set is not available.
UNIT . . . . . . . . . . . . ________
VOLSER . . . . . . . . . . . ________

F1=Help F2=Split F9=Swap F12=Cancel

Figure 72. Db2 High Performance Unload utility

4. If you selected Disk:
• If the data set already exists, leave the fields UNIT and VOLSER blank. If you need to create a new
data set, enter the required information in both the fields.
If you selected Tape:
• Specify the tape unit in the UNIT field, and the tape label in the VOLSER field
5. When you are finished, press Enter.
A JCL is created and saved in your library so that it can be used later. When the JCL is launched two
data sets are automatically created. One is used to reload data (SYSPUNCH), the other contains the
data unloaded by the utility.

Sample control statement for Db2 High Performance Unload utility

Data has been unloaded from the AVAILABILITY_D table; the DDNAME for SYSPUNCH data set must be
completed with UNIT and VOLSER information. The data set input from panel is SYSREC00.

164 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

//DB2HPU JOB (ACCOUNT),'NAME'

//*
//* THIS JCL HAS BEEN REWRITTEN IN ORDER
//* TO PROPERLY UNLOAD THE DATA FROM Db2 TABLES.
//* THE Db2 High Performance Unload (INZUTILB)
//* IS USED FOR UNLOAD DATA IN BATCH MODE.
//* THEREFORE, PLEASE, NOTE THAT THIS IS ONLY
//* A SAMPLE THAT NEEDS TO BE PROPERLY CUSTOMIZED.
//* WARNINGS :
//* V=Db2 VERSION, AND R=Db2 RELEASE;
//* TWO NEW DATASETS ARE DEFINED (SYSREC00 AND SYSPUNCH).
//* SYSPUNCH DATASET, IS CREATED AT UNLOAD STEP,
//* as USERID.SYSPUNCH (USERID.SYSPUNCH).
//* SYSREC00 DATASET IS SELECTED FROM the PREVIOUS PANEL.
//*
//* I M P O R T A N T :
//* CHECK THE DATA SET PARAMETER IF YOU HAVE CHOSEN
//* THE UNLOAD ON TAPE.
//*
//STEP1 EXEC PGM=INZUTILB,REGION=0M,DYNAMNBR=99,
// PARM='DSN6,DB2UNLOAD'
//STEPLIB DD DSN=DSN710.SINZLINK,DISP=SHR
//*
//SYSIN DD *
UNLOAD TABLESPACE PRM1DB.DRLSCOM
DB2 YES
QUIESCE YES QUIESCECAT YES
OPTIONS DATE DATE_A
SELECT * FROM PRM1.AVAILABILITY_D
OUTDDN (SYSREC00)
FORMAT DSNTIAUL
LOADDDN SYSPUNCH LOADOPT (RESUME NO REPLACE)
/*
//SYSPRINT DD SYSOUT=*
//*
//******* DDNAMES USED BY THE SELECT STATEMENTS ********
//*
//SYSREC00 DD DSN=SAMPLE.DAT,
// UNIT=3390,
// SPACE=(4096,(1,1)),
// DISP=(NEW,CATLG,CATLG),
// DCB=(RECFM=FB,LRECL=410,BLKSIZE=27880),
// VOL=SER=MYVOL
//SYSPUNCH DD DSN=USERID.SYSPUNCH,
// UNIT=xxxx,
// VOL=SER=xxxxxx,
// SPACE=(4096,(1,1)),
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920),
// DISP=(NEW,CATLG,CATLG)

Working with tables and update definitions

The rest of this chapter describes working with tables and update definitions.

Opening a table to display columns

About this task

You can use the administration dialog to view a table definition.
To open a table:

Procedure
1. From the Tables window (Figure 64 on page 154), select the table definition you plan to view.
2. Press Enter.
The table definition is opened. Figure 73 on page 166 shows an example of an opened table definition.

Chapter 4. Administering IBM Z Decision Support 165

Working with tables and update definitions

Table SAMPLE_H ROW 1 TO 9 OF 9

Select a column. Then press Enter to display the definition.

Database . . : DRLDB Tablespace . . : DRLSSAMP

Comments . . . This table provides hourly sample data. >
/ Column Type Length Nulls Primary Key
_ DATE DATE 4 No Yes
_ TIME TIME 3 No Yes
_ SYSTEM_ID CHAR 4 No Yes
_ DEPARTMENT_NAME CHAR 8 No Yes
_ USER_ID CHAR 8 No Yes
_ TRANSACTIONS INTEGER 4 Yes No
_ RESPONSE_SECONDS INTEGER 4 Yes No
_ CPU_SECONDS FLOAT 8 Yes No
_ PAGES_PRINTED INTEGER 4 Yes No
******************************* BOTTOM OF DATA ********************************

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F5=Add col F6=Indexes F7=Bkwd
F8=Fwd F9=Swap F10=Show fld F12=Cancel

Figure 73. Table window

3. Type changes to comments in the Comments field and press Enter.
Note: Press F10 to see the entire Comments field.
The changes to the comments are saved.

Displaying and modifying a column definition

About this task

To display and modify a column definition:

Procedure
1. From the Table window, select the column, and press Enter.
The Column Definition window for the column is displayed (Figure 74 on page 166).

Table SAMPLE_H ROW 1 TO 9 OF 9

S Column Definition

D Modify comments if required. Then press Enter to save and return.

C
/ Name.... : CPU_SECONDS
– Comments.. : Total CPU time, in seconds. This is the >
– Length... : 8
– Type.... : FLOAT
– Primary key: No
– Nulls... : Yes
–
–
s
–
*
F1=Help F2=Split F9=Swap F10=Show fld F12=Cancel

Command ===>
F1=Help F2=Split F3=Exit F5=Add col F6=Indexes F7=Bkwd
F8=Fwd F9=Swap F10=Show fld F12=Cancel

Figure 74. Column Definition window

2. Type changes to comments in the Comments field, and press Enter.

166 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Note: Press F10 to see the entire Comments field.

The changes are saved and you are returned to the Tables window.

Adding a column to a table

About this task

You can add columns to a table, but you cannot delete columns.
To add a column to a table:

Procedure
1. From the Table window, press F5.
The Add Column window is displayed(Figure 75 on page 167).

– Add Column
S
Type column information. Then press Enter to save and return.
D
C Name (required)
/ Comments >
– Length Primary key . 2 1. Yes
– 2. No
– Type 1. Char Nulls 1 . 1. Default
– 2. Varchar 2. NOT NULL
– 3. Smallint 3. NOT NULL WITH
– 4. Integer DEFAULT
– 5. Float
– 6. Decimal
– 7. Date
* 8. Time
9. Timestamp
10. Graphic
11. Vargraphic
12. Long varchar
C 13. Long vargraphic
F1=Help F2=Split F9=Swap F10=Show fld F12=Cancel

Figure 75. Add Column window

2. Type information for the new column in the window, and press Enter.
The new column is added to the table andyou are returned to the Add Column window.
3. When you finish adding columns to the table, press F12.
You are returned to the Tables window.

Displaying and adding a table index

About this task

If a table has a primary key, it must have an index on that key (the primary index). Some queries access
tables using the primary index.
A table can have more than one index. Secondary indexes can give you faster data retrieval, but increase
the amount of time that collect requires to update those tables.
Note: If you want to work with index spaces, see “Displaying and modifying a table or index space” on
page 176.
To view or add indexes to a table:

Chapter 4. Administering IBM Z Decision Support 167

Working with tables and update definitions

Procedure
1. From the Tables window, select a table and press Enter.
2. From the Table window, press F6.
The Indexes window is displayed (Figure 76 on page 168).

Indexes ROW 1 FROM 1

Select an index. Then press Enter to display.

/ Indexes Table Unique Cluster

_ SAMPH_IX SAMPLE_H Yes Yes
******************************* BOTTOM OF DATA ********************************

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F5=Add ind F7=Bkwd F8=Fwd
F9=Swap F11=Delete F12=Cancel

Figure 76. Indexes window

3. To view an index definition, select the index and press Enter.
The Index window is displayed (Figure 77 on page 168). The index on the primary key should be a
unique, clustering index. Refer to the Db2 documentation for a description of the other index options.

Index SAMPH_IX ROW 1 TO 7 OF 9

S
Press Enter to return.
/
/ Table name : SAMPLE_H
* *
Storage group : SYSDEFLT Subpages. . . :4
Primary quantity : 6 Unique . . . :YES
Secondary quantity : 3 Cluster . . . :YES
Erase : NO Buffer pool . :BPO

Column name Column type Seq Order

DATE DATE 1 ASC
TIME TIME 2 ASC
SYSTEM_ID CHAR 3 ASC
DEPARTMENT_NAME CHAR 4 ASC
USER_ID CHAR 5 ASC
TRANSACTIONS INTEGER
RESPONSE_SECONDS INTEGER

C Command ===>

F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 77. Index window

4. Press Enter to return to the Indexes window.
5. From the Indexes window, press F5 to add an index to the table.
The Add Index window is displayed (Figure 78 on page 169).

168 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Add Index ROW 1 TO 5 OF 9

S
Type information. Then press Enter to save and return.
/
Index name (required)
Table Name : SAMPLE_H

Storage group Subpages

Primary quantity Unique 2 1. Yes
Secondary quantity 2. No
Erase 1 1. No Cluster 2 1. Yes
2. Yes 2. No
Bufferpool BP0
Column name Column type Seq Order
DATE DATE
TIME TIME
SYSTEM_ID CHAR
DEPARTMENT_NAME CHAR
USER_ID CHAR

C Command ===>
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 78. Add Index window

6. Type the information for the new index and press Enter.
The index is added to the table and you are returned to the Indexes window.

What to do next
Note: To modify an index, delete and recreate it.

Deleting a table index

About this task

To delete a table index:

Procedure
1. From the Indexes window, select the index and press F11.
A confirmation window is displayed.
2. Press Enter to confirm the deletion.
You are returned to the Indexes window.

Displaying and modifying update definitions of a table

About this task

The instructions for entering data from logs into Db2 tables in the product database are provided by
update definitions. An update definition describes how the data in a source (a record or a table) is
summarized into a target table during the collect process. Refer to the Language Guide and Reference for
information about how to define update definitions using the log collector language.
Update definitions are supplied for all data tables. You can use the administration dialog to modify these
update definitions.
To display and edit the update definitions of a table:

Chapter 4. Administering IBM Z Decision Support 169

Working with tables and update definitions

Procedure
1. From the Tables window (Figure 64 on page 154), select the table and press F5.
The Update Definitions window for the table is displayed (Figure 79 on page 170). All update
definitions where the selected table is either the source or the target are included.

Update Definitions ROW 1 TO 2 OF 2

Select an update definition. Then press Enter to display definition.

/ Updates Source Target

_ SAMPLE_H_M SAMPLE_H SAMPLE_M
_ SAMPLE_01_H SAMPLE_01 SAMPLE_H
******************************* BOTTOM OF DATA *******************************

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F5=New F6=Prt list F7=Bkwd
F8=Fwd F9=Swap F10=Save def F11=Delete F12=Cancel

Figure 79. Update Definitions window

2. Select the update definition to modify and press Enter.
The Update Definition window for the update definition is displayed (Figure 80 on page 170).

SAMPLE_01_H Update Definition ROW 1 TO 9 OF 9

Type information. Press F3 to save.

Source . . : SAMPLE_01 Prefix : (blank for record)

Target . . : SAMPLE_H Prefix : DRL
Section . . . __________________ +
Condition . . ________________________________________ >
Comments . . ________________________________________ >

Column Function Expression

DATE __________ S01DATE >
TIME __________ ROUND(S01TIME,1 HOUR) >
SYSTEM_ID __________ S01SYST >
DEPARTMENT_NAME __________ VALUE(LOOKUP DEPARTMENT_NAME IN DRL >
USER_ID __________ S01USER >
TRANSACTIONS SUM S01TRNS >
RESPONSE_SECONDS SUM S01RESP >
CPU_SECONDS SUM S01CPU/100.0 >
PAGES_PRINTED SUM S01PRNT >

Command ===> ______________________________________________________________

F1=Help F2=Split F3=Exit F4=Prompt F5=Abbrev F6=Distrib
F7=Bkwd F8=Fwd F9=Swap F10=Show fld F11=Schedule F12=Cancel

Figure 80. Update Definition window

Complete these fields in the window:

Section
The name of a repeated section in a source record.
If the source is a record, you can type the name of a repeated section in this field. IBM Z Decision
Support uses the update during collection to process each repeated section.

170 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Condition
A condition that is applied to source fields or columns.
Type an expression that evaluates as either true or false in this field. IBM Z Decision Support
evaluates the expression to determine if it is true before processing the source with the update.
Comments
A description of the update definition.
Column
All columns of the target table.
Function
Describes the accumulation function to use. Blank means that the column is a key (a GROUP BY
column). For data columns, the value of this field can be SUM, MIN, MAX, COUNT, FIRST, LAST,
AVG, and PERCENT.
To use the MERGE function, identify input to the function by designating a column for each of these
functions: INTTYPE, START, END, and QUIET.
Expression
Describes how the value in the column should be derived from source fields, columns, or
abbreviated names of expressions. (See “Working with abbreviations” on page 172 for more
information.) If the update does not affect the value of the column, there is no entry in the
expression field.
For an AVG column, type the expression, followed by a comma, and a column name. For a
PERCENT column, type the expression, followed by a comma, a column name, a comma, and a
percentile value (without the percent sign).
Refer to the Language Guide and Reference for more information about using log collector language:
• Functions
• Accumulation functions
• Expressions
• Statements
• Averages
• Percentiles
3. Type any modifications to the update definition in the fields.
4. Press F5 to modify abbreviations in this update definition.
The Abbreviations window is displayed. See “Working with abbreviations” on page 172, for more
information.
5. Press F6 to modify the distribution clause associated with the update definition.
The Distribution window is displayed. See “Modifying a distribution clause” on page 173 for more
information.
6. Press F11 to modify the apply schedule clause associated with an update definition.
The Apply Schedule window is displayed. See “Modifying an apply schedule clause” on page 173 for
more information.
7. Press F3 when you finish modifying the update definition.
The changes are saved and you are returned to the Update Definitions window.
8. Repeat this procedure to modify other update definitions or press F3 again to return to the Tables
window.

Chapter 4. Administering IBM Z Decision Support 171

Working with tables and update definitions

Working with abbreviations

About this task

You can use abbreviations to give names to long expressions that are used several times. Using
abbreviations improves product performance because expressions are evaluated only once.
Defining abbreviations with the administration dialog is equivalent to using the LET clause in a log
collector DEFINE UPDATE statement to assign an expression to a variable name. (Refer to the description
of the DEFINE UPDATE statement in the Language Guide and Reference for more information.)
To modify an abbreviation:

Procedure
1. From the Update Definition window (Figure 80 on page 170), press F5.
The Abbreviations window is displayed (Figure 81 on page 172).

Abbreviations ROW 1 TO 3 OF 3

Modify expressions if required. Press F3 to save and return.

/ Abbreviation Expression
TS1 TIMESTAMP(SMF70DAT,SMF70IST)+(SMF70INT
D1 DATE(TS1)
T1 TIME(TS1)
BOTTOM OF DATA

Command ===>
F1=Help F2=Split F3=Exit F5=Add abbr F7=Bkwd
F8=Fwd F9=Swap F10=Show fld F11=Delete F12=Cancel

Figure 81. Abbreviations window

2. Type modifications in the fields and press Enter.
The changes are saved and you are returned to the Update Definition window.

Adding an abbreviation to an update definition

About this task

To add an abbreviation to an update definition:

Procedure
1. From the Abbreviations window, press F5.
The Abbreviation window is displayed.
2. Type the abbreviation and the expression in the fields and press Enter.
The abbreviation is added and you are returned to the Abbreviations window.

172 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Deleting an abbreviation from an update definition

About this task

To delete an abbreviation from an update definition:

Procedure
From the Abbreviations window, select the abbreviation to delete, and press F11.
The abbreviation is deleted from the list.

Modifying a distribution clause

About this task

The distribution clause of an update definition specifies that source fields or columns are distributed over
a time period. It can be used when you have a record that contains data for a long time period and you do
not want all values to be summarized at the start or end time.
To modify the distribution clause associated with an update definition:

Procedure
1. From the Update Definition window (Figure 80 on page 170), press F6.
The Distribution window is displayed (Figure 82 on page 173).

Distribution ROW 1 TO 7 OF 65

Type information. Then press Enter to save and return.

By period 60 VALUE(LOOKUP TIME_RESOLUTION IN DRL.M > (seconds)

Start timestamp TIMESTAMP(SMF33TSD,SMF33TST) >
End timestamp TIMESTAMP(SMF33TED,SMF33TET) >
Timestamp INTERVAL_START (any ID)
Interval INTERVAL_LENGTH(any ID)

/ Column/Field
– SMF33ACL
– SMF33ACT
– SMF33ALN
– SMF33AOF
– SMF33AON
/ SMF33CN
/ SMF33CNA

Command ===>
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap
F10=Show fld F11=Delete F12=Cancel

Figure 82. Distribution window

2. Type modifications in the fields and press Enter.
The changes are saved and you are returned to the Update Definition window.

Modifying an apply schedule clause

About this task

IBM Z Decision Support uses the apply schedule clause of an update definition in calculating availability.
The clause specifies how the product should merge schedule information in control tables (see “Control
tables” on page 222) with detailed availability information.

Chapter 4. Administering IBM Z Decision Support 173

Working with tables and update definitions

To modify the apply schedule clause associated with an update definition:

Procedure
1. From the Update Definition window (Figure 80 on page 170), press F11.
The Apply Schedule window is displayed (Figure 83 on page 174).

AVAIL_T_D Update Defintion ROW 1 TO 9 OF 15

Apply Schedule

Type information. Then press Enter to save and return.

Name LOOKUP SCHEDULE_NAME IN DRL.AVAILABILITY > (expression)

Interval type INTERVAL_TYPE + (column)

Start time START_TIME + (column)
Stop time END_TIME + (column)

Status SCHED_STAT Any ID

F1=Help F2=Split F4=Prompt F9=Swap F10=Show fld

F11=Delete F12=Cancel

MEASURED_HOURS SUM INT_TIME >

UP_IN_SCHEDULE SUM CASE WHEN INT_TYPE = '= ' AND SCHED_ >

Command ===>
F1=Help F2=Split F3=Exit F4=Prompt F5=Abbrev F6=Distrib
F7=Bkwd F8=Fwd F9=Swap F10=Show fld F11=Schedule F12=Cancel

Figure 83. Apply Schedule window

2. Type modifications in the fields and press Enter.
The changes are saved and you are returned to the Update Definition window.

What to do next
Refer to the Language Guide and Reference for more information about using the log collector language to:
• Determine resource availability
• Calculate the actual availability of a resource
• Compare actual availability to scheduled availability

Displaying and editing the purge condition of a table

About this task

IBM Z Decision Support uses purge conditions to specify when old data should be purged from tables. A
table can have only one purge condition. Purge conditions are supplied for all data tables. You can use the
administration dialog to modify the purge condition of a table.
The administrative report PRA003 produces a complete list of all current product purge definitions. For
more information about this report, see “PRA003 - Table Purge Condition” on page 258.
To display and edit the purge condition of a table:

Procedure
1. From the Tables window (Figure 64 on page 154), select the table to update and press F6.

174 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

The Retention Period window is displayed (Figure 84 on page 175) if the purge condition is blank or
has the standard format (column_name < CURRENT DATE - n DAYS), and if the column name,
which can be an expression (for example, DATE(START_TIMESTAMP)), is less than 18 characters.

Table Maintenance Utilities Edit View Other Help

D Retention Period for MVS_ADDRSPACE_D

S Type information. Then press Enter to save and return.

/ Retention period 30 Days

Column DATE + Date/Timestamp

s

F1=Help F2=Split F4=Prompt F5=Conditio F9=Swap

F11=Save def F12=Cancel

MVS_WORKLOAD_HV2 DRL VIEW

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

Figure 84. Retention Period window

2. Modify information in the fields. The column is the date or timestamp column in the table that IBM Z
Decision Support uses to determine the age of the rows.
3. Press Enter.
The changes are saved and you are returned to the Tables window.
4. If the purge condition does not have the standard format, the Purge Condition window is displayed
(Figure 85 on page 175) instead of the Retention Period window.
This window is displayed also if you press F5 from the Retention Period window.

Table Maintenance Utilities Edit View Other Help

D MVS_ADDRSPACE_T Purge Condition

S Modify as required. Then press Enter to save and return.

/ SQL condition

( JOB_TIMESTAMP < CURRENT TIMESTAMP - 7 DAYS AND SYSTEM_ABEN

D_CODE IS NULL AND USER_ABEND_CODE IS NULL ) OR ( JOB _TIMEST
AMP < CURRENT TIMESTAMP - 45 DAYS AND ( SYSTEM_ABEND_CODE IS
NOT NULL OR USER_ABEND_CODE IS NOT NULL ) )

F1=Help F2=Split F9=Swap F11=Save def F12=Cancel

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

Figure 85. Purge Condition window

5. Modify the SQL condition, and press Enter.
The changes are saved and the previous window is displayed.

Chapter 4. Administering IBM Z Decision Support 175

Working with tables and update definitions

Displaying and modifying a table or index space

About this task

Each table in the product database is in a table space, and each index is in an index space. IBM Z Decision
Support usually uses one table space for each component. You can use the administration dialog to work
with table and index spaces.
Note: The method described here makes changes directly to your Db2 database, and does not affect
the component definition. You lose such direct changes if you delete and reinstall a component. To
change the component definition to keep it in line with the database, use the Space pull-down in the
Components window, in addition to making the direct change as described in the following steps.
To make a change to a table space:

Procedure
1. From the Tables window, select the Maintenance pull-down. Do not select a table first.
2. The pull-down has these options:

1. Tablespace...
2. Index and index space...

To change table space parameters, select 1. The Tablespace window is displayed (with the Tablespace
pull-down illustrating the options available: you can use the Utilities pull-down to reorganize or get
statistics on a table space).

Tablespace Utilities Other Help

1. New... F5 ces in SVTDB database Row 1 to 20 of 234

2. Open... Enter
3. Delete ess Enter to open a tablespace definition.
4. Save definition
5. Print List
6. Exit ondary Storage grp Type Locksize
20 SVTSG SEGMENTED TABLE
DRLSCI01 60000 30000 SVTSG SEGMENTED TABLE
DRLSCI02 60000 30000 SVTSG SEGMENTED TABLE
DRLSCI03 60000 30000 SVTSG SEGMENTED TABLE
DRLSCI04 40000 20000 SVTSG SEGMENTED TABLE

DRLSIMST 100000 50000 SVTSG SEGMENTED TABLE

DRLSIMSY 100000 50000 SVTSG SEGMENTED TABLE
DRLSINFO 600 300 SVTSG SEGMENTED TABLE
DRLSMAA 60000 30000 SVTSG SEGMENTED TABLE

Command ===>
F1=Help F2=Split F3=Exit F5=New F7=Bkwd F8=Fwd
F9=Swap F10=Actions F12=Cancel

Figure 86. Tablespaces window

You can use the Save definition option to create SQL commands that can recreate the selected table
space. Note that this does not update the component definition: only the definition of the selected
table space is saved.
3. Select a table space and press Enter. The Tablespace window is displayed, which you can use to
change the table space parameters. Change the parameters and press Enter.

176 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Tablespace DRLSCI06

Type information. Then press Enter to save and return.

Type . . . . . . . . . : 2 1.Simple
2.Segmented
3.Partitioned

Storage group . . . . . SVTSG VCAT . . . ________

Primary quantity . . 20000
Secondary quantity 10000
Erase . . . . . . . . 2 1. Yes
2. No

Locksize . . . . . . . . 4 1. Any
2. Tablespace
3. Page
4. Table

Close . . . . . . . . . 1 1. Yes Compress __ 1. Yes

2. No 2. No

Bufferpool . . . . . . . BP0 Dsetpass . . . . . . . . ________

Freepage . . . . . . . . 0 Segment size . . . . . : 8
Pctfree . . . . . . . . 5 Number of partitions . : 0

F1=Help F2=Split F5=Tables F6=Parts F7=Bkwd F8=Fwd

F9=Swap F12=Cancel

Figure 87. Tablespace DRLxxx

IBM Z Decision Support takes action depending on the parameters to be changed:

Where reorganization is needed
Some parameter changes need a database reorganization before they take effect. In this case the
product :
a. Makes the change, using the ALTER TABLESPACE command.
b. Creates a batch job to reorganize the database, which you can submit when it is convenient.
Where the database needs to be stopped
Some parameter changes need exclusive use of the database. In this case the product creates a
batch job that:
a. Stops the database.
b. Makes the change, using the ALTER TABLESPACE command.
c. Starts the database again.
Do not submit the job if some task, for example a collect, is using the table space, because this
stops the collect job.
In other cases
Some parameter changes can be made immediately. IBM Z Decision Support issues the ALTER
TABLESPACE command online.
Press F1 to get more information about a parameter, or refer to the discussion of designing a database
in Db2 for z/OS: Administration Guide and Reference.

Making changes to an index space

About this task

To make a change to an index space:

Chapter 4. Administering IBM Z Decision Support 177

Working with tables and update definitions

Procedure
1. From the Tables window (Figure 64 on page 154), select the Maintenance pull-down. Do not select a
table first.
2. To change index space parameters, select 2. The Indexes window is displayed (with the Index pull-
down illustrating the options available; you can use the Utilities pull-down to reorganize an index
space).

Index Utilities Other Help

1. Open...Enter ndexes in SVTDB database Row 1 to 21 of 443

2. Delete
3. Print List ress Enter to display.
4. Exit Indexspace
Table name Indexspace Unique Cluster
AVAILD_IX AVAILABILITY_D AVAILDRI YES YES
AVAILM_IX AVAILABILITY_M AVAILMRI YES YES
AVAILP_IX AVAILABILITY_PARM AVAILPRI YES YES
AVAILT_IX AVAILABILITY_T AVAILTRI YES YES
AVAILW_IX AVAILABILITY_W AVAILWRI YES YES

CICS_DLI_TRAN_D CICS_DLI_TRAN_D CICS1TA1 YES YES

CICS_DLI_TRAN_W CICS_DLI_TRAN_W CICS1TR4 YES YES
CICS_DLI_USR_D CICS_DLI_USR_D CICS1SKV YES YES

Command ===>
F1=Help F2=Split F3=Exit F7 =Bkwd F8=Fwd F9=Swap
F10=Actions 12=Cancel

Figure 88. Indexes window

3. Select an index space and press Enter. An index window will be displayed, which you can use to
change the index space parameters: change the parameters and press Enter.

Index CICS_A_DLI_USR_W

Press Enter to save and return.

Table name . . . . . . : CICS_A_DLI_USR_W

Indexspace name . . . : CICS1S6O

Storage group . . . . . SVTSG VCAT . . . . . . . . ________

Primary quantity . . 20000 Unique . . . . . . . 1 1. Yes
Secondary quantity 10000 2. No
Erase . . . . . . . . 2 1. Yes Cluster . . . . . . 1 1. Yes
2. No 2. No
Close . . . . . . . . . 1 1. Yes Part . . . . . : 2 1. Yes
2. No 2. No

Subpages . . . . . . . . 4 Pctfree . . . . . . 10
Bufferpool . . . . . . . BP0 Dsetpass . . . . . . ________
Freepage . . . . . . . . 0

F1=Help F2=Split F5=Columns F6=Parts F7=Bkwd F8=Fwd

F9=Swap F12=Cancel

Figure 89. Index window

IBM Z Decision Support takes action depending on the parameters to be changed:

Where the index must be recreated
In this case the product:
a. Asks you to confirm the change.
b. Deletes the index, with the DROP command.
c. Redefines the index, using the DEFINE command.
Where the database needs to be stopped
Some parameter changes need exclusive use of the database. In this case the product creates a
batch job that:
a. Stops the database.
b. Makes the change, using the ALTER command.
c. Starts the database again.

178 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Do not submit the job if some task, for example a collect, is using the index space, because this
stops the collect job.
In other cases
Some parameter changes can be made immediately. IBM Z Decision Support issues the ALTER
command online.
Press F1 to get more information about a parameter, or refer to the discussion of designing a database
in Db2 for z/OS: Administration Guide and Reference.

Making table space parameter changes that do not require offline or batch action

About this task

If you want just to make table space parameter changes that do not require offline or batch action, you
can use this alternative method:

Procedure
1. From the Tables window (Figure 64 on page 154), select a table in the table space to open.
2. Select 5, Open Tablespace, from the Table pull-down.
IBM Z Decision Support displays the Tablespace window.

- Tablespace DRLSSAMP
D
Type information. Then press Enter to save and return.
S
More: +
/ Name ......... : DRLSSAMP
s
Type ......... : 2 1.Simple
2.Segmented
3.Partitioned

VCAT

Storage group SYSDEFLT

Primary quantity 3
Secondary quantity 3
Erase 2. 1. Yes
2. No

Command ===>
C F1=Help F2=Split F5=Tables F7=Bkwd F8=Fwd F9=Swap
F12=Cancel

Figure 90. Tablespace window

3. Type any changes in the fields.
Note: You can scroll the window to display more options.
4. Press F5 to see a list of tables in the table space.
The Tables window is displayed.
5. Press Enter when you finish viewing this window.
You are returned to the Tablespace window.
6. Press Enter.
The changes to the tables pace are saved and you are returned to the Tables window.

Chapter 4. Administering IBM Z Decision Support 179

Working with tables and update definitions

Displaying a view definition

About this task

You can use the administration dialog to display a view definition created with SQL statements.
To display the view definition:

Procedure
1. From the Tables window, select a view to display, and press Enter.
The View window is displayed (Figure 91 on page 180).

Table Utilities Edit View Other Help

View MSG_SYSLOG_DV ROW 1 TO 4 OF 4

S Type information. Then press Enter to save and return.

/ Comments ..... This view provides daily statistics on J >

Column Comments
DATE Date when the SYSLOG records were written >
PERIOD_NAME Name of the period. This is derived using >
/
JES_COMPLEX Name of the JES complex. From the SET JE >
MESSAGES_TOT Total number of messages. This is the co >
BOTTOM OF DATA

Command ===>
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap
F10=Showfld F12=Cancel

F8=Fwd F9=Swap F10=Actions F11=Display F12=Cancel

Figure 91. View window

2. You can change any of the comments in a view definition. To change a comment, type the text in the
Comments field.
3. Press Enter when you finish displaying the view definition.
The changes are saved and you are returned to the Tables window.

Printing a list of IBM Z Decision Support tables

About this task

IBM Z Decision Support maintains a list of all tables in the product database. You can use the
administration dialog to print a list of these tables.

Procedure
1. From the Table pull-down in the Tables window (Figure 64 on page 154), select 8, Print list.
The Print Options window is displayed.
2. Type the required information, and press Enter.
The list of IBM Z Decision Support tables is routed to the destination you specified.

180 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Saving a table definition in a data set

About this task

Each table in the IBM Z Decision Support database is defined using SQL. You can use the administration
dialog to save the SQL table definition statement in a data set.
To save a table definition statement in a data set:

Procedure
1. From the Tables window (Figure 64 on page 154), select the table definition to save in a data set.
2. Select 7, Save definition, from the Table pull-down.
The Save Data Set window is displayed.
3. Type the data set name in the field, and press Enter.
The table definition in the data set that you specified is saved and you are returned to the Tables
window.

Listing a subset of tables in the Tables window

About this task

When you select 4, Tables, from the Administration window, all tables in the IBM Z Decision Support
database are listed in the Tables window. You can use the administration dialog to list only a subset of
tables in the IBM Z Decision Support database in the Tables window.
To specify which tables should appear in the Tables window:

Procedure
1. From the View pull-down in the Tables window (Figure 64 on page 154), select 2, Some, and press
Enter.
IBM Z Decision Support displays the Select Table window.
2. Type selection criteria in the fields, and press Enter.
Note: You can see a list of components by pressing F4.
The tables that correspond to the criteria you specified are listed.
To list all the tables, from the View pull-down in the Tables window, select 1, All. All the tables in the
IBM Z Decision Support database are listed.

Creating a table

About this task

IBM Z Decision Support stores data collected from logs in Db2 tables. Each component includes table
definitions for tables that it uses. However, you might need to create additional tables.
You can use the administration dialog to create a table. You should have a working knowledge of Db2
databases before attempting to create a table. Refer to the Db2 documentation for more information.
Note: Views cannot be created from the administration dialog. Refer to the Db2 documentation for a
description of how to create views using SQL.
To create a table:

Chapter 4. Administering IBM Z Decision Support 181

Working with tables and update definitions

Procedure
1. From the Table pull-down in the Tables window (Figure 64 on page 154), select 1, New, and press
Enter.
The New Table window is displayed (Figure 92 on page 182).
2. Type required information in the fields.
3. To see a list of available table spaces, place the cursor in the Tablespace field, and press F4.
The Prompt for Tablespace window is displayed.
4. Select a table space from the list, and press Enter.
The product returns to the New Table window, and the table space appears in the Tablespace field.
Note: To create a table space, see “Creating a table space” on page 183.

New Table

Type information. Then press F5 to add columns. To select an already

added column, press Enter.

Table name . . __________________ Prefix . . . . DRL

Database . . . DRLDB Tablespace . . ________ +
Comments . . . ________________________________________ >

/ Column Type Length Nulls Primary Key

******************************* BOTTOM OF DATA ********************************

Command ===> __________________________________________________________

F1=Help F2=Split F3=Exit F4=Prompt F5=Add col F6=Indexes
F7=Bkwd F8=Fwd F9=Swap F10=Show fld F11=Delete F12=Cancel

Figure 92. New Table window

5. Press F5 to add a column to the table.
The product displays the Add Column window (Figure 75 on page 167).
6. Type the required information in the fields, and press Enter.
You are returned to the Add Column window.
7. When you finish adding columns to the table, press F12.
You are returned to the New Table window.
8. Press F6 to add indexes to the table.
The Indexes window is displayed (Figure 76 on page 168).
9. Press F5 to add an index.
The Add Index window is displayed (Figure 78 on page 169).
10. Type the required information in the fields, and press Enter.
The index is added and you are returned to the Indexes window.
11. Press F3 to return to the New Table window.
12. Press F3 when you finish typing information.
The table is added to the database and you are returned to the Tables window.

Deleting a table or view

About this task

To delete a table or view:

182 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Procedure
1. Select the table or view to delete in the Tables window (Figure 64 on page 154) and select 6, Delete,
from the Table pull-down.
Note: IBM Z Decision Support prevents you from deleting table definitions that affect, or are affected
by, other product objects. To delete a table definition, remove links from the table to other product
objects.
A confirmation window is displayed.
2. Verify the deletion by pressing Enter.
The table or view is deleted and you are returned to the Tables window.
Note: A table in a partitioned table space cannot be explicitly deleted (dropped). You can drop the
table space that contains it. This does not have any impact on other tables because only one table can
be defined in a single table space.

Creating a table space

About this task

Db2 tables are in table spaces. For a new table, you might need to create a table space.
You can use the administration dialog to create a table space. You must have some knowledge of Db2
databases before creating the table space. See “Understanding table spaces” on page 97 for more
information about table spaces, or refer to the discussion of designing a database in Db2 for z/OS:
Administration Guide and Reference.
To create a table space:

Procedure
1. From the New Table window (Figure 92 on page 182), place the cursor in the Tablespace field and
press F4.
The Prompt for Tablespace window is displayed.
2. From the Prompt for Tablespace window, press F5.
The New Tablespace window is displayed.
3. Type required information in the fields, and press Enter.
A table space is created and you are returned to the Prompt for Tablespace window.
4. Press Enter again to return to the New Table window.
5. Continue creating the table as described in “Creating a table” on page 181.
Note: It is also possible to create a table space without creating a table: use the Maintenance pull-
down in the Tables window (as described in “Displaying and modifying a table or index space” on page
176) and select New from the Tablespace pull-down in the Tablespaces window.

Creating an update definition

About this task

In IBM Z Decision Support, update definitions specify how to store data from log records in Db2
tables and how to use data from one table to update another. Each component includes all the update
definitions that it uses. However, if you tailor the objects used during a collect, or create components of
your own, you might need to create more update definitions.
You can use the administration dialog to create an update definition. You can also use log collector
language. Refer to the Language Guide and Reference for more information about defining update
definitions using log collector language.

Chapter 4. Administering IBM Z Decision Support 183

Working with tables and update definitions

To create an update definition:

Procedure
1. From the Tables window (Figure 64 on page 154), select a table for addition of an update definition,
and press F5.
The Update Definitions window is displayed (Figure 79 on page 170).
2. To use an existing update definition as a template, select one of the update definitions from the list
and press F5. Otherwise, do not select an update definition.
The New Update Definition window is displayed. The columns are filled with values from the template.
3. To create an update definition without a template, press F5 from the Update Definitions window.
You are prompted for the name of the target table in the Target Table of New Update window. Type the
name of the target table, and press Enter.
The New Update Definition window is displayed.
4. Type required information in the fields, and press F3.
The new update definition is saved and you are returned to the Update Definitions window.
You might choose to use abbreviations for expressions in the expression fields. Or you might require
that data be distributed over some interval or used in availability processing. See these topics in
““Displaying and modifying update definitions of a table” on page 169” for information:
• “Working with abbreviations” on page 172
• “Modifying a distribution clause” on page 173
• “Modifying an apply schedule clause” on page 173
5. Press F3 again to return to the Tables window.

Deleting an update definition

About this task

Update definitions are supplied for all data tables. You can use the administration dialog to delete an
update definition you no longer need. IBM Z Decision Support removes all references to the update from
its system tables. However, it does not delete the definition member; you can use the dialog to reinstall it.
To delete an update definition of a table:

Procedure
1. From the Tables window (Figure 64 on page 154), select the table and press F5.
The Update Definitions window for the table is displayed (Figure 79 on page 170). All update
definitions where the selected table is either the source or the target are included.
2. Select the update definition to delete, and press F11.
A confirmation window is displayed.
3. Verify the deletion by pressing Enter.
The definition is updated and you are returned to the Update Definitions window.
4. Press F3 to return to the Tables window.

184 IBM Z Decision Support : Administration Guide and Reference

 Working with tables and update definitions

Administering user access to tables

About this task

When you install a component, IBM Z Decision Support grants read access to the users or groups you
have specified in dialog parameters (the default is the DRLUSER group). You can use the administration
dialog to grant or revoke table access to other IBM Z Decision Support users.
To grant table access to other users:

Procedure
1. From the Tables window (Figure 64 on page 154), select one or more tables to grant access to.
2. Select 5, Grant, from the Utilities pull-down.
The Grant Privilege window is displayed (Figure 93 on page 185).

Table Maintenance Utilities Edit View Other Help

Tables ROW 186 TO 198 OF 212

S Grant Privilege ion.

/ Type information. Then press Enter to save and return.

s
Table : DRL.SAMPLE_H

User ID

Access 1 1. Read only

2. Read and update
3. All

C F1=Help F2=Split F9=Swap F12=Cancel

F7=Bkwd
F8=Fwd F9=Swap F10=Actions F11=Dispay F12=Cancel

Figure 93. Grant Privilege window

3. Type required information in the fields, and press Enter.
The user ID is granted access to the table.
4. When you finish granting access to the table, press F12.
If you selected more than one table, the Grant Privilege window for the next table is displayed. When
you complete the Grant Privilege window for the last table, you are returned to the Tables window.

Revoking table access

About this task

To revoke table access:

Procedure
1. From the Tables window (Figure 64 on page 154), select one or more tables to revoke access to.
2. Select 6, Revoke, from the Utilities pull-down.
The Revoke Privilege window (Figure 94 on page 186) is displayed.

Chapter 4. Administering IBM Z Decision Support 185

Summary of how the log data manager is used

Revoke Privilege ROW 1 TO 5 OF 5

Select one more user IDs. Then press Enter to execute.

/ User ID Table Privilege Grantor

– DRL DRL.SAMPLE_H DELETE DRL
– DRL DRL.SAMPLE_H UPDATE DRL
– DRL DRL.SAMPLE_H INSERT DRL
– DRL DRL.SAMPLE_H SELECT DRL
– DRLUSER DRL.SAMPLE_H SELECT DRL
BOTTOM OF DATA

Command ===>
F1=Help F2=Split F7=Bkwd F8=Fwd F9=Swap F12=Cancel

Figure 94. Revoke Privilege window

3. Select the user IDs with table access privileges to revoke, and press Enter.
The access privileges are revoked and you are returned to the Tables window.

Working with the log data manager option

This section contains information about the IBM Z Decision Support log data manager option, which
automates and simplifies the collection of data.
After providing a summary of the log data manager, this section then describes:
• How the log data manager is invoked from the administration dialog (page “Summary of how the log
data manager is used” on page 186).
• The job for recording of log data sets for collection (page “Job step for recording a log data set for
collection” on page 187).
• Modifying log collector statements to be used in the collect (page “Modifying log collector statements”
on page 189).
• Modifying the list of log data sets to be collected (page “Listing and modifying the list of log data sets to
be collected” on page 192).
• The collect job and the parameters it uses (page “The DRLJLDMC collect job and the parameters it
uses” on page 195).
• Modifying the list of successfully collected log data sets (page “Listing and modifying the list of log data
sets to be collected” on page 192).
• Modifying the list of unsuccessfully collected log data sets (page “Modifying the list of unsuccessfully
collected log data sets” on page 200).

Summary of how the log data manager is used

You usually include a log data set for use with the log data manager by inserting a job step DRLELDML in
the job that creates the log data set. The job step DRLELDML records the log data set as being ready to be
collected by the log data manager collect job. You must run the job step DRLELDML for each log data set
that you want to be collected.
The log data manager collect job DRLELDMC then performs the data collection and updates the database
tables.
You can also use the Administration dialog windows to do the following:

186 IBM Z Decision Support : Administration Guide and Reference

 Invoking the log data manager

• Amend the list of log data sets to be collected.

• Amend the list of the log data sets that were successfully or unsuccessfully collected.
• Amend the collect statements used in a collect.

Invoking the log data manager

About this task

To invoke the log data manager:

Procedure
1. From the Administration Dialog window, select 3, Logs, to display the Logs window.
2. Select one of the displayed logs, then select 5, Open Log Data Manager (a new option provided with
the log data manager) from the Log pull-down.
The log data manager Main Selection window (Figure 95 on page 187) is displayed.

DRLDLDML Log Data Management of SMF logs

Select one of the following. Then press Enter.

__ 1. Log collector statements

2. Log data set to be collected
3. Log data sets collected successfully
4. Log data sets collected with failure

F1=Help F2=Split F9=Swap F12=Cancel

Figure 95. Log Data Manager Main Selection window.

Each of these options is discussed in the sections of this chapter.

3. The Main Selection window gives you the possibility to:
• Browse, add, delete and modify log collector statements.
• Add, delete, and change the list of log data sets to be collected by the collect job.
• List the log data sets that were collected successfully by the collect job.
• List the log data sets that were collected unsuccessfully by the collect job.

Job step for recording a log data set for collection

The job step DRLJLDML records a log data set as being ready to be collected. The collect job DRLJLDMC
then performs the collection of this log data set (described in “The DRLJLDMC collect job and the
parameters it uses” on page 195).
After job step DRLJLDML has successfully run, IBM Z Decision Support will have created a record in
system table DRLLDM_LOGDATASETS (described in “DRLLDM_LOGDATASETS” on page 206). You must
run this job step for each log data set that you want to be collected by the log data manager. The list of log
data sets to be collected can then be displayed, changed, or deleted, or a log data set added for collection
(an alternative to using the DRLJLDML job), using the Log Data Sets To Be Collected window, described in
“Listing and modifying the list of log data sets to be collected” on page 192.

Using the DRLJLDML job step

About this task

To use the DRLJLDML job step:

Procedure
1. Ensure that your log data sets are cataloged (otherwise the DRLJLDML job step does not work).

Chapter 4. Administering IBM Z Decision Support 187

Job step for recording a log data set for collection

2. Take a copy of the supplied sample DRLJLDML job step.

3. Insert the DRLJLDML job step in each job that creates a log data set, and which you want to be
collected by the log data manager. For Generation Data Sets, you must insert the DRLJLDML job step
after each Generation Data Set member that has been created.
4. Enter the name of the log data set (*.stepname.ddname) in the DRLLOG DD statement of the job step
(described in “DRLJLDML sample job” on page 188).
5. Run the job you have now amended, to create the log data set.

DRLJLDML sample job

This job is shipped with IBM Z Decision Support as sample job DRLJLDML.

//DRLJLDML JOB (ACCT#),'LOGS'

//********************************************************************
//* Name: DRLJLDML *
//* *
//* Function: *
//* Log Data Manager - register a log data set sample job *
//* *
//* This job is used to register the log data set (only one) *
//* specified in DRLLOG in the DRLLDM_LOGDATASETS as being ready *
//* for collect by the Log Data Manager. *
//* *
//* Input: *
//* The exec DRLELDML accepts the following parameters: *
//* *
//* SYSPREFIX=xxxxxxxx Prefix for system tables. default=DRLSYS *
//* PLAN=xxxxxxxx Db2 plan name default=DRLPLAN *
//* SYSTEM=xxxxxx Db2 subsystem name. default=DSN *
//* SHOWSQL=xxx Show SQL. YES/NO default=NO *
//* LOGTYPE=xxxxxxxxxx Log type (e.g. SMF). Required. *
//* LOGID=xxxxxx Log ID. If not specified (or =''), a blank *
//* Log ID is generated, and the default collect*
//* statement is used in collect. *
//* ONTAPE=N/Y Specify if the LOG name is on DASD or not. If*
//* not coded, it defaults to NO. *
//* *
//* DRLLOG DD card: Name of log data set to be registered *
//* (can refer to a previous step). *
//* It must be cataloged. *
//* *
//* Output: Log data set name registered in *
//* sysprefix.DRLLDM_LOGDATASETS together *
//* with LOG_NAME, LOG_ID and TIME_ADDED. *
//* Confirmation message including data set name *
//* *
//* Notes: *
//* Before you submit the job, do the following: *
//* 1. Fill in a correct log data set name. *
//* 2. Check that the steplib db2loadlibrary is correct. *
//* 3. Change the input parameters to DRLELDML as required. *
//* 4. Change the Db2 load library name according to *
//* the naming convention of your installation. *
//* Default is 'db2loadlibrary'. *
//* 5. Change the TDSz high level qualifier. Default id 'DRLvrm'. *
//* *
//********************************************************************
//LDMLOG EXEC PGM=IKJEFT01
//*
//SYSPROC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC
//STEPLIB DD DISP=SHR,DSN=DRLvrm.SDRLLOAD
// DD DISP=SHR,DSN=db2loadlibrary <--
//***********************************************
//* MESSAGES
//*
//DRLOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//***********************************************
//* LOG DATA SET
//* DSN=*.stepname.ddname can be used
//*
//DRLLOG DD DISP=SHR,DSN=... <--
//***********************************************
//* START EXEC DRLELDML
//*
//SYSPRINT DD SYSOUT=*

188 IBM Z Decision Support : Administration Guide and Reference

 Modifying log collector statements

//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLELDML SYSTEM=DSN SYSPREFIX=DRLSYS -
LOGTYPE=SMF -
LOGID='' ONTAPE=N
/*

Setting the parameters for job DRLJLDML

About this task

These are the rules for entering parameter values:
1. LOGTYPE is the only parameter that must be changed by you. The remaining parameters are optionally
changed by you.
2. Blanks must not exist before or after an equal (=) sign.
3. Blanks must not exist within a parameter value.
4. A parameter value must not be enclosed in apostrophes.
5. A continuation mark (-) can be placed in any column.
The following are the DRLJLDML job parameters:
SYSPREFIX
The prefix of all IBM Z Decision Support system and control Db2 tables. If you do not specify a value
here, the default DRLSYS is used.
SYSTEM
The Db2 subsystem. The default value is DSN.
PLAN
The name of the Db2 application plan. The default value is DRLPLAN.
SHOWSQL
When this value is set to YES, all executed SQL statements will be written to an output file. The default
value is NO.
LOGTYPE, LOGID
Each combination of LOGTYPE and LOGID identifies the collect statements to be used by the collect
job (which is run after this job):
• If you do not enter a value for LOGID, or if you enter two apostrophes with no blank between (''), the
default collect statements for this LOGTYPE will be used for collecting the log data set.
• If you set LOGID to a user-defined value, the collect statements for the user-defined value will be used
for this LOGTYPE, when collecting the log data set.
• Using different values of LOGID will produce more than one collect for a specific LOGTYPE. These
collects will normally be run serially. However, you can run these collects in parallel by setting up your
system accordingly.

Modifying log collector statements

In order to modify log collector statements, this section describes the following:
• “Listing the data sets containing collect statements” on page 190
• “Editing the collect statements” on page 190
• “Adding a log ID and collect statements data set” on page 191
• “Changing the collect statements data set name” on page 192

Chapter 4. Administering IBM Z Decision Support 189

Modifying log collector statements

Listing the data sets containing collect statements

About this task

To list the log collector statements used with a log type:

Procedure
Select 1, Log collector statements, from the log data manager Main Selection window.
The Collect Statements window (Figure 96 on page 190) is displayed,one row for each log ID defined for
the log type. When a default row is created during installation of a product component, the field log ID is
always blank.

DRLDLDMS Log Data Manager Collect Statements for SMF

Select a Log ID. Then press Enter to edit the collect statement

/ Log ID Collect statement data set

s DRLxxx.SDRLDEFS(DRLBSMF)
_ MVSA DRLxxx.LOCAL.DEFS(MVSACOLL)
_ MVSB DRLxxx.LOCAL.DEFS(MVSBCOLL)
_ MVSX DRLxxx.LOCAL.DEFS(MVSXCOLL)
_ MVS1 DRLxxx.LOCAL.DEFS(MVS1COLL)
_ SYS1 DRLxxx.LOCAL.DEFS(SYS1COLL)

Command ===> ___________________________________________________________

F1=Help F2=Split F3=Exit F5=Add F6=Modify F7=Bkwd F8=Fwd
F9=Swap F11=Delete F12=Cancel

Figure 96. Collect Statements window

Editing the collect statements

About this task

To edit (default action) the collect statements for a log ID:

Procedure
1. Select the log ID whose collect statements you want to edit, and press Enter. The Edit window (Figure
97 on page 191) is displayed.
2. Edit the collect statements using the ISPF editor. If the member does not exist, it will be automatically
created by the edit. If the collect statements data set does not exist or is not cataloged, an error
message is displayed. A confirmation window is displayed if a member of the product definition
library is selected for editing. If you want to edit collect statements that reside in the product
distribution library, follow the instructions given in “Modifying IBM Z Decision Support-supplied collect
statements” on page 191
3. On completion of the editing, you are returned to the Log Data Manager Collect Statements window.

Results
Note: The COMMIT AFTER BUFFER FULL ONLY parameter will not be accepted in the collect statement
member if the collect involves concatenated log data sets (an appropriate error message is displayed).
The reason is that such concatenated data sets are never recorded in the DRLLOGDATASETS system table
as being collected.

190 IBM Z Decision Support : Administration Guide and Reference

 Modifying log collector statements

EDIT ---- DRLxxx.SDRLDEFS(DRLBSMF)---------------------------- COLUMNS 0

****** ***************************** TOP OF DATA ***********************
000001 COLLECT SMF;
****** **************************** BOTTOM OF DATA *********************

COMMAND ===> SCROLL ===

F1=Help F2=Split F3=Exit F5=Rfind F6=Rchange F7=Up
F8=Down F9=Swap F10=Left F11=Right F12=Cancel

Figure 97. Edit collect statements window

Modifying IBM Z Decision Support-supplied collect statements

About this task

Not all the components have a default collect statement supplied by the product. You must modify the
collect statements for these log types to use with these components. You might also want to modify other
IBM Z Decision Support-supplied collect statements. In all cases, a warning is displayed if you attempt to
edit a collect statement member that resides in the product distribution library.
Note: Any modifications you make to IBM Z Decision Support-supplied collect statements are lost if a PTF
or new release updates the member containing the collect statements.
To modify an IBM Z Decision Support-supplied collect statement member:

Procedure
1. Copy the member containing the collect statements to your local library.
2. Use option F6=Modify of the Log Data Manager Collect Statements window to change the data set
name of the default log ID (see “Modifying log collector statements” on page 189 for details).
3. Edit the collect statements member as you require.

Adding a log ID and collect statements data set

About this task

To add a log ID and data set name to the list:

Procedure
1. Press F5 and the Add Collect Statements Definition window is displayed (Figure 98 on page 192
2. Type a log ID and data set name and press Enter. The log ID and data set name are added to the Log
Data Manager Collect Statements list in alphanumeric sequence. However, a non-existent data set is
not created

Chapter 4. Administering IBM Z Decision Support 191

Modifying log collector statements

DRLDLDMA Add Collect Statements Definition for SMF

Type information. Then press Enter to save.

Log ID ________ (blank for default collect statements)

Data set name __________________________________________________

F1=Help F2=Split F9=Swap F12=Cancel

Figure 98. Add Collect Statements Definition window

Changing the collect statements data set name

About this task

To change the name of a collect statements data set:

Procedure
1. Select the log ID corresponding to the data set name which you want to modify, and press F6. The
Modify Collect Statements Definition window is displayed (Figure 99 on page 192)
2. Type the modified data set name and press Enter. The data set name is changed in the Log Data
Manager Collect Statements list.

DRLDLDMB Modify Collect Statements Definition for SMF

Type information. Then press Enter to save.

Log ID MVSA____
Data set DRLxxx.LOCAL.DEFS(MVSACOLL)__________________________

F1=Help F2=Split F9=Swap F12=Cancel

Figure 99. Modify Collect Statements Definition window

Listing and modifying the list of log data sets to be collected

In order to list and modify the list of log data sets to be collected, this section describes the following:
• “Listing the log data sets to be collected” on page 192
• “Modifying the log ID for a log data set” on page 193
• “Deleting information about a log data set” on page 194
• “Recording a log data set to be collected again” on page 194
• “Adding a log data set to be collected” on page 194

Listing the log data sets to be collected

About this task

To list the log data sets to be collected:

Procedure
Select 2, Log data sets to be collected, from the log data manager Main Selection window.
The Log Data Sets To Be Collected window (Figure 100 on page 193) is displayed, one row for each log ID
and log data set.

192 IBM Z Decision Support : Administration Guide and Reference

 Modifying log collector statements

What to do next
Each list of log data sets are sorted firstly by log ID, and then by the date the log data set was added.
Each log data set displayed in this window has a value in the Status column, which can contain one of
these values:
• blank
The log data set is ready to be collected by the DRLMLDMC job (see “The DRLJLDMC collect job and the
parameters it uses” on page 195 for details).
• 'SELECT'
This value occurs when the log data set has been selected for collect by the DRLMLDMC job, but the
collect has not completed. The data set is protected from a collect by a “parallel” invocation of the
DRLMLDMC job. If theDRLMLDMC job abends, the action you take depends upon how many log data
sets have the status 'SELECT' after the abend has occurred:
– If there are many log data sets with status 'SELECT', run job DRLELDMC with parameter
CLEANUP=YES, to record the log data sets as ready for collection again.
– If there are only a few log data sets with status 'SELECT', it is easier to manually record the data sets
as ready for collection again by selecting F4=Rerun for these log data sets.
• A log collector return code or a system or user abend code
This occurs when the log data set was collected with a failure, and the Rerun option was selected for
this log data set in the Log Data Sets Collected with Failure window (described in “Modifying the list of
unsuccessfully collected log data sets” on page 200). The data set is collected again the next time job
DRLELDMC is run.

DRLDLDMT SMF Log Data Sets To Be Collected

Select a data set. Then press Enter to modify Log ID.

/ Log ID Log data set Time added Status

_ SYS170.SMFLOG.SLOG9501222 2004-11-22.13
s MVSA SYS170.SMFLOGA.SLOG950122 2004-11-21.23 SELECT
_ MVSB SYS170.SMFLOGB.SLOG950122 2004-11-22.01
_ MVSX SYS170.SMFLOGX.SLOG950122 2004-11-22.01
_ MVS1 SYS170.SMFLOG1.SLOG02 2004-11-21.23 8
_ MVS2 SYS170.SMFLOG.MVS2.SLOG01 2004-11-21.10 U0005
_ SYS1 SYS170.SMFLOG.SYS1.SLOG01 2004-11-18.10 20

Command ===> ___________________________________________________________

F1=Help F2=Split F3=Exit F4=Rerun F5=Add F7=Bkwd F8=Fwd
F9=Swap F11=Delete F12=Cancel

Figure 100. SMF Log Data Sets To Be Collected window

Modifying the log ID for a log data set

About this task

To modify the log ID (the default action) to be used with a log data set:

Procedure
1. Select the log ID and press Enter.
The Modify Log ID for a Log Data Set window is displayed (Figure 101 on page 194).
2. Type the modified log ID and press Enter. The log ID is then changed in the Log Data Sets To Be
Collected list.
Note: You can also use this window to display the full length of a truncated log data set name. Data set
names longer than 34 characters are truncated in the Log Data Sets To Be Collected window, but are
displayed in full in the Modify Log ID for a Log Data Set window.

Chapter 4. Administering IBM Z Decision Support 193

Modifying log collector statements

DRLDLDMM Modify Log ID for a SMF Log Data Set

Type Log ID. Then press Enter to save.

Log ID MVSA (blank for default collect statements)

Data set SYS150.SMFLOGA.SLOG950122

F1=Help F2=Split F9=Swap F12=Cancel

Figure 101. Modify Log ID For a Log Data Set window.

Deleting information about a log data set

About this task

To delete an entry from the Log Data Sets To Be Collected window:

Procedure
1. Select the log ID and log data set and press F11.
2. Press Enter to confirm deletion.

Recording a log data set to be collected again

About this task

A log data set can be recorded for collection again if it has the value 'SELECT' in the Status column,
caused by the collect job abending and as a result, the log data set still having the value 'SELECT in the
Status column.
After the log data set has been recorded for collection again, it is included in the next collect job
(described in “The DRLJLDMC collect job and the parameters it uses” on page 195).
To record a log data set to be collected again:

Procedure
1. Select the log ID and log data set and press F4
2. Press Enter to confirm.

Adding a log data set to be collected

About this task

To add an entry to the Log Data Sets To Be Collected list:

Procedure
1. Press F5 and the Add a Data Set To Be Collected window is displayed (Figure 102 on page 195).
2. Type the log ID and log data set name and press Enter.
The Log Data Sets To Be Collected window is displayed, containing the added entry.

194 IBM Z Decision Support : Administration Guide and Reference

 The collect job and the parameters it uses

DRLDLDMN Add a SMF Data Set To Be Collected

Type information. Then press Enter to save.

Log ID ________ (blank for default collect statements)

Data set name ____________________________________________________

F1=Help F2=Split F9=Swap F12=Cancel

Figure 102. Add a Data Set To Be Collected window

An error message is displayed in this window if you attempt to add an already existing log data set.

The DRLJLDMC collect job and the parameters it uses

The job DRLJLDMC is used to collect log data sets that are recorded as being ready for collection.
A system table (described in “DRLLDM_COLLECTSTMT” on page 206) is used to identify the data set
containing the collect statements to be used for the collect.
Log data sets are recorded as ready for collection either by running the job DRLJLDML (see “Job step
for recording a log data set for collection” on page 187 for details), or by using the Log Data Sets To Be
Collected window (see “Listing and modifying the list of log data sets to be collected” on page 192 for
details).

Deciding which log data sets to collect

Using the two parameters LOGTYPE and LOGID you specify which log data sets you want to collect. If
you omit both parameters, all log data sets that are ready to be collected are collected. If, however,
you decide to enter values for LOGTYPE and LOGID, a subset only of the log data sets belonging to the
specified log type is collected.

Concatenation of log data sets

Each time you run the DRLELDMC EXEC, all log data sets corresponding to the values you enter for the
parameters LOGTYPE and LOGID are serially collected. The log collector function is used only once for all
log data sets of the same log type and log ID. Log data sets are added to the log collector file DRLLOG in
the order in which they were recorded by the Log Data Manager. As a result, the log collector output files
DRLOUT and DRLDUMP may contain the output from many log data sets.
You should also note that if the collect of such a concatenated log data set fails after one or more log data
sets have been successfully collected, the remaining log data sets in the concatenation are not collected.
You must then rerun the DRLJLDMC collect job, to collect these remaining log data sets.

Running collect jobs in parallel

If you do not specify the LOGID and/or the LOGTYPE parameters, the DRLELDMC EXEC calls the log
collector and runs the collect job each time a combination of log type and log ID is processed. If you
want to decrease the total elapsed time of these collects, you can run DRLJLDMC collect jobs in parallel.
However, you should not run jobs with the same LOGTYPE parameter in parallel.

DRLELDMC sample job

This job is shipped with the product as sample job DRLJLDMC.
DRLJLDMC

//DRLJLDMC JOB (ACCT#),'COLLECT'

//********************************************************************
//* Name: DRLJLDMC *
//* *
//* Function: *
//* Log Data Manager Collect Log Data Sets sample job *

Chapter 4. Administering IBM Z Decision Support 195

The collect job and the parameters it uses

//* *
//* This job is used to collect log data sets that are recorded *
//* in the DRLLDM_LOGDATASETS system table as being ready for *
//* collect by the Log Data Manager. *
//* *
//* Input: *
//* The exec DRLELDMC accepts the following parameters: *
//* *
//* SYSPREFIX=xxxxxxxx Prefix for system tables. default=DRLSYS *
//* SYSTEM=xxxxxx Db2 subsystem name. default=DSN *
//* PREFIX=xxxxxxxx Prefix for all other tables.default=DRL *
//* PLAN=xxxxxxxx Db2 plan name default=DRLPLAN *
//* DSPREFIX=xxxxxxxx Prefix for creation of data sets DRLOUT and *
//* DRLDUMP. default=DRL *
//* SHOWSQL=xxx Show SQL. YES/NO default=NO *
//* SHOWINPUT=xxx Copy DRLIN to DRLOUT. YES/NO default=YES *
//* LOGTYPE=xxxxxxxxxx Log type (e.g. SMF). If not specified, *
//* all log types are selected for processing. *
//* LOGID=xxxxxx Log ID. If not specified, all log id's are *
//* are selected for processing. Default Log ID *
//* should be coded as =''. *
//* RETENTION=xxx Retention period for DRLOUT, DRLDUMP and *
//* collect result info. default=10 days *
//* PURGE=xxx Purge info for successful collects that *
//* are older than its Retention period *
//* YES/NO default=YES *
//* CLEANUP=xxx Option only to be used after an Abend. *
//* No collect is done. Processes only log data *
//* sets marked with SELECT in the Log Data Sets*
//* To Be Collected list (on panel DRLDLDMT). *
//* Output: the data set being collected when *
//* the abend occurred will be moved to the *
//* Collected With Failure list. Other concate- *
//* nated data sets are moved to the Successful *
//* list or made ready for a renewed collect. *
//* YES/NO default=NO *
//* *
//* DRLOUT/DRLDUMP DD card: if any of these files are specified *
//* they will be used by all collects started by*
//* this job. They will then not be controlled *
//* or viewed by the Log Data Manager dialog. *
//* *
//* DRLLOG DD card: Must not be allocated. *
//* *
//* LMDLOG EXEC card: The value used for DYNAMNBR should be *
//* as a minimum, 2 plus the number of *
//* log data sets to be collected. *
//* *
//* Output: The results of the collects are recorded in *
//* sysprefix.DRLLDM_LOGDATASETS together *
//* with LOG_NAME, LOG_ID and TIME_ADDED. *
//* Job messages in the DRLMSG file *
//* *
//* Notes: *
//* Before you submit the job, do the following: *
//* 1. Check that the steplib db2loadlibrary is correct. *
//* 2. Change the parameters to DRLELDMC as required. *
//* 3. Change the Db2 load library name according to *
//* the naming convention of your installation. *
//* Default is 'db2loadlibrary'. *
//* 4. Change the TDSz data set HLQ (default is DRLvrm.) *
//* *
//********************************************************************
//LDMLOG EXEC PGM=IKJEFT01,DYNAMNBR=20
//*
//SYSPROC DD DISP=SHR,DSN=DRLvrm.SDRLEXEC --
//STEPLIB DD DISP=SHR,DSN=DRLvrm.SDRLLOAD --
// DD DISP=SHR,DSN=db2loadlibrary --
//*********************************************************
//*DRLOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//*DRLDUMP DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//*********************************************************
//* MESSAGES
//*
//DRLMSG DD SYSOUT=*,DCB=(RECFM=F,LRECL=80)
//*********************************************************
//* Add the next three DD statements if you collect IMS.
//* Note 1: IMSVER must specify the same release as the
//* collect statement used by the Log Data Manager.
//* Note 2: DRLICHKI must be DUMMY or point out an empty
//* data set after an IMS restart.
//*********************************************************

196 IBM Z Decision Support : Administration Guide and Reference

 The collect job and the parameters it uses

//*DRLICHKI DD DSN=Generation data set(0),DISP=SHR

//*DRLICHKO DD DSN=Generation data set(+1),DISP(NEW,CATLG)
//*DRLIPARM DD *
//*IMSVER=71 -- IMS release being processed. 71 is default
//*MAXOUTPUT=50 -- Allow up to 50 outputs per transaction/BMP
//*MAXUOR=50 -- Allow up to 50 UOR's per BMP
//**********************
//* START EXEC DRLELDMC
//*
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
%DRLELDMC SYSTEM=DSN SYSPREFIX=DRLSYS PREFIX=DRL -
DSPREFIX=DRL -
LOGTYPE=SMF -
LOGID=''
/*

Setting the DYNAMNBR value

The value for the EXEC parameter DYNAMNBR should be a minimum of the number of log data sets to be
collected, plus 2.
The supplied default is 20.

Setting the parameters for job DRLJLDMC

The rules for entering parameter values are as follows:
1. All parameters are optional.
2. Blanks must not exist before or after an equal sign (=).
3. Blanks must not exist within a parameter value.
4. A parameter value must not be enclosed in apostrophes.
5. A continuation mark (-) can be placed in any column.
These are the DRLJLDMC job parameters:
SYSPREFIX
The prefix of all product system and control Db2 tables. If you do not specify a value here, the default
DRLSYS is used.
SYSTEM
The Db2 subsystem. The default value is DSN.
PREFIX
The prefix used with all other tables. The default value is DRL.
PLAN
The name of the Db2 application plan. The default value is DRLPLAN.
DSPREFIX
The prefix used for the creation of data sets DRLOUT and DRLDUMP. The default is DRL. The
names of these data sets are 'dsprefix_value.Ddate.Ttime.DRLOUT/DRLDUMP' where date and time
are generated. The maximum length of DSPREFIX is 20 characters.
SHOWSQL
When this value is set to YES, all executed SQL statements are written to an output file. The default
value is NO.
SHOWINPUT
When this value is set to YES, all DRLIN statements are written to DRLOUT. The default value is YES.
LOGTYPE, LOGID
Each combination of LOGTYPE and LOGID identifies the log IDs to be used in the collect. If log type
is not specified, all log types are selected for processing. If log ID is not specified, all log IDs for the
log type specified are selected for processing. The default log ID is selected by setting this value to
straight quotes (").

Chapter 4. Administering IBM Z Decision Support 197

Modifying the list of successfully collected log data
sets

RETENTION
The retention period for DRLOUT, DRLDUMP and the log data manager information that is produced by
the collects. The default is 10 days.
PURGE
This parameter determines whether or not the information resulting from successful collects should
be purged when the date of the information is older than the retention period. The parameter can be
set to the value YES or NO. If PURGE is set to YES, all log data manager information about successfully
collected log data sets is deleted (for all log types and log IDs). The default value is PURGE=YES.
CLEANUP
This parameter is used when the DRLELDMC job has had an abend during a collect of concatenated
log data sets. If you run the DRLELDMC job with parameter CLEANUP set to YES, log data sets that
were successfully collected before the abend occurred are moved to the Log Data Sets Successfully
Collected list. The log data set that was being collected when the abend occurred is moved to the Log
Data Sets Collected With Failure list. The default value is CLEANUP=NO.
DRLOUT DD statement
If this file is specified, it is used by all collects started by this job. However, this file is not used by the
log data manager dialog.
DRLDUMP DD statement
If this file is specified, it is used by all collects started by this job. However, this file is not used by the
log data manager dialog.
DRLLOG DD statement
Must not be allocated.

Modifying the list of successfully collected log data sets

About this task

To list the log data sets that have been successfully collected:

Procedure
Select 3, Log data sets collected successfully, from the log data manager Main Selection window.
The Log Data Sets Collected Successfully window (Figure 103 on page 198) is displayed, one row for each
log data set that has been successfully collected by the Log Data Manager for this log type.
The list of data sets are sorted by the Time collected column.

DRLDLDMC Log Data Sets Collected Successfully for SMF

Select a data set. Then press Enter to view DRLOUT.

/ Log data set Time collected RC

_ SYS170.SMFLOGX.SLOG950120 2004-11-21.02.03.25 0
_ SYS170.SMFLOGB.SLOG950120 2004-11-21.01.33.25 0
_ SYS170.SMFLOGA.SLOG950120 2004-11-21.01.15.10 0
_ SYS170.SMFLOG.SLOG950120B 2004-11-21.01.01.20 0
_ SYS170.SMFLOG.SLOG950120A 2004-11-21.00.45.20 0
_ SYS170.SMFLOGA.SLOG950119 2004-11-20.23.15.10 0
_ SYS170.SMFLOG.SLOG950119B 2004-11-20.01.45.20 0
_ SYS170.SMFLOGB.SLOG950119 2004-11-20.01.13.25 0
_ SYS170.SMFLOGX.SLOG950119 2004-11-20.01.13.25 0
_ SYS170.SMFLOG.SLOG950119A 2004-11-20.00.45.20 0

Command ===> ___________________________________________________________

F1=Help F2=Split F3=Exit F5=DRLDUMP F6=Retent. F7=Bkwd
F8=Fwd F9=Swap F11=Delete F12=Cancel

Figure 103. Log Data Sets Collected Successfully window

198 IBM Z Decision Support : Administration Guide and Reference

 Modifying the list of successfully collected log data
sets

Viewing the information about successfully collected log data sets

About this task

To view the log data manager information about a log data set (the default action):

Procedure
Select a log data set and press Enter.
The DRLOUT data set is displayed in ISPF Browse mode (if a DRLOUT statement was not included in the
collect job).

Viewing the dump data set

Procedure
Select the log data set and press F5.
The DRLDUMP data set is displayed using the ISPF Browse function, if a DRLDUMP DD statement was not
present in the collect job. DRLDUMP should be empty if the return code from the collect was 0.

Changing the retention period of information about a log data set

About this task

To change the retention period for the log data managerlog data manager information about a log data
set:

Procedure
1. Select the log data set and press F6. The Retention Period for Collect Information window is displayed
(Figure 104 on page 199).
2. Type the retention period field the number of days you require, and press Enter
Note: You are not changing the retention period for the collected log data here, but only the retention
period for the log data manager information about the log data set.

DRLDLDMR Retention period for collect information

Type Retention period. Then press Enter to save.

Data set DRL181.SMFLOGA.SLOG950122

Retention period 10 days

F1=Help F2=Split F9=Swap F12=Cancel

Figure 104. Retention Period window

Deleting the information about a log data set

About this task

To delete the log data manager information about a log data set together with DRLOUT and DRLDUMP
data sets (if they exist):

Procedure
1. Select the log data set for which you want to delete the log data manager information from, and press
F11.

Chapter 4. Administering IBM Z Decision Support 199

Modifying the list of successfully collected log data
sets

2. Press Enter to confirm deletion.

Note: You are not deleting the log data set itself, but only the log data manager information about the
log data set.

Modifying the list of unsuccessfully collected log data sets

About this task

To list the log data sets that have been unsuccessfully collected:

Procedure
Select 4, Log Data Sets Collected with Failure, from the log data manager Main Selection window.
The Log Data Sets Collected with Failure window (Figure 105 on page 200) is displayed, one row for each
log data set that has been unsuccessfully collected by the Log Data Manager for this log type.
The list of data sets are sorted by the Time collected column.

DRLDLDMF Log Data Sets Collected with Failure for SMF

Select a data set. Then press Enter to view DRLOUT.

/ Log data set Time collected RC

_ SYS170.SMFLOG1.SLOG01 2004-11-20.23.22.10 8
_ SYS170.SMFLOG.SYS1.SLOG0 2004-11-18.10.16.22 20

Command ===> ___________________________________________________________

F1=Help F2=Split F3=Exit F4=Rerun F5=DRLDUMP F7=Bkwd
F8=Fwd F9=Swap F11=Delete F12=Cancel

Figure 105. Log Data Sets Collected with Failure window

Viewing the unsuccessfully collected log data set

About this task

To view the log data set (the default action):

Procedure
1. Select the log data set and press Enter.
2. The DRLOUT data set is displayed in ISPF Browse mode (if a DRLOUT statement was not included in
the collect job).

Viewing the dump data set

About this task

To view the dump data set (DRLDUMP):

Procedure
Select the log data set and press F5.
The DRLDUMP data set is displayed using the ISPF Browse function, if a DRLDUMP DD statement was not
present in the collect job. DRLDUMP is empty in most cases if the return code from the collect was 0.

200 IBM Z Decision Support : Administration Guide and Reference

 Modifying the list of successfully collected log data
sets

Recording a log data set to be collected again

About this task

If you record a log data set for collection again, it is included in the next collect job (described in “The
DRLJLDMC collect job and the parameters it uses” on page 195).
However, the entry you select to be collected again is not deleted from the Log Data Sets Collected with
Failure window.
If you select a log data set to be collected a second time (using the F4=Rerun option) after it has already
been successfully collected, the log collector detects this incorrect selection and the collect attempt is
rejected. However, if you have specified REPROCESS=YES in the collect job to recollect a successfully
collected log data set, the log collector does not reject the collect.
To record a log data set to be collected again:

Procedure
1. Select the log data set.
2. Press F4.
An error message is displayed if this log data set is already included in the list of data sets to be
collected.

Deleting the information about a log data set

About this task

To delete the information about a log data set from the list shown, together with DRLOUT and DRLDUMP
data sets (if they exist):

Procedure
1. Select the log data set you want to delete, and press F11.
2. Press Enter to confirm deletion.

Working with the Continuous Collector

This topic shows the commands to stop or modify the operation of the Continuous Collector.
When the Continuous Collector is running, log stream overflow data sets that have been marked as
freeable may not be correctly freed until the log stream is closed.
If required, the log stream being read by the Continuous Collector may be closed and re-opened using the
MODIFY LOGSTREAM command.
The MODIFY jobname,LOGSTREAM FREE command has several options; the function may be performed
ad hoc with the NOW option or started to run regularly at a selected interval.

Stopping the Continuous Collector

To stop the Continuous Collector, enter the following command:

Command Explanation
Stop the Continuous Collector.
STOP jobname

P jobname

Chapter 4. Administering IBM Z Decision Support 201

Modifying the list of successfully collected log data
sets

Modify commands
To modify the Continuous Collector during operation, choose from the following commands:

Command Explanation
Turn the commit heart beat message DRL0383I ON
MODIFY jobname,INTERVAL MESSAGE ON|OFF
or OFF. The message is ON by default when the
COMMIT phrase FULL STATISTICS AFTER is used.
F jobname,INTERVAL MESSAGE ON|OFF

F jobname,IM ON|OFF

Enable or disable messages at the start and end

MODIFY jobname,COMMIT TIME ON|OFF
of database updates and database commits. This
function is OFF initially but may be turned on to
F jobname,COMMIT TIME ON|OFF
give an indication of how long the Db2 update and
commit are taking. It is not advisable to leave this
F jobname,CT ON|OFF
turned on for a long period of time as performance
may be impacted and additional output is written
to the DRLOUT data set.
FSA count (FULL STATISTICS AFTER count) alters
MODIFY jobname,FULL STATISTICS AFTER count
the interval at which the collect statistics are
displayed. This is initially set by the COLLECT
F jobname,FULL STATISTICS AFTER count
syntax FULL STATISTICS AFTER integer COMMITS.
This may be used to set an interval for the collect
F jobname,FSA count
statistics for the first time when FULL STATISTICS
AFTER integer COMMITS is not specified on the
COLLECT statement.
Pause the Continuous Collector until a RESUME
MODIFY jobname,PAUSE
command is received. While in the paused state,
all MODIFY or STOP commands are still accepted,
F jobname,PAUSE
but no data is read from the input log stream. You
can use the pause process to avoid contention with
other activities in the IBM Z Decision Support Db2
subsystem.
Resume the Continuous Collector. Any parameters
MODIFY jobname,RESUME
changed while the collector was paused come
into effect. When a RESUME command is received,
F jobname,RESUME
processing restarts from where it paused.

MODIFY jobname,LOGSTREAM FREE NOW This command will cause the Continuous Collector
to close and re-open the log stream immediately.
F jobname,LOGSTREAM FREE NOW This enables log stream overflow data sets that
have been marked as freeable to be freed. This
command does not change frequency or the ON
or OFF status of the hourly log stream free set by
the LOGSTREAM FREE ON or LOGSTREAM FREE n
commands.

MODIFY jobname,LOGSTREAM FREE OFF This command turns off the regular close and re-
open of the log stream function started by the
F jobname,LOGSTREAM FREE OFF LOGSTREAM FREE ON or LOGSTREAM FREE n
commands.

202 IBM Z Decision Support : Administration Guide and Reference

 Modifying the list of successfully collected log data
sets

Command Explanation

MODIFY jobname,LOGSTREAM FREE ON If the log stream close and re-open function is off
by default or has been turned off by the MODIFY
F jobname,LOGSTREAM FREE ON jobname,LOGSTREAM FREE OFF command, it may
be turned on again using this command. When
turned back on, the close and re-open will happen
immediately and then repeat at the interval that
was last set, the default being one hour.

MODIFY jobname,LOGSTREAM FREE n Start the log stream close and re-open function at
the frequency required. The options are 1, 2, 3, 4,
F jobname,LOGSTREAM FREE n 5, or 6 hours. After this command, the log stream
close and re-open will happen immediately and
then repeat at the selected interval. This command
may be repeated with a different interval without
an intervening LOGSTREAM FREE OFF command.

DataSplitter
Overview
The DataSplitter is used with the newly enhanced SMF Extractor to distribute raw SMF data from
additional log stream outputs to one or more subscribers. If the users have not already done so, please
review the “Introduction to the DataSplitter and the SMF Extractor” on page 9
The only other component the DataSplitter requires to be installed and running is the SMF Extractor.
The user can set up a DataMover (Catcher or Receiver) to receive the streamed raw SMF records and write
them to disk , if that makes it easier for the client to process them. If the user chose to implement your
own TCPIP code to receive the streamed SMF records from the DataSplitter, they will arrive packed into
IBM Common Data Provider Type 2 Open Streaming API Data Packets “Receiving raw SMF records from
the SMF Extractor” on page 10.

Configuring the SMF Extractor

If the user needs to send a stream of raw SMF records to one or more specific receivers it is best
to configure the SMF Extractor to write those specific records to a separate log stream. This lets the
DataSplitter process them efficiently (having it read records only to discard them is a waste of CPU) and
it prevents the other consumers of SMF data – the IBM Z Decision Support DataMover and, optionally, the
IBM Z Decision Support Collator from having to process and discard SMF records that are only of interest
to the DataSplitter.
The user will need to allocate a new DASD log stream for the SMF Extractor to write the SMF records the
DataSplitter is to process to.

Installing the DataSplitter

Unpack the DataSplitters tar file:

tar -xvof /usr/lpp/IBM/IZDS/v1r9m0/IBM/DRLPJDS -C /var/IZDS

Copy the DataSplitter directory to where the user wants the working directory for the DataSplitter.
• Each DataSplitter that the user wants to run should have its own working directory.
Edit the DataSplitter.sh file and fill in the configuration details.
• The path to the working directory

Chapter 4. Administering IBM Z Decision Support 203

Modifying the list of successfully collected log data sets

• The path to a 64-bit Java 8 installation

There are two JCL samples in the CNTL data set. User will need to copy them to a JCL data set.
• DRLJDSP is the PROC to run the DataSplitter
– The user will need to change the working directory name
• DRLJDSJ is JCL to run the PROC as a JOB
– The user will need to change the PROCLIB
When the user submits the job, the DataSplitter will start running. The user needs to prepare its
configuration before you do this.

Configuring the DataSplitter

Like other DataMover class tools, the DataSplitter reads its configuration from a .properties file in its
config directory. The following sample configuration is provided:
• RawSplitter – which sends the data directly to each targeted receiver

Understanding the sourcetype attribute

SourceType is an attribute of a Data Packet. It is a text string that identifies the nature of the contents
of the packet – much like a declaration on an envelope or a parcel. It allows the packet to be efficiently
routed without the need to continuously open and repack it in order to determine where to send its
contents.
The DataSplitter uses a Collate stage in .mode=split to sort the raw SMF data into data packets and tag
them each with a SourceType. The value it puts into the SourceType attribute is the name of the collation
group that trapped the SMF records. The same SMF record may be trapped by multiple collation groups.
Receivers that are being sent multiple data streams need to be aware of the possibility that they may
get sent the same record multiple times in different streams – depending on how the collate stage is
programmed.
• Outside of SPLIT mode, the COLLATE stage ends up putting the resolved data sets name in the
SourceType, from where it is picked up by the ZWriter stage.

Direct streaming
If the user uses the Raw Splitter configuration, each TCPIP output stage will use the Source Type attribute
to decide which packets to send to its receiver. Each receiver will only get packets that the DataSplitter
has been configured to send them.

204 IBM Z Decision Support : Administration Guide and Reference

 Log collector system tables

Chapter 5. Administration reference

System tables and views

This section describes system tables and views. These tables are used by the product log collector
and dialogs. They are created during installation of the product base, with the prefix for system tables
specified in userid.DRLFPROF. The default prefix for the tables is DRLSYS.
System tables do not appear in the tables list in the administration dialog.
Each table description includes information about the table, a description of each key column and data
column in the table, and an example of the table's contents.
Key columns are marked with a "K".
Data columns are listed after the last key column.
The tables appear in alphabetical order, with any underscores ignored.

Log collector system tables

These tables contain definitions used by the log collector. They are maintained by the log collector. Do not
modify them.

DRLEXPRESSIONS
This system table contains one row for each expression or condition in a log, record, record procedure, or
update definition.

Column name Data type Description

OBJECT_TYPE K CHAR(8) Object type. This is LOG, RECORD, RECPROC, or UPDATE.
OBJECT_NAME K VARCHAR(18) Name of the object.
EXPRESSION_NO K SMALLINT Expression sequence number within the object.
EXPRESSION VARCHAR(2000) Original expression text.
PARSED_EXPRESSION VARCHAR(2000) Parsed version of the expression.

DRLFIELDS
This system table contains one row for every field in each defined record type.

Column name Data type Description

RECORD_NAME K VARCHAR(18) Name of the record. For a log header, this is *log-name*.
FIELD_NO K SMALLINT Field sequence number within the record.
FIELD_NAME VARCHAR(18) Name of the field.

© Copyright IBM Corp. 1993, 2017 205

Log collector system tables

Column name Data type Description

TYPE CHAR(8) Type of the field. The following values are possible:

Type Field Format

BINARY BINARY
BINARYS BINARY SIGNED
EINTEGER EXTERNAL INTEGER
HEXIN EXTERNAL HEX
DECIMAL DECIMAL(p,s)
ZONED ZONED(p,s)
FLOAT FLOAT
CHAR CHAR or CHAR(n)
CHAR(*) CHAR(*) or LENGTH * CHAR
VARCHAR VARCHAR
BIT BIT or BIT(n)
HEX HEX
DATE_001 DATE(0CYYDDDF)
DATE_002 DATE(YYYYDDDF)
DATE_003 DATE(MMDDYY)
DATE_004 DATE(YYDDDF)
DATE_005 DATE(CYYMMDDF)
DATE_006 DATE(YYMMDD)
DATE_007 DATE(MMDDYYYY)
TIME_001 TIME(1/100S)
TIME_002 TIME(HHMMSSTF)
TIME_003 TIME(0HHMMSSF)
TIME_004 TIME(HHMMSSTH)
TIME_005 TIME(HHMMSSXF)
TIME_006 TIMER(HHMMSS)
TIME_007 TIME(HHMMSSU6)I
NTV_001 INTV(MMSSTTTF)
TSTAMP_ 1TIMESTAMP(TOD)

LENGTH SMALLINT Length of the field. For DECIMAL and ZONED fields, this is a
1-byte precision followed by a 1-byte scale.
OFFSET SMALLINT Offset of the field in the record or section.
INSECTION_NO SMALLINT Number of the section where the field is contained. This is
zero if the field is not in a section.
REMARKS VARCHAR(254) Description of the field, set by the COMMENT ON statement.

DRLLDM_COLLECTSTMT
This system table contains one row for each combination of log type and log ID that is defined to the Log
Data Manager. Each row identifies the collect statement that is used for the log type/log ID combination.

Column name Data type Description

LOG_NAME K VARCHAR(18) Name of the log type.
LOG_ID K CHAR(8) The log ID.
COLLECT_STMT_DS VARCHAR(54) Name of the data set that contain the collect statement,
including the member name (for a PDS member).

DRLLDM_LOGDATASETS
This system table contains one or more rows for each log data set recorded by the Log Data Manager.

206 IBM Z Decision Support : Administration Guide and Reference

 Log collector system tables

Column name Data type Description

DATASET_NAME K VARCHAR(54) Name of the log data set, including the member name (for a
PDS member).
LOG_NAME K VARCHAR(18) Name of the log type.
TIME_COLLECTED K TIMESTAMP Timestamp of the collect. For a data set not yet collected
it is 0001-01-01-00.00.00.000000. For a successfully
collected data set it is set to the value of the
TIME_COLLECTED field in the corresponding entry in
DRLLOGDATASETS. For an unsuccessfully collected data set,
or a successfully collected data set in which no record was
recognized, it set to the timestamp when DRLELDMC called
the log collector.
LOG_ID CHAR(8) The log ID currently associated with this data set.
TIME_ADDED TIMESTAMP Timestamp when the log data set was first recorded.
TIME_COLLECT_CALL TIMESTAMP Timestamp when the DRLELDMC exec called the log
collector to process the log data set.
COLLECT_RC CHAR(5) The return code from the collect. It is blank if not yet
collected; '0' or '4' if successfully collected; >= '8' if
unsuccessfully collected without abend; 'Unn' if the collect
ended with a user abend; 'Snn' if the collect ended with a
system abend.
OUTPUT_DS VARCHAR(35) The high level qualifiers used when DRLOUT
and/or DRLDUMP data sets were created.
'OUTPUT_DS_value.DRLOUT' is the data set name of the
DRLOUT file. This value is blank if no DRLOUT or DRLDUMP
data set has been created.
RETENTION SMALLINT Retention period in days. Null field if not yet collected.
RETENTION_DATE INTEGER Collect date expressed as number of days from January 1,
Year 1. This field is used for purge calculations. Null field if
not yet collected.
COMPLETE CHAR(1) Flag indicating the status of the log data set. It is blank if the
data set is ready to be collected; 'S' if the collect is running;
'Y' if successfully collected; 'F' it collected with failure.

DRLLOGDATASETS
This system table contains one row for each collected log data set.

Column name Data type Description

LOG_NAME K VARCHAR(18) Name of the log definition.
FIRST_RECORD K VARCHAR(80) First 80 bytes of the first identified record in the data set.
This is used to identify the data set and make sure that it
is not collected again. If the record is a user defined one,
avoid beginning the record with data needed to distinguish
two records. For more information, refer to Language Guide
and Reference.
DATASET_NAME K VARCHAR(54) Name of the data set, including the member name (for a PDS
member).
VOLUME CHAR(6) Volume serial number for the data set.
LOG_SOURCE CHAR(16) Reserved.
FIRST_TIMESTAMP TIMESTAMP Timestamp of the first record in the log. This is only set if
TIMESTAMP expression is specified for the log.

Chapter 5. Administration reference 207

Log collector system tables

Column name Data type Description

LAST_TIMESTAMP TIMESTAMP Timestamp of the last record in the log. This is only set if
TIMESTAMP expression is specified for the log.
NCOLLECTS SMALLINT Number of times the data set has been collected. If this is
greater than 1, it means that collect has been run with the
REPROCESS operand to collect the data set again.
TIME_COLLECTED TIMESTAMP Date and time when collect ended.
USER_ID CHAR(8) ID of the user running collect.
COMPLETE CHAR(1) Shows whether the data set has been completely processed.
This is Y (the data set has been completely processed) or N
(the data set has only been partly processed).
RETURN_CODE SMALLINT Return code from collect; 0 or 4.
NRECORDS INTEGER Number of records read from the log data set.
NSELECTED INTEGER Number of records identified.
NUPDATES INTEGER Number of database rows updated when the data set was
collected.
NINSERTS INTEGER Number of database rows inserted when the data set was
collected.
NDELETES INTEGER Number of database rows deleted when the data set was
collected.
ELAPSED_SECONDS INTEGER Collect elapsed time, in seconds. The actual collect elapsed
time is a bit longer since there is some activity after this
table has been updated.
NSKIPPED INTEGER Number of records skipped due to timestamp overlap
(applies when ON TIMESTAMP OVERLAP SKIP specified).
LOGSTREAM_BLK_ID CHAR(8) The block ID number of the log stream record that was read
prior to the last SQL COMMIT performed by the Continuous
Collector. On a restart, the Continuous Collector will attempt
to continue reading the log stream at the saved block ID
number plus one.
LOGSTREAM_TS CHAR(8) The timestamp of the log stream record that was read
prior to the last SQL COMMIT performed by the Continuous
Collector.

DRLLOGS
This system table contains one row for each defined log type.

Column name Data type Description

LOG_NAME K VARCHAR(18) Name of the log.
VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
HEADER CHAR(1) Shows whether a header is defined for the log. This is Y (a
header is defined) or N (no header is defined). If there is a
header, it is contained in the DRLRECORDS and DRLFIELDS
tables.
REC_FMT CHAR(1)

208 IBM Z Decision Support : Administration Guide and Reference

 Log collector system tables

Column name Data type Description

LENGTH_EXPR_NO SMALLINT
TIMESTAMP_EXPR_NO SMALLINT Number of the TIMESTAMP expression in the
DRLEXPRESSIONS table. This is zero if no TIMESTAMP
expression is specified.
LOG_SOURCE_EXPR_NO SMALLINT
FIRST_CONDITION_NO SMALLINT Number of the FIRST RECORD condition in the
DRLEXPRESSIONS table. This is zero if no FIRST RECORD
condition is specified.
LAST_CONDITION_NO SMALLINT Number of the LAST RECORD condition in the
DRLEXPRESSIONS table. This is zero if no LAST RECORD
condition is specified.
LOGPROC CHAR(8) Name of the log procedure to use for the log. This is blank if
no log procedure is specified.
LOGPROC_LANGUAGE CHAR(8) Programming language that the log procedure is written in.
This is ASM or C.
LOGPROC_PARM_NO SMALLINT Number of the log procedure PARM expression in the
DRLEXPRESSIONS table. This is zero if no PARM expression
is specified.
TIME_DEFINED TIMESTAMP Date and time when the log was defined.
CREATOR CHAR(8) ID of the user who defined the log.
REMARKS VARCHAR(254) Description of the log, set by the COMMENT ON statement.

DRLPURGECOND
This system table contains one row for each purge condition in defined data tables.

Column name Data type Description

TABLE_PREFIX K CHAR(8) Prefix of the table.
TABLE_NAME K VARCHAR(18) Name of the table.
VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
SQL_CONDITION VARCHAR(254) An SQL condition that defines rows to be deleted from the
database when the PURGE statement is executed.
TIME_DEFINED TIMESTAMP Date and time when the purge condition was defined.
CREATOR CHAR(8) ID of the user who defined the purge condition.

DRLRECORDPROCS
This system table contains one row for each defined record procedure.

Column name Data type Description

PROGRAM_NAME K CHAR(8) Name of the record procedure (name of the load module
that gets invoked).

Chapter 5. Administration reference 209

Log collector system tables

Column name Data type Description

VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
LANGUAGE CHAR(8) Programming language that the record procedure is written
in. This is ASM or C.
PARAMETER_EXPR_NO SMALLINT Number of the PARM expression in the DRLEXPRESSIONS
table. This is zero if no PARM expression is specified.
TIME_DEFINED TIMESTAMP Date and time when the record procedure was defined.
CREATOR CHAR(8) ID of the user who defined the record procedure.
REMARKS VARCHAR(254) Description of the record procedure, set by the COMMENT
ON statement.

DRLRECORDS
This system table contains one row for each defined record type and one row for each defined header in
log definitions.

Column name Data type Description

RECORD_NAME K VARCHAR(18) Name of the record. For a log header, this is *log-name*.
VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
LOG_NAME VARCHAR(18) Name of the log that contains the record.
BUILT_BY CHAR(8) Name of the record procedure that builds the record, if any.
NFIELDS SMALLINT Number of fields in the record.
NSECTIONS SMALLINT Number of sections in the record.
CONDITION_NO SMALLINT Number of the IDENTIFIED BY condition in the
DRLEXPRESSIONS table. This is zero if no IDENTIFIED BY
condition is specified.
TIME_DEFINED TIMESTAMP Date and time when the record was defined.
CREATOR CHAR(8) ID of the user who defined the record.
REMARKS VARCHAR(254) Description of the record, set by the COMMENT ON
statement.

DRLRPROCINPUT
This system table contains one row for every defined record type that must be processed by a record
procedure.

Column name Data type Description

PROGRAM_NAME K CHAR(8) Name of the record procedure.
RECORD_NAME K VARCHAR(18) Name of the record that is input to the record procedure.

210 IBM Z Decision Support : Administration Guide and Reference

 Log collector system tables

DRLSECTIONS
This system table contains one row for every defined section in defined record types.

Column name Data type Description

RECORD_NAME K VARCHAR(18) Name of the record.
SECTION_NO K SMALLINT Section sequence number within the record.
SECTION_NAME VARCHAR(18) Name of the section.
CONDITION_NO SMALLINT Number of the PRESENT IF condition in the
DRLEXPRESSIONS table. This is zero if no PRESENT IF
condition is specified.
OFFSET_EXPR_NO SMALLINT Number of the OFFSET expression in the DRLEXPRESSIONS
table. This is zero if no OFFSET expression is specified.
LENGTH_EXPR_NO SMALLINT Number of the LENGTH expression in the DRLEXPRESSIONS
table. This is zero if no LENGTH expression is specified.
NUMBER_EXPR_NO SMALLINT Number of the NUMBER expression in the
DRLEXPRESSIONS table. This is zero if no NUMBER
expression is specified.
INSECTION_NO SMALLINT Number of the section that this section is contained in. This
is zero if the section is not contained in another section.
REPEATED CHAR(1) Shows whether the section is repeated. This is Y (the section
is repeated) or N (the section is not repeated).

DRLUPDATECOLS
This system table contains one row for every column in each update definition, including GROUP BY, SET,
and MERGE columns.

Column name Data type Description

UPDATE_NAME K VARCHAR(18) Name of the update definition.
UPDATECOL_NO K SMALLINT Sequence number of the column in the update definition.
COLUMN_NAME VARCHAR(18) Name of the column.
COLUMN_NO SMALLINT Number of the column in the table definition.
FUNCTION CHAR(8) This is blank for GROUP BY columns; SUM, MAX, MIN,
COUNT, FIRST, LAST, AVG, or PERCENT for SET columns; or
INTTYPE, START, END, or QUIET for MERGE columns.
EXPRESSION_NO SMALLINT Number of the expression in the DRLEXPRESSIONS table.
COUNT_COLUMN VARCHAR(18) If the function is AVG or PERCENT, this contains the name of
the column that contains the count of values.
PERCENTILE SMALLINT If the function is PERCENT, this contains the percentile value
(1 - 99).

DRLUPDATEDISTR
This system table contains one row for every distributed field or column in each update definition.

Column name Data type Description

UPDATE_NAME K VARCHAR(18) Name of the update definition.
DISTR_NO K SMALLINT Field or column sequence number in the DISTRIBUTE
clause.

Chapter 5. Administration reference 211

Log collector system tables

Column name Data type Description

FIELD_NAME VARCHAR(18) Name of the field or column to be distributed.

DRLUPDATELETS
This system table contains one row for every identifier in the LET clause of each update definition. (The
identifiers are defined as abbreviations in the administration dialog.)

Column name Data type Description

UPDATE_NAME K VARCHAR(18) Name of the update definition.
LET_NO K SMALLINT Sequence number of the identifier in the LET clause.
LET_NAME VARCHAR(18) Name of the identifier.
EXPRESSION_NO SMALLINT Number of the expression in the DRLEXPRESSIONS table.

DRLUPDATES
This system table contains one row for each update definition.

Column name Data type Description

UPDATE_NAME K VARCHAR(18) Name of the update definition.
VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
SOURCE_PREFIX CHAR(8) Prefix of the source table. This is blank if the source is a
record.
SOURCE_NAME VARCHAR(18) Name of the source. This is a record name or a table name.
TARGET_PREFIX CHAR(8) Prefix of the target table.
TARGET_NAME VARCHAR(18) Name of the target table.
SECTION_NAME VARCHAR(18) Name of the repeated section, if any, that is used in the
update definition.
CONDITION_NO SMALLINT Number of the WHERE condition in the DRLEXPRESSIONS
table. This is zero if no WHERE condition is specified.
NLETS SMALLINT Number of identifiers specified in the LET clause.
NUPDATECOLS SMALLINT Number of columns in the GROUP BY, SET, and MERGE
clauses.
SCHEDULE_EXPR_NO SMALLINT Number of the APPLY SCHEDULE expression in the
DRLEXPRESSIONS table. This is zero if APPLY SCHEDULE is
not specified.
SCHEDULE_CALEXP_NO SMALLINT
SCHEDULE_INTTYPE VARCHAR(18) Name of the source column or field that defines the interval
type.
SCHEDULE_START VARCHAR(18) Name of the source column or field that defines the interval
start timestamp.
SCHEDULE_END VARCHAR(18) Name of the source column or field that defines the interval
end time stamp.
SCHEDULE_STATUS VARCHAR(18) Name of the identifier that contains the schedule status.

212 IBM Z Decision Support : Administration Guide and Reference

 Log collector system tables

Column name Data type Description

NDISTR_FIELDS SMALLINT Number of fields or columns that are distributed.
DISTR_BY_EXPR_NO SMALLINT Number of the DISTRIBUTE BY expression in the
DRLEXPRESSIONS table. This is zero if DISTRIBUTE is not
specified.
DISTR_FROM_EXPR_NO SMALLINT Number of the DISTRIBUTE FROM expression in the
DRLEXPRESSIONS table. This is zero if DISTRIBUTE is not
specified.
DISTR_TO_EXPR_NO SMALLINT Number of the DISTRIBUTE TO expression in the
DRLEXPRESSIONS table. This is zero if DISTRIBUTE is not
specified.
DISTR_TIMESTAMP VARCHAR(18) Name of the identifier that contains the distribution interval
start timestamp.
DISTR_INTERVAL VARCHAR(18) Name of the identifier that contains the distribution interval
length.
TIME_DEFINED TIMESTAMP Date and time when the update was defined.
CREATOR CHAR(8) ID of the user who defined the update.
REMARKS VARCHAR(254) Description of the update definition, set by the COMMENT
ON statement.

GENERATE_PROFILES
This system table contains one row for each profile for each generate statement profile. It is used
when installing components that use the GENERATE statement to create table spaces, partitioning, and
indexes.

Column name Data type Description

PROFILE K VARCHAR(18) Profile name. This value is specified on the PROFILE
parameter of the GENERATE TABLESPACE and GENERATE
INDEX statements.
COMPONENT_ID K VARCHAR(18) IBM Z Decision Support component ID or %. Allows for a
unique profile for an IBM Z Decision Support component.
SUBCOMPONENT_ID K VARCHAR(18) IBM Z Decision Support subcomponent ID or %. Allows for a
unique profile for an IBM Z Decision Support subcomponent.
An explicit subcomponent is only valid for a profile where an
explicit value is specified for COMPONENT_ID.
TABLESPACE_NAME K VARCHAR(18) Table space name or %. An explicit value can be
specified even if explicit values are not also specified for
COMPONENT_ID and SUBCOMPONENT_ID.
TABLESPACE_TYPE VARCHAR(9) Table space type (RANGE, GROWTH, SEGMENTED). If
invalid, GROWTH will be used. For type RANGE, there must
be a set of definitions in the GENERATE_KEYS system table
with the same profile name.
MAXPARTS INTEGER Maximum partitions. Used with TABLESPACE_TYPE of
GROWTH or SEGMENTED.
NUMPARTS INTEGER Initial number of partitions. Used with TABLESPACE_TYPE of
GROWTH. (For range partitioning, NUMPARTS is calculated
from the number of entries in the GENERATE_KEYS table).
SEGSIZE INTEGER Segment size for all table space types.

Chapter 5. Administration reference 213

Log collector system tables

Column name Data type Description

TBSPACE1 VARCHAR(250) The first set of SQL options allowed for GENERATE
TABLESPACE. (TBSPACE1 contains parameters that are in
the select group prior to the parameter DSSIZE in the Db2
SQL Reference syntax diagram for the CREATE TABLESPACE
statement.)
TBSPACE2 VARCHAR(250) The second set of SQL options allowed for GENERATE
DEFAULT TABLESPACE. (TBSPACE2 contains parameters
that are in the select group prior to the parameter SEGSIZE
in the Db2 SQL Reference syntax diagram for the CREATE
TABLESPACE statement.)
INDEX1 VARCHAR(250) The first set of SQL options allowed for GENERATE INDEX.
(INDEX1 contains parameters that are in the select group
following the parameter partition-element in the Db2
SQL Reference syntax diagram for the CREATE INDEX
statement.)
INDEX2 VARCHAR(250) The second set of SQL options allowed for GENERATE
INDEX. (INDEX2 contains parameters that are in the
select group starting with BUFFERPOOL-bpname in the
Db2 SQL Reference syntax diagram for the CREATE INDEX
statement.)

GENERATE_KEYS
This system table contains one row for each partition of a generate statement profile using range-
partitioning. It is used when installing components that use the GENERATE statement to create range-
partitioned table spaces, partitioning and indexes.

Column name Data type Description

PROFILE K VARCHAR(18) Profile name. This value is specified on the PROFILE
parameter of the GENERATE PARTITIONING statement.
COMPONENT_ID K VARCHAR(18) IBM Z Decision Support component ID or %. Allows for a
unique profile for an IBM Z Decision Support component.
SUBCOMPONENT_ID K VARCHAR(18) IBM Z Decision Support subcomponent ID or %. Allows for a
unique profile for an IBM Z Decision Support subcomponent.
An explicit subcomponent is only valid for a profile where an
explicit value is specified for COMPONENT_ID.
TABSPACE_NAME K VARCHAR(18) Table space name or %. An explicit value can be
specified even if explicit values are not also specified for
COMPONENT_ID and SUBCOMPONENT_ID.
PART_NUM K INTEGER The number of the physical partition for the table space.
NUMPARTS for a RANGE table space is the number of
PART_NUM entries for this profile name.
PARTITION_OPTIONS VARCHAR(250) A string of partition options added to each partition of the
partition-by-range specification of the generated CREATE
TABLESPACE statement.
RANGE_COLUMNS VARCHAR(250) Specifies the columns of the range-partitioning key. Provide
a comma-separated list of the columns comprising the
range-partitioning key. Column options as defined by the
Db2 ALTER TABLE … ADD PARTITION BY RANGE syntax may
also be specified.
PARTITION_KEY VARCHAR(250) The limiting key value for the partition boundary.
INCLUSIVE CHAR(1) Specifies if the range values are included in the data
partition: either Y (for inclusive) or N (for not inclusive).

214 IBM Z Decision Support : Administration Guide and Reference

 Dialog system tables

Dialog system tables

These tables contain definitions used by IBM Z Decision Support dialogs and utilities. Do not modify
them.

DRLCHARTS
This system table stores information extracted from the host graphical report formats (ADMCFORM data).
Data is inserted into this table at installation time by the host DRLIRD2 member. If GDDM version 3 or
later is installed and available, DRLCHARTS is also updated by the host exec DRLECHRT when a report is
saved in the host ISPF dialog.

Column name Data type Description

CHART_NAME K CHAR(8) ADMCFORM name. This is the same as the CHART column in
the DRLREPORTS table.
TYPE SMALLINT This column shows a number identifying the chart type:
1
Line chart
2
Surface chart
3
Histogram
41, 42, 43
Bar chart. The 4 indicates that this is a bar chart; 1,
2, or 3 indicates whether the bars are side by side (1),
stacked (2), or overlaid (3).
5
Pie chart
6
Venn diagram
7
Polar chart
8
Tower diagram
9
Table. This is not used.
10
Combination chart.

VALUES SMALLINT This column contains one of the values 0, 1, 2, or 3. The

column is valid only for chart types 4 (bar) and 5 (pie). For
bar charts, the values are:
0
No values are shown
1
Values are shown at the top/end of the bar
2
Values are shown inside the bars
3
Values are shown as in GDDM version 1 release 3
For pie charts, the values are:
1
Values are shown
2
No values are shown

Chapter 5. Administration reference 215

Dialog system tables

Column name Data type Description

AXIS_ORIENT SMALLINT Axis orientation. This can be 1 or 2. 1 means vertical y-axis
and bars. 2 means horizontal y-axis and bars.
Y_DATA_TYPE VARCHAR(50) If the chart type is 10 (combination), this column shows the
chart type for each data group:
1
Line chart
2
Surface chart
3
Histogram
41, 42, 43
Bar chart
For example, 1, 42, 42, 42, 42 identifies a combination
chart with a line chart and stacked bars. For a bar chart, the
number is concatenated to indicate bar position as in TYPE
above.
X_AXIS_TITLE VARCHAR(52) This is a string containing the x-axis title.
Y_AXIS_TITLE VARCHAR(52) This is a string containing the y-axis title.

DRLCOMPONENTS
This system table contains one row for each IBM Z Decision Support component.

Column name Data type Description

COMPONENT_NAME K VARCHAR(18) Name of the component.
DESCRIPTION VARCHAR(50) Description of the component that is shown in the dialog.
STATUS CHAR(1) Component status. This is blank if the component is not
installed, I if the component is installed online, or B if the
component is installed in batch.
TIME_INSTALLED TIMESTAMP Date and time when the component was installed or defined.
USER_ID CHAR(8) ID of the user who installed or defined the component.

DRLCOMP_OBJECTS
This system table contains one row for every object in each component.

Column name Data type Description

COMPONENT_NAME K VARCHAR(18) Name of the component.
OBJECT_NAME K VARCHAR(18) Name of the object.
OBJECT_TYPE K CHAR(8) Type of object. This is LOG, RECORD, RECPROC, TABSPACE,
LOOKUP, TABLE, UPDATE, REPORT, or REPGROUP.
MEMBER_NAME CHAR(8) Name of the member in the SDRLDEFS or SDRLRxxx library
where the object is defined.
PART_NAME VARCHAR(18) Name of the component part that the object belongs to, if
any.
EXCLUDE_FLAG CHAR(1) Flag to determine if this object is excluded from installation
of the component.

216 IBM Z Decision Support : Administration Guide and Reference

 Dialog system tables

DRLCOMP_PARTS
This system table contains one row for every part in each component.

Column name Data type Description

COMPONENT_NAME K VARCHAR(18) Name of the component.
PART_NAME K VARCHAR(18) Name of the component part.
DESCRIPTION VARCHAR(50) Description of the component part that is shown in the
dialog.
STATUS CHAR(1) Component part status. This is blank if the component part
is not installed, I if the component part is installed online, or
B if the component is installed in batch.
TIME_INSTALLED TIMESTAMP Date and time when the component part was installed or
defined.
USER_ID CHAR(8) ID of the user who installed or defined the component part.

DRLGROUPS
This system table contains one row for each defined report group.

Column name Data type Description

GROUP_NAME K VARCHAR(18) Group ID.
GROUP_OWNER K CHAR(8) Owner of the group. This is blank for a public group.
VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
DESCRIPTION VARCHAR(50) Description of the group that is shown in the dialog.
TIME_CREATED TIMESTAMP Date and time when the group was defined.
CREATOR CHAR(8) ID of the user who defined the group.

DRLGROUP_REPORTS
This system table contains one row for every report in each defined report group.

Column name Data type Description

GROUP_NAME K VARCHAR(18) Group ID.
GROUP_OWNER K CHAR(8) Owner of the group.
REPORT_NAME K VARCHAR(18) ID of the report that belongs to the group.
REPORT_OWNER K CHAR(8) Owner of the report that belongs to the group.

DRLREPORTS
This system table contains one row for each defined report.

Column name Data type Description

REPORT_NAME K VARCHAR(18) Report ID.
REPORT_OWNER K CHAR(8) Owner of the report. This is blank for a public report.

Chapter 5. Administration reference 217

Dialog system tables

Column name Data type Description

VERSION VARCHAR(18) Version level. The value of VERSION is set for an object
when the object is defined and is taken from the value
of keyword VERSION. For definitions supplied by IBM, the
value is IBM.nnn[.APAR_number], where nnn is the version,
release, modification level of the object.
DESCRIPTION VARCHAR(50) Description of the report that is shown in the dialog.
TYPE CHAR(8) Type of report. This is QUERY, TABDATA, or GRAPH.
BATCH CHAR(1) Y if the report should be produced in batch; N otherwise.
PRINT CHAR(1) Y if the report should be printed when produced in batch; N
otherwise.
SAVE CHAR(1) Y if the report should be saved when produced in batch; N
otherwise.
RUN_CYCLE CHAR(8) Batch run cycle for the report. This is DAILY, WEEKLY, or
MONTHLY.
QUERY_PREFIX CHAR(8) Prefix of the QMF query that should be run when the report
is produced.
QUERY VARCHAR(18) Name of the QMF query that should be run when the report
is produced.
FORM_PREFIX CHAR(8) Prefix of the QMF form that should be used when the report
is produced.
FORM VARCHAR(18) Name of the QMF form that should be used when the report
is produced.
CHART CHAR(8) Name of the GDDM-ICU format to be used for the report.
Blank means that the report is tabular.
FILE CHAR(8) Name of the member where the data is saved (if type is
TABDATA or GRAPH), or where the data should be saved
when the report is produced in batch (if save is Y).
MACRO CHAR(8) Not used.
TABLE_NAME VARCHAR(254) Name of the table or tables on which the the report is bases.
This is extracted from the query when the report is defined.
NVARIABLES SMALLINT Number of variables defined for the report or extracted from
the query.
NATTRIBUTES SMALLINT Number of attributes defined for the report.
TIME_CREATED TIMESTAMP Date and time when the report was defined.
CREATOR CHAR(8) ID of the user who defined the report.
REMARKS VARCHAR(254) Long free-format description of the report that can be
entered from the dialog.
FINAL_SUMMARY CHAR(3) This is valid when QMF is not used. If FINAL_SUMMARY is
set to YES, a row containing totals for all numeric columns is
generated at the end of the report.
ACROSS_SUMMARY CHAR(3) If ACROSS_SUMMARY is set to YES for a report of the Across
type, a summary column is created to the right in the report.
It contains one total value for each row. This is valid when
QMF is not used.

DRLREPORT_ATTR
This system table contains one row for every attribute in each defined report.

218 IBM Z Decision Support : Administration Guide and Reference

 Dialog system tables

Column name Data type Description

REPORT_NAME K VARCHAR(18) Report ID.
REPORT_OWNER K CHAR(8) Owner of the report. This is blank for a public report.
ATTRIBUTE_NO K SMALLINT Attribute sequence number.
ATTRIBUTE VARCHAR(18) Attribute value.

DRLREPORT_COLUMNS
This system table contains one row for every column in each defined report if QMF is not used. The
information is taken from the QMF form.

Column name Data type Description

REPORT_NAME K VARCHAR(18) Report ID.
REPORT_OWNER K CHAR(8) Owner of the report. This is blank for a public report.
COLUMN_NO K SMALLINT Column number.
HEADING VARCHAR(40) Column heading.
USAGE CHAR(7) Usage code.
INDENT SMALLINT Column indentation.
WIDTH SMALLINT Column width.
EDIT CHAR(5) Edit code.
SEQ SMALLINT Column sequence number.
DEFINITION VARCHAR(50) The DEFINITION column can define an additional report
column, which is not present in the SQL query. The definition
must be a valid REXX expression, and may contain numeric
constants and variables of the &n type, where n is an existing
column number. The DEFINITION column is intended only
for existing IBM Z Decision Support reports and is not used
for user-defined reports.

DRLREPORT_QUERIES
This system table contains one row for every query line in each defined report, if QMF is not used.

Column name Data type Description

REPORT_NAME K VARCHAR(18) Report ID.
REPORT_OWNER K CHAR(8) Owner of the report. This is blank for a public report.
LINE_NO K SMALLINT Line number in the query.
QUERY_LINE VARCHAR(80) Query text.

DRLREPORT_TEXT
This system table is used for for host reports when QMF is not used. It contains one row for every heading
and footing row. It also contains one row if there is a final summary line with a final text, and one row if
there is an expression that limits the number of output rows in the report.

Column name Data type Description

REPORT_NAME K VARCHAR(18) Report ID.
REPORT_OWNER K CHAR(8) Owner of the report. This is blank for a public report.

Chapter 5. Administration reference 219

Dialog system tables

Column name Data type Description

TYPE K CHAR(8) Text type. This is HEADING, FOOTING, DETAIL, FINAL or
ROWS.
LINE_NO K SMALLINT Line number for HEADING and FOOTING.
ALIGNMENT CHAR(6) Shows how the text should be aligned; left, center, or right.
TEXT VARCHAR(55) Text for one line of a report text (see TYPE above).

DRLREPORT_VARS
This system table contains one row for every variable in each defined report. The variables may be
specified in the DEFINE REPORT statement or extracted from the query.

Column name Data type Description

REPORT_NAME K VARCHAR(18) Report ID.
REPORT_OWNER K CHAR(8) Owner of the report. This is blank for a public report.
VARIABLE_NO K SMALLINT Sequence number of the variable.
VARIABLE_NAME VARCHAR(18) Name of the variable.
EXPRESSION VARCHAR(80) Expression in the query that is compared with the variable,
if the variable is found in the query. This is used, with
TABLE_NAME in the DRLREPORTS table, to find a list of
possible values for the variable.
OPERATOR CHAR(4) Operator that is used when comparing the variable and the
expression, if the variable is found in the query. This is =, <=,
>=, IN, or LIKE.
DATA_TYPE CHAR(8) Data type of the variable, if specified. This is CHAR,
NUMERIC, DATE, TIME, or TIMESTAMP.
REQUIRED CHAR(1) Shows whether the variable must be given a value. This is Y
for yes, or N or blank for no.
DEFAULT VARCHAR(40) Default value to use for the variable, if specified.
IN_HEADER CHAR(1) Variable to determine if the IBM Z Decision Support variable
is used in the header. This is Y for yes, or N for no.
IN_HEADER_VALUE VARCHAR(35) Default header value for a non-required variable without a
substitution value.

DRLSEARCH_ATTR
This system table contains one row for every attribute in each saved report search.

Column name Data type Description

SEARCH_NAME K VARCHAR(18) Name of the saved search.
SEARCH_OWNER K CHAR(8) Owner of the saved search. This is blank for a public search.
ATTR_SET_NO K SMALLINT Attribute set sequence number. The attribute sets are
logically ORed together.
ATTRIBUTE_NO K SMALLINT Attribute sequence number within the attribute set. The
attributes within a set are logically ANDed together.
ATTRIBUTE VARCHAR(18) Attribute value. This can contain global search characters.

220 IBM Z Decision Support : Administration Guide and Reference

 Views

DRLSEARCHES
This system table contains one row for each saved report search.

Column name Data type Description

SEARCH_NAME K VARCHAR(18) Name of the saved search.
SEARCH_OWNER K CHAR(8) Owner of the saved search. This is blank for a public search.
DESCRIPTION VARCHAR(50) Description of the search that is shown in the dialog.
NATTR_SETS SMALLINT Number of attribute sets used in the search.
REPORT_DESC VARCHAR(50) Report description used in the search. This can contain
global search characters.
REPORT_TYPE CHAR(8) Report type specified in the search.
REPORT_OWNER CHAR(8) Report owner specified in the search.
TIME_CREATED TIMESTAMP Date and time when the search was saved.
CREATOR CHAR(8) ID of the user who saved the search.

Views on Db2 and QMF tables

These views on Db2 tables are required for users without access to the tables.

View name Description

DRLCOLUMNS This view is based on SYSIBM.SYSCOLUMNS in the Db2 catalog. It is used to get column
names and comments.
DRLINDEXES This table is based on SYSIBM.SYSINDEXES in the Db2 catalog. It is used to get table
index information.
DRLINDEXPART This view is based on SYSIBM.SYSINDEXPART in the Db2 catalog. It is used to get index
partition information.
DRLKEYS This view is based on SYSIBM.SYSKEYS in the Db2 catalog. It is used to get information on
index keys.
DRLOBJECT_DATA This view is based on Q.OBJECT_DATA, a QMF control table that contains information
about QMF objects.
DRLTABAUTH This view is based on SYSIBM.SYSTABAUTH in the Db2 catalog. It is used to get table
privilege information.
DRLTABLEPART This view is based on SYSIBM.SYSTABLEPART in the Db2 catalog. It is used to get table
space information.
DRLTABLES This view is based on SYSIBM.SYSTABLES in the Db2 catalog. It is used to get a list of
tables and comments for the tables.
DRLTABLESPACE This view is based on SYSIBM.SYSTABLESPACE in the Db2 catalog. It is used to get a list of
table spaces.
DRLVIEWS This view is based on SYSIBM.SYSVIEWS in the Db2 catalog. It is used to get view
definitions.

Views on IBM Z Decision Support system tables

These views on IBM Z Decision Support dialog system tables are required for users without access to the
tables.

Chapter 5. Administration reference 221

Views

View Name Description

DRLUSER_GROUPREPS This view is based on DRLGROUP_REPORTS. It allows a user to update only his own report
groups.
DRLUSER_GROUPS This view is based on DRLGROUPS. It allows a user to update only his own report groups.
DRLUSER_REPORTATTR This view is based on DRLREPORT_ATTR. It allows a user to update only his own reports.
DRLUSER_REPORTS This view is based on DRLREPORTS. It allows a user to update only his own reports.
DRLUSER_REPORTVARS This view is based on DRLREPORT_VARS. It allows a user to update only his own reports.
DRLUSER_SEARCHATTR This view is based on DRLSEARCH_ATTR. It allows a user to update only his own searches.
DRLUSER_SEARCHES This view is based on DRLSEARCHES. It allows a user to update only his own searches.
DRLUSER_REPORTQRYS This view is based on DRLREPORT_QUERIES. It allows a user to update only his own
reports.
DRLUSER_REPORTCOLS This view is based on DRLREPORT_COLUMNS. It allows a user to update only his own
reports.
DRLUSER_REPORTTEXT This view is based on DRLREPORT_TEXT. It allows a user to update only his own reports.

Control tables and common tables

This chapter describes control tables and common tables. These tables are used by many IBM Z Decision
Support components. The tables are provided with the IBM Z Decision Support base.
Each table description includes information about the table, and a description of each key column and
data column in the table.
Key columns are marked with a "K".
Data columns come after the last key column and are sorted in alphabetical order, with any underscores
ignored.
The tables appear in alphabetical order, with any underscores ignored.
Note: Data tables with similar contents (that is, data tables with the same name but different suffixes) are
described under one heading. For example, “AVAILABILITY_D, _W, _M” on page 226 contains information
about three similar tables:

AVAILABILITY_D
AVAILABILITY_W
AVAILABILITY_M

Except for the DATE column and TIME column, the contents of these three tables are identical.
Differences in the contents of similar tables are explained in the column descriptions.
The DATE and TIME information are stored in the standard Db2 format and displayed in the local format.

Control tables
The control tables are created during installation of the IBM Z Decision Support base. The tables control
results returned by some log collector functions.
Control tables appear in the tables list in the administration dialog.

DAY_OF_WEEK
This control table defines the day type to be returned by the DAYTYPE function for each day of the week.
The day type is used as a key in the PERIOD_PLAN and SCHEDULE control tables.

Column name Data type Description

DAY_OF_WEEK K SMALLINT Day of week number, 1 through 7 (Monday through Sunday).

222 IBM Z Decision Support : Administration Guide and Reference

 Views

Column name Data type Description

DAY_TYPE CHAR(8) Day type for the day of week.

Example of table contents

DAY
OF DAY
WEEK TYPE
------ --------
1 MON
2 TUE
3 WED
4 THU
5 FRI
6 SAT
7 SUN

PERIOD_PLAN
This control table defines the periods to be returned by the PERIOD function, which is described in the
Language Guide and Reference. A period plan defines the partition of a day into periods (such as shifts) for
each day type defined by the DAY_OF_WEEK and SPECIAL_DAY control tables.

Column name Data type Description

PERIOD_PLAN_ID K CHAR(8) You can have different sets of period names for different systems. Each
application normally uses a system ID from the log to match this field, for
example the MVS system ID for an MVS performance application. Specify % for
the rows that specify your default set of period names. This can contain global
search characters.
DAY_TYPE K CHAR(8) Day type the period applies to. This can be any of the day types specified in the
DAY_OF_WEEK and SPECIAL_DAY control tables.
START_TIME K TIME Time when the period starts.
END_TIME TIME Time when the period ends.
PERIOD_NAME CHAR(8) Name of the period.

Example of table contents

PERIOD
PLAN DAY START END PERIOD
ID TYPE TIME TIME NAME
-------- -------- -------- -------- --------
% MON 00.00.00 08.00.00 NIGHT
% MON 08.00.00 17.00.00 PRIME
% MON 17.00.00 24.00.00 NIGHT
% TUE 00.00.00 08.00.00 NIGHT
% TUE 08.00.00 17.00.00 PRIME
% TUE 17.00.00 24.00.00 NIGHT
% WED 00.00.00 08.00.00 NIGHT
% WED 08.00.00 17.00.00 PRIME
% WED 17.00.00 24.00.00 NIGHT
% THU 00.00.00 08.00.00 NIGHT
% THU 08.00.00 17.00.00 PRIME
% THU 17.00.00 24.00.00 NIGHT
% FRI 00.00.00 08.00.00 NIGHT
% FRI 08.00.00 17.00.00 PRIME
% FRI 17.00.00 24.00.00 NIGHT
% SAT 00.00.00 24.00.00 WEEKEND
% SUN 00.00.00 24.00.00 WEEKEND
% HOLIDAY 00.00.00 24.00.00 HOLIDAY

SCHEDULE
This control table defines the schedules to be returned by the APPLY SCHEDULE function. A schedule is a
time period when a resource is planned to be up; it is used in availability calculations.

Chapter 5. Administration reference 223

Views

Column name Data type Description

SCHEDULE_NAME K CHAR(8) Name of the schedule. By giving different names to schedules, you
can have different schedules for the various systems or resources. The
AVAILABILITY_PARM table controls which schedule name to use for a
resource.
DAY_TYPE K CHAR(8) Day type the schedule applies to. This can be any of the day types specified in
the DAY_OF_WEEK and SPECIAL_DAY control tables.
START_TIME K TIME Time when the schedule starts.
END_TIME TIME Time when the schedule ends.

Example of table contents

SCHEDULE DAY START END
NAME TYPE TIME TIME
-------- -------- -------- --------
STANDARD MON 08.00.00 17.00.00
STANDARD TUE 08.00.00 17.00.00
STANDARD WED 08.00.00 17.00.00
STANDARD THU 08.00.00 17.00.00
STANDARD FRI 08.00.00 17.00.00
STANDARD SAT 00.00.00 00.00.00
STANDARD SUN 00.00.00 00.00.00
STANDARD HOLIDAY 00.00.00 00.00.00

SPECIAL_DAY
This control table defines the day type to be returned by the DAYTYPE function for special dates such as
holidays. The day type is used as a key in the PERIOD_PLAN and SCHEDULE control tables.

Column name Data type Description

DATE K DATE Date to be defined as special day.
DAY_TYPE CHAR(8) Day type for the date; for example, HOLIDAY.

Example of table contents

DAY
DATE TYPE
---------- --------
1999-12-25 HOLIDAY
2000-01-01 HOLIDAY

CICS control tables

The CICS control tables are created during installation of the IBM Z Decision Support base. The tables
control results returned by some log collector functions during CICS log data collection.
CICS control tables appear in the tables list in the administration dialog.

CICS_DICTIONARY
This control table is used during CICS log data collection. The CICS record procedure, DRL2CICS,
uses CICS_DICTIONARY to store the latest dictionary record processed for each unique combination
of MVS_SYSTEM_ID, CICS_SYSTEM_ID, CLASS and VERSION. For more information, refer to the CICS
Performance Feature Guide and Reference.

Column name Data type Description

MVS_SYSTEM_ID K CHAR(4) MVS system ID. From SMFMNSID (V3) or SMFSID (V2).
CICS_SYSTEM_ID K CHAR(8) CICS generic ID. This is the VTAM® application identifier for the CICS system
that produced the dictionary. From SMFMNPRN (V3) or SMFPSPRN (V2).

224 IBM Z Decision Support : Administration Guide and Reference

 Common data tables

Column name Data type Description

CLASS K SMALLINT Monitoring class. This is 2 for accounting (CICS/MVS V2 only), 3 for
performance data, and 4 for exception data (CICS/MVS V2 only). From
SMFMNCL (V3) or MNSEGCL (V2).
VERSION K SMALLINT Version of the CICS system that produced the dictionary. This is 2 for CICS/MVS
(V2) and 3 for CICS/ESA (V3). Set by DRL2CICS based on SMFMNSTY (V3) or
SMFSTY (V2).
FIELD_NO K SMALLINT Assigned connector for this dictionary entry (CMODCONN). This is also the
index to the dictionary entry array.
CICS_VER K CHAR(4) CICS version and release that created this dictionary (from the field
SMFMNRVN). EX. 0410.
DICT_ENTRY_ID CHAR(12) Dictionary entry ID. It is made up of the CMODNAME, CMODTYPE and
CMODIDNT fields in the dictionary entry. It is used to uniquely identify each
dictionary entry.
OUTPUT_LENGTH SMALLINT Field length for matching DICT_ENTRY_ID in CICS_FIELD. It is used for building
the output record.
OUTPUT_OFFSET SMALLINT Field offset for matching DICT_ENTRY_ID in CICS_FIELD. It is used for building
the output record.
USED CHAR(8) A flag indicating (if = Y) that this dictionary entry has been updated with field
length and offset data from a matching DICT_ENTRY_ID in CICS_FIELD.

CICS_FIELD
This control table is used during CICS log data collection. The CICS record procedure, DRL2CICS, uses
CICS_FIELD to store field lengths and offsets for dictionary fields described in “CICS_DICTIONARY”
on page 224. For more information, refer to the CICS Performance Feature Guide and ReferenceCICS
Performance Feature Guide and Reference.

Column name Data type Description

CLASS K SMALLINT CMF record class. 2 for accounting (CICS/MVS V2 only), 3 for performance
data (transaction and global (CICS/MVS V2 only)) and 4 for exception data
(CICS/MVS V2 only).
DICT_ENTRY_ID K CHAR(12) This is the dictionary entry ID. It is made up of the CMODNAME, CMODTYPE
and CMODIDNT fields in the dictionary entry. It is used to uniquely identify
each dictionary entry.
FIRST_CICS_VER K CHAR(4) This is first version of CICS that introduced this CMODTYPE and CMODIDNT
with these attributes. This allows multiple versions of the same key as many
fields were changed with CICS TS 3.2
OUTPUT_LENGTH SMALLINT This is the field length that is used to build the output record.
OUTPUT_OFFSET INTEGER This is the field offset that is used to build the output record. This offset
should match the SMF_CICS_T, _G, _A, _E2 record definitions.

Common data tables

These tables are ordinary data tables that are used by many components. They are provided with the IBM
Z Decision Support base, but not created until the installation of the first component that uses them.

Naming standard for common data tables

Names of IBM Z Decision Support common data tables are in this format:
content_suffix
where:

Chapter 5. Administration reference 225

Common data tables

• content is a description (for example, AVAILABILITY for system and resource availability data).
• suffix indicates the summarization level of the data in the table (for example, AVAILABILITY_D for
availability data summarized by day).
A common table name can have these summarization-level suffixes:
_T
The table holds nonsummarized data (timestamped data).
_D
The table holds data summarized by day.
_W
The table holds data summarized by week.
_M
The table holds data summarized by month.

AVAILABILITY_D, _W, _M
These tables provide daily, weekly, and monthly statistics on the availability of systems and subsystems.
They contain consolidated data from the AVAILABILITY_T table.
The default retention periods for these tables are:
AVAILABILITY_D
90 days
AVAILABILITY_W
400 days
AVAILABILITY_M
800 days

Column name Data type Description

DATE K DATE Date that the availability data applies to. For the _W table, this is
the date of the first day of the week. For the _M table, this is the
date of the first day of the month.
SYSTEM_ID K CHAR(8) System ID such as an MVS or VM system ID.
AREA K CHAR(8) Major area the resource is related to, such as MVS or NETWORK.
RESOURCE_TYPE K CHAR(8) Resource type.
RESOURCE_NAME K CHAR(8) Resource name.
RESOURCE_GROUP K CHAR(8) Resource group.
AVAIL_OBJ_PCT DECIMAL(4,1) Availability objective for the resource, in percent. This is from the
column AVAIL_OBJ_PCT in the AVAILABILITY_PARM lookup table.
This value should be compared with the actual availability, which is
calculated as: 100*UP_IN_SCHEDULE/SCHEDULE_HOURS.
MEASURED_HOURS FLOAT Number of hours measured.
SCHEDULE_DAYS SMALLINT Number of days during the week or month that the resource was
scheduled to be up. This column is only present in the _W and _M
tables.
SCHEDULE_HOURS FLOAT Number of hours the resource was scheduled to be up.
STARTS SMALLINT Number of times the resource was started.
STARTS_IN_SCHEDULE SMALLINT Number of times the resource was started within the schedule.
STOPS SMALLINT Number of times the resource was stopped.
STOPS_IN_SCHEDULE SMALLINT Number of times the resource was stopped within the schedule.

226 IBM Z Decision Support : Administration Guide and Reference

 Common data tables

Column name Data type Description

UP_HOURS FLOAT Number of hours the resource was up.
UP_IN_SCHEDULE FLOAT Number of hours the resource was up within the schedule.

AVAILABILITY_T
This table provides detailed availability data about the system as a whole and all its subsystems. The data
comes from many different sources. For every resource tracked, this table contains one row for each time
interval with a different status.
The default retention period for this table is 10 days.

Column name Data type Description

SYSTEM_ID K CHAR(8) System ID such as an MVS or VM system ID.
AREA K CHAR(8) Major area the resource is related to, such as MVS or NETWORK.
RESOURCE_TYPE K CHAR(8) Resource type.
RESOURCE_NAME K CHAR(8) Resource name.
RESOURCE_GROUP K CHAR(8) Resource group.
INTERVAL_TYPE K CHAR(3) Interval type. Possible values are: ===, |==, ==|, |=|, XXX, |XX, XX|, |X|,
and blank, where:
=
Indicates that the resource is up (available)
X
Indicates that the resource is down
|
Indicates an interval start or end
blank
Means that the status is unknown

START_TIME K TIMESTAMP Start time of the interval.

END_TIME TIMESTAMP End time of the interval.
QUIET_INTERVAL_SEC INTEGER Number of seconds after the interval end that the resource is expected
to remain in the same status. If another interval with a start time
within this range appears, the two intervals are merged.

EXCEPTION_T
This table provides a list of exceptions that have occurred in the system and require attention. The data
comes from many different sources.
The layout of this table cannot be changed by the user.
The default retention period for this table is 14 days.

Column name Data type Description

DATE K DATE Date when the exception occurred.
TIME K TIME Time when the exception occurred.
SYSTEM_ID K CHAR(8) System where the exception occurred.
AREA K CHAR(8) Major area the exception is related to, such as MVS or NETWORK.
EXCEPTION_ID K VARCHAR(18) Short description of the exception type. This can be used to count the
number of exceptions of different types.

Chapter 5. Administration reference 227

Common lookup tables

Column name Data type Description

RESOURCE_NAME1 K CHAR(8) Name of the first resource that the exception is related to.
RESOURCE_NAME2 K CHAR(8) Name of the second resource that the exception is related to.
DATE_GENERATED DATE Date when the problem was recorded in the Information/Management
database. This is null if no problem record has been generated.
EXCEPTION_DESC VARCHAR(45) Text that describes the exception, in any format.
PROBLEM_FLAG CHAR(1) Controls whether a problem record should be automatically generated
for the exception. This can be Y (generate a problem record) or N (do
not generate a problem record).
PROBLEM_NUMBER CHAR(8) The Information/Management problem-record number. This is null if
no problem record has been generated.
SEVERITY CHAR(2) Severity of the problem. This is user-defined.
TRANSACT_NUMBER INTEGER Transaction identifier number.
TRANSACT_CHAR CHAR(4) Transaction number in character format. (in some special cases CICS
system tasks are identified as III, JBS, J01-J99, TCB.)
PROGRAM_NAME CHAR(8) Name of the program.

MIGRATION_LOG
This table holds information on what migration jobs have been run, and the results of each step.
The layout of this table cannot be changed by the user.
The default retention period for this table is 14 days.

Column name Data type Description

JOB_NAME K CHAR(8) Migration job name.
STEP_NO K INTEGER Step number of job.
START_DATE K DATE Start date of job.
START_TIME K TIME Start time of job.
STEP_NAME CHAR(30) Step name of job.
RETURN_CODE INTEGER Step status code.
COMPLETED_CODE CHAR Y - Completed successfully
U - Abend

END_DATE DATE End date of last migration step.

END_TIME TIME End time of last migration step.

Common lookup tables

These tables are ordinary lookup tables that are used by many components. They are provided with the
IBM Z Decision Support base, but not created until the installation of the first component that uses them.

AVAILABILITY_PARM
This lookup table sets availability parameters. It contains the schedule names and availability objectives
to use for the different resources in the system. Its values are used in the AVAILABILITY_D, _W, and _M
tables.

228 IBM Z Decision Support : Administration Guide and Reference

 Common lookup tables

Column name Data type Description

SYSTEM_ID K CHAR(8) System ID associated with the resource. This can contain global
search characters.
AREA K CHAR(8) Major area that the resource is related to, such as MVS or NETWORK.
This can contain global search characters.
RESOURCE_TYPE K CHAR(8) Resource type. This can contain global search characters.
RESOURCE_NAME K CHAR(8) Resource name. This can contain global search characters.
RESOURCE_GROUP K CHAR(8) Resource group. This can contain global search characters.
AVAIL_OBJ_PCT DECIMAL(4,1) Availability objective for the resource, in percent.
SCHEDULE_NAME CHAR(8) Schedule name to use for the resource.

Example of table contents

AVAIL
SYSTEM RESOURCE RESOURCE RESOURCE SCHEDULE OBJ
ID AREA TYPE NAME GROUP NAME PCT
-------- -------- -------- -------- -------- -------- -------
% % % % % STANDARD 95.0
⋮

USER_GROUP
This lookup table groups the users of the system into user groups. The values are used in many tables.
You can also assign division and department names to the user groups; however, the names are left blank
in the predefined tables.

Column name Data type Description

SYSTEM_ID K CHAR(8) System ID such as an MVS or VM system ID. This can contain global search
characters.
SUBSYSTEM_ID K CHAR(8) Subsystem ID such as TSO or a CICS* system ID. This can contain global search
characters. This is not used in the predefined tables.
USER_ID K CHAR(8) User ID of the user to be grouped. This can contain global search characters.
DEPARTMENT CHAR(8) Department that the user belongs to. This is not used in the predefined tables.
DIVISION CHAR(8) Division that the user belongs to. This is not used in the predefined tables.
GROUP_NAME CHAR(8) Name of the group that the user belongs to.

Example of table contents

SYSTEM SUBSYSTEM USER GROUP
ID ID ID DIVISION DEPARTMENT NAME
-------- --------- -------- -------- ---------- --------
* * USER1 GROUP1
* * USER2 GROUP2
⋮

TIME_RES
This lookup table defines the time resolution to use for each row of data stored in a set of tables. This
enables you to specify that data should be recorded for a time period other than 1 hour. The values are
used in these data tables:
• D_DB2_BUFF_POOL_T
• D_DB2_DATABASE_T
• D_DB2_SYSTEM_T

Chapter 5. Administration reference 229

Common lookup tables

• D_KPM_DB2_BP_T
• D_KPM_DB2_DBASE_T
• D_KPM_DB2_SYSTEM_T

Column name Data type Description

HOUR K CHAR(2) Hour of the day (that the time resolution applies to), 00 to 23.
PERIOD_NAME K CHAR(8) Name of the period. This can contain global search characters.
SYSTEM_ID K CHAR(8) Name of the system. This can contain global search characters.
TABLE_SET_NAME K CHAR(18) Name that identifies the set of tables the time resolution is defined for.
TIME_RESOLUTION SMALLINT Time resolution for the set of tables, in minutes. This defines the time period for
which data is to be recorded. Valid values are 1, 2, 3, 5, 6, 10, 12, 15, 20, 30, or
any multiple of 60.

Example of table contents

HOUR PERIOD_NAME SYSTEM_ID TABLE_SET_NAME TIME_RESOLUTION

---- ----------- --------- ----------------- ---------------
% % % D_DB2_BUFF_POOL_T 15
% % % D_DB2_DATABASE_T 15
% % % D_DB2_SYSTEM_T 15
% % % D_KPM_DB2_BP_T 15
% % % D_KPM_DB2_DBASE_T 15
% % % D_KPM_DB2_SYSTEM_T 15

AGGR_VALUE
This table is to be used to assign a default value to a key field if it is not required in the aggregation. If a
record is found in the AGGR_VALUE for a particular table and column, then the default value is used in the
aggregation. This has the potential to reduce the number of rows collected for that particular table.

Column name Data type Description

AGGR_TABLE K CHAR(18) Name of TDS table.
AGGR_COLUMN K CHAR(18) Name of TDS column.
AGGR_DEF_VALUE CHAR(16) Default value to assign to field.

Example of table contents

AGGR AGGR AGGR
TABLE COLUMN DEF
VALUE
------------------ ------------------ ----------------
DB2_PACKAGE_H CORRELATION_ID $USER
DB2_PACKAGE_H PRIMARY_AUTH_ID $USER

Sample component
This topic describes the Sample component, the only component shipped with the IBM Z Decision
Support base product. You can use the Sample component for testing the installation of the base product
or to demonstrate IBM Z Decision Support.
The sample component consists of:
• A sample log and record definition
• Three sample tables with update definitions
• Three sample reports
• A log data set with sample data that can be collected

230 IBM Z Decision Support : Administration Guide and Reference

 Sample component

Figure 106 on page 231 shows an overview of the flow of data from the sample log data set, DRLSAMPL
(in the DRLxxx.SDRLDEFS library), through the Sample component of IBM Z Decision Support, and finally
into reports.

Sample log data set

Collect

Records

SAMPLE_01

Data tables

Lookup and
control tables
SAMPLE_H
SAMPLE_M
SAMPLE_USER

Reports

Figure 106. Sample data flow

Sample component
You can use the Sample component for testing the installation of the base product or to demonstrate .

SAMPLE_H, _M data tables

These tables provide hourly and monthly sample data.

Column name Data type Description

DATE K DATE Date. For the _M table, this is the date of the first day of the month. From
S01DATE.
TIME K TIME Time rounded down to the nearest hour. This applies only to the _H table.
From S01TIME.
SYSTEM_ID K CHAR(4) System ID. From S01SYST.
DEPARTMENT_NAME K CHAR(8) Department name. From DEPARTMENT_NAME in the SAMPLE_USER
lookup table. This is derived using field S01USER from the record as key.
USER_ID K CHAR(8) User ID. From S01USER.
CPU_SECONDS FLOAT Total processor time, in seconds. Calculated as the sum of S01CPU/
100.0.
PAGES_PRINTED INTEGER Number of pages printed. This is the sum of S01PRNT.
RESPONSE_SECONDS INTEGER Total response time, in seconds. This is the sum of S01RESP.
TRANSACTIONS INTEGER Number of transactions. This is the sum of S01TRNS.

Chapter 5. Administration reference 231

Lookup table

SAMPLE_USER lookup table

This lookup table assigns department names to users.

Column name Data type Description

USER_ID K CHAR(8) User ID
DEPARTMENT_NAME CHAR(8) Department name

Example of table contents

USER DEPARTMENT
ID NAME
-------- ----------
ADAMS Appl Dev
GEYER Finance
GOUNOT Retail
HAAS Finance
JONES Appl Dev
KWAN Marketng
LEE Manufact
LUTZ Manufact
MARINO Retail
MEHTA Manufact
PARKER Finance
PEREZ Retail

Sample component reports

In the report descriptions that follow, this information is included:
Heading
The title of the report.
Introduction
A brief introduction to the purpose of the report.
Report ID
IBM Z Decision Support assigns each report a unique report identifier. Each report ID consists of
SAMPLE and a sequential number, such as SAMPLE01.
Report group
To make it easier to find reports, IBM Z Decision Support organizes reports into report groups, which
correspond to feature components. Sample component reports belong to the Sample report group.
Source
Each Sample report contains information adapted from either the SAMPLE_H or SAMPLE_M source
tables.
Attributes
Attributes are keys that you can use to search for a particular report. The Sample component reports
each have one attribute, Sample.
Variables
Each report has several variables associated with it. When you select a report to display, IBM Z
Decision Support prompts you for the variables listed in the description.
Example report
Each example illustrates a typical report.
Column descriptions
Column descriptions identify the information contained within the report, in detail. If the column
contains a calculated value, the formula used for the calculation is included.

232 IBM Z Decision Support : Administration Guide and Reference

 Reports

Sample Report 1
This surface chart shows the processor time consumed by different projects. It gives an hourly profile for
an average day.
This information identifies the report:
Report ID
SAMPLE01
Report group
Sample Reports
Source
SAMPLE_H
Chart format
DRLGSURF
Attributes
Sample
Variables
System ID

Figure 107. Sample Report 1

The report contains this information:

Horizontal axis
Hour, in the format hh.mm
Vertical axis
Processor time, in seconds
Legend
Department name

Chapter 5. Administration reference 233

Reports

Sample Report 2
This report shows the resources consumed by each user and department.
This information identifies the report:
Report ID
SAMPLE02
Report group
Sample Reports
Source
SAMPLE_M
Attributes
Sample
Variables
From_month, To_month, System_ID

Sample Report 2

Average
Month Department User Trans- response CPU Pages
start date name ID actions seconds seconds printed
---------- ---------- -------- -------- -------- -------- --------
2000-01-01 Appl Dev ADAMS 1109 3.84 244.13 821
JONES 1138 3.40 228.79 1055
SMITH 870 4.27 183.03 864
-------- -------- -------- --------
* 3117 3.84 655.95 2740

Finance GEYER 509 4.29 115.97 529

HAAS 786 3.56 137.48 648
PARKER 462 6.79 171.51 704
SPENCER 800 3.33 172.82 640
-------- -------- -------- --------
* 2557 4.50 597.78 2521
⋮
======== ======== ======== ========
36396 4.03 7868.97 38711

IBM Z Decision Support Report: SAMPLE02

Figure 108. Sample Report 2

The columns in this report contain this information:

Month start date
Date of the first day in the month.
Department name
Name of the department that the user belongs to.
User ID
ID of the user.
Transactions
Number of transactions run by the user.
Average response seconds
The average response time, in seconds for all transactions. Calculated as RESPONSE_SECONDS/
TRANSACTIONS.
CPU seconds
Number of processor seconds consumed.
Pages printed
Number of pages printed.

234 IBM Z Decision Support : Administration Guide and Reference

 Reports

Sample Report 3
This bar chart shows the processor time consumed by each project during the selected time period,
sorted as a toplist.
This information identifies the report:
Report ID
SAMPLE03
Report group
Sample Reports
Source
SAMPLE_M
Chart format
DRLGHORB
Attributes
Sample
Variables
From_date, To_date, System_ID

Figure 109. Sample Report 3

The report contains this information:

Horizontal axis
Processor time, in seconds
Vertical axis
Department name

Record definitions supplied with IBM Z Decision Support

In addition to the records used by the components, the IBM Z Decision Support base product contains
definitions of many records. This chapter lists all the records defined by the base product, except for
those built by IBM Z Decision Support exits and utilities.

Chapter 5. Administration reference 235

SMF records

SMF records
Record name Member name Description
SMF_000 DRLRS000 IPL
SMF_002 DRLRS002 Dump header
SMF_003 DRLRS003 Dump trailer
SMF_004 DRLRS004 Step termination
SMF_005 DRLRS005 Job termination
SMF_006 DRLRS006 JES2/JES3/PSF/External writer
SMF_007 DRLRS007 Data lost
SMF_008 DRLRS008 I/O configuration
SMF_009 DRLRS009 VARY device ONLINE
SMF_010 DRLRS010 Allocation recovery
SMF_011 DRLRS011 VARY device OFFLINE
SMF_014 DRLRS014 INPUT or RDBACK data set activity
SMF_015 DRLRS015 OUTPUT, UPDAT, INOUT, or OUTIN data set activity
SMF_016 DRLRS016 DFSORT statistics
SMF_017 DRLRS017 Scratch data set status
SMF_018 DRLRS018 Rename data set status
SMF_019 DRLRS019 Direct access volume
SMF_020 DRLRS020 Job initiation
SMF_021 DRLRS021 Error statistics by volume
SMF_022 DRLRS022 Configuration
SMF_023 DRLRS023 SMF status
SMF_024 DRLRS024 JES2 spool offload
SMF_025 DRLRS025 JES3 device allocation
SMF_026 DRLRS026 JES2/JES3 job purge
SMF_028 DRLRS028 NPM statistics. SMF_028 maps all subtypes of SMF type 28. To improve
performance, the subtypes used by IBM Z Decision Support are mapped
with special record definitions (SMF_028_xxx). Note that SMF_028 cannot
be used together with these definitions because each log record can be
mapped by only one record definition.
SMF_028_NTRI DRLRSNTR NPM NTRI statistics
SMF_028_TRANSIT DRLRSNTT NPM transit time statistics
SMF_028_TRANS_SUM DRLRSNT1 NPM Transit Time summary statistics
SMF_028_X25 DRLRSX25 NPM X25 statistics
SMF_028_PU DRLRSNPU NPM PU statistics
SMF_028_NPM DRLRSNPM NPM internal statistics
SMF_028_LINE DRLRSNLI NPM line statistics
SMF_028_NEO DRLRSNEO NPM NEO statistics
SMF_028_NCP DRLRSNCP NPM NCP statistics

236 IBM Z Decision Support : Administration Guide and Reference

 SMF records

Record name Member name Description

SMF_028_LAN DRLRSLAN NPM LAN statistics
SMF_028_VTAM DRLRSVTM NPM VTAM statistics
SMF_030 DRLRS030 Common address space work
SMF_031 DRLRS031 TIOC initialization
SMF_032 DRLRS032 TSO user work accounting
SMF_033 DRLRS033 APPC/MVS TP accounting
SMF_034 DRLRS034 TS-step termination
SMF_035 DRLRS035 LOGOFF
SMF_036 DRLRS036 ICF catalog
SMF_037_HW DRLRS037 NetView Hardware Monitor
SMF_037_VPD DRLRSVPD Network configuration (VPD)
SMF_039_1_TO_7 DRLRS039 NetView Session Monitor, SMF 39, subtypes 1 to 7
SMF_039_8 DRLRS039 NetView Session Monitor, SMF 39, subtype 8
SMF_040 DRLRS040 Dynamic DD
SMF_041 DRLRS041 Data-in-virtual Access/Unaccess
SMF_042_1 DRLRS042 BMF performance statistics
SMF_042_2 DRLRS042 DFP cache control unit statistics
SMF_042_3 DRLRS042 DFP SMS configuration statistics
SMF_042_5 DRLRSX42 DFSMS storage class statistics
SMF_042_6 DRLRSX42 DFSMS Data Set statistics
SMF_042_14 DRLRADSM ADSTAR Distributed Storage Manager (ADSM) server statistics
SMF_042_11 DRLRSX42 DFP Extended Remote Copy (XRC) session statistics
SMF_043_2 DRLRS043 JES2 start
SMF_043_5 DRLRS043 JES3 start
SMF_045_2 DRLRS045 JES2 withdrawal
SMF_045_5 DRLRS045 JES3 stop
SMF_047_2 DRLRS047 JES2 SIGNON/start line (BSC only)
SMF_047_5 DRLRS047 JES3 SIGNON/start line/LOGON
SMF_048_2 DRLRS048 JES2 SIGNOFF/stop line (BSC only)
SMF_048_5 DRLRS048 JES3 SIGNOFF/stop line/LOGOFF
SMF_049_2 DRLRS049 JES2 integrity (BSC only)
SMF_049_5 DRLRS049 JES3 integrity
SMF_050 DRLRS050 ACF/VTAM* tuning statistics
SMF_052 DRLRS052 JES2 LOGON/start line (SNA only)
SMF_053 DRLRS053 JES2 LOGOFF/start line (SNA only)
SMF_054 DRLRS054 JES2 integrity (SNA only)
SMF_055 DRLRS055 JES2 network SIGNON
SMF_056 DRLRS056 JES2 network integrity

Chapter 5. Administration reference 237

SMF records

Record name Member name Description

SMF_057_2 DRLRS057 JES2 network SYSOUT transmission
SMF_057_5 DRLRS057 JES3 networking transmission
SMF_058 DRLRS058 JES2 network SIGNOFF
SMF_059 DRLRS059 MVS/BDT file-to-file transmission
SMF_060 DRLRS060 VSAM volume data set updated
SMF_061 DRLRS061 ICF define activity
SMF_062 DRLRS062 VSAM component or cluster opened
SMF_063 DRLRS063 VSAM entry defined
SMF_064 DRLRS064 VSAM component or cluster status
SMF_065 DRLRS065 ICF delete activity
SMF_066 DRLRS066 ICF alter activity
SMF_067 DRLRS067 VSAM entry delete
SMF_068 DRLRS068 VSAM entry renamed
SMF_069 DRLRS069 VSAM data space defined, extended, or deleted
SMF_070 DRLRS070 RMF CPU activity
SMF_071 DRLRS071 RMF paging activity
SMF_072_1 DRLRS072 RMF workload activity
SMF_072_2 DRLRSX72 RMF storage data
SMF_072_3 DRLRS072 RMF goal mode workload activity
SMF_072_4 DRLRSX72 RMF goal mode delay and storage frame data
SMF_073 DRLRS073 RMF channel path activity
SMF_074_1 DRLRS074 RMF device activity
SMF_074_2 DRLRS074 RMF XCF activity
SMF_074_3 DRLRSX74 RMF Device OMVS activity
SMF_074_4 DRLRSX74 RMF XES/CF activity
SMF_074_6 DRLRX74 File system statistics
SMF_075 DRLRS075 RMF page/swap data set activity
SMF_076 DRLRS076 RMF trace activity
SMF_077 DRLRS077 RMF enqueue activity
SMF_078_1 DRLRS078 RMF I/O queueing activity for the 308x, 908x, and 4381 processors
SMF_078_2 DRLRS078 RMF virtual storage activity
SMF_078_3 DRLRS078 RMF I/O queueing activity for the 3090, 9021, 9121, and 9221 processors
SMF_079 DRLRS079 RMF Monitor II activity
SMF_080 DRLRS080 RACF processing
SMF_081 DRLRS081 RACF initialization
SMF_082_1 DRLRS082 PCF record
SMF_082_2 DRLRS082 CUSP record
SMF_083 DRLRS083 RACF audit record for data sets

238 IBM Z Decision Support : Administration Guide and Reference

 SMF records

Record name Member name Description

SMF_084_1 DRLRS084 JMF - FCT analysis
SMF_084_2 DRLRS084 JMF - FCT summary and highlights
SMF_084_3 DRLRS084 JMF - spool data management
SMF_084_4 DRLRS084 JMF - resqueue cellpool, JCT and control block utilization
SMF_084_5 DRLRS084 JMF - job analysis
SMF_084_6 DRLRS084 JMF - JES3 hot spot analysis
SMF_084_7 DRLRS084 JMF - JES internal reader DSP analysis
SMF_084_8 DRLRS084 JMF - JES3 SSI response time analysis
SMF_084_9 DRLRS084 JMF - JES3 SSI destination queue analysis
SMF_085 DRLRS085 OAM record
SMF_088 DRLRS088 System logger
SMF_089 DRLRS089 Product Usage Data
SMF_090 DRLRS090 System status
SMF_092 DRLRS092 z/OS UNIX activity
SMF_094 DRLRS094 3494, 3495 Tape library data server statistics
SMF_099 DRLRS099 SMS System Resource Manager decisions
SMF_100_0 DRLRS100 Db2 statistics, system services
SMF_100_1 DRLRS100 Db2 statistics, database services
SMF_100_2 DRLRS100 Db2 statistics, dynamic ZPARMs
SMF_100_3 DRLRS100 Db2 statistics, Buffer, Manager Group Buffer Pool
SMF_101 DRLRS101 Db2 accounting
SMF_101_1 DRLRS101 Db2 accounting, Packages extension
SMF_102 DRLRS102 Db2 system initialization parameters
SMF_110_0 DRLRS110 CICS/ESA journaling record
SMF_110_0_V2 DRLRS110 CICS/MVS monitoring record
SMF_110_1 DRLRS110 CICS/ESA monitoring record
SMF_110_1_1 DRLRS110 CICS/TS <3.2 record
SMF_110_1_5 DRLR110T CICS transaction resource - expanded
SMF_110_2 DRLR1102 CICS/ESA and CICS/TS statistics record
SMF_110_3 DRLRS1103 CICS/TS statistics record
SMF_110_4 DRLR1103 CICS/TS CF statistics record
SMF_110_5 DRLR1103 CICS/TS NC statistics record
SMF_110_1_C DRLRS110 CICS/TS 3.2+ - may be compressed
SMF_110_1_CO DRLRS110 CICS/TS 3.2+ - expanded
SMF_110_E DRLRS110 CICS/ESA exception record - expanded
SMF_112_203_C DRLRS112 OMEGAMON® XE for CICS file and database usage - compressed
SMF_112_203 DRLRS112 OMEGAMON XE for CICS file and database usage - expanded
SMF_114_1 DRLRS114 System Automation Tracking

Chapter 5. Administration reference 239

SMF records

Record name Member name Description

SMF_115 DRLRS115 WebSphere MQ for z/OS statistics
SMF_116 DRLRS116 WebSphere MQ for z/OS statistics
SMF_117 DRLRS117 Websphere Message Broker
SMF_118_1 DRLRS118 TCP/IP API calls record
SMF_118_3 DRLRS118 TCP/IP FTP client calls record
SMF_118_4 DRLRS118 TCP/IP TELNET client calls record
SMF_118_20 DRLRS118 TCP/IP TELNET server record
SMF_118_5 DRLRS118 TCP/IP general statistics record
SMF_118_70 DRLRS118 TCP/IP FTP server record
SMF_119_1 DRLRS119 TCP connection initiation
SMF_119_2 DRLRS119 TCP connection termination
SMF_119_3 DRLRS119 FTP client transfer completion
SMF_119_4 DRLRS119 TCP/IP Profile Information record
SMF_119_5 DRLRS119 TCP/IP statistics
SMF_119_6 DRLRS119 Interface statistics
SMF_119_7 DRLRS119 Server port statistics
SMF_119_8 DRLRS119 TCP/IP stack start/stop
SMF_119_10 DRLRS119 UDP socket close
SMF_119_20 DRLRS119 TN3270 server SNA session initiation
SMF_119_21 DRLRS119 TN3270 server SNA session termination
SMF_119_22 DRLRS119 TSO telnet client connection initiation
SMF_119_23 DRLRS119 TSO telnet client connection termination
SMF_119_70 DRLRS119 FTP server transfer completion
SMF_119_72 DRLRS119 FTP server logon failure
SMF_119_73 DRLRS119 IPSec IKE Tunnel Activation/Refresh record
SMF_119_74 DRLRS119 IPSec IKE Tunnel Deactivation/Expire record
SMF_119_75_80 DRLRS119 IPSec Dynamic Tunnel Activation/Refresh
SMF_119_75_80 DRLRS119 IPSec Dynamic Tunnel Deactivation record
SMF_119_75_80 DRLRS119 IPSec Dynamic Tunnel Added record
SMF_119_75_80 DRLRS119 IPSec Dynamic Tunnel Removed record
SMF_119_75_80 DRLRS119 IPSec Manual Tunnel Activation record
SMF_119_75_80 DRLRS119 IPSec Manual Tunnel Deactivation record
SMF_120_1 DRLRS121 Server activity record
SMF_120_2 DRLRS122 WebSphere Application Server container activity record
SMF_120_3 DRLRS123 Server interval record
SMF_120_4 DRLRS124 WebSphere Application Server container interval record
SMF_120_5 DRLRSJWA J2EE container activity record
SMF_120_6 DRLRSJWI J2EE container interval record

240 IBM Z Decision Support : Administration Guide and Reference

 DFSMS/RMM records

Record name Member name Description

SMF_120_7 DRLRSJWA Web container activity record
SMF_120_8 DRLRSJWI Web container interval record
SMF_120_9 DRLRS129 Request Activity record
SMF_120_10 DRLRS12A Outbound Request record
SMF_120_11 DRLRSRWL Liberty request record
SMF_120_12 DRLRSJWL Liberty Java batch job record
SMF_123_1 DRLR123 z/OS Connect EE Record
SMF_123_1_V2 DRLR123 z/OS Connect EE Record V2
SMF_123_2_V2 DRLR123 z/OS Connect EE Record ST2 V2
SMF_194 DRLRS194 TS7700 Virtualization Engine statistics record
SMF_IXFP_01 DRLRIXFP IXFP subsystem performance
SMF_IXFP_02 DRLRIXFP IXFP channel interface statistics
SMF_IXFP_03 DRLRIXFP IXFP functional device performance
SMF_IXFP_04 DRLRIXFP IXFP device module performance
SMF_IXFP_05 DRLRIXFP IXFP deleted data space release
SMF_IXFP_06 DRLRIXFP IXFP snapshot event data
SMF_IXFP_07 DRLRIXFP IXFP space utilization record
SMF_IXFP_08 DRLRIXFP IXFP snapshot extended event data record

These records are user-defined; that is, they are not part of the standard IBM records in the range 0-127.
However, they are written by IBM licensed programs.
The default record numbers are provided within parentheses.

Record name Member name Description

SMF_CACHE_03 DRLRS245 Cache RMF Reporter, 3990 model 03 (245)
SMF_CACHE_06 DRLRS245 Cache RMF Reporter, 3990 model 06 (245)
SMF_CACHE_13 DRLRS245 Cache RMF Reporter, 3880 model 13 (245)
SMF_CACHE_23 DRLRS245 Cache RMF Reporter, 3880 model 23 (245)
SMF_FTP DRLRSFTP NetView File Transfer Program (FTP) log record (252)

DFSMS/RMM records
Record name Member name Description
DFRMM_VOLUME DRLRRMMV Extract file volume record
DFRMM_RACK DRLRRMMR Extract file rack number record
DFRMM_SLBIN DRLRRMMS Extract file storage location bin record
DFRMM_PRODUCT DRLRRMMP Extract file product record
DFRMM_VRS DRLRRMMK Extract file VRS record
DFRMM_OWNER DRLRRMMO Extract file owner record
DFRMM_DATASET DRLRRMMD Extract file data set record

Chapter 5. Administration reference 241

IMS SLDS records

IMS SLDS records

These records come from the IMS recovery log.
No reliable release indicators exist in the IMS records, so one log definition exists for each IMS release
supported. The log and record names contain Vnn where nn is the IMS version and release; B1 for IMS
V11, C1 for IMS V12, D1 for IMS V13, E1 for IMS V14, F1 for IMS V15.
The records are described in IMS mapping macros.

Record name Member name Description

IMS_Vnn0_01 DRLRInnS Message Queue record (message received from a CNT)
IMS_Vnn0_02 DRLRInnS IMS command record
IMS_Vnn0_03 DRLRInnS Message Queue record (message received from an SMB or IMS)
IMS_Vnn0_06 DRLRInnS IMS event accounting record
IMS_Vnn0_07 DRLRInnS Program termination accounting record
IMS_Vnn0_08 DRLRInnS Program schedule record
IMS_Vnn0_10 DRLRInnS Security violation record
IMS_Vnn0_11 DRLRInnS Start of conversation record
IMS_Vnn0_12 DRLRInnS End of conversation record
IMS_Vnn0_13 DRLRInnS SPA insert record
IMS_Vnn0_16 DRLRInnS Sign on/off record
IMS_Vnn0_18 DRLRInnS Extended checkpoint record
IMS_Vnn0_20 DRLRInnS Database open record
IMS_Vnn0_21 DRLRInnS Database close record
IMS_Vnn0_24 DRLRInnS Database error record
IMS_Vnn0_30 DRLRInnS Message queue prefix changed record
IMS_Vnn0_31 DRLRInnS Message queue GU record
IMS_Vnn0_32 DRLRInnS Message queue reject record
IMS_Vnn0_33 DRLRInnS Message queue DRRN free record
IMS_Vnn0_34 DRLRInnS Message queue cancel record
IMS_Vnn0_35 DRLRInnS Message queue enqueue record
IMS_Vnn0_36 DRLRInnS Message queue dequeue record
IMS_Vnn0_37 DRLRInnS Message queue syncpoint transfer record
IMS_Vnn0_38 DRLRInnS Message queue syncpoint fail record
IMS_Vnn0_4C DRLRInnS Program/Database start/stop record
IMS_Vnn0_400D DRLRInnS Checkpoint CCB record
IMS_Vnn0_400E DRLRInnS Checkpoint SPA record
IMS_Vnn0_4001 DRLRInnS Checkpoint begin
IMS_Vnn0_4002 DRLRInnS Checkpoint message queue record
IMS_Vnn0_4003 DRLRInnS Checkpoint CNT record
IMS_Vnn0_4004 DRLRInnS Checkpoint SMB record
IMS_Vnn0_4005 DRLRInnS Checkpoint CTB record

242 IBM Z Decision Support : Administration Guide and Reference

 IMS SLDS records

Record name Member name Description

IMS_Vnn0_4006 DRLRInnS Checkpoint DMB record
IMS_Vnn0_4007 DRLRInnS Checkpoint PSB record
IMS_Vnn0_4008 DRLRInnS Checkpoint CLB record
IMS_Vnn0_4014 DRLRInnS Checkpoint SPA QB record
IMS_Vnn0_4015 DRLRInnS Checkpoint EQE record
IMS_Vnn0_4020 DRLRInnS Checkpoint CIB record
IMS_Vnn0_4021 DRLRInnS Checkpoint VTCB record
IMS_Vnn0_4070 DRLRInnS Checkpoint MSDB begin
IMS_Vnn0_4071 DRLRInnS Checkpoint MSDB ECNT record
IMS_Vnn0_4072 DRLRInnS Checkpoint MSDB header
IMS_Vnn0_4073 DRLRInnS Checkpoint MSDB pagefixed
IMS_Vnn0_4074 DRLRInnS Checkpoint MSDB pageable
IMS_Vnn0_4079 DRLRInnS Checkpoint MSDB end
IMS_Vnn0_4080 DRLRInnS Checkpoint Fast Path begin
IMS_Vnn0_4081 DRLRInnS Checkpoint Fast Path ECNT record
IMS_Vnn0_4082 DRLRInnS Checkpoint Fast Path EMHB record
IMS_Vnn0_4083 DRLRInnS Checkpoint Fast Path RCTE record
IMS_Vnn0_4084 DRLRInnS Checkpoint Fast Path DMCB/DMAC record
IMS_Vnn0_4085 DRLRInnS Checkpoint Fast Path MTO buffer record
IMS_Vnn0_4086 DRLRInnS Checkpoint Fast Path DMHR/DEDB buffer record
IMS_Vnn0_4087 DRLRInnS Checkpoint Fast Path ADSC record
IMS_Vnn0_4088 DRLRInnS Checkpoint Fast Path IEEQE record
IMS_Vnn0_4089 DRLRInnS Checkpoint Fast Path end
IMS_Vnn0_4098 DRLRInnS Checkpoint end blocks record
IMS_Vnn0_4099 DRLRInnS Checkpoint end queues record
IMS_Vnn0_41 DRLRInnS Checkpoint batch record
IMS_Vnn0_42 DRLRInnS Log buffer control record
IMS_Vnn0_43 DRLRInnS Log data set control record
IMS_Vnn0_45FF DRLRInnS End of statistics
IMS_Vnn0_450A DRLRInnS Statistics latch record
IMS_Vnn0_450B DRLRInnS Statistics dispatch storage record
IMS_Vnn0_450C DRLRInnS Statistics DFSCBT00 storage record
IMS_Vnn0_450D DRLRInnS Statistics RecAny pool record
IMS_Vnn0_450E DRLRInnS Statistics fixed pools storage record
IMS_Vnn0_450F DRLRInnS Dispatcher statistics record
IMS_Vnn0_4502 DRLRInnS Statistics queue pool record
IMS_Vnn0_4503 DRLRInnS Statistics format buffer pool record
IMS_Vnn0_4504 DRLRInnS Statistics database buffer pool

Chapter 5. Administration reference 243

DCOLLECT records

Record name Member name Description

IMS_Vnn0_4505 DRLRInnS Statistics main pools record
IMS_Vnn0_4506 DRLRInnS Statistics scheduling stats record
IMS_Vnn0_4507 DRLRInnS Statistics logger record
IMS_Vnn0_4508 DRLRInnS Statistics VSAM subpool record
IMS_Vnn0_4509 DRLRInnS Statistics program isolation record
IMS_Vnn0_47 DRLRInnS Statistics active region record
IMS_Vnn0_48 DRLRInnS OLDS padding record
IMS_Vnn0_5050 DRLRInnS Full function database update undo/redo successful record
IMS_Vnn0_5051 DRLRInnS Full function database update unsuccessful record
IMS_Vnn0_5052 DRLRInnS Full function database update undo KSDS insert record
IMS_Vnn0_5501FE00 DRLRInnS External sub-system Db2 snap in doubt record
IMS_Vnn0_56 DRLRInnS External sub-system record
IMS_Vnn0_5901 DRLRInnS EMH input record
IMS_Vnn0_5903 DRLRInnS EMH output record
IMS_Vnn0_5920 DRLRInnS Fast path MSDB change record
IMS_Vnn0_5921 DRLRInnS Fast path DEDB area data set open record
IMS_Vnn0_5922 DRLRInnS Fast path DEDB area data set close record
IMS_Vnn0_5923 DRLRInnS Fast path DEDB area data set status record
IMS_Vnn0_5924 DRLRInnS Fast path DEDB area data set EQE creation record
IMS_Vnn0_5936 DRLRInnS EMH dequeue record
IMS_Vnn0_5937 DRLRInnS EMH FP syncpoint record
IMS_Vnn0_5938 DRLRInnS EMH FP syncpoint failure record
IMS_Vnn0_5950 DRLRInnS Fast Path database update record
IMS_Vnn0_5953 DRLRInnS Fast Path database update (utilities) record
IMS_Vnn0_5954 DRLRInnS Fast Path database DEDB open record
IMS_Vnn0_5955 DRLRInnS Fast Path sequential dependent syncpoint record
IMS_Vnn0_5957 DRLRInnS Fast Path database DMAC record
IMS_Vnn0_5970 DRLRInnS Fast Path hot standby MSDB relocation record
IMS_Vnn0_67 DRLRInnS Communications trace, DMHR on I/O error and snap trace records
IMS_Vnn0_67FA DRLRInnS Trace table log record
IMS_Vnn0_7201 DRLRInnS ETO user create record
IMS_Vnn0_7202 DRLRInnS ETO user delete record
IMS_Vnn0_7203 DRLRInnS ETO user modify record
IMS_Vnn0_7204 DRLRInnS ETO lterm addition record

DCOLLECT records
These records are produced by the DFP DCOLLECT utility.
For a description of these records, refer to z/OS DFSMS: Access Method Services for Catalog.

244 IBM Z Decision Support : Administration Guide and Reference

 EREP records

Record name Member name Description

DCOLLECT_A DRLRDCOA VSAM base cluster association name
DCOLLECT_AG DRLRDCAG Aggregate Group information
DCOLLECT_B DRLRDCOB Data set backup version information
DCOLLECT_BC DRLRDCBC Base Configuration information
DCOLLECT_C DRLRDCOC DASD capacity planning information
DCOLLECT_D DRLRDCOD Active data set information
DCOLLECT_DC DRLRDCDC. Data Class construct information
DCOLLECT_DR DRLRDCDR. Optical Drive information
DCOLLECT_LB DRLRDCLB. Optical Library information
DCOLLECT_M DRLRDCOM Migration data set information
DCOLLECT_MC DRLRDCMC Management Class construct information
DCOLLECT_SC DRLRDCSC Storage Class construct information
DCOLLECT_SG DRLRDCSG Storage Group construct information
DCOLLECT_T DRLRDCOT Tape capacity planning information
DCOLLECT_V DRLRDCOV Volume information
DCOLLECT_VL DRLRDCVL. SMS Volume information

EREP records
For a description of these records, refer to the Environmental Record Editing and Printing Program (EREP)
User's Guide and Reference.

Record name Member name Description

EREP_30 DRLRE030 DASD long outboard record
EREP_36 DRLER036 VTAM long outboard record
EREP_50 DRLER050 IPL system initialization record

Linux on zSeries records

These records are produced by the zLinux programs on your zLinux nodes.

Record name Member name Description

ZLINUX_CPU DRLRZPCP zLinux CPU performance record
ZLINUX_DISK_FS DRLRZPDI zLinux disk space performance record
ZLINUX_DISKIO DRLRZPIO zLinux disk I/O performance record
ZLINUX_PAGING DRLRZPPA zLinux paging space performance record
ZLINUX_HARDCONF DRLRZCNF zLinux hardware configuration record
ZLINUX_SOFTCONF DRLRZCNF zLinux software configuration record
ZLINUX_USR_CMD DRLRZACO zLinux process/command accounting record
ZLINUX_WTMP_INFO DRLRZMTP zLinux connect accounting record
ZLINUX_REC_PI DRLRLNX1 PI log record reformatted to fixed layout
ZLINUX_REC_DF DRLRLNX1 DF log record reformatted to fixed layout

Chapter 5. Administration reference 245

RACF records

Record name Member name Description

ZLINUX_REC_WW DRLRLNX1 WW log record reformatted to fixed layout
ZLINUX_REC_TO DRLRLNX1 TO log record reformatted to fixed layout

RACF records
These records come from the RACF Database Unload utility output that contains RACF configuration data.
For a description of these records, refer to RACF Macros and Interfaces.

Record name Member name Description

RACF_100 DRLRR100 Group basic data
RACF_200 DRLRR200 User basic data
RACF_205 DRLRR205 User connect data
RACF_400 DRLRR400 Data set basic data
RACF_402 DRLRR402 Data set conditional access
RACF_404 DRLRR404 Data set access
RACF_500 DRLRR500 General resource basic data
RACF_505 DRLRR505 General resource access
RACF_507 DRLRR507 General resource conditional access

IBM Z Workload Scheduler

These records come from the OPC track log.
For a description of these records, refer to the IBM Z Workload Scheduler: Diagnosis Guide and Reference.

Record name Member name Description

OPC_03_P DRLROP03 OPC current plan operation
OPC_03_C DRLROP03 OPC current plan occurrence
OPC_03_3 DRLROP03 OPC current plan system automation
OPC_04 DRLROP04 OPC current plan job name table
OPC_23 DRLROP23 OPC operation event
OPC_24 DRLROP24 OPC MCP event
OPC_27 DRLROP27 OPC missed feedback
OPC_29 DRLROP29 OPC auto tracked event

VM accounting records
For a description of these records, refer to z/VM: CP Planning and Administration.

Record name Member name Description

VMACCT_01 DRLRVA01 Virtual machine resource use
VMACCT_02 DRLRVA02 Dedicated devices
VMACCT_03 DRLRVA03 Temporary disk space
VMACCT_04 DRLRVA04 LOGON or AUTOLOG with invalid password
VMACCT_05 DRLRVA05 Successful LINK to protected minidisk

246 IBM Z Decision Support : Administration Guide and Reference

 VMPRF records

Record name Member name Description

VMACCT_06 DRLRVA06 LINK with invalid password
VMACCT_07 DRLRVA07 Log off from VSCS-controlled device
VMACCT_08 DRLRVA08 Disconnect or log off

VMPRF records
For a description of these records, refer to the VMPRF User's Guide and Reference.

Record name Member name Description

VMPRF_01 DRLRVM01 VMPRF system data
VMPRF_02 DRLRVM02 VMPRF processor data
VMPRF_11 DRLRVM11 VMPRF configuration data
VMPRF_41 DRLRVM41 VMPRF user data
VMPRF_61 DRLRVM61 VMPRF DASD data

z/VM Performance Toolkit records

For a description of these records, refer to the z/VM Performance Toolkit manual.

Record name Member name Description

VMPERFT_00 DRLRPT00 System configuration data
VMPERFT_01 DRLRPT01 General system load data
VMPERFT_02 DRLRPT02 Processor load data
VMPERFT_03 DRLRPT03 Logical processor load data (LPAR only)
VMPERFT_04 DRLRPT04 Minidisk cache data
VMPERFT_05 DRLRPT05 CP services activity data
VMPERFT_06 DRLRPT06 Channel busy (HF sampling)
VMPERFT_07 DRLRPT07 Channel measurement facility data
VMPERFT_08 DRLRPT08 Extended channel measurement facility data
VMPERFT_3A DRLRPT3A Overall user transaction data
VMPERFT_3C DRLRPT3C Shared segment data
VMPERFT_3E DRLRPT3E Shared data spaces
VMPERFT_41 DRLRPT41 User resource usage and wait states
VMPERFT_42 DRLRPT42 User class resource usage and wait states (same layout as FC41)
VMPERFT_43 DRLRPT43 System totals for user resource usage and wait states (same layout as FC41)
VMPERFT_44 DRLRPT44 User transactions and response time
VMPERFT_45 DRLRPT45 User class transactions and response time data (same layout as FC44)
VMPERFT_46 DRLRPT46 System totals for user transactions and response time data
VMPERFT_51 DRLRPT51 I/O processor activity data
VMPERFT_55 DRLRPT55 Virtual switch records
VMPERFT_61 DRLRPT61 General DASD data
VMPERFT_65 DRLRPT65 DASD cache data

Chapter 5. Administration reference 247

IBM Z Decision Support dialog options

Record name Member name Description

VMPERFT_68 DRLRPT68 DASD CP owned (system areas)
VMPERFT_6F DRLRPT6F SCSI device records
VMPERFT_6D DRLRPT6D Queued Direct Input Output (QDIO) support
VMPERFT_71 DRLRPT71 DASD SEEKS data
VMPERFT_A2 DRLRPTA2 SFS and BFS server data
VMPERFT_A4 DRLRPTA4 Multitasking users data
VMPERFT_A6 DRLRPTA6 TCP/IP server data
VMPERFT_A7 DRLRPTA7 TCP/IP links data
VMPERFT_A8 DRLRPTA8 Reusable server kernel summary data
VMPERFT_A9 DRLRPTA9 Linux application data

Administration dialog options and commands

This chapter describes actions you can access from primary windows in the IBM Z Decision Support
administration dialog. These actions include dialog window pull-downs and commands you issue from the
command line. These sections describe the actions:
• “IBM Z Decision Support dialog options” on page 248
• “IBM Z Decision Support commands” on page 254

IBM Z Decision Support dialog options

This section describes the menu bar options for the IBM Z Decision Support windows. Under each menu
bar option, there is a list of pull-down options available, with references to where the pull-down options
are described.

Administration window

Options Other Utilities Help

------------------------------------------------------------------------------
IBM Z Decision Support Administration
Option ===> __________________________________________________________________

1 System Perform IZDS system tasks System ID . . : AUS1

2 Components Install IZDS components Db2 Subsystem : DEC1
3 Logs Show installed IZDS log objects IZDS plan name : DRLPLAN
4 Tables Show installed IZDS data tables System tables : DRLSYSYY
5 Reports Run IZDS reports Data tables . : DRLYY

F1=Help F2=Split F3=Exit F9=Swap F10=Actions F12=Cancel

The menu bar options of the Administration window are:

Options

_ 1. Dialog parameters...
2. Reporting dialog defaults...
3. Exit

Dialog parameters
See “Dialog parameters - variables and fields” on page 63.

248 IBM Z Decision Support : Administration Guide and Reference

 IBM Z Decision Support dialog options

Reporting dialog defaults

Refer to the Guide to Reporting for more information.
Exit
Returns to the previous window.
Other

_ 1. QMF
2. DB2I
3. ISPF/PDF
4. Process IZDS statements...
5. Messages...

QMF
Refer to the Guide to Reporting for more information. If your installation does not use QMF, this
item is not selectable.
DB2I
See “Using available tools to work with the IBM Z Decision Support database” on page 110.
ISPF/PDF
Displays the ISPF/PDF primary menu.
Process IZDS statements
See “Working with fields in a record definition” on page 147.
Messages
Refer to the Guide to Reporting for more information.
Utilities

_ 1. Network
2. Workstation interface
3. Generate problem records...
4. System Diagnostics
5. TPM Extract
6. Search installed objects

Network
Refer to the Network Performance Feature Installation and Administration manual .
Generate problem records
See “Administering problem records” on page 117.
System Diagnostics
Refer to the topic "System Diagnostics" in the Messages and Problem Determination manual.
TPM Extract
Extracts usage data from IBM Z Decision Support data tables which can be imported into Tivoli
Performance Modeller.
Search installed objects
Utility for searching installed component objects such as table columns, table comments, records,
updates, and reports.
Help

_ 1. Using help
2. General help
3. Keys help
4. Product information

Using help
Refer to the Guide to Reporting for more information.

Chapter 5. Administration reference 249

IBM Z Decision Support dialog options

General help
Refer to the Guide to Reporting for more information.
Keys help
Refer to the Guide to Reporting for more information.
Online books
Refer to the Guide to Reporting for more information.
Search information
Refer to the Guide to Reporting for more information.
Product information
Displays IBM Z Decision Support copyright and release information.

Components window

Component Space Other Help

-------------------------------------------------------------------------
Components Row 1 to 32 of 92
Command ===> ____________________________________________________________

Select one or more components. Then press Enter to Open component.

/ Components Status Date

_ z/OS Performance Management (MVSPM) Installed 2019-08-29

The menu bar options of the Components window are:

Component
New
See “Creating a component” on page 133.
Open component
See “Viewing objects in a component” on page 130.
Install
See “Installing a component” on page 120.
Uninstall
See “Uninstalling a component” on page 127.
Delete
See “Deleting a component” on page 133.
Print list
See “Printing a list of IBM Z Decision Support tables” on page 180 for a description of a similar
action, printing a list of tables.
Show user objects
See “Controlling objects that you have modified” on page 129.
Show excluded
See “Controlling objects that you have modified” on page 129.
Exit
Saves changes and returns to the previous window.
Space
Table spaces
See “Installing a component” on page 120.
Indexes
See “Installing a component” on page 120.

250 IBM Z Decision Support : Administration Guide and Reference

 IBM Z Decision Support dialog options

Other
QMF
Refer to the Guide to Reporting for more information. If your installation does not use QMF, this
item is not selectable.
DB2I
See “Using available tools to work with the IBM Z Decision Support database” on page 110.
ISPF/PDF
Displays the ISPF/PDF primary menu.
Process IBM Z Decision Support statements
See “Working with fields in a record definition” on page 147.
Messages
Refer to the Guide to Reporting for more information.
Help
As for Help on the Administration window (see “Help” on page 249).

Logs window

Log Utilities View Other Help

--------------------------------------------------------------------------
Logs Row 1 to 3 of 3
Command ===> ____________________________________________________________

Select a log. Then press Enter to display record definitions.

/ Logs Description
_ DCOLLECT DFSMS DCOLLECT log

The menu bar options of the Logs window are:

Log
New
See “Creating a log definition” on page 144.
Open log definition
See “Viewing and modifying a log definition” on page 142.
Open record definitions
See “Viewing and modifying a record definition” on page 146.
Open collected log data sets
See “Viewing a list of log data sets collected” on page 135.
Open Log Data Manager
See “Working with the log data manager option” on page 186.
Delete
See “Deleting a log definition” on page 145.
Save definition
See “Saving a table definition in a data set” on page 181 for a description of a similar action,
saving definitions for tables.
Print list
See “Printing a list of IBM Z Decision Support tables” on page 180 for a description of a similar
action, printing a list of tables.
Exit
Saves changes and returns to the previous window.
Utlities
Collect
See “Collecting data from a log into Db2 tables” on page 137.

Chapter 5. Administration reference 251

IBM Z Decision Support dialog options

Display log
See “Displaying the contents of a log” on page 139.
Show log statistics
See “Displaying log statistics” on page 138.
View
All
Lists all logs in the Logs window.
Some
Restricts the list of logs displayed in the Logs window when you specify selection criteria.
Other
QMF
Refer to the Guide to Reporting for more information. If your installation does not use QMF, this
item is not selectable.
DB2I
See “Using available tools to work with the IBM Z Decision Support database” on page 110.
ISPF/PDF
Displays the ISPF/PDF primary menu.
Process IBM Z Decision Support statements
See “Working with fields in a record definition” on page 147.
Messages
Refer to the Guide to Reporting for more information.
Help
As for Help on the Administration window (see “Help” on page 249).

Tables window

Table Maintenance Utilities Edit View Other Help

--------------------------------------------------------------------------
Tables Row 1 to 33 of 161
Command ===> ____________________________________________________________

/ Tables Prefix Type

_ AGGR_VALUE DRLSYSYY TABLE
_ GENERATE_KEYS DRLSYSYY TABLE
_ GENERATE_PROFILES DRLSYSYY TABLE
_ KPMZ_CPUMF_PT_T DRLYY TABLE

The menu bar options of the Tables window are:

Table
New
See “Creating a table” on page 181.
Open table definition
See “Opening a table to display columns” on page 165.
Open updates
See “Displaying and modifying update definitions of a table” on page 169.
Open purge conditions
See “Displaying and editing the purge condition of a table” on page 174.
Open table space
See “Displaying and modifying a table or index space” on page 176.
Delete
See “Deleting a table or view” on page 182.
Save definition
See “Saving a table definition in a data set” on page 181.

252 IBM Z Decision Support : Administration Guide and Reference

 IBM Z Decision Support dialog options

Print list
See “Printing a list of IBM Z Decision Support tables” on page 180.
Exit
Saves changes and returns to the previous window.
Maintenance
Table space
See “Displaying and modifying a table or index space” on page 176.
Index and index space
See “Displaying and modifying a table or index space” on page 176.
Utilities
Display
See “Displaying the contents of a table” on page 154.
Show size
See “Showing the size of a table” on page 156.
Import
See “Importing the contents of an IXF file to a table” on page 159. If your installation does not use
QMF, this item is not selectable.
Export
See “Exporting table data to an IXF file” on page 159. If your installation does not use QMF, this
item is not selectable.
Grant
See “Administering user access to tables” on page 185.
Revoke
See “Administering user access to tables” on page 185.
Recalculate
See “Recalculating the contents of a table” on page 157.
Purge
See “Purging a table” on page 160.
Unload
See “Unloading and loading tables” on page 160.
Load
See “Unloading and loading tables” on page 160.
Edit
Add rows
See “Editing the contents of a table” on page 155. If your installation does not use QMF, this item
is not selectable.
Change rows
See “Editing the contents of a table” on page 155. If your installation does not use QMF, this item
is not selectable.
ISPF editor
See “Editing the contents of a table” on page 155.
View
All
See “Listing a subset of tables in the Tables window” on page 181.
Some
See “Listing a subset of tables in the Tables window” on page 181.

Chapter 5. Administration reference 253

Administration dialog commands

Other
QMF
Refer to the Guide to Reporting for more information. If your installation does not use QMF, this
item is not selectable.
DB2I
See “Using available tools to work with the IBM Z Decision Support database” on page 110.
ISPF/PDF
Displays the ISPF/PDF primary menu.
Process IBM Z Decision Support statements
See “Working with fields in a record definition” on page 147.
Messages
Refer to the Guide to Reporting for more information.
Help
As for Help on the Administration window (see “Help” on page 249).

IBM Z Decision Support commands

You can immediately execute an action anywhere in an IBM Z Decision Support dialog by typing these
commands on the command line (uppercase letters show the abbreviation for the command):
COMPonen (see Note)
Displays the Components window.
DB2I
Starts a DATABASE 2 Interactive (DB2I) facility session and displays its primary menu.
DISPLay RECORD record_type (see Note)
Lets you identify a log data set in the Record Selection window from which IBM Z Decision Support
displays records of the specified type in the Record Data window.
DISPLay report_ID
Displays the specified report from the Reports window.
DISPLay REPort report_ID
Displays the specified report. By default, report IDs are listed in the IBM Z Decision Support Report
window next to their corresponding report descriptions. You can toggle the display to show either the
report IDs or the report types and owners by pressing F11.
If you do not use a prefix for the report ID (prefix.report_ID), IBM Z Decision Support assumes the
report is public. Otherwise, the prefix must be the owner of the private report.
DISPLAY TABLE table_name (see Note)
Displays the specified table.
IBM Z Decision Support assumes a prefix that is the value of the Other table prefix field from the
Dialog Parameters window:

DISPL TAB DRLSYS.DRLTABLES

DISPL TAB MVS_SYSTEM_H or DISPL TAB DRL.MVS_SYSTEM_H

DISPLay table_name (see Note)

Displays the specified table from the Tables window.
DRLESTRA
Displays the Set/Reset Trace Options window.
HELP
Displays general help or, if a message appears, help for the message.
ISPF
Displays the ISPF primary menu.

254 IBM Z Decision Support : Administration Guide and Reference

 Administration dialog commands

LOcate argument
In an IBM Z Decision Support window, locates the first row that starts with argument in the column
that was last sorted.
LOGS (see Note)
Displays the Logs window.
PDF
Displays the ISPF primary menu.
QMF
If your installation uses QMF, this command starts QMF and displays either its SQL primary window or
its prompted query primary menu.
REPORTs
Starts the reporting dialog.
SOrt column_name|position ASC|DES
Sorts an IBM Z Decision Support list by the column you specify as column_name in either ascending
or descending order. (You can also sort by column number by specifying the number of the column
instead of the name. The first column after the selection field column on the left is column 1.)
SYStem (see Note)
Displays the System window.
TABle (see Note)
Displays the Tables window.
Note: This command is not available in end-user mode from the reporting dialog.

Administration reports
This chapter describes the administration reports that are created when you create or update the IBM Z
Decision Support system tables. The reports listed in this chapter are the following:

3270 Reports
• “PRA001 - Indexspace Cross-Reference” on page 256
• “PRA002 - Actual Tablespace Space Allocation” on page 257
• “PRA003 - Table Purge Condition” on page 258
• “PRA004 - Table Structure with Comments” on page 259
• “PRA005 - Table Names with Comments” on page 260
• “PRA006 - Object Change Level” on page 261
• “PRA007 - Collected Log Data Sets” on page 262
• “PRA008 - Components and Subcomponents” on page 263
• “PRA009 - Tablespace Allocation” on page 264
• “PRA010 - Update Definitions” on page 265
• “PRA011 - Update Details” on page 266
• “PRA012 - Table Name to Tablespace Cross-Reference ” on page 267
• “PRA013 - Tablespace to Table Name Cross-Reference ” on page 268
• “PRA014 - System Tables” on page 269
• “PRA015 - Non-System Tables Installed” on page 270

Cognos Reports
• “PRA001 - Indexspace Cross-Reference” on page 271
• “PRA002 - Actual Tablespace Space Allocation” on page 272

Chapter 5. Administration reference 255

PRA001 - Indexspace Cross-Reference

• “PRA003 - Table Purge Condition” on page 273

• “PRA004 - Table Structure with Comments” on page 274
• “PRA005 - Table Names with Comments” on page 275
• “PRA006 - Object Change Level” on page 276
• “PRA007 - Collected Log Data Sets” on page 278
• “PRA008 - Components and Subcomponents” on page 279
• “PRA009 - Tablespace Allocation” on page 280
• “PRA010 - Update Definitions” on page 281
• “PRA011 - Update Details” on page 283
• “PRA012 - Table Name to Tablespace Cross-Reference ” on page 284
• “PRA013 - Tablespace to Table Name Cross-Reference ” on page 285
• “PRA014 - System Tables” on page 287
• “PRA015 - Non-System Tables Installed” on page 288

3270 reports
PRA001 - Indexspace Cross-Reference
The PRA001 report provides a cross-reference between index spaces and indexes that are present in the
IBM Z Decision Support environment at the time of running the report. This report enables you to extract
the real name of an index, so that you can locate the index in the administration dialog and adjust its
space allocation if required
This report enables you to extract the real name of an index, so that you can locate the index in the
administration dialog and adjust its space allocation if required.
This information identifies the report:
Report ID
PRA001
Report group
ADMIN
Reports Source
DRLINDEXES

256 IBM Z Decision Support : Administration Guide and Reference

 PRA002 - Actual Tablespace Allocation

Figure 110. Indexspace Cross-Reference report

The report contains the following information:

Indexspace
The name of the index space whose index name has been extracted. This is either the name
associated with a single index space or the complete cross reference between index and index space
names for all indexes.
Index Name
The name of the index associated with the indexspace.
For information about:
• The DRLINDEXES system table, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.
• How to display or modify tables or index spaces, see “Displaying and modifying a table or index
space” on page 176.

PRA002 - Actual Tablespace Space Allocation

The PRA002 report shows the actual space allocated to tables. Use the information in this report,
together with the information in PRA003, to estimate future space requirements.
This information identifies the report:
Report ID
PRA002
Report group
ADMIN
Reports Source
DRLTABLESPACE

Chapter 5. Administration reference 257

PRA003 - Table Purge Condition

Figure 111. Actual Tablespace Space Allocation report

The report contains the following information:

Tablespace Name
The name of the table space whose space allocation has been extracted.
Space Allocated
The SPACE value as reported in the Db2 catalog (SYSIBM.SYSTABLESPACES table). The column
SPACE contains data only if the STOSPACE utility has been run.
For information about:
• The DRLTABLESPACE system table, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.
• How to display or modify tables or index spaces, see “Displaying and modifying a table or index space”
on page 176.
• The SYSTABLESPACE table, refer to the Db2 for z/OS: SQL Reference.

PRA003 - Table Purge Condition

This report shows a printable list of current purge conditions. It enables you to review purge criteria and
decide which adjustments to make without the need to use the online dialog.
This information identifies the report:
Report ID
PRA003
Report group
ADMIN
Reports Source
DRLPURGECOND
Variables
TABLE_NAME. Optional. You can select the purge condition associated with a single table, or accept
the default setting to obtain a complete list of current purge conditions.

258 IBM Z Decision Support : Administration Guide and Reference

 PRA004 - Table Structure with Comments

BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN

Figure 112. Table Purge Condition report

The report contains the following information:

Table Prefix
The prefix of the table.
Table Name
The name of the table to which the purge condition applies.
Latest Change
The latest change level recorded in the SDRLDEFS.
PURGE CONDITION
The purge condition that applies to the table.
Date Installed
The date the purge condition was installed.
Creator
The ID of the person who installed the purge condition.
For information about:
• The DRLPURGCOND system table, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.
• How to display or edit purge conditions, see “Displaying and editing the purge condition of a table” on
page 174.

PRA004 - Table Structure with Comments

This report shows the column remarks for the selected table.
This information identifies the report:
Report ID
PRA004
Report group
ADMIN
Reports Source
DRLCOLUMNS
Variables
TABLE NAME.

Chapter 5. Administration reference 259

PRA005 - Table Names with Comments

Figure 113. Table Structure with Comments report

The report contains the following information:

Keyseq
The column's numeric position within the table's primary key. 0 if it is not part of a primary key.
Table Name
The table name.
ColNo
Column number withing the table.
Keyseq
The column's numeric position within the table's primary key.
Column Name
Table column name.
Nulls
Y - the column may contain NULLS.
Length
Column length.
Comments
Column comment (if defined for the table column). It is 255 char long.

PRA005 - Table Names with Comments

This report lists all the tables with comments.
This information identifies the report:
Report ID
PRA005
Report group
ADMIN
Reports Source
DRLCOLUMNS

260 IBM Z Decision Support : Administration Guide and Reference

 PRA006 - Object Change Level

Figure 114. Table Names with Comments report

The report contains the following information:

Table Name
Table column name.
Comments
Table comment. It is 255 characters long.

PRA006 - Object Change Level

The PRA006 report displays a list of all the items as well as their current change level.
This information identifies the report.
Report ID
PRA006
Report group
ADMIN
Reports Source
DRLCOMP_OBJECTS, DRLRECORDS, DRLRECORDPROCS, DRLLOGS, DRLUPDATES, DRLREPOSTS
Variables
COMPONENT. Optional. Type a component name if you want the user-modified objects for a single
component. If you do not specify any value, the complete list of user modified objects is displayed for
all component.

Chapter 5. Administration reference 261

PRA007 - Collected Log Data Sets

Figure 115. Object Change Level report

The report contains the following information:

Component
Name of the component which the objects belong to.
Object Type
Type of object (Record, Update, Log…).
Object Name
Name of the object.
Member Name
Name of the member in the IZDS libraries where the object definition is stored.
Subcomponent
Subcomponent name, if any.
Latest Change
The latest change level of the object. You modify this field when you change any objects. It indicates
whether an object has been modified.
For information about:
• The DRLCOMP_OBJECTS, DRLRECORDS, DRLRECORDPROCS, DRLLOGS, DRLUPDATES, DRLREPOSTS
system tables, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.

PRA007 - Collected Log Data Sets

The PRA007 report provides the list of all the data sets that have been collected.
This information identifies the report.
Report ID
PRA007
Report group
ADMIN
Reports Source
DRLLOGDATASETS

262 IBM Z Decision Support : Administration Guide and Reference

 PRA008 - Components and Subcomponents

Figure 116. Collected Log Data Sets report

The report contains the following information:

Log Name
Name of the log type.
Data Set Name
The name of the data set collected.
Complete
Y if the log was completely collected.
Number of Collects
The number of times this data set has been collected.
Time Collected
Date and time of the last collect of this data set.
First Timestamp
First timestamp located on the log data set.
Last Timestamp
Last timestamp located on the log data set.
User ID
The ID of the person who collected the log data sets.

PRA008 - Components and Subcomponents

The PRA008 report provides a list of all the components and subcomponents available. The report gives a
status of INSTALLED for each component or subcomponent that is installed and the date it was installed.
This information identifies the report.
Report ID
PRA008
Report group
ADMIN
Reports Source
DRLCOMPONENTS, DRLCOMP_PARTS
Variables
Component Name and Status are optional.

Chapter 5. Administration reference 263

PRA009 - Table space Allocation

Figure 117. Components and Subcomponents report

The report contains the following information:

Component
Name of the component.
Component Status
The status of the component (INSTALLED or NOT INSTALLED).
Subcomponent
Name of the subcomponent.
Subcomponent Status
The status of the subcomponent (INSTALLED or NOT INSTALLED).
Date Installed
The date the component and/or subcomponent was installed.

PRA009 - Tablespace Allocation

The PRA009 report provides a list of all tables spaces and the tables they contain.
This information identifies the report.
Report ID
PRA009

264 IBM Z Decision Support : Administration Guide and Reference

 PRA010 - Update Definition

Report group
ADMIN
Reports Source
DRLTABLESPACE, DRLTABLES

Figure 118. Tablespace Allocation report

The report contains the following information:

Tablespace
Name of the tablespace.
Table Name
The table name(s) contained within the tablespace.
Space KB
Space occupied in KB.
Number of Partitions
Lock Rule
The lock size for the tablespace.
Page Size
Max Lock
Number of Tables
The number of tables in this tablespace.
Seg Size
The segment size.

PRA010 - Update Definitions

The PRA010 report provides a list of update definitions for all installed components.
This information identifies the report.
Report ID
PRA010
Report group
ADMIN
Reports Source
DRLUPDATES

Chapter 5. Administration reference 265

PRA011 - Update Details

BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN

Figure 119. Update Definitions report

The report contains the following information:

Update Name
Name of the update definition.
Latest Change
The last change level for the update definition.
Source Prefix
The prefix of the source when the source is another Db2 table.
Source Name
The name of the source. This is either a record definition or a Db2 table.
Target Prefix
The prefix of the target Db2 table.
Target name
The name of the target Db2 table.
Date Installed
The date the definition was installed.
Creator
The name of the installer.

PRA011 - Update Details

The PRA011 report provides a list of field update criteria for each field of an update definition.
This information identifies the report.
Report ID
PRA011
Report group
ADMIN
Reports Source
DRLUPDATECOLS, DRLEXPRESSIONS

266 IBM Z Decision Support : Administration Guide and Reference

 PRA012 - Table Name to Tablespace Cross-Reference

Figure 120. Update Details report

The report contains the following information:

Update Name
Name of the update definition.
Update Col No
The relative position of the field in the update definition.
Column Name
The column name.
Column No
The column number in the target Db2 table.
Function
Expression No
The expression number in the DRLEXPRESSIONS table relative to the update name.
Expression
The update expression.

PRA012 - Table Name to Tablespace Cross-Reference

The PRA012 report provides a cross-reference list of Db2 table names to the tablespace the table is
defined in.
This information identifies the report.
Report ID
PRA012
Report group
ADMIN
Reports Source
DRLTABLES

Chapter 5. Administration reference 267

PRA013 - Tablespace to Table Name Cross-Reference

BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN

Figure 121. Table Name to Tablespace Cross-Reference report

The report contains the following information:

Table Name
Name of the Db2 table.
Tablespace
The name of the tablespace that contains the table.
No Columns
The number of columns in the table.
No Pages
The number pages the table is occupying.
Creator
The name of the user who installed the table.
Space
The space occupied by the table.

PRA013 - Tablespace to Table Name Cross-Reference

The PRA013 report provides a cross-reference list of tablespaces to the Db2 table names that it contains.
This information identifies the report.
Report ID
PRA013
Report group
ADMIN
Reports Source
DRLTABLES

268 IBM Z Decision Support : Administration Guide and Reference

 PRA014 - System Tables

BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN
BKEN

Figure 122. Tablespace to Table Name Cross-Reference report

The report contains the following information:

Tablespace
The name of the tablespace that contains the table.
Table Name
Name of the Db2 table.
No Columns
The number of columns in the table.
No Pages
The number pages the table is occupying.
Creator
The name of the user who installed the table.
Space
The space occupied by the table.

PRA014 - System Tables

The PRA014 report provides a list of all the system tables.
This information identifies the report.
Report ID
PRA014
Report group
ADMIN
Reports Source
DRLTABLES

Chapter 5. Administration reference 269

PRA015 - Non-System Tables Installed

Figure 123. System Tables report

The report contains the following information:

Style Table Name
Name of the system table.
Prefix
The prefix used for the system tables.
Type
The type of table (table or view).

PRA015 - Non-System Tables Installed

The PRA015 report provides a list of all installed Db2 tables.
This information identifies the report.
Report ID
PRA011
Report group
ADMIN
Reports Source
DRLTABLES

270 IBM Z Decision Support : Administration Guide and Reference

 PRA001 - Indexspace Cross-Reference

Figure 124. Non-System Tables Installed report

The report contains the following information:

Table Name
Name of the Db2 table.
Prefix
The prefix used for the system tables.
Type
The type of table (table or view).

Cognos reports
PRA001 - Indexspace Cross-Reference
The PRA001 report provides a cross-reference between index spaces and indexes that are present in the
IBM Z Decision Support environment at the time of running the report. This report enables you to extract
the real name of an index, so that you can locate the index in the administration dialog and adjust its
space allocation if required
This report enables you to extract the real name of an index, so that you can locate the index in the
administration dialog and adjust its space allocation if required.
This information identifies the report:
Report ID
PRA001
Report group
ADMIN
Reports Source
DRLINDEXES

Chapter 5. Administration reference 271

PRA002 - Actual Tablespace Allocation

Variables
Indexspace. Optional.

Figure 125. Indexspace Cross-Reference report

The report contains the following information:

Indexspace
The name of the index space whose index name has been extracted. This is either the name
associated with a single index space or the complete cross reference between index and index space
names for all indexes.
Index Name
The name of the index associated with the indexspace.
For information about:
• The DRLINDEXES system table, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.
• How to display or modify tables or index spaces, see “Displaying and modifying a table or index
space” on page 176.

PRA002 - Actual Tablespace Space Allocation

The PRA002 report shows the actual space allocated to tables. Use the information in this report,
together with the information in PRA003, to estimate future space requirements.
This information identifies the report:
Report ID
PRA002
Report group
ADMIN
Reports Source
DRLTABLESPACE

272 IBM Z Decision Support : Administration Guide and Reference

 PRA003 - Table Purge Condition

Variables
Table space. Optional.

Figure 126. Actual Tablespace Space Allocation report

The report contains the following information:

Tablespace Name
The name of the table space whose space allocation has been extracted.
Space Allocated
The SPACE value as reported in the Db2 catalog (SYSIBM.SYSTABLESPACES table). The column
SPACE contains data only if the STOSPACE utility has been run.
For information about:
• The DRLTABLESPACE system table, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.
• How to display or modify tables or index spaces, see “Displaying and modifying a table or index space”
on page 176.
• The SYSTABLESPACE table, refer to the Db2 for z/OS: SQL Reference.

PRA003 - Table Purge Condition

This report shows a printable list of current purge conditions. It enables you to review purge criteria and
decide which adjustments to make without the need to use the online dialog.
This information identifies the report:
Report ID
PRA003
Report group
ADMIN

Chapter 5. Administration reference 273

PRA004 - Table Structure with Comments

Reports Source
DRLPURGECOND
Variables
Table Name, Latest Changes and Creator are optional. You can select the purge condition associated
with a single table or accept the default setting to obtain a complete list of current purge conditions.

PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER
PARKER

Figure 127. Table Purge Condition report

The report contains the following information:

Table Prefix
The prefix of the table.
Table Name
The name of the table to which the purge condition applies.
Latest Change
The latest change level recorded in the SDRLDEFS.
PURGE CONDITION
The purge condition that applies to the table.
Date Installed
The date the purge condition was installed.
Creator
The ID of the person who installed the purge condition.
For information about:
• The DRLPURGCOND system table, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.
• How to display or edit purge conditions, see “Displaying and editing the purge condition of a table” on
page 174.

PRA004 - Table Structure with Comments

This report shows the column remarks for the selected table.
This information identifies the report:

274 IBM Z Decision Support : Administration Guide and Reference

 PRA005 - Table Names with Comments

Report ID
PRA004
Report group
ADMIN
Reports Source
DRLCOLUMNS
Variables
Table Name. Optional.

Figure 128. Table Structure with Comments report

The report contains the following information:

Table Name
The table name.
ColNo
Column number withing the table.
Keyseq
The column's numeric position within the table's primary key.
Column Name
Table column name.
Nulls
Y - the column may contain NULLS.
Length
Column length.
Comments
Column comment (if defined for the table column). It is 255 char long.

PRA005 - Table Names with Comments

This report lists all the tables with comments.
This information identifies the report:
Report ID
PRA005
Report group
ADMIN

Chapter 5. Administration reference 275

PRA006 - Object Change Level

Reports Source
DRLCOLUMNS
Variables
Table Name. Optional.

Figure 129. Table Names with Comments report

The report contains the following information:

Table Name
Table column name.
Comments
Table comment. It is 255 characters long.

PRA006 - Object Change Level

The PRA006 report displays a list of all the items as well as their current change level.
This information identifies the report.
Report ID
PRA006
Report group
ADMIN
Reports Source
DRLCOMP_OBJECTS, DRLRECORDS, DRLRECORDPROCS, DRLLOGS, DRLUPDATES, DRLREPOSTS
Variables
Component Name. Optional. Select a component name if you want the user-modified objects for
a single component. If you do not specify any value, the complete list of user modified objects is
displayed for all each installed component.

276 IBM Z Decision Support : Administration Guide and Reference

 PRA006 - Object Change Level

Figure 130. Object Change Level report

The report contains the following information:

Component
Name of the component which the objects belong to.
Object Type
Type of object (Record, Update, Log…).
Object Name
Name of the object.
Member Name
Name of the member in the IZDS libraries where the object definition is stored.
Subcomponent
Subcomponent name, if any.
Latest Change
The latest change level of the object. You modify this field when you change any objects. It indicates
whether an object has been modified.
For information about:

Chapter 5. Administration reference 277

PRA007 - Collected Log Data Sets

• The DRLCOMP_OBJECTS, DRLRECORDS, DRLRECORDPROCS, DRLLOGS, DRLUPDATES, DRLREPOSTS

system tables, see “Views on Db2 and QMF tables” on page 221.
• How to run reports, see “Administering reports” on page 111.

PRA007 - Collected Log Data Sets

The PRA007 report provides the list of all the data sets that have been collected.
This information identifies the report.
Report ID
PRA007
Report group
ADMIN
Reports Source
DRLLOGDATASETS
Variables
Log Name and Data Set Name are optional.

PARKER
PARKER
PARKER
PARKER
PARKER
SMITH
SMITH
SMITH
SMITH
SMITH
SMITH
ODIN
ODIN
ODIN
ODIN
ODIN
ODIN
FORTE
FORTE
FORTE

Figure 131. Collected Log Data Sets report

The report contains the following information:

Log Name
Name of the log type.
Data Set Name
The name of the data set collected.
Complete
Y if the log was completely collected.
Number of Collects
The number of times this data set has been collected.
Time Collected
Date and time of the last collect of this data set.
First Timestamp
First timestamp located on the log data set.

278 IBM Z Decision Support : Administration Guide and Reference

 PRA008 - Components and Subcomponents

Last Timestamp
Last timestamp located on the log data set.
User ID
The ID of the person who collected the log data sets.

PRA008 - Components and Subcomponents

The PRA008 report provides a list of all the components and subcomponents available. The report gives a
status of INSTALLED for each component or subcomponent that is installed and the date it was installed.
This information identifies the report.
Report ID
PRA008
Report group
ADMIN
Reports Source
DRLCOMPONENTS, DRLCOMP_PARTS
Variables
Component Name and Status are optional.

Figure 132. Components and Subcomponents report

Chapter 5. Administration reference 279

PRA009 - Table space Allocation

The report contains the following information:

Component
Name of the component.
Component Status
The status of the component (INSTALLED or NOT INSTALLED).
Subcomponent
Name of the subcomponent.
Subcomponent Status
The status of the subcomponent (INSTALLED or NOT INSTALLED).
Date Installed
The date the component and/or subcomponent was installed.

PRA009 - Tablespace Allocation

The PRA009 report provides a list of all tables spaces and the tables they contain.
This information identifies the report.
Report ID
PRA009
Report group
ADMIN
Reports Source
DRLTABLESPACE, DRLTABLES
Variables
Table Name. Optional.

280 IBM Z Decision Support : Administration Guide and Reference

 PRA010 - Update Definition

Figure 133. Tablespace Allocation report

The report contains the following information:

Tablespace
Name of the tablespace.
Table Name
The table name(s) contained within the tablespace.
Space KB
Space occupied in KB.
Number of Partitions
Lock Rule
The lock size for the tablespace.
Page Size
Max Lock
Number of Tables
The number of tables in this tablespace.
Seg Size
The segment size.

PRA010 - Update Definitions

The PRA010 report provides a list of update definitions for all installed components.
This information identifies the report.

Chapter 5. Administration reference 281

PRA010 - Update Definition

Report ID
PRA010
Report group
ADMIN
Reports Source
DRLUPDATES
Variables
Source Prefix, Source Name, Target Name, Target Prefix and Creator are optional.

ODIN
FORTE
FORTE
FORTE
FORTE
FORTE
FORTE
ODIN
ODIN
ODIN
SMITH
SMITH
SMITH
SMITH
SMITH
PARKER
PARKER
PARKER
PARKER
PARKER

Figure 134. Update Definitions report

The report contains the following information:

Update Definition
Name of the update definition.
Latest Change
The last change level for the update definition.
Source Prefix
The prefix of the source when the source is another Db2 table.
Source Name
The name of the source. This is either a record definition or a Db2 table.
Target Prefix
The prefix of the target Db2 table.
Target name
The name of the target Db2 table.
Date Installed
The date the definition was installed.

282 IBM Z Decision Support : Administration Guide and Reference

 PRA011 - Update Details

Creator
The name of the installer.

PRA011 - Update Details

The PRA011 report provides a list of field update criteria for each field of an update definition.
This information identifies the report.
Report ID
PRA011
Report group
ADMIN
Reports Source
DRLUPDATECOLS, DRLEXPRESSIONS
Variables
Update Name. Required.

Figure 135. Update Details report

The report contains the following information:

Update Column Number
The relative position of the field in the update definition.
Column Name
The column name.
Column Number
The column number in the target Db2 table.
Function
Expression Number
The expression number in the DRLEXPRESSIONS table relative to the update name.
Expression
The update expression.

Chapter 5. Administration reference 283

PRA012 - Table Name to Tablespace Cross-Reference

PRA012 - Table Name to Tablespace Cross-Reference

The PRA012 report provides a cross-reference list of Db2 table names to the tablespace the table is
defined in.
This information identifies the report.
Report ID
PRA012
Report group
ADMIN
Reports Source
DRLTABLES
Variables
Tablespace. Optional.

Figure 136. Table Name to Tablespace Cross-Reference report

284 IBM Z Decision Support : Administration Guide and Reference

 PRA013 - Tablespace to Table Name Cross-Reference

The report contains the following information:

Table Name
Name of the Db2 table.
Tablespace
The name of the tablespace that contains the table.
No Columns
The number of columns in the table.
No Pages
The number pages the table is occupying.
Creator
The name of the user who installed the table.
Space
The space occupied by the table.

PRA013 - Tablespace to Table Name Cross-Reference

The PRA013 report provides a cross-reference list of tablespaces to the Db2 table names that it contains.
This information identifies the report.
Report ID
PRA013
Report group
ADMIN
Reports Source
DRLTABLES

Chapter 5. Administration reference 285

PRA013 - Tablespace to Table Name Cross-Reference

Figure 137. Tablespace to Table Name Cross-Reference report

The report contains the following information:

Table Name
Name of the Db2 table.
Tablespace
The name of the tablespace that contains the table.
Number of Columns
The number of columns in the table.
Number of Pages
The number pages the table is occupying.
Creator
The name of the user who installed the table.
Space
The space occupied by the table.

286 IBM Z Decision Support : Administration Guide and Reference

 PRA014 - System Tables

PRA014 - System Tables

The PRA014 report provides a list of all the system tables.
This information identifies the report.
Report ID
PRA014
Report group
ADMIN
Reports Source
DRLTABLES
Variables
System Table Name. Optional.

Figure 138. System Tables report

Chapter 5. Administration reference 287

PRA015 - Non-System Tables Installed

The report contains the following information:

Style Table Name
Name of the system table.
Prefix
The prefix used for the system tables.
Type
The type of table (table or view).

PRA015 - Non-System Tables Installed

The PRA015 report provides a list of all installed Db2 tables.
This information identifies the report.
Report ID
PRA011
Report group
ADMIN
Reports Source
DRLTABLES
Variables
Table Name. Optional.

288 IBM Z Decision Support : Administration Guide and Reference

 PRA015 - Non-System Tables Installed

Figure 139. Non-System Tables Installed report

The report contains the following information:

Table Name
Name of the Db2 table.
Prefix
The prefix used for the system tables.
Type
The type of table (table or view).

Chapter 5. Administration reference 289

Calling the DRL1SQLX module

Using the REXX-SQL interface

This chapter contains General-use Programming Interface and Associated Guidance Information.
IBM Z Decision Support provides a REXX-SQL interface through the DRL1SQLX module, which supports:
• Loading a Db2 table into an array of REXX variables
• Using SQL EXECUTE IMMEDIATE to execute an argument string that is a valid SQL statement
For more information about Db2 terms and statements mentioned in this chapter, refer to the Db2 for
z/OS: SQL Reference.

Calling the DRL1SQLX module

The module derives its input data from the argument on the CALL instruction and from predefined REXX
variables. There are reserved REXX variables that the calling REXX exec defines before calling the module.
If a REXX exec passes an SQL SELECT statement as the argument, DRL1SQLX executes the SELECT and
returns table data in an array of REXX variables. The module can return any Db2 data type but graphic
strings.
The module return code result, set in the variable RESULT, is available to the calling REXX program.
The syntax for running the DRL1SQLX module is:

CALL DRL1SQLX 'INIT'

sql-statement

'TERM'

where:
INIT
Establishes a call attachment facility (CAF) connection to Db2 that leaves the connection open until
a DRL1SQLX TERM statement is executed. There is not an implied COMMIT until the DRL1SQL TERM
statement.
If the REXX program passes INIT as the argument for the CALL DRL1SQLX statement, the
connection remains open for each SQL statement call. The connection does not terminate until a
CALL DRL1SQLX TERM statement closes it.
If the REXX program does not pass INIT as the argument for the CALL DRL1SQLX statement,
the connection is opened at the beginning of each CALL DRL1SQLXsql_statement and closed at its
conclusion, which makes SQL ROLLBACK impossible.
If you are making more than three calls to DRL1SQLX, it is more efficient to use the CALL DRL1SQLX
INIT statement first.
sql-statement
An SQL SELECT or another SQL statement that can be executed with an EXECUTE IMMEDIATE
statement. DRL1SQLX appends the SQL statement to SQL EXECUTE IMMEDIATE and executes it.
TERM
Terminates an existing connection to Db2 and performs an implied COMMIT.

Input REXX variables

The calling program can define these variables before calling DRL1SQLX:
DB2SUBS
The Db2 subsystem that DRL1SQLX addresses.
There is no default for this variable; it must be defined.

290 IBM Z Decision Support : Administration Guide and Reference

 Calling the DRL1SQLX module

DB2PLAN
The name of the Db2 application plan. This variable should be coded only if the installation changed
the default plan name DRLPLAN when the IBM Z Decision Support bind job was run.
SQLSTEM
The stem of the REXX array that DRL1SQLX uses to return table values when the argument is an SQL
SELECT statement.
The stem has an initial value of SQLDATA.
SQLMAX
The maximum number of rows to fetch when the argument is an SQL SELECT statement.
SQLMAX has an default value of 5000. Pick an SQLMAX limit that protects you from runaway queries.
The maximum supported value is 99999999.

Output REXX variables

DRL1SQLX always sets these variables:
RESULT
The DRL1SQLX return code.
When the argument is an SQL SELECT, DRL1SQLX sets RESULT to 4 if the number of rows in the table
is greater than the value of SQLMAX. It issues a message, DRL1007W, to warn you of the condition but
completes the select, returning the number of rows specified in SQLMAX.
DRL1SQLX sets these return codes in RESULT:
0
Successful execution.
4
SQLCODE > 0, SQLMAX invalid or the SQLMAX limit was reached. The error message is in SQLMSG.
8
SQLCODE < 0 indicates an SQL error. The error message is in SQLMSG.
12
An error that is not an SQL error. The error message is in SQLMSG.
16
There was either insufficient REXX storage or a REXX variable that could not be set. The error
appears in SQLMSG, if possible.
20
The REXX communication routine IRXEXCOM could not be loaded. There is no indication of the
error in SQLMSG.
SQLCODE
The SQL return code.
This value is positive when there is an SQL warning and negative when there is an SQL error. It is
returned in combination with a RESULT of 4 or 8, exclusively.
SQLMSG.0
The number of different message values returned when RESULT > 0
SQLMSG.1
The value of the first message returned when RESULT > 0
Up to 5 messages can be returned.
SQLMSG.n
The value of the last message returned when RESULT > 0
The value of n is the value of SQLMSG.0.

Chapter 5. Administration reference 291

Calling the DRL1SQLX module

These variables are set by DRL1SQLX after a successful execution of an SQL SELECT statement. For each
variable below, sqlstem is the value of the SQLSTEM input variable, y is the column number, and z is the
row number:
sqlstem.NAME.0
The number of selected columns.
sqlstem.NAME.y
The names of the selected columns.
The column name of an expression is blank. Each value of y is a whole number from 1 through
sqlstem.NAME.0.
sqlstem.LENGTH.y
The maximum length of the value of the selected columns.
A column name can be longer than the value. Each value of y is a whole number from 1 through
sqlstem.NAME.0.
sqlstem.TYPE.y
The data types of the selected columns.
Each type is copied from the SQLTYPE field in the SQL descriptor area (SQLDA) and is a number
ranging from 384 to 501. Each value of y is a whole number from 1 through sqlstem.NAME.0.
sqlstem.0
The number of rows in the result table.
sqlstem.y.z
The value of the column.
Each value of y is a whole number from 1 through sqlstem.NAME.0.
Each value of z is a whole number from 1 through sqlstem.0.

Reserved REXX variable

DRL1SQLX always sets the variable SQLHANDLE on the INIT statement. It must not be reset except by
the TERM statement, which must be able to read the value set by the last INIT statement.
SQLHANDLE contains the handle returned when DRL1SQLX connects to Db2 with the INIT statement.

292 IBM Z Decision Support : Administration Guide and Reference

 IBM DB2 Analytics Accelerator

REXX example of calling DRL1SQLX

/**REXX**********************************************************/
/* Execute an SQL SELECT statement and display output */
/****************************************************************/

sqlstmt = "SELECT *",

"FROM DRL.MVS_SYSTEM_H",
"WHERE DATE = '2000-05-02'"

db2subs = 'DB2T' /* subsystem name */

sqlstem = 'RES' /* name of stem */
sqlmax = 100 /* limit on nbr of rows */

Call DRL1SQLX sqlstmt /* execute SQL statement */

Say 'DRL1SQLX return code:' result

Say 'SQL return code SQLCODE:' sqlcode

If sqlmsg.0 > 0 Then

Do n = 1 To sqlmsg.0 /* up to 5 error msgs */
Say sqlmsg.n
End

If res.name.0 > 0 Then /* number of columns */

/**************************************************************/
/* Display column names and values for all rows */
/**************************************************************/
If res.0 > 0 Then /* number of rows */
Do z = 1 To res.0
Say ' '
Say 'Following values were returned for row 'z':'
Do y = 1 To res.name.0
Say res.name.y': 'res.y.z
End
End
Else
Say 'No rows were returned'
Exit

Figure 140. Example of REXX-SQL interface call

Using the IBM Db2 Analytics Accelerator

The IBM® Db2 Analytics Accelerator is a high-performance appliance that integrates business insights into
operational processes.

IBM Z Decision Support includes Analytics Components that are designed to support the IBM Db2
Analytics Accelerator. These components are based on existing non-Analytics components that are
modified to allow for the following functions:
• Store data directly to an IBM Db2 Analytics Accelerator removing the need to store data on Db2 for
z/OS®.
• Allow for more detailed timestamp level records to be stored.
• Allow for more CPU work to move from z/OS to the IBM Db2 Analytics Accelerator appliance.
• Report to make use of the high query speeds of the IBM Db2 Analytics Accelerator.
The System Data Engine component of the IBM Common Data Provider for z Systems® is used to convert
SMF log data into data sets that contain the IBM Tivoli® Decision Support for z/OS Analytics components
tables in Db2 internal format. The IBM Db2 Analytics Accelerator Loader for z/OS is then used to load the
Db2 internal format data sets directly into the IBM Db2 Analytics Accelerator.
The Analytics components comprise the following items:
• Analytics - z/OS Performance
• Analytics - Db2
• Analytics - KPM CICS®

Chapter 5. Administration reference 293

IBM DB2 Analytics Accelerator

• Analytics - KPM Db2

• Analytics - KPM z/OS

Relationship of Analytics Components to non-Analytics Components

The Analytics components are based on the following existing non-Analytics components:
Table 8. Relationship of Analytics components to non-Analytics components
Analytics Non-Analytics

Analytics - Db2 Db2

Analytics - KPM CICS Key Performance Metrics - CICS
Analytics - KPM Db2 Key Performance Metrics - Db2
Analytics - KPM z/OS Key Performance Metrics - z/OS
Analytics - z/OS Performance z/OS Performance Management (MVSPM)

The Analytics components include Lookup tables that must be customized as per their equivalent Lookup
tables in the non-Analytics components:
Table 9. Relationship of Analytics Lookup table to non-Analytics Lookup table
Member name Analytics Lookup table non-Analytics Lookup table

DRLTA2AP A_DB2_APPLICATION DB2_APPLICATION

DRLTA2AC A_DB2_ACCUMAC DB2_ACCUMAC
DRLTALUG A_USER_GROUP USER_GROUP
DRLTALKP A_KPM_THRESHOLDS_L KPM_THRESHOLDS
DRLTALW2 A_WORKLOAD2_L MVS_WORKLOAD2_TYPE
DRLTALDA A_DEVICE_ADDR_L MVSPM_DEVICE_ADDR
DRLTALUT A_UNIT_TYPE_L MVSPM_UNIT_TYPE
DRLTALMI A_MIPS_L MVS_MIPS_T
DRLTALSP A_SYSPLEX_L MVS_SYSPLEX
DRLTALWL A_WORKLOAD_L MVS_WORKLOAD_TYPE
DRLTALTR A_TIME_RES_L MVSPM_TIME_RES

The following table lists all the reports per Analytics component, and their equivalent non-Analytics
component reports.

294 IBM Z Decision Support : Administration Guide and Reference

 IBM DB2 Analytics Accelerator

Table 10. Relationship of Analytics component report to non-Analytics component report

Report name Analytics Report ID non-Analytics Report ID

Db2 Buffer Pool Exceptions ADB219 DB219

Db2 Buffer Pool Statistics, Detail ADB215 DB215
Db2 Buffer Pool Statistics, Overview ADB216 DB216
Db2 DBRMs Class 7,8 Times, Overview ADB222 DB222
Db2 General Measure by Profile, Overview ADB212 DB212
Db2 IDAA Statistics by Transaction, Detail ADB244 DB244
Db2 Packages Class 7,8 Times, Overview ADB221 DB221
Db2 Transaction Statistics, Detail ADB204 DB204
Db2 Transaction Statistics, Overview ADB205 DB205

The following table lists all the tables per Analytics component, and their equivalent non-Analytics
component tables.

Chapter 5. Administration reference 295

IBM DB2 Analytics Accelerator

Table 11. Relationship of Analytics component table to non-Analytics component table

Component Type Analytics component table Equivalent to non-Analytics
component table
Analytics - z/OS Table A_PM_CF_I MVSPM_CF_H
Performance A_PM_CF_LINK_I MVSPM_CF_LINK_H
A_PM_CF_PROC_I MVSPM_CF_PROC_H
A_PM_CF_REQ_I MVSPM_CF_REQUEST_H
A_PM_CF_CF_I MVSPM_CF_TO_CF_H
A_PM_XCF_MEMBER_I MVSPM_XCF_MEMBER_H
A_PM_XCF_PATH_I MVSPM_XCF_PATH_H
A_PM_XCF_SYS_I MVSPM_XCF_SYS_H
A_PM_OMVS_BUF_I MVSPM_OMVS_BUF_H
A_PM_OMVS_FILE_I MVSPM_OMVS_FILE_H
A_PM_OMVS_GHFS_I MVSPM_OMVS_GHFS_H
A_PM_OMVS_HFS_I MVSPM_OMVS_HFS_H
A_PM_OMVS_KERN_I MVSPM_OMVS_KERN_H
A_PM_OMVS_MOUNT_I MVSPM_OMVS_MOUNT_H
A_PM_SYS_CLUST_I MVSPM_CLUSTER_H
A_PM_SYS_CPU_I MVSPM_CPU_H
A_PM_SYS_CPUMT_I MVSPM_CPUMT_H
A_PM_SYS_ENQ_I MVSPM_ENQUEUE_H
A_PM_SYS_LPAR_I MVSPM_LPAR_H
A_PM_SYS_SYS_I MVSPM_SYSTEM_H
A_PM_SYS_PROD_I MVSPM_PROD_T
A_PM_SYS_PRDINT_I MVSPM_PROD_INT_T
A_PM_SYS_MSU_I MVSPM_LPAR_MSU_T
A_PM_WL_GOAL_I MVSPM_GOAL_ACT_H
A_PM_WL_SERVED_I MVSPM_WLM_SERVED_H
A_PM_WL_STATE_I MVSPM_WLM_STATE_H
A_PM_WL_WKLD_I MVSPM_WORKLOAD_H
A_PM_WL_WKLD2_I MVSPM_WORKLOAD2_H
A_PM_IO_DATASET_I MVSPM_DATASET_H
A_PM_IO_VOLUME_I MVSPM_VOLUME_H
A_PM_IO_LCU_I MVSPM_LCU_IO_H
A_PM_GS_BMF_I MVSPM_BMF_H
A_PM_GS_CACHE_I MVSPM_CACHE_H
A_PM_GS_PAGEDS_I MVSPM_PAGE_DS_H
A_PM_GS_PAGING_I MVSPM_PAGING_H
A_PM_GS_STORAGE_I MVSPM_STORAGE_H
A_PM_GS_STORCLS_I MVSPM_STORCLASS_H
A_PM_GS_SWAP_I MVSPM_SWAP_H
A_PM_GS_CACHESS_I MVSPM_CACHE_ESS_H
A_PM_VS_VLF_I MVSPM_VLF_H
A_PM_VS_CSASQA_I MVSPM_VS_CSASQA_H
A_PM_VS_PRIVATE_I MVSPM_VS_PRIVATE_H
A_PM_VS_SUBPOOL_I MVSPM_VS_SUBPOOL_H
A_PM_DEV_CHAN_I MVSPM_CHANNEL_H
A_PM_DEV_HSCHAN_I MVSPM_HS_CHAN_H
A_PM_DEV_AP_I MVSPM_DEVICE_AP_H
A_PM_DEV_DEVICE_I MVSPM_DEVICE_H
A_PM_DEV_FICON_I MVSPM_FICON_H
A_PM_DEV_RAID_I MVSPM_RAID_RANK_H
A_PM_DEV_ESSLNK_I MVSPM_ESSLINK_H
A_PM_DEV_ESSEXT_I MVSPM_ESS_EXTENT_H
A_PM_DEV_ESSRNK_I MVSPM_ESS_RANK_H
A_PM_DEV_PCIE_I MVSPM_PCIE_H
A_PM_CRYP_PCI_I MVSPM_CRYPTO_PCI_H
A_PM_CRYP_CCF_I MVSPM_CRYPTO_CCF_H
A_PM_APP_APPL_I MVSPM_APPL_H

296 IBM Z Decision Support : Administration Guide and Reference

 IBM DB2 Analytics Accelerator

Table 11. Relationship of Analytics component table to non-Analytics component table (continued)
Component Type Analytics component table Equivalent to non-Analytics
component table
Analytics - Db2 Table A_DB2_SYS_PARM_I DB2_SYS_PARAMETER
A_DB2_DB_I DB2_DATABASE_T
A_DB2_DB_BIND_I DB2_DATABASE_T
A_DB2_DB_QIST_I DB2_DATABASE_T
A_DB2_DB_SYS_I DB2_SYSTEM_T
A_DB2_BP_I DB2_BUFFER_POOL_T
A_DB2_USERTRAN_I DB2_USER_TRAN_H
A_DB2_UT_BP_I DB2_USER_TRAN_H
A_DB2_UT_SACC_I DB2_USER_TRAN_H
A_DB2_UT_IDAA_I DB2_USER_TRAN_H
A_DB2_IDAA_STAT_I DB2_IDAA_STAT_H
A_DB2_IDAA_ACC_I DB2_IDAA_ACC_H
A_DB2_IDAA_ST_A_I DB2_IDAA_STAT_A_H
A_DB2_IDAA_ST_S_I DB2_IDAA_STAT_S_H
A_DB2_PACK_I DB2_PACKAGE_H
A_DB2_SHR_BP_I DB2_BP_SHARING_T
A_DB2_SHR_BPAT_I DB2_BPATTR_SHR_T
A_DB2_SHR_LOCK_I DB2_LOCK_SHARING_T
A_DB2_SHR_INIT_I DB2_SHARING_INIT
A_DB2_SHR_TRAN_I DB2_US_TRAN_SHAR_H
A_DB2_DDF_I DB2_USER_DIST_H
A_DB2_SYSTEM_I DB2_SYSTEM_DIST_T
A_DB2_STORAGE_I DB2_STORAGE_T

View A_DB2_TRAN_IV DB2_TRANSACTION_D

A_DB2_DATABASE_IV DB2_DATABASE_T

Analytics - KPM Db2 Table A_KD_UT_I KPM_DB2_USERTRAN_H

A_KD_UT_BP_I KPM_DB2_USERTRAN_H
A_KD_EU_I KPM_DB2_ENDUSER_H
A_KD_EU_BP_I KPM_DB2_ENDUSER_H
A_KD_PACKAGE_I KPM_DB2_PACKAGE_H
A_KD_SYS_IO_I KPM_DB2_SYSTEM_T
A_KD_SYS_TCBSRB_I KPM_DB2_SYSTEM_T
A_KD_SYS_LATCH_I KPM_DB2_LATCH_T
A_KD_SYS_BP_I KPM_DB2_BP_T
A_KD_SYS_BP_SHR_I KPM_DB2_BP_SHR_T
A_KD_SYS_ST_DBM_I KPM_DB2_STORAGE_T
A_KD_SYS_ST_DST_I KPM_DB2_STORAGE_T
A_KD_SYS_ST_COM_I KPM_DB2_STORAGE_T
A_DB_SYS_DB_WF_I KPM_DB2_DATABASE_T
A_DB_SYS_DB_EDM_I KPM_DB2_DATABASE_T
A_DB_SYS_DB_SET_I KPM_DB2_DATABASE_T
A_DB_SYS_DB_LOCK_I KPM_DB2_LOCK_T

Analytics - KPM CICS Table A_KC_MON_TRAN_I KPMC_MON_TRAN_H

Chapter 5. Administration reference 297

IBM DB2 Analytics Accelerator

Table 11. Relationship of Analytics component table to non-Analytics component table (continued)
Component Type Analytics component table Equivalent to non-Analytics
component table
Analytics - KPM z/OS Table A_KPM_EXCEPTION_I KPM_EXCEPTION_T
A_KZ_JOB_INT_I KPMZ_JOB_INT_T
A_KZ_JOB_STEP_I KPMZ_JOB_STEP_T
A_KZ_LPAR_I KPMZ_LPAR_T
A_KZ_STORAGE_I KPMZ_STORAGE_T
A_KZ_WORKLOAD_I KPMZ_WORKLOAD_T
A_KZ_CHANNEL_I KPMZ_CHANNEL_T
A_KZ_CF_I KPMZ_CF_T
A_KZ_CF_STRUC_I KPMZ_CF_STRUCTR_T
A_KZ_CPUMF_I KPMZ_CPUMF_T
A_KZ_CPUMF1_I KPMZ_CPUMF1_T
A_KZ_CPUMF_PT_I KPMZ_CPUMF_PT_T
A_KZ_CPUMF1_PT_I KPMZ_CPUMF1_PT_T
A_KZ_SRM_WKLD_I KPMZ_SRM_WKLD_T

There are cases where multiple tables from an Analytics component are combined into a single view. In
these cases, the resulting view matches an existing table from an IBM Z Decision Support non-Analytics
component. See the following table for views in the Analytics components that are based on multiple
tables from non-Analytics components.
Table 12. Relationship of Analytics component tables used in view to non- Analytics component tables used in view
Component View Analytics component Equivalent to non-
tables used in view Analytics component
table
Analytics - Db2 A_DB2_USERTRAN_IV A_DB2_USERTRAN_I DB2_USER_TRAN_H
A_DB2_UT_BP_I
A_DB2_UT_SACC_I
A_DB2_UT_IDAA_I

Analytics - Db2 A_DB2_DATABASE_IV A_DB2_DB_I DB2_DATABASE_T

A_DB2_DB_BIND_I
A_DB2_DB_QIST_I

Analytics - KPM Db2 A_KD_USERTRAN_IV A_KD_UT_I KPM_DB2_USERTRAN_H

A_KD_UT_BP_I

Analytics - KPM Db2 A_KD_ENDUSER_IV A_KD_EU_I KPM_DB2_ENDUSER_H

A_KD_EU_BP_I

Analytics - KPM Db2 A_KD_SYSTEM_IV A_KD_SYS_IO_I KPM_DB2_SYSTEM_T

A_KD_SYS_TCBSRB_I

Analytics - KPM Db2 A_KD_STORAGE_IV A_KD_SYS_ST_DBM_I KPM_DB2_STORAGE_T

A_KD_SYS_ST_DST_I
A_KD_SYS_ST_COM_I

Analytics - KPM Db2 A_KD_DATABASE_IV A_DB_SYS_DB_WF_I KPM_DB2_DATABASE_T

A_DB_SYS_DB_EDM_I
A_DB_SYS_DB_SET_I

298 IBM Z Decision Support : Administration Guide and Reference

 IBM DB2 Analytics Accelerator

Configuring Analytics Components for use with IBM Db2 Analytics

Accelerator

About this task

You can complete the following steps that are required for IBM IBM Z Decision Support to use the IBM
Db2 Analytics Accelerator to contain the data for the tables of the Analytics components. Tables that are
created on an IBM Db2 Analytics Accelerator (IDAA) can be loaded without loading data into Db2, which
requires the following items:
• The System Data Engine (SDE) component of the IBM Z Common Data Provider to collect the SMF data
instead of using TDSz Collect. The PTFs for APARs OA52196 and OA52200 must be applied.
• The IBM Db2 Analytics Accelerator Loader for z/OS
The Analytics components comprise the following items:
• Analytics - z/OS Performance
• Analytics - Db2
• Analytics - KPM CICS
• Analytics - KPM Db2
• Analytics - KPM z/OS
The Analytics components allow for tables to be created as either kind of the following tables:
• Db2 for z/OS tables
• IBM Db2 Analytics Accelerator Accelerator-shadow tables
• IBM Db2 Analytics Accelerator Accelerator-only tables

Procedure
1. Ensure to apply the PTFs for APAR PI70968 to the IBM Z Decision Support system.
2. Bind the Db2 plan that is used by IBM Z Decision Support by specifying the BIND option
QUERYACCELERATION(ELIGIBLE) or QUERYACCELERATION(ENABLE). For example, assuming the
default plan name to be DRLPLAN, the BIND PACKAGE to set ELIGIBLE for the query acceleration
register is as follows:

//SYSTSIN DD *
DSN SYSTEM(DSN)
BIND PACKAGE(DRLPLAN) OWNER(authid) MEMBER(DRLPSQLX) -
ACTION(REPLACE) ISOLATION(CS) ENCODING(EBCDIC) -
QUERYACCELERATION(ELIGIBLE)
BIND PLAN(DRLPLAN) OWNER(authid) PKLIST(*.DRLPLAN.*) -
ACTION(REPLACE) RETAIN
RUN PROGRAM(DSNTIAD) PLAN(DSNTIAxx) -
LIB(’xxxx.RUNLIB.LOAD’)
END

For more information about the sample instructions to BIND with QUERYACCELERATION specified, see
SDRLCNTL(DRLJDBIN).
3. Modify the DRLFPROF data set to reflect the settings to apply when installing Analytics components.
DRLFPROF is the IBM Z Decision Support data set that contains user modified parameters. The
following parameters in DRLFPROF provide support for the IBM Db2 Analytics Accelerator:
def_useaot = "YES" | "NO"
"YES": Tables are created as Accelerator Only Tables.
"NO": Tables are created in Db2 and are suitable for use either as Db2 tables or as IDAA_ONLY
tables. The default value is "NO".

Chapter 5. Administration reference 299

IBM DB2 Analytics Accelerator

def_accelerator = "xxxxxxxx"
"xxxxxxxx": The name of the Accelerator where the tables reside. Required only if using
Accelerator Only Tables.
def_timeint = "H" | "S" | "T"
"H": The timestamp for records is rounded to hourly intervals that is similar to non-Analytics tables
with a suffix of "_H" in other components.
"S": The timestamp for records is rounded to intervals of a second that is similar to non-Analytics
tables with time field instead of timestamp in other components.
"T": The timestamp for tables is the actual timestamp in the SMF log record that is similar to
non-Analytics tables with suffix "_T". The default value is "T".
4. Important: This step is required only if you use IBM Z Decision Support to collect and populate the
component tables on Db2 for z/OS, or if you use IBM Z Decision Support reporting. If you only collect
data into the IBM Db2 Analytics Accelerator and does not have the data reside on Db2 for z/OS,
configure the lookup tables in the Common Data Provider for z Systems. See the information about
collecting data for direct load to the Accelerator in the Z Common Data Provider User Guide.
Customize each lookup table in the Analytics components as per the existing IBM Z Decision Support
non-Analytics lookup tables.
For example, insert the same rows that are currently in DB2_APPLICATION into
A_DB2_APPLICATION.
5. Install the desired Analytics component(s).
6. Add tables to the Accelerator.
If IBM Z Decision Support uses Accelerator Only Tables (AOTs), i.e. the DRLFPROF setting for
def_useaot is "YES", Db2 creates the tables on the IBM Db2 Analytics Accelerator when the Analytics
components are being installed.
If IBM Z Decision Support doesn't use AOTs, the tables need to be added to the IBM Db2 Analytics
Accelerator. Tables can be added by using the Data Studio Eclipse application, or by using stored
procedures. To use stored procedures to add the tables to an IBM Db2 Analytics Accelerator, modify
and submit the SDRLCNTL members in the following table:

Table 13. Relationship of SDRLCNTL member name to Analytics component

SDRLCNTL member name Component

DRLJA2DA Analytics - Db2

DRLJAPMA Analytics - z/OS Performance
DRLJAKCA Analytics - KPM CICS
DRLJAKDA Analytics - KPM Db2
DRLJAKZA Analytics - KPM z/OS

7. Load data into lookup tables on the Accelerator.

If IBM Z Decision Support uses Accelerator Only Tables (AOTs), the lookup tables are populated on the
IBM Db2 Analytics Accelerator when the Analytics components are being installed.
If IBM Z Decision Support doesn't use AOTs, the contents of the lookup tables need to be loaded into
the IBM Db2 Analytics Accelerator. Modify and submit the SDRLCNTL members in the following table
to move the contents of the lookup tables into the Accelerator
Note: Not all components have lookup tables.

300 IBM Z Decision Support : Administration Guide and Reference

 IBM DB2 Analytics Accelerator

Table 14. Relationship of SDRLCNTL member name to Analytics component

SDRLCNTL member name Component

DRLJAPMK Analytics - z/OS Performance

DRLJAKDK Analytics - KPM Db2
DRLJAKZK Analytics - KPM z/OS

Collecting data for direct load to the Accelerator

To collect data for direct load to tables on an IBM Db2 Analytics Accelerator, the following items are
required:
• The System Data Engine (SDE) component of the IBM Z Common Data Provider to collect the SMF data
instead of using IBM Z Decision Support Collect. The PTFs for APARs OA52196 and OA52200 must be
applied.
• The IBM Db2 Analytics Accelerator Loader for z/OS
See the information about collecting data for direct load to the Accelerator in the Z Common Data Provider
User Guide.
After the data has been collected, it can be loaded direct to the IBM Db2 Analytics Accelerator.

Loading data into the Accelerator

About this task

The Db2 Analytics Accelerator Loader for z/OS V2.1 (Loader) is used to load the Db2 internal format data
sets, which are created by the System Data Engine (SDE), directly into the Db2 Analytics Accelerator
(Accelerator) without the data residing in Db2 for z/OS.
The Loader is invoked via the Db2 LOAD utility with the following amendments:
• A DD statement that indicates the Loader is to intercept the Db2 LOAD utility:

//HLODUMMY DD DUMMY

• A statement that tells the loader to load data into the Accelerator. This statement indicates the data is
only to reside on the IDAA_ONLY Accelerator, the name of the Accelerator, the schema (e.g. DRLxx) and
the table name:

//SYSIN DD *
LOAD DATA RESUME YES LOG NO INDDN input_data_set_ddname
IDAA_ONLY ON accelerator-name
INTO TABLE DRLxx.table-name FORMAT INTERNAL;

Procedure
1. To load the data that is created by the System Data Engine, modify and submit the SDRLCNTL
members in the following table based on the installed components:

Chapter 5. Administration reference 301

IBM DB2 Analytics Accelerator

Table 15. Relationship of SDRLCNTL member name to Analytics component

SDRLCNTL member name Component

DRLJA2DD Analytics - Db2

DRLJAPMD Analytics - z/OS Performance
DRLJAKCD Analytics - KPM CICS
DRLJAKDD Analytics - KPM Db2
DRLJAKZD Analytics - KPM z/OS

2. Enable acceleration of tables after first data load.

If IBM Z Decision Support uses Accelerator Only Tables (AOTs), i.e. the DRLFPROF setting for
def_useaot is "YES", you don't need to enable the tables on the IBM Db2 Analytics Accelerator.
If IBM Z Decision Support doesn't use AOTs and the Db2 LOAD is the first load for an IDAA_ONLY
Accelerator table, after the load has been completed, the table must be enabled for acceleration
in the Accelerator. Tables can be enabled by using the Data Studio Eclipse application, or by using
stored procedures. To use stored procedures to enable the tables, modify and submit the SDRLCNTL
members in the following table:

Table 16. Relationship of SDRLCNTL member name to Analytics component

SDRLCNTL member name Component

DRLJA2DE Analytics - Db2

DRLJAPME Analytics - z/OS Performance
DRLJAKCE Analytics - KPM CICS
DRLJAKDE Analytics - KPM Db2
DRLJAKZE Analytics - KPM z/OS

Uninstalling components used with an IBM Db2 Analytics Accelerator

About this task

To uninstall Analytics components that have been configured for use with an IBM Db2 Analytics
Accelerator, perform the following steps:

Procedure
1. Remove tables from the Accelerator.
If IBM Z Decision Support uses Accelerator Only Tables (AOTs), i.e. the DRLFPROF setting for
def_useaot is "YES", you don't need to remove tables on the IBM Db2 Analytics Accelerator because
the next step will automatically remove them.
If IBM Z Decision Support doesn't use AOTs, the tables must be removed from the Accelerator prior to
uninstalling the component. Modify and submit the SDRLCNTL members in the following table based
on the components to be uninstalled. Modify and submit the SDRLCNTL members in the following
table according to the components to be uninstalled.

302 IBM Z Decision Support : Administration Guide and Reference

 IBM DB2 Analytics Accelerator

Table 17. Relationship of SDRLCNTL member name to Analytics component

SDRLCNTL member name Component

DRLJA2DR Analytics - Db2

DRLJAPMR Analytics - z/OS Performance
DRLJAKCR Analytics - KPM CICS
DRLJAKDR Analytics - KPM Db2
DRLJAKZR Analytics - KPM z/OS

2. Uninstall the Analytics component(s) by using IBM Z Decision Support menus.

Chapter 5. Administration reference 303

IBM DB2 Analytics Accelerator

304 IBM Z Decision Support : Administration Guide and Reference

Appendix A. Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides a number of
ways for you to obtain the support you need.
• Searching knowledge bases: You can search across a large collection of known problems and
workarounds, Technotes, and other information.
• Obtaining fixes: You can locate the latest fixes that are already available for your product.
• Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with
someone from IBM, you can use a variety of ways to contact IBM Support.

Contacting IBM Support

This section describes how to contact IBM Support if you have been unable to resolve a problem with IBM
Z Decision Support.
Before contacting IBM Support, your company must have an active IBM software maintenance contract,
and you must be authorized to submit problems to IBM. The type of software maintenance contract
that you need depends on the type of product you have. For more information, refer to the IBM Support
website at the following links:
IBM Support
https://www.ibm.com/mysupport/s/
Z Decision Support
https://www.ibm.com/mysupport/s/topic/0TO0z0000006v25GAA/z-decision-support
To contact IBM Support to report a problem (open a case), follow these steps:
1. Determine the business impact.
2. Describe the problem and gather information.
3. Submit the problem report.

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 problem that you are reporting. Use the following
criteria:
Severity 1
The problem has a critical business impact. You are unable to use the program, resulting in a critical
impact on operations. This condition requires an immediate solution.
Severity 2
The problem has a significant business impact. The program is usable, but it is severely limited.
Severity 3
The problem has some business impact. The program is usable, but less significant features (not
critical to operations) are unavailable.
Severity 4
The problem has minimal business impact. The problem causes little impact on operations, or a
reasonable circumvention to the problem was implemented.

Describing the problem and gathering information

When describing a problem to IBM, be as specific as possible. Include all relevant background
information so that IBM Support specialists can help you solve the problem efficiently. To save time,
know the answers to the following questions:

© Copyright IBM Corp. 1993, 2017 305

 • What software versions were you running when the problem occurred?
• Do you have logs, traces, and messages that are related to the problem symptoms? IBM Support is
likely to ask for this information.
• Can you re-create the problem? If so, what steps were performed to re-create the problem?
• Did you make any changes to the system? For example, did you make changes to the hardware,
operating system, networking software, product-specific customization, and so on.
• Are you currently using a workaround for the problem? If so, be prepared to explain the workaround
when you report the problem.

Submitting the problem

You can submit your problem to IBM Support in either of the following ways:
Online
Go to https://www.ibm.com/mysupport/s/, click on Open a case, and enter the relevant details into
the online form.
By email or phone
For the contact details in your country, go to the Contact IBM website at https://www.ibm.com/
contact/global. Scroll down for a list of countries by geographic region. Select your country to find the
contact details for general inquiries, technical support, and customer support.
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM
Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in
detail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR is
resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support website, so that other
users who experience the same problem can benefit from the same resolution.

306 IBM Z Decision Support : Administration Guide and Reference

Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the
products, services, or features discussed in this document in other countries. Consult your local IBM
representative for information on the products and services currently available in your area. Any reference
to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not
infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to
evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any 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 IBM Intellectual Property
Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan, Ltd.
19-21, Nihonbashi-Hakozakicho, Chuo-ku
Tokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,
this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in
any manner serve as an endorsement of those websites. The materials at those websites are not part of
the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who want to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this
one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.

© Copyright IBM Corp. 1993, 2017 307

Trademarks

Such information may be available, subject to appropriate terms and conditions, including in some cases
payment of a fee.
The licensed program described in this information and all licensed material available for it are provided
by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or
any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be
the same on generally available systems. Furthermore, some measurements may have been estimated
through extrapolation. Actual results may vary. Users of this document should verify the applicable data
for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without
notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
Copyright and trademark information at https://www.ibm.com/legal/copytrade.

308 IBM Z Decision Support : Administration Guide and Reference

Bibliography

IBM Z Decision Support publications

The IBM Z Decision Support library contains the following publications and related documents.
The publications are available online in the IBM Documentation at the following link, from where you can
also download the associated PDF:
https://www.ibm.com/docs/en/z-decision-support/1.9.0
• Administration Guide and Reference, SC27-9055
Provides information about initializing the IBM Z Decision Support database and customizing and
administering IBM Z Decision Support.
• AS/400 System Performance Feature Guide and Reference, SC27-9060
Provides information for administrators and users about collecting and reporting performance data
generated by AS/400 systems.
• CICS Performance Feature Guide and Reference, SC27-9057
Provides information for administrators and users about collecting and reporting performance data
generated by Customer Information Control System (CICS).
• Distributed Systems Performance Feature Guide and Reference, SC27-9059
Provides information for administrators and users about collecting and reporting performance data
generated by operating systems and applications running on a workstation.
• Guide to Reporting, SC27-9066
Provides information for users who display existing reports, for users who create and modify reports,
and for administrators who control reporting dialog default functions and capabilities.
• IMS CSQ Feature Guide and Reference, SC27-9058
Provides information for administrators and users about collecting and reporting performance data
generated by Information Management System (IMS).
• Language Guide and Reference, GI13-4376
Provides information for administrators, performance analysts, and programmers who are responsible
for maintaining system log data and reports.
• Messages and Problem Determination, GC27-9056
Provides information to help operators and system programmers understand, interpret, and respond to
IBM Z Decision Support messages and codes.
• Network Performance Feature Installation and Administration, SC28-3205
Provides information for network analysts or programmers who are responsible for setting up the
network reporting environment.
• Network Performance Feature Reference, SC28-3206
Provides reference information for network analysts or programmers who use the Network Performance
feature.
• Network Performance Feature Reports, SC28-3207
Provides information for network analysts or programmers who use the Network Performance feature
reports.
• Resource Accounting for z/OS, SC28-3208

© Copyright IBM Corp. 1993, 2017 309

 Provides information for users who want to use IBM Z Decision Support to collect and report
performance data generated by Resource Accounting.
• System Performance Feature Guide, SC28-3209
Provides information for performance analysts and system programmers who are responsible for
meeting the service-level objectives established in your organization.
• System Performance Feature Reference Volume I, SC27-9062
Provides information for administrators and users with a variety of backgrounds who want to use IBM Z
Decision Support to analyze z/OS, z/VM, zLinux, and their subsystems, performance data.
• System Performance Feature Reference Volume II, SC27-9063
Provides information for administrators and users with a variety of backgrounds who want to use IBM Z
Decision Support to analyze z/OS, z/VM, zLinux, and their subsystems, performance data.
• Usage and Accounting Collector User Guide, SC27-9064
Provides information about the functions and features of the Usage and Accounting Collector.

310 IBM Z Decision Support : Administration Guide and Reference

Glossary
A
administration
An IBM Z Decision Support task that includes maintaining the database, updating environment
information, and ensuring the accuracy of data collected.
administration dialog
A set of host windows used to administer IBM Z Decision Support.
C
collect
A process used by IBM Z Decision Support to read data from input log data sets, interpret records in
the data set, and store the data in Db2 tables in the IBM Z Decision Support database.
compatibility mode
A mode of processing, in which the IEAIPSxx and IEAICSxx members of SYS1.PARMLIB determine
system resource management.
component
An optionally installable part of an IBM Z Decision Support feature. Specifically in IBM Z Decision
Support , a component refers to a logical group of objects used to collect log data from a specific
source, to update the IBM Z Decision Support database using that data, and to create reports from
data in the database.
control table
A predefined IBM Z Decision Support table that controls results returned by some log collector
functions.
D
data table
An IBM Z Decision Support table that contains performance data used to create reports.
DFHSM
In this book, DFHSM is referred to by its new product name. See DFSMShsm.
DFSMShsm
Data Facility Storage Management Subsystem hierarchical storage management facility. A functional
component of DFSMS/MVS used to back up and recover data, and manage space on volumes in the
storage hierarchy.
DFSMS
Data Facility Storage Management Subsystem. An IBM licensed program that consists of DFSMSdfp,
DFSMSdss, and DFSMShsm.
E
environment information
All of the information that is added to the log data to create reports. This information can include data
such as performance groups, shift periods, installation definitions, and so on.
G
goal mode
A mode of processing where the active service policy determines system resource management.
H
host
The MVS system where IBM Z Decision Support runs collect and where the IBM Z Decision Support
database is installed.
K

© Copyright IBM Corp. 1993, 2017 311

 key columns
The columns of a Db2 table that together constitute the key.
L
log collector
An IBM Z Decision Support program that processes log data sets and provides other IBM Z Decision
Support services.
log data set
Any sequential data set that is used as input to IBM Z Decision Support.
log definition
The description of a log data set processed by the log collector.
log procedure
A program module that is used to process all record types in certain log data sets.
lookup table
An IBM Z Decision Support Db2 table that contains grouping, conversion, or substitution information.
P
IBM Z Decision Support database
A set of Db2 tables that includes data tables, lookup tables, system tables, and control tables.
R
record definition
The description of a record type contained in the log data sets used by IBM Z Decision Support,
including detailed record layout and data formats.
record procedure
A program module that is called to process some types of log records.
record type
The classification of records in a log data set.
report group
A collection of IBM Z Decision Support reports that can be referred to by a single name.
reporting dialog
A set of host or workstation windows used to request reports.
resource group
A collection of network resources that are identified as belonging to a particular department or
division. Resources are organized into groups to reflect the structure of an organization.
S
section
A structure within a record that contains one or more fields and may contain other sections.
service class
A group of work which has the same performance goals, resource requirements, or business
importance. For workload management, you assign a service goal and optionally a resource group,
to a service class.
source
In an update definition, the record or Db2 table that contains the data used to update an IBM Z
Decision Support Db2 table.
sysplex
A set of MVS systems communicating and cooperating with each other through certain multisystem
hardware components and software services to process customer workloads.
system table
A Db2 table that stores information that controls log collector processing, IBM Z Decision Support
dialogs, and reporting.
T

312 IBM Z Decision Support : Administration Guide and Reference

target
In an update definition, the Db2 table in which IBM Z Decision Support stores data from the source
record or table.
threshold
The maximum or minimum acceptable level of usage. Usage measurements are compared with
threshold levels.
U
update definition
Instructions for entering data into Db2 tables from records of different types or from other Db2 tables.
V
view
An alternative representation of data from one or more tables. A view can include all or some of the
columns contained in the table on which it is defined.

Glossary 313
314 IBM Z Decision Support : Administration Guide and Reference
Index

A backup, incremental-image or full-image 106

batch
abbreviation generating problem records in 118
adding to an update definition 172 running reports 111
deleting from an update definition 173 batch mode
accessibility xiii collect 87
activating installing component 124
automated data gathering 45 installing component in 124
adding a column to a table 167 reporting 117
adding a log data set for collection 194 batch print SYSOUT class dialog parameter 66
adding a log ID and collect statements data set 191 books xiii
adding an abbreviation to an update definition 172 books for IBM Z Decision Support 309
adding an object to a component 131
ADMDEFS nickname ddname, description 111
ADMGDF ddname, graphic reports data set 111
C
administering lookup and control tables 110 calculating and monitoring table space requirements 98
administering problem records 117 calculating table space requirements
administering reports 111 monitoring, and 98
administering the IBM Z Decision Support database 96 changes in this edition xv
administering user access to tables 185 changing space definitions 30
administration dialog changing the collect statements data set name 192
collecting data 86 changing the retention period of information about a log data
collecting log data 87 set 199
commands 254 CICS control tables
introduction 7 CICS_DICTIONARY 224
options CICS_FIELD 225
Administration window 248 clearing
Components window 248 log stream 43
Components window options collect
Help pull-down 248 batch mode 87
Logs window 248 COLLECT log collector language statement 87
Primary Menu 248 deciding which data sets to 195
Tables window 248 improving performance 95
ADMINISTRATION parameter 21 log collector messages 90
Administration window options monitoring activity 90
Other pull-down network configuration data collect job 89
DB2I option 110 sample collect job 87
ISPF/PDF option 248 vital product data collect job 89
AGGR_VALUE control table 230 collect activity
allocating libraries in the generic logon procedure monitoring 90
SYSPROC collect messages
DRL.LOCAL.EXEC 21 sample 90
allocation overview, ddname 72 using 91
APAR (Authorized Program Analysis Report) 305 collect performance
APPLY SCHEDULE clause improving 95
modifying 173 collect process 4
authorization ID, Db2 secondary 18 collect statements
Authorized Program Analysis Report (APAR) 305 changing data set name 192
automated data gathering editing 190
activating 45 IBM Z Decision Support supplied, modifying 191
AVAILABILITY_D, _W, _M 226 collect statements data set
AVAILABILITY_PARM lookup table 228 adding 191
AVAILABILITY_T 227 collect statements for log data manager
listing data sets containing 190
B Collect Statistics window 93
Collect window 28
backing up the IBM Z Decision Support database 105 collected data sets

Index 315
collected data sets (continued) considerations when running DRLJTBSR 100
viewing information about 199 continuous collector
collecting data modifying 201
through administration dialog 86 stopping 201
collecting data from a log into Db2 tables 137 working with 201
collecting data from IMS 89 Continuous Collector
collecting data from Tivoli Information Management for z/OS customizing JCL 32, 33
89 starting 33
collecting log data 86 control and common tables
collecting multiple log data sets 94 AGGR_VALUE 230
collecting network configuration data 89 AGGR_VALUE, lookup tables 228
column AVAILABILITY_PARM 228
adding to a table 167 CICS control tables
column definition CICS_DICTIONARY 224
displaying and modifying 166 CICS_FIELD 225
commands and options, administration dialog 248 common data tables 226
common data tables DAY_OF_WEEK 222
AVAILABILITY_D, _W, _M 226 description, lookup tables 228
AVAILABILITY_T 227 PERIOD_PLAN 223
EXCEPTION_T 227 SCHEDULE 223
MIGRATION_LOG 228 SPECIAL_DAY 224
retention periods 226 TIME_RES 229
summarization level 225 USER_GROUP 229
COMPonen command 254 control and lookup tables
component administering 110
adding an object 131 controlling objects that you have modified 129
creating 133 conventions
deleting 133 typeface xiv
deleting object 131 correcting corrupted data in the IBM Z Decision Support
installation database 107
definition members 73 correcting out-of-space condition in table or index space 107
installing and uninstalling 120 corrupted data in the IBM Z Decision Support database
installing online 122 correcting 107
Sample component create invoices and reports
definition member 73 running DRLNJOB3 51
description 230 create system tables 26
uninstalling 127 creating a component 133
viewing objects 130 creating a log definition 144
component definition creating a record definition 149
working with 129 creating a record procedure definition 151
component installation creating a report on a record 140
excluding and object from 132 creating a table 181
including an object 132 creating a table space 183
components creating an update definitions 183
installing 31 creating and updating system tables with a batch job 27
Components window 120 creating report groups 117
Components window options customer support
Component pull-down contacting IBM Support 305
Print list option 250 customizing
Other pull-down Continuous Collector JCL 32, 33
DB2I option 110 DRLEINI1 21
ISPF/PDF option 249 generic logon procedure 21
Space pull-down 30 JCL sample jobs 27
concatenation customizing Usage and Accounting Collector
of log data sets 195 execute DRLNINIT 46
concatenation of log data sets 195
configuration options
DASD-only log stream 60
D
DRLJSMFO 58 DASD-only log streamRETPD
DRLJSMFX 58 defining 60
sample members 58 data
configuring collecting from IBM Tivoli Information Management for
DataMover 37, 43 z/OS 89
configuring SMF Extractor 34, 40 collecting from IMS 89

316 IBM Z Decision Support : Administration Guide and Reference

data backup, incremental-image or full-image 106 Db2 (continued)
data collecting subsystem name dialog parameter 64
batch collect 90 tools 110
IMS 89 Db2 concepts
data from IBM Tivoli Information Management for understanding 96
z/OS Db2 High Performance Unload
collecting 89 integration 163
data in tables Db2 High Performance Unload utility
working with 154 running 164
data security sample control statement 164
controlling 96 Db2 tables
initializing 20 collecting data from a log into 137
Data Selection window 28 Db2 utility
data set RUNSTATS 156
prefix dialog parameter 66 DB2I
saving a table definition in 181 concepts 97
data sets DB2I Primary Option Menu 110
deciding which to collect 195 IBM Z Decision Support interaction 97
data sets collected secondary authorization IDs 20
viewing list 135 statistics 108
data tables, common tools 110
AVAILABILITY_D, _W, _M 226 DB2I command 254
AVAILABILITY_T 227 DCOLLECT records 244
EXCEPTION_T 227 DEBUG parameter 21
MIGRATION_LOG 228 deciding which log data sets to collect 195
retention periods 226 DEFINE LOG log collector language statement 3, 76
summarization level 225 DEFINE RECORD
database log collector language statement 3
access 109 DEFINE RECORD log collector language statement 76
administration 96 DEFINE UPDATE
backing up 105, 106 log collector language statement 3
error recovery 107 DEFINE UPDATE log collector language statement 77
initialization 20 defining objects, overview 73
introduction 6 defining reports 79
monitoring size 108 defining table spaces and indexes using the GENERATE
name dialog parameter 64 statement 78
security 17, 18, 109 defining updates and views 78
tools 110 definition members
database access component definitions 73
monitoring 109 DRLxxxx.SDRLDEFS library 75
database backup feature 75, 76
determining when 106 installation order 75
database security log 76
maintaining 109 record 76
DataMover report 79
configuring 37, 43 Sample component definition member 75
started task 37, 44 table and update definition members 77
tailoring 37, 43 table space 76
testing 37, 44 deleting a component 133
unpacking 37, 43 deleting a log data set 136
DataSplitter and SMF Extractor deleting a log definition 145
introduction 9 deleting a record definition 150
date set deleting a record procedure definition 152
viewing dump 199 deleting a table index 169
DAY_OF_WEEK control table 222 deleting a table or view 182
Db2 deleting an abbreviation from an update definition 173
data sets prefix dialog parameter 66 deleting an object from a component 131
Db2 plan name for TDS 64 deleting an update definition 184
how IBM Z Decision Support uses 97 deleting information about a log data set 194
locking and concurrency 108 deleting the information about a log data set 199, 201
messages detail tables
during system table creation 26 AVAILABILITY_T 227
performance 20 EXCEPTION_T 227
statistics 108 MIGRATION_LOG 228

Index 317
determining partitioning mode and keys 31 DRLJCOLL sample collect job 87
determining when to back up the IBM Z Decision Support DRLJCOVP network VPD collect job 89
database 106 DRLJEXCE problem record job 118
dialog DRLJLDMC
commands 254 setting the parameters for job 197
Dialog Parameters window DRLJLDMC collect job
when QMF is not used 62 parameters it uses 195
DRLEINI1 initialization exec 21 DRLJLDML
language options 66 job step, using 187
parameters 23, 26 sample job 188
preparing 21 setting the parameters for 189
dialog parameters DRLJLDML sample job 188
variables and fields 63 DRLJPURG purge job 103
Dialog Parameters DRLJRFT report format table 89
window 23 DRLJRUNS job
Dialog Parameters window RUNSTATS utility 108
overview 61, 203 DRLJSMFO
QMF not used 62 SMF Extractor control file 58
when QMF is used 61 DRLJSMFX
DISPLay RECORD record_type command 254 SMF Extractor startup procedure 58
DISPLay REPort report_ID command 254 DRLKEYS view on Db2 catalog 221
DISPLay report_ID command 254 DRLLDM_COLLECTSTMT
DISPLay TABLE table_name command 254 system table 206
DISPLay table_name command 254 DRLLDM_LOGDATASETS
displaying a view definition 180 system table 206
displaying and adding a table index 167 DRLLOGDATASETS
displaying and editing the purge condition of a table 174 system table 207
displaying and modifying a column definition 166 DRLLOGDATASETS system table 93
displaying and modifying a table or index space 176 DRLLOGS
displaying and modifying update definitions of a table 169 system table 208
displaying log statistics 138 DRLNINIT
displaying the contents of a log 139 executing 46
displaying the contents of a table 154 DRLNJOB2
displaying update definitions associated with a record 149 processing SMF data, using 49
distribution clause DRLOBJECT_DATA view on Q.OBJECT_DATA 221
modifying 173 DRLPURGECOND
documentation system table 209
IBM Z Decision Support 309 DRLRECORDPROCS
DRL.LOCAL.CHARTS 111 system table 209
DRL.LOCAL.DEFS definitions library 67 DRLRECORDS
DRL.LOCAL.EXEC, allocating 21 system table 210
DRL.LOCAL.REPORTS 111 DRLREP ddname, tabular reports data set 111
DRL.LOCAL.USER.DEFS definitions library 67 DRLREPORT_ATTR system table 218
DRLCHARTS system table 215 DRLREPORT_COLUMNS system table 219
DRLCOLUMNS view on Db2 catalog 221 DRLREPORT_QUERIES system table 219
DRLCOMP_OBJECTS system table 216 DRLREPORT_TEXT system table 219
DRLCOMP_PARTS system table 217 DRLREPORT_VARS system table 220
DRLCOMPONENTS system table 216 DRLREPORTS system table 217
DRLEINI1 listing 61 DRLRPROCINPUT system table 210
DRLELDMC DRLSEARCH_ATTR system table 220
sample job 195 DRLSEARCHES system table 221
DRLESTRA command 254 DRLSECTIONS
DRLEXPRESSIONS system table 211
system table 83, 205 DRLTABAUTH view on Db2 catalog 221
DRLFIELDS DRLTABLEPART view on Db2 catalog 221
system table 205 DRLTABLES view on Db2 catalog 221
DRLGROUP_REPORTS system table 217 DRLTABLESPACE view on Db2 catalog 221
DRLGROUPS system table 217 DRLUPDATECOLS
DRLINDEXES view on Db2 catalog 221 system table 211
DRLINDEXPART view on Db2 catalog 221 DRLUPDATEDISTR
DRLJBATR batch reporting job 112 system table 211
DRLJCOIM DRLUPDATELETS
IMS collect job 89 system table 212
DRLJCOIN collect job 89 DRLUPDATES system table 212

318 IBM Z Decision Support : Administration Guide and Reference

DRLUSER_GROUPREPS 222 generating problem records in batch 118
DRLUSER_GROUPS 222 generic logon procedure, customizing 21
DRLUSER_REPORTATTR 222 graphic reports
DRLUSER_REPORTCOLS 222 data set ddname, ADMGDF
DRLUSER_REPORTQRYS 222 allocation overview 72
DRLUSER_REPORTS 222 dialog parameter description 68
DRLUSER_REPORTTEXT 222
DRLUSER_REPORTVARS 222
DRLUSER_SEARCHATTR 222
H
DRLUSER_SEARCHES 222 hardware
DRLVIEWS view on Db2 catalog 221 prerequisites 13
DRLvrm.SDRLDEFS header fields
naming convention for members 80 working with 143
DRLVRM.SDRLRENU HELP command 254
naming convention for members 80 hub 17, 34
DRLxxx.SDRLDEFS definitions library hub and spoke 17
definition members 75
DRLxxx.SDRLEXEC, allocating 21
DRLxxx.SDRLLOAD, allocating in the logon procedure 21 I
DSNxxx.SDSNLOAD, allocating in the logon procedure 21
IBM Support 305
dump data set
IBM Z Decision Support
viewing 199, 200
administration dialog windows
DYNAMNBR
System Tables window 26
setting the value 197
Administration window options 248
component installation 73
E data flow 4
data sets 15
editing data sets prefix dialog parameter 67
object definition 131 database administration 96
editing the collect statements 190 database, introduction to 6
editing the contents of a table 155 feature installation 54
EREP installation
records shipped with IBM Z Decision Support 245 data sets 15
errors, recovering from database 107 database security 17
EXCEPTION_T detail table 227 Db2 database initialization 20
exceptions personal dialog parameters 23
reviewing 117 QMF setup 24
exceptions and problem records 117 test 28
excluding an object from a component installation 132 introducing 1
exporting table data to an IXF file 159 migration 13
objects overview 73
F performance features 2
Primary Menu options 248
features, IBM Z Decision Support performance record definitions shipped with IBM Z Decision Support
definition member description 235
record 76 IBM Z Decision Support administration dialog windows
update and view 78 Administration window 23
installation with base 15 Data Selection window 28
flow of IBM Z Decision Support 4 Dialog Parameters window 61, 62
Logs window 28
Primary Menu 23
G system window 23
GDDM IBM Z Decision Support definition members
allocating load library 21 naming convention 80
GDDM-PGF IBM Z Decision Support dialog options 248
formats data set 67 IBM Z Decision Support performance features
local formats data set 67 introduction 2
nicknames, ADMDEFS ddname 111 IBM Z Decision Support Primary Menu 23
GDDM.SADMMOD, allocating in the logon procedure 21 IBM Z Decision Support tables
GENERATE statement printing list 180
defining table spaces and indexes 78 IBM Z Decision Support Version variable format 74
GENERATE_KEYS 214 IBM Z Workload Scheduler
GENERATE_PROFILES 213 records shipped 246

Index 319
importing the contents of an IXF file to a table 159 K
improving collect performance 95
including an object in a component installation 132 Key Performance Metrics components
index space introduction 8
displaying and modifying 176
making changes 177
out of space 107
L
index space definitions 30 language-dependent data sets 15
index space, out of space condition 107 library allocation in the generic logon procedure
Indexes window options STEPLIB
Utilities pull-down DRLxxx.SDRLLOAD 21
Run Db2 REORG utility 97 SYSEXEC 21
installation library definition members, DRLxxx.SDRLDEFS 75
base product and feature installation 15, 28 listing
DRLEINI1 listing, variables 61 subset of tables in the Tables window 181
hardware prerequisites 13 listing a subset of tables in the Tables window 181
software prerequisites 13 listing the log data sets to be collected 192
installation prerequisites 13 loading tables 160
installation reference 60 local data sets 15
installing local definitions data set dialog parameter 67
feature (separate SMP/E job) 54 local messages data set dialog parameter 68
Usage and Accounting Collector 46 local user definitions data set dialog parameter 67
installing a component 120 LOcate argument command 255
installing and uninstalling a component 120 locking and concurrency 108
installing components 31 log and record definitions
installing IBM Z Decision Support working with 134
determining partitioning mode and keys 31 log and record procedures 4
installing components 31 log collector
reviewing results of SMP/E installation 15 introduction 3
installing IBM Z Decision Support features modifying statements 189
separately 54 system tables 205
installing other IBM Z Decision Support systems 53 log collector language
Installing SMF Extractor 33, 40 COLLECT 87
installing the component in batch mode 124 DEFINE LOG 3, 76
installing the component online 122 DEFINE RECORD 76
installing Usage and Accounting Collector DEFINE UPDATE 77
DRLNJOB1 48 SQL 73
DRLNJOB3 (DRLCMONY), running 51 SQL CREATE 77
JCL log data
customizing Usage and Accounting Collector 46 collecting 86
processing Usage and Accounting Collector subsystems log data manager
53 invoking 187
integration with Db2 High Performance Unload 163 listing log data sets containing collect statements 190
introduction to the Key Performance Metrics components 8 modifying list of log data sets to be collected 192
invoking the log data manager 187 summary of use of 186
ISPF log data manager option
ISPF.PROFILE 21 working with 186
ISPF command 254 log data set
IXF adding for collection 194
exporting table data to 159 changing the retention period of information 199
IXF file deleting 136
importing contents to a table 159 deleting information about 194, 199, 201
modifying log ID 193
J recording for re-collection 194
recording to be collected again 201
JCL viewing unsuccessfully collected 200
Continuous Collector 32, 33 log data sets
JCL sample jobs concatenation of 195
customizing 27 listing sets to be collected 192
job statement information dialog parameter 68 modifying list of successfully collected 198
job step for recording a log data set for collection 187 modifying the list of unsuccessfully collected 200
viewing information about successfully collected 199
viewing list collected 135
log definition

320 IBM Z Decision Support : Administration Guide and Reference

log definition (continued) modifiable area of DRLEINI1 61
creating 144 modifying a distribution clause 173
deleting 145 modifying an apply schedule clause 173
viewing and modifying 142 modifying IBM Z Decision Support supplied collect
log definitions statements 191
defining a log 76 modifying log collector statements 189
introduction 3 modifying the continuous collector 201
working with 142 modifying the list of successfully collected log data sets 198
log ID modifying the list of unsuccessfully collected log data sets
adding collect statements data set 191 200
log statistics modifying the log ID for a log data set 193
displaying 138 monitoring collect activity 90
log stream monitoring database access 109
clearing 43 monitoring size of the IBM Z Decision Support database 108
define a DASD-only log stream 60 monitoring table space requirements
logon procedure, customizing 21 calculating, and 98
logs multiple IBM Z Decision Support , installing 53
working with the contents of 135 multiple log data sets
LOGS command 255 collecting 94
Logs window options
Log pull-down
Exit option 251
N
Print list option 251 naming convention for IBM Z Decision Support definition
Save definition option 251 members 80
Other pull-down naming convention for members of DRLvrm.SDRLDEFS 80
DB2I option 110 naming convention for members of DRLVRM.SDRLRENU 80
ISPF/PDF option 251 navigation-administration dialog options and commands 248
View pull-down network
All option 252 collecting configuration data 89
Some option 252 network configuration data
LOGSTAT, log data set statistics 93, 138 collecting 89
lookup and control tables network data collect job 89
administering 110 nonsummarized data tables 227, 228
AGGR_VALUE 230
AGGR_VALUE, lookup tables 228
AVAILABILITY_PARM 228 O
CICS control tables
object
CICS_DICTIONARY 224
excluding from a component installation 132
CICS_FIELD 225
including in a component installation 132
common data tables 226
object definition
DAY_OF_WEEK 222
viewing or editing 131
description, lookup tables 228
object definitions 73
PERIOD_PLAN 223
objects
SCHEDULE 223
controlling 129
SPECIAL_DAY 224
overview 73
TIME_RES 229
viewing in a component 130
USER_GROUP 229
online publications
accessing xiii
M OPC/ESA
records shipped 246
maintaining database security 109 opening a table to display columns 165
making changes to an index space 177 operating routines
making table space parameter changes that do not require setting up 86
offline or batch action 179 options and commands, administration dialog 248
manuals out of space condition
IBM Z Decision Support 309 correcting 107
marking objects user-modified 129 output options for reports 111
messages overview of defining objects 73, 87
collect 90 overview of Dialog Parameters window 61, 203
Db2 overview of IBM Z Decision Support data flow 4
system table creation 26
migration instructions 13
migration of objects, using VERSION variable 74
MIGRATION_LOG detail table 228

Index 321
P R
parameters RACF
setting for job DRLJLDMC 197 records shipped 246
table space reporting 99 recalculating the content of a table 157
parameters for table space reporting 99 Receiving raw SMF records from the SMF Extractor
partitioning mode and keys introduction 10
determining 31 record
PDF command 255 creating a report 140
performing routine data collection 90 record definition
PERIOD_PLAN control table 223 creating 149
prefix for all other tables dialog parameter 64 deleting 150
prefix for system tables dialog parameter 64 viewing and modifying 146
prerequisites working with sections 148
software 13 record definition fields
Primary Menu options working with 147
Options pull-down record definitions
Dialog parameters option 63 DEFINE RECORD log collector language statement 76
printed reports from batch 112 definition members 76, 79
Printer line count per page dialog parameter 66 introduction 3, 76
printing a list of tables IBM Z Decision Support tables 180 record definitions shipped with IBM Z Decision Support
problem determination, IBM Support DCOLLECT 244
determining business impact 305 EREP 245
problem records IBM Z Workload Scheduler 246
administering 117 IMS SLDS 242
generating 117 OPC 246
procedures SMF 236
log and record 4 VM accounting 246
processing SMF data VMPRF 247
using DRLNJOB2 (DRLCDATA and DRLCACCT) 49 record definitions in a log
processing Usage and Accounting Collector subsystems 53 working with 145
publications Record Definitions window options
accessing online xiii Other pull-down
IBM Z Decision Support 309 DB2I option 110
pull-down options ISPF/PDF option 251
Administration window 248 record procedure definition
Components window 248 creating 151
Logs window 248 viewing and modifying 150
Primary Menu 248 record procedure definitions
Tables window 248 deleting 152
purge condition recording a log data set
displaying and editing 174 job step for 187
Purge utility 103 recording a log data set for re-collection 194
purging a table 160 recording a log data set to be collected again 201
purging data 103 records
Linux on zSeries 245
recovering from database errors 107
Q reference, installation 60
Q.OBJECT_DATA QMF control table, view of 221 Reorg/Discard utility 101
QMF report
batch reporting 117 creating on a record 140
data sets prefix dialog parameter 67 report definition language, defining report groups 79
initialization 24 report format table, DRLJRFT 89
language option dialog parameter 65 reporting dialog
query 24 introduction 7
query, importing 24 reporting dialog mode dialog parameter 66
setup 24 reports
view on objects table 221 PRA002 257
QMF command 255 PRA003 258
QMFxxx.SDSQLOAD, allocating in the logon procedure 21 PRA004 259
query reports and report groups
modifying to eliminate report variables 112 adding to report group 117
typical report 112 administering 111
administration 112, 116

322 IBM Z Decision Support : Administration Guide and Reference

reports and report groups (continued) sample job
batch creation 114 DRLELDMC 195
creating groups 117 DRLJLDML 188
customizing for batch processing 112 SAMPLE log type
defining 79 collecting log data 86
examples 79 saved charts data set dialog parameter 68
graphic reports 111 saved reports data set dialog parameter 68
output options 111 saved reports, batch creation 116
print options 111 saving a table definition in a data set 181
printing or saving in batch 112 SCHEDULE control table 223
QMF batch reporting 117 secondary authorization IDs
query example 112 security without 19
Reports window 28 sections in a record definition
running in batch 111, 114 working with 148
saved reports 111 security
saving in batch 112, 116 without secondary authorization IDs 19
REPORTs command 255 security without secondary authorization IDs 19
REPORTS parameter 21 security, database
requirements secondary authorization IDs 18
software 13 setting the DYNAMNBR value 197
RESET parameter 21 setting the parameters for job DRLJLDMC 197
retention periods, common data tables 226 setting the parameters for job DRLJLDML 189
RETPD severity
DASD-only log stream 60 contacting IBM Support 305
Review the SID parameter 57 determining business impact 305
Review your SYS settings 57 show TDS environment data 65
reviewing Db2 parameters 30 showing the size of the table 156
reviewing exceptions and generating problem records 117 SLDS records 242
reviewing table space profiles prior to installation 128 SMF Configuration 57
reviewing the GENERATE statements for table spaces, SMF Extractor
tables, and indexes 129 configuring 34, 40
reviewing the results of the SMP/E installation 15 DRLJSMFO 58
routine data collection DRLJSMFX 58
performing< 90 installing 33, 40
routines introduction 9
performing data collection 90 SMF records 236
running Db2 High Performance Unload utility 164 SMF_VPD data collect 89
running DRLJTBSR SMP/E installation
considerations 100 reviewing results 15
running DRLNJOB3 to create invoices and reports 51 software
running reports in batch 111 prerequisites 13
RUNSTATS utility SOrt column_name|position ASC|DES command 255
DRLJRUNS job 108 SPECIAL_DAY control table 224
spoke 17
Spoke 40
S SQL ID to use (in QMF) dialog parameter 65
sample collect messages 90 SQL log collector language statement 73
Sample component SQLMAX dialog parameter 66
component definition member 73 started task
description 230 DataMover 37, 44
object definition members 73 starting
Sample Report 1 233 Continuous Collector 33
Sample Report 2 234 stop the continuous collector 201
Sample Report 3 235 storage group default dialog parameter 64
SAMPLE_H, _M tables 231 subset of tables
SAMPLE_USER lookup table 232 listing in the Tables window 181
Sample component reports successfully collected data sets
introduction 232 modifying list of 198
sample configuration members 58 Support
sample configurations contacting IBM 305
DASD-only log stream 60 describing problems 305
DRLJSMFO 58 determining business impact 305
DRLJSMFX 58 submitting problems 305
sample JCL jobs 27 support information 305

Index 323
supported products and releases System Tables window 26, 54
software prerequisites 13 system window
SYSOUT class (in QMF) dialog parameter 65 IBM Z Decision Support administration dialog windows
SYSPROC system window 23
DRL.LOCAL.EXEC 21 systems, installing other IBM Z Decision Support 53
SYStem command 255
system table
DRLEXPRESSIONS 83, 205
T
DRLFIELDS 205 table
system tables adding a column 167
log collector 205 creating 181
system tables and views deleting 182
creating system tables 26 deleting index 169
dialog system tables 215 displaying and adding index 167
DRLCHARTS 215 displaying and editing purge condition of 174
DRLCOLUMNS 221 displaying and modifying 169
DRLCOMP_OBJECTS 216 displaying contents of 154
DRLCOMP_PARTS 217 editing contents of 155
DRLCOMPONENTS 216 opening to display columns 165
DRLGROUP_REPORTS 217 purging 160
DRLGROUPS 217 recalculating contents of 157
DRLINDEXES 221 table access 185
DRLINDEXPART 221 table and update definitions
DRLKEYS 221 creating
DRLLDM_COLLECTSTMT 206 system tables 26
DRLLDM_LOGDATASETS 206 definition members 77
DRLLOGDATASETS 93, 207 introduction 77
DRLLOGS 208 IXF files, importing 159
DRLOBJECT_DATA 221 lookup and control tables 110
DRLPURGECOND 209 modifying an APPLY SCHEDULE clause 173
DRLRECORDPROCS 209 TABle command 255
DRLRECORDS 210 table data
DRLREPORT_ATTR 218 exporting to an IXF file 159
DRLREPORT_COLUMNS 219 table definition
DRLREPORT_QUERIES 219 saving in a data set 181
DRLREPORT_TEXT 219 table definitions
DRLREPORT_VARS 220 introduction 4
DRLREPORTS 217 table space
DRLRPROCINPUT 210 backing up 106
DRLSEARCH_ATTR 220 creating 183
DRLSEARCHES 221 definition members 76
DRLSECTIONS 211 displaying and modifying 176
DRLTABAUTH 221 introduction 7
DRLTABLEPART 221 making parameter changes that do not require offline or
DRLTABLES 221 batch action 179
DRLTABLESPACE 221 out of space 107
DRLUPDATECOLS 211 table space definitions 30
DRLUPDATEDISTR 211 table space profiles
DRLUPDATELETS 212 reviewing prior to installation 128
DRLUPDATES 212 working with 128
DRLUSER_GROUPREPS 222 table space reporting
DRLUSER_GROUPS 222 parameters 99
DRLUSER_REPORTATTR 222 table space, out of space condition 107
DRLUSER_REPORTCOLS 222 table spaces
DRLUSER_REPORTQRYS 222 understanding 97
DRLUSER_REPORTS 222 table spaces, tables and indexes
DRLUSER_REPORTTEXT 222 reviewing the GENERATE statements 129
DRLUSER_REPORTVARS 222 table summarization levels, common 225
DRLUSER_SEARCHATTR 222 tables
DRLUSER_SEARCHES 222 administering user access to 185
DRLVIEWS 221 unloading and loading 160
GENERATE_KEYS 214 tables and update definitions
GENERATE_PROFILES 213 working with 153
updating system tables 54 tables and views

324 IBM Z Decision Support : Administration Guide and Reference

tables and views (continued) tables, control and common (continued)
GENERATE_PROFILES 213 description, lookup tables 228
tables and views, system PERIOD_PLAN 223
creating system tables 26 SCHEDULE 223
dialog system tables 215 SPECIAL_DAY 224
DRLCHARTS 215 TIME_RES 229
DRLCOLUMNS 221 USER_GROUP 229
DRLCOMP_OBJECTS 216 tables, control and lookup
DRLCOMP_PARTS 217 administering 110
DRLCOMPONENTS 216 tabular reports, DRLREP ddname 111
DRLGROUP_REPORTS 217 tailoring
DRLGROUPS 217 DataMover 37, 43
DRLINDEXES 221 tech note
DRLINDEXPART 221 migration instructions 13
DRLKEYS 221 temporary data sets prefix dialog parameter 67
DRLLOGDATASETS 93 testing
DRLOBJECT_DATA 221 DataMover 37, 44
DRLREPORT_ATTR 218 testing component
DRLREPORT_COLUMNS 219 verify proper installation 127
DRLREPORT_QUERIES 219 testing the component to verify its proper installation 127
DRLREPORT_TEXT 219 the DRLJLDMC collect job and the parameters it uses 195
DRLREPORT_VARS 220 TIME_RES lookup table 229
DRLREPORTS 217 timestamp tables
DRLSEARCH_ATTR 220 AVAILABILITY_T 227
DRLSEARCHES 221 EXCEPTION_T 227
DRLSECTIONS 211 typeface conventions xiv
DRLTABAUTH 221
DRLTABLEPART 221
DRLTABLES 221
U
DRLTABLESPACE 221 understanding Db2 concepts 96
DRLUPDATECOLS 211 understanding how IBM Z Decision Support uses Db2 97
DRLUPDATEDISTR 211 understanding how IBM Z Decision Support uses Db2 locking
DRLUPDATELETS 212 and concurrency 108
DRLUPDATES 212 understanding table spaces 97
DRLUSER_GROUPREPS 222 uninstalling
DRLUSER_GROUPS 222 component 127
DRLUSER_REPORTATTR 222 uninstalling a component 127
DRLUSER_REPORTCOLS 222 unloading and loading tables 160
DRLUSER_REPORTQRYS 222 unloading tables 160
DRLUSER_REPORTS 222 unpacking
DRLUSER_REPORTTEXT 222 DataMover 37, 43
DRLUSER_REPORTVARS 222 update definition
DRLUSER_SEARCHATTR 222 adding an abbreviation 172
DRLUSER_SEARCHES 222 creating 183
DRLVIEWS 221 deleting 184
GENERATE_KEYS 214 deleting an abbreviation 173
updating system tables 54 Update Definition window 172
tables naming standard, common 225 update definitions
Tables Window APPLY SCHEDULE clause 173
listing a subset of tables 181 definition member 78
Tables window options displaying 149
Other pull-down displaying and modifying 169
ISPF/PDF option 252 introduction 3, 77
Table pull-down Usage and Accounting Collector
Exit option 253 installing 46
tables, control and common introduction 11
AGGR_VALUE 230 USER_GROUP lookup table 229
AGGR_VALUE, lookup tables 228 using collect messages 91
AVAILABILITY_PARM 228 using the DRLCHECKPOINT table 89
CICS control tables using the DRLJLDML job step 187
CICS_DICTIONARY 224 utility
CICS_FIELD 225 Purge 103
common data tables 226 Reorg/Discard 101
DAY_OF_WEEK 222

Index 325
V views and tables, system (continued)
DRLUSER_REPORTCOLS 222
variables and fields DRLUSER_REPORTQRYS 222
dialog parameters 63 DRLUSER_REPORTS 222
variables, eliminating report 112 DRLUSER_REPORTTEXT 222
verify installation DRLUSER_REPORTVARS 222
testing the component 127 DRLUSER_SEARCHATTR 222
VERSION DRLUSER_SEARCHES 222
IBM Z Decision Support variable format 74 DRLVIEWS 221
VERSION variable 74 GENERATE_PROFILES 213
view updating system tables 54
deleting 182 views on Db2 catalog tables 221
view definition views on IBM Z Decision Support system tables 221
changing a comment 180 VM accounting records 246
displaying 180 VMPRF
view definitions record definitions 247
definition member 78 VPD data collecting 89
viewing
object definition 131
viewing a list of log data sets collected 135
W
viewing and modifying a log definition 142 what's new xv
viewing and modifying a record definition 146 windows, administration dialog windows
viewing and modifying a record procedure definition 150 Administration window 7, 23
viewing objects in a component 130 Collect Statistics window 93
viewing or editing an object definitions 131 Collect window 28
viewing the dump data set 199, 200 Data Selection window 28
viewing the information about successfully collected log data Logs window 28
sets 199 Primary Menu 23
viewing the unsuccessfully collected log data set 200 Reports window 28
views and tables, system System Tables window 26, 54
creating system tables 26 system window 23
dialog system tables 215 System window 24
DRLCHARTS 215 working with a component definition 129
DRLCOLUMNS 221 working with abbreviations 172
DRLCOMP_OBJECTS 216 working with components 119
DRLCOMP_PARTS 217 working with data in tables 154
DRLCOMPONENTS 216 working with fields in a record definition 147
DRLGROUP_REPORTS 217 working with header fields 143
DRLGROUPS 217 working with log and record definitions 134
DRLINDEXES 221 working with log definitions 142
DRLINDEXPART 221 working with record definitions in a log 145
DRLKEYS 221 working with sections in a record definition 148
DRLLOGDATASETS 93 working with table space profiles 128
DRLOBJECT_DATA 221 working with tables and update definitions 153, 165
DRLREPORT_ATTR 218 working with the contents of logs 135
DRLREPORT_COLUMNS 219 working with the continuous collector 201
DRLREPORT_QUERIES 219 working with the log data manager option 186
DRLREPORT_TEXT 219
DRLREPORT_VARS 220
DRLREPORTS 217 Z
DRLSEARCH_ATTR 220
z/VM Performance Toolkit
DRLSEARCHES 221
record definitions 247
DRLSECTIONS 211
DRLTABAUTH 221
DRLTABLEPART 221
DRLTABLES 221
DRLTABLESPACE 221
DRLUPDATECOLS 211
DRLUPDATEDISTR 211
DRLUPDATELETS 212
DRLUPDATES 212
DRLUSER_GROUPREPS 222
DRLUSER_GROUPS 222
DRLUSER_REPORTATTR 222

326 IBM Z Decision Support : Administration Guide and Reference

IBM®

SC27-9055-03