Tivoli Decision Support for z/OS: CICS Performance Feature

Tivoli Tivoli Decision Support for z/OS
®
Version 1.8.1
CICS Performance Feature
Guide and Reference
SH19-6820-10
Tivoli Tivoli Decision Support for z/OS
®
Version 1.8.1
CICS Performance Feature
Guide and Reference
SH19-6820-10
Note
Before using this information and the product it supports, read the information in “Notices” on page 381.
Eleventh Edition (October 2009)
This edition applies to version 1, release 8, modification level 1 of Tivoli Decision Support for z/OS (program
number 5698-B06) and to all subsequent releases and modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 1994, 2009.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii
Chapter 3. Monitoring CICS
Performance . . . . . . . . . . . . 27
Preface . . . . . . . . . . . . . . . ix
Monitoring availability . . . . . . . . .
Monitoring CICS resource availability . . .
Monitoring file and data base usage . . . . .
Monitoring response time . . . . . . . .
Monitoring resource use . . . . . . . . .
Monitoring processor use . . . . . . . .
Monitoring storage use . . . . . . . .
Monitoring volumes and throughput . . . . .
Interpreting combined CICS and DB2 performance
data . . . . . . . . . . . . . . . .
Monitoring exception and incident data . . . .
Monitoring SYSEVENT data . . . . . . . .
Understanding CICS unit-of-work reporting . .
Examining MRO and ISC characteristics . . .
Who should read this book . . . . . . . . . ix
What this book contains . . . . . . . . . . x
Publications . . . . . . . . . . . . . . x
Tivoli Decision Support for z/OS library . . . . xi
Accessing terminology online . . . . . . . xii
Using LookAt to look up message explanations
xii
Accessing publications online . . . . . . . xiii
Ordering publications. . . . . . . . . . xiii
Accessibility . . . . . . . . . . . . . . xiii
Tivoli technical training . . . . . . . . . . xiv
Support information . . . . . . . . . . . xiv
Conventions used in this book . . . . . . . . xiv
Typeface conventions . . . . . . . . . . xiv
Changes in this edition . . . . . . . . . . xv
Part 1. CICS performance feature
Guide . . . . . . . . . . . . . . . 1
Chapter 1. Introducing the CICS
Performance feature . . . . . . . . . 3
Implementing performance management .
Defining performance objectives . . . .
Collecting performance data . . . . .
.
.
.
.
.
.
.
.
.
. 3
. 4
. 7
Chapter 2. Implementing the CICS
Performance feature . . . . . . . . . 9
Planning the implementation process . . . . . . 9
Considering which components to install . . . . 10
Evaluating the CICS monitoring component . . 13
Evaluating the CICS OMEGAMON monitoring
component . . . . . . . . . . . . . 15
Evaluating the CICS statistics component . . . 16
Evaluating the CICS transaction and unit-of-work
analysis component. . . . . . . . . . . 16
Making input data available . . . . . . . . . 16
Verifying CICS/ESA and CICS/TS requirements 16
Verifying CICS/MVS requirements . . . . . 17
Verifying OMEGAMON XE for CICS
requirements . . . . . . . . . . . . . 18
Optimizing data collection . . . . . . . . 19
Defining the operating environment . . . . . . 19
Installing the components . . . . . . . . . 20
Updating the lookup tables . . . . . . . . . 23
Updating CICS_TIMEZONES . . . . . . . 24
Updating CICS_LOOKUP_APPL . . . . . . 24
Updating CICS_LOOKUP_SYSTEM . . . . . 25
Updating other lookup tables . . . . . . . 26
Testing the installation. . . . . . . . . . . 26
Putting the feature into production . . . . . . 26
© Copyright IBM Corp. 1994, 2009
.
.
.
.
.
.
.
.
27
28
29
29
32
32
34
35
.
.
.
.
.
36
37
37
38
38
Chapter 4. Using the CICS Partitioning
feature . . . . . . . . . . . . . . . 41
Considering which components to install . . . .
Evaluating the CICS monitoring component . .
Evaluating the CICS statistics component . . .
Evaluating the CICS transaction and unit-of-work
analysis component. . . . . . . . . . .
How the CICS Partitioning feature processes CMF
data . . . . . . . . . . . . . . . . .
Data tables in the CICS Partitioning feature . . .
Naming standard for CICS Partitioning tables . .
Tables in the CICS monitoring component . . .
Tables in the CICS statistics component . . . .
Tables in the CICS transaction and unit-of-work
analysis component. . . . . . . . . . .
Environment restrictions . . . . . . . . . .
Customization considerations . . . . . . . .
41
42
44
44
44
46
47
47
47
48
48
49
Part 2. CICS performance feature
Reference . . . . . . . . . . . . . 51
Chapter 5. Data flow and Tivoli
Decision Support for z/OS objects . . . 55
Tivoli Decision Support for z/OS data flow: an
overview . . . . . . . . . . . . . . .
Record processing by the CICS Performance feature
How Tivoli Decision Support for z/OS processes
CMF data . . . . . . . . . . . . . . .
How Tivoli Decision Support for z/OS processes
dictionary data . . . . . . . . . . . .
How Tivoli Decision Support for z/OS processes
CICS data records . . . . . . . . . . .
How Tivoli Decision Support for z/OS processes
CICS/ESA statistics. . . . . . . . . . .
55
58
62
66
67
68
iii
Chapter 6. Data tables, lookup tables,
and control tables . . . . . . . . . . 69
Naming standard for CICS Performance tables . . 69
Table descriptions . . . . . . . . . . . . 70
Tables in the CICS monitoring component . . . . 70
1. Basic subcomponent data tables . . . . . 71
2. DBCTL subcomponent . . . . . . . . . 94
3. DL/I subcomponent . . . . . . . . . 96
4. Basic application analysis subcomponent . . 97
5. DBCTL application analysis subcomponent
100
6. DL/I application analysis subcomponent . . 102
7. CICS/MVS subcomponent (global +
accounting) . . . . . . . . . . . . . 103
8. Basic transaction subcomponent . . . . . 104
9. DBCTL transaction subcomponent . . . . 107
10. DL/I transaction subcomponent . . . . . 109
11. Basic application user subcomponent . . . 111
12. DBCTL application user subcomponent . . 114
13. DL/I application user subcomponent . . . 116
14. CICS TS Transaction Resources
subcomponent . . . . . . . . . . . . 117
15. CICS TS Enterprise Java Beans
subcomponent . . . . . . . . . . . . 120
16. CICS Resource Manager Interface
subcomponent . . . . . . . . . . . . 121
Tables in the CICS OMEGAMON monitoring
component . . . . . . . . . . . . . . 124
1. File and Database subcomponent data tables 124
2. File and Database Application subcomponent
data tables . . . . . . . . . . . . . 127
3. File and Database Transaction subcomponent
data tables . . . . . . . . . . . . . 127
4. File and Database Application User
subcomponent data tables . . . . . . . . 128
5. File and Database Detailed usage
subcomponent data tables . . . . . . . . 129
Tables in the CICS statistics component. . . . . 133
CICS_AVAIL_T . . . . . . . . . . . . 133
CICS_AVAIL_D,_W . . . . . . . . . . 134
CICS_MVSTCB_D . . . . . . . . . . . 135
CICS_MVSTCB_H . . . . . . . . . . . 135
CICS_MVSTCB_RES_D . . . . . . . . . 136
CICS_MVSTCB_RES_H . . . . . . . . . 137
CICS_PIPELINE_T . . . . . . . . . . 137
CICS_DOCT_RES_D . . . . . . . . . . 138
CICS_DOCT_RES_H . . . . . . . . . . 139
CICS_S_AUTO_TERM_T . . . . . . . . 140
CICS_S_AUTO_TERM_D . . . . . . . . 142
CICS_S_CFDT_GREQ_T . . . . . . . . . 143
CICS_S_CFDT_GREQ_D. . . . . . . . . 144
CICS_S_CFDT_SERV_T . . . . . . . . . 145
CICS_S_CFDT_SERV_D . . . . . . . . . 147
CICS_S_CFDT_STOR_T . . . . . . . . . 150
CICS_S_CFDT_TBAC_T . . . . . . . . . 150
CICS_S_CFDT_TBAC_D . . . . . . . . . 151
CICS_S_DB2CONN_T . . . . . . . . . 152
CICS_S_DB2CONN_D . . . . . . . . . 155
CICS_S_DB2ENTRY_T . . . . . . . . . 157
CICS_S_DB2ENTRY_D . . . . . . . . . 159
CICS_S_DBCTL_T . . . . . . . . . . . 160
CICS_S_DBCTL_D. . . . . . . . . . . 162
iv
CICS_S_DISPATCH_T .
CICS_S_DISPATCH_D .
CICS_S_DLI_T . . . .
CICS_S_DLI_D . . . .
CICS_S_DSPOOL_T . .
CICS_S_DSPOOL_D . .
CICS_S_DUMP_T . . .
CICS_S_DUMP_D . . .
CICS_S_ENQUE_MGR_T
CICS_S_ENQUE_MGR_D
CICS_S_ENTBEANS_T,_D
CICS_S_FEPI_T. . . .
CICS_S_FEPI_D . . .
CICS_S_FILE_T. . . .
CICS_S_FILE_D . . .
CICS_S_GLB_TCPIP_T .
CICS_S_GLB_TCPIP_D .
CICS_S_GLBURIMAP_T.
CICS_S_GLBURIMAP_D
CICS_S_GLOBAL_T . .
CICS_S_GLOBAL_D . .
CICS_S_INTERCOM_T .
CICS_S_INTERCOM_D .
CICS_S_JOURNAL_T. .
CICS_S_JOURNAL_T2 .
CICS_S_JOURNAL_D .
CICS_S_JOURNAL_D2 .
CICS_S_JVM_PROF_T,_D
CICS_S_JVM_PROG_T,_D
CICS_S_JVMPOOL_T,_D
CICS_S_LOGSTREAM_T
CICS_S_LOGSTREAM_D
CICS_S_LSR_POOL_T .
CICS_S_LSR_POOL_D .
CICS_S_LSRP_FILE_T .
CICS_S_LSRP_FILE_D .
CICS_SMD_SUBP_D . .
CICS_SMD_SUBP_H . .
CICS_S_MONITOR_T .
CICS_S_MONITOR_D .
CICS_S_NC_LSTRUC_T .
CICS_S_NC_LSTRUC_D.
CICS_S_NCS_STOR_T .
CICS_S_PIPELINE_T . .
CICS_S_PROGRAM_T .
CICS_S_PROGRAM_D .
CICS_S_RECOV_MGR_T
CICS_S_RECOV_MGR_D
CICS_S_STOR_DOM_T .
CICS_S_STOR_DOM_D .
CICS_S_STOR_DSA_T .
CICS_S_STOR_DSA_D .
CICS_S_STOR_TASK_T .
CICS_S_STOR_TASK_D .
CICS_S_TCLASS_T . .
CICS_S_TCLASS_D . .
CICS_S_TCPIP_T . . .
CICS_S_TCPIP_D . . .
CICS_S_TERMINAL_T .
CICS_S_TERMINAL_D .
CICS_S_TRAN_T . . .
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
162
164
166
167
169
170
171
172
172
174
175
176
178
179
182
184
185
186
188
189
193
197
202
207
207
208
209
210
211
212
213
214
215
217
219
220
221
222
222
224
225
226
227
228
228
230
232
233
235
236
236
239
241
242
243
244
245
247
248
250
251
CICS_S_TRAN_D, _M . . .
CICS_S_TRANSIENT_T . . .
CICS_S_TRANSIENT_D . . .
CICS_S_TS_BPOOL_T . . .
CICS_S_TS_BPOOL_D . . .
CICS_S_TS_CF_T . . . . .
CICS_S_TS_CF_D . . . . .
CICS_S_TS_STOR_T . . . .
CICS_S_TS_STOR_D . . . .
CICS_S_URIMAP_T . . . .
CICS_S_WEBSERV_T . . . .
CICS_TCPIP_CONN_D . . .
CICS_TCPIP_CONN_H . . .
Tables in the CICS transaction and
analysis component . . . . .
CICS_T_TRAN_T . . . . .
CICSBTS_T_TRAN_T . . . .
CICSCHN_T_TRAN_T . . .
CICSDOC_T_TRAN_T . . .
CICSWEB_T_TRAN_T . . .
CICS_T_UOW_TV1 . . . .
CICS_T_UOW_TV2 . . . .
CICS_WMQ_CONN_D . . .
CICS_WMQ_CONN_H . . .
Lookup tables . . . . . . .
CICS_AVAIL_RES . . . . .
CICS_LOOKUP_APPL . . .
CICS_LOOKUP_SYSTEM . .
CICS_OMEG_FIELD . . . .
CICS_TIMEZONES . . . .
Control tables . . . . . . .
CICS_DICTIONARY . . . .
CICS_FIELD. . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
unit-of-work
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
252
253
255
257
258
259
261
263
264
265
266
267
269
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
270
270
284
286
288
290
291
291
292
293
294
294
295
296
296
299
299
299
300
Chapter 7. Reports . . . . . . . . . 301
Report format and general description . . . . .
Report ID . . . . . . . . . . . . .
Report group . . . . . . . . . . . .
Source . . . . . . . . . . . . . . .
Attributes . . . . . . . . . . . . .
Variables . . . . . . . . . . . . . .
Reports in the CICS monitoring component . . .
CICS Transaction Performance, Detail . . . .
CICS Transaction Channel Performance, Detail
CICS Application Channel Performance, Detail
CICS Application Response Times, Overview
CICS Application Response Times, Trend . . .
CICS Application Response Times, Detail . . .
CICS Application CPU Utilization, Trend . . .
CICS Application I/O Wait Times, Detail . . .
CICS Application Main Response Times, Detail
CICS Application Wait Times, Detail. . . . .
CICS Application DLI Call Utilization, Trend
CICS/MVS CMF Transaction Statistics . . . .
CICS Transaction Processor Utilization, Daily
CICS Transaction Processor Utilization, Monthly
CICS Transactions Resources Details, Daily . .
CICS Enterprise Java Beans Details, Daily . . .
Reports in the CICS OMEGAMON monitoring
component . . . . . . . . . . . . . .
301
301
301
301
302
302
302
302
304
305
307
308
309
311
312
314
316
317
318
319
319
320
321
CICS OMEGAMON database/file total requests,
hourly . . . . . . . . . . . . . . .
CICS OMEGAMON database/file total
commands, hourly . . . . . . . . . .
CICS OMEGAMON database/file avg request
response, daily . . . . . . . . . . . .
CICS OMEGAMON database/file avg
command response, daily . . . . . . . .
CICS OMEGAMON transaction database/file
requests, daily . . . . . . . . . . . .
CICS OMEGAMON transaction database/file
commands, daily . . . . . . . . . . .
CICS OMEGAMON transaction DB2 averages,
hourly . . . . . . . . . . . . . . .
Reports in the CICS statistics component . . . .
CICS Global Loader . . . . . . . . . .
CICS Global Temporary Storage . . . . . .
CICS Global VTAM . . . . . . . . . .
CICS Global DTB . . . . . . . . . . .
CICS Global IRC Batch . . . . . . . . .
CICS Transaction Usage . . . . . . . . .
CICS Program Usage . . . . . . . . . .
CICS Dynamic Storage (DSA) Usage . . . .
CICS File Statistics . . . . . . . . . .
CICS ISC/IRC Function Shipping by Connection
CICS ISC/IRC Global . . . . . . . . .
CICS ISC/IRC Mode Entries . . . . . . .
CICS ISC/IRC System Entries by Connection
CICS TS Recovery Manager . . . . . . .
CICS TS Enqueue Manager . . . . . . . .
CICS TS Logstreams . . . . . . . . . .
CICS DB2 Connection: TCB Statistics . . . .
CICS DB2 Connection: Buffer Pool Statistics . .
CICS DB2 Connection: Command Statistics . .
CICS DB2 Entries: Resource Info . . . . . .
CICS DB2 Entries: Request Statistics . . . . .
CICS DB2 Entries: Performance Statistics . . .
CICS Shared TS queue server: Buffer Pool
Statistics . . . . . . . . . . . . . .
CICS Shared TS queue server: Storage Statistics
CICS TCP/IP Global statistics . . . . . . .
CICS TCP/IP Service Statistics . . . . . .
CICS TCP/IP Service Requests Statistics . . .
CICS TCP/IP Service Requests: Daily Trend . .
CICS CFDT Server Statistics . . . . . . .
CICS CFDT Storage Statistics . . . . . . .
CICS NC Storage Statistics . . . . . . . .
CICS URIMAP Global statistics . . . . . .
CICS URIMAP Resource statistics . . . . .
CICS JVM Profile Statistics, Daily. . . . . .
CICS Transaction Processor Utilization, Daily
CICS Transaction Processor Utilization, Monthly
CICS Availability Reports . . . . . . . .
Reports in the CICS transaction and unit-of-work
analysis component . . . . . . . . . . .
CICS UOW Response Times . . . . . . .
Reports common to all components . . . . . .
CICS Exceptions . . . . . . . . . . .
CICS Incidents . . . . . . . . . . . .
322
323
324
324
325
326
327
328
328
329
330
331
332
333
334
335
336
337
338
339
341
342
343
345
346
347
349
350
351
352
353
355
356
357
358
359
360
361
361
362
363
365
366
367
368
369
369
371
371
372
322
Part 3. Appendixes . . . . . . . . 375
Contents
v
Appendix. Support information . . . . 377
Notices . . . . . . . . . . . . . . 381
Searching knowledge bases . . . .
Searching the information center .
Searching the Internet . . . .
Obtaining fixes . . . . . . . .
Receiving weekly support updates .
Contacting IBM Software Support .
Determining the business impact .
Describing problems and gathering
Submitting problems . . . . .
Trademarks .
vi
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
information
. . . . .
377
377
377
377
378
379
379
380
380
.
.
.
.
.
.
.
.
.
.
.
.
. 383
Glossary . . . . . . . . . . . . . 385
Bibliography . . . . . . . . . . . . 387
Tivoli Decision Support publications.
.
.
.
.
. 387
Index . . . . . . . . . . . . . . . 389
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Figures
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
Performance-management cycle . . . . . . 4
Organizing and presenting system performance
data . . . . . . . . . . . . . . . 8
Implementation process for the CICS
Performance feature. . . . . . . . . . 10
CICS Performance feature structure . . . . 12
Sample COLLECT job with an INCLUDE
clause . . . . . . . . . . . . . . 19
Tivoli Decision Support for z/OS
Administration window . . . . . . . . 20
Components window . . . . . . . . . 21
CICSMON Component Parts window . . . . 22
Installation Options window . . . . . . . 23
Sample fill in for the CICS_TIMEZONES
lookup table . . . . . . . . . . . . 24
Sample update to the CICS_LOOKUP_APPL
lookup table . . . . . . . . . . . . 25
Update definition supplied in subcomponent 4,
basic application analysis . . . . . . . . 25
Sample update to the
CICS_LOOKUP_SYSTEM lookup table . . . 26
Daily steps involved in using Tivoli Decision
Support for z/OS . . . . . . . . . . 26
CICS Application Response Times, Detail
report . . . . . . . . . . . . . . 29
CICS internal response-time elements . . . . 29
CICS Application Response Times, Overview
report . . . . . . . . . . . . . . 30
CICS Application Response Times, Trend
report . . . . . . . . . . . . . . 31
CICS Application Response Times, Detail
report . . . . . . . . . . . . . . 31
Example of deteriorating response time due to
increased workload . . . . . . . . . . 32
CICS Application CPU Utilization, Trend
report . . . . . . . . . . . . . . 33
CICS Transaction Processor Utilization,
Monthly report . . . . . . . . . . . 34
Dynamic Storage (DSA) Usage report . . . . 35
CICS Transaction Performance, Detail report
36
Correlating a CICS performance-monitoring
record with a DB2 accounting record . . . . 36
CICS UOW Response Times report. . . . . 39
CICS Partitioning feature structure . . . . . 42
How CMF performance records are processed
by the CICS Partitioning feature . . . . . 45
How CICS/TS transaction resource records are
processed by the CICS Partitioning feature . . 46
Overview of data flow from SMF log into
Tivoli Decision Support for z/OS . . . . . 56
Overview of data flow within Tivoli Decision
Support for z/OS . . . . . . . . . . 57
Data flow from CICS into Tivoli Decision
Support for z/OS tables and reports . . . . 61
How CMF performance records are processed 63
© Copyright IBM Corp. 1994, 2009
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
How CICS/TS transaction resource records are
processed by the CICS Performance feature . . 65
Sample JCL to run the monitoring dictionary
utility (DFHMNDUP) . . . . . . . . . 67
Example of a CICS Transaction Performance,
Detail report . . . . . . . . . . . . 303
Example of a CICS Transaction Channel
Performance, Detail report . . . . . . . 304
Example of a CICS Application Channel
Performance, Detail report . . . . . . . 306
Example of a CICS Application Response
Times, Overview report . . . . . . . . 307
Example of a CICS Application Response
Times, Trend report . . . . . . . . . 308
Example of a CICS Application Response
Times, Detail report . . . . . . . . . 309
Example of a CICS Application CPU
Utilization, Trend report . . . . . . . . 311
Example of a CICS Application Main
Response Times, Detail report . . . . . . 314
Example of a CICS Application DLI Call
Utilization, Trend report . . . . . . . . 317
Example of a CICS/MVS CMF Transaction
Statistics report . . . . . . . . . . . 318
Example of a CICS Transaction Processor
Utilization, Daily report . . . . . . . . 319
Example of a CICS Transaction Processor
Utilization, Monthly report . . . . . . . 320
Example of a CICS Transactions Resources
Details, Daily report . . . . . . . . . 321
Example of a CICS Transactions Resources
Details, Daily report . . . . . . . . . 321
Example of a CICS OMEGAMON
database/file total requests, hourly report . . 323
Example of a CICS OMEGAMON
database/file total commands, hourly report . 323
Example of a CICS OMEGAMON
database/file avg request response, daily
report . . . . . . . . . . . . . . 324
Example of a CICS OMEGAMON
database/file avg command response, daily
report . . . . . . . . . . . . . . 325
Example of a CICS OMEGAMON transaction
database/file requests, daily report . . . . 326
Example of a CICS OMEGAMON transaction
database/file commands, daily report . . . 327
Example of a CICS OMEGAMON transaction
DB2 averages, hourly report . . . . . . 328
Example of a CICS Global Loader report
329
Example of a CICS Global Temporary Storage
report . . . . . . . . . . . . . . 330
Example of a CICS Global VTAM report
331
Example of a CICS Global DTB report
331
Example of a CICS Global IRC Batch report
332
Example of a CICS Transaction Usage report 333
Example of a CICS Program Usage report
335
vii
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
viii
Example of a CICS Dynamic Storage (DSA)
Usage report . . . . . . . . . . .
Example of a CICS File Statistics report
Example of a CICS ISC/IRC Function
Shipping by Connection report. . . . .
Example of a CICS ISC/IRC Global report
Example of a CICS ISC/IRC Mode Entries
report . . . . . . . . . . . . .
Example of a CICS ISC/IRC System Entries
by Connection report . . . . . . . .
Example of a CICS TS Recovery Manager
report . . . . . . . . . . . . .
Example of a CICS TS Recovery Manager
report . . . . . . . . . . . . .
Example of a CICS TS Logstream report
Example of a CICS DB2 Connection: TCB
Statistics report . . . . . . . . . .
Example of a CICS DB2 Connection: Buffer
Pool Statistics report . . . . . . . .
Example of a CICS DB2 Connection:
Command Statistics report . . . . . .
Example of a CICS DB2 Entries: Resource
Info report . . . . . . . . . . .
Example of a CICS DB2 Entries: Requests
Statistics report . . . . . . . . . .
78.
. 336
337
. 338
339
79.
80.
. 340
81.
82.
. 341
83.
. 342
84.
. 344
345
85.
86.
. 346
87.
. 347
88.
. 349
89.
. 351
. 352
90.
91.
Example of a CICS DB2 Entries: Performance
Statistics report . . . . . . . . . . .
Example of a CICS Shared TS queue server:
Buffer Pool Statistics report . . . . . . .
Example of a CICS Shared TS queue server:
Storage Statistics report . . . . . . . .
Example of a CICS Global Statistics report
Example of a CICS URIMAP Global statistics
report . . . . . . . . . . . . . .
Example of a CICS URIMAP Global statistics
report . . . . . . . . . . . . . .
Example of a CICS JVM Profile Statistics,
Daily report . . . . . . . . . . . .
Example of a CICS Transaction Processor
Utilization, Daily report . . . . . . . .
Example of a CICS Transaction Processor
Utilization, Monthly report . . . . . . .
Example of a CICS-DB2 Connection
Availability, Daily Overview report . . . .
Example of an CICS Subsystem Availability,
Daily Trend report . . . . . . . . . .
Example of a CICS UOW Response Times
report . . . . . . . . . . . . . .
Example of a CICS Exceptions report
Example of a CICS Incidents report . . . .
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
353
354
355
356
362
364
365
366
367
368
369
370
371
372
Preface
This book describes how to use IBM® Tivoli® Decision Support for z/OS®
(hereafter referred to as Tivoli Decision Support for z/OS) and the CICS®
Performance feature to collect and report performance data generated by Customer
Information and Control System (CICS).
This book:
v Helps you understand general performance characteristics
v Describes performance issues and how they affect the level of services you can
offer users
v Guides you through the component-selection, installation, and implementation
processes
v Explores performance characteristics shown in Tivoli Decision Support for z/OS
reports so that you can analyze the characteristics of your system
The terms MVS™, OS/390, and z/OS are used interchangeably throughout this
book.
Who should read this book
The CICS Performance Feature Guide and Reference is for:
v Anyone who analyzes or monitors CICS performance
v Anyone responsible for establishing or meeting service-level objectives for CICS
user groups
v Tivoli Decision Support for z/OS administrators (primarily as a guide to feature
installation and as a reference to table and report definitions)
v Users with various backgrounds who are interested in analyzing CICS
performance data and improving CICS performance
The Tivoli Decision Support for z/OS CICS Performance feature helps you monitor
CICS, even if you have little experience with CICS. However, to make the best use
of the CICS Performance feature to improve CICS performance, you should know
CICS, the terms that are unique to CICS, and the terminology associated with
database design and performance. (If you are not familiar with CICS, refer to the
CICS General Information manual which describes the basic concepts of CICS and
introduces you to some CICS terminology.)
Also, the better you understand the interaction of processor cycles, storage, and
I/O, the easier it is to identify performance constraints. The CICS product library
(specifically the Performance Guide and the Customization Guide for either
CICS/Enterprise Systems Architecture (CICS/ESA®) or CICS/Multiple Virtual
Storage (CICS/MVS®) is the authoritative source for information about
understanding and tuning CICS performance.
Note: For information about licensed programs either required or recommended
for use with Tivoli Decision Support for z/OS, refer to the Administration
Guide and Reference.
© Copyright IBM Corp. 1994, 2009
ix
What this book contains
What this book contains
Use this book for guidance in collecting CICS-generated performance data from
SMF logs and creating the reports supplied with the CICS Performance feature.
This book explains how to create and display Tivoli Decision Support for z/OS
reports to both monitor and understand CICS performance.
This book contains the following parts:
v Use Part I, ″Guide″ for developing and executing your performance and
service-level strategy:
– Chapter 1, “Introducing the CICS Performance feature” explains basic
concepts of systems management and offers suggestions on establishing
performance objectives and service-level agreements. It also describes the
CICS Performance feature’s role in the Tivoli Decision Support for z/OS
environment.
– Chapter 2, “Implementing the CICS Performance feature” contains a
task-oriented description of how to plan for and set up the CICS Performance
feature so that useful reports and information for decision-support is available
immediately.
– Chapter 3, “Monitoring CICS Performance” describes certain issues and
concerns associated with systems management and how you can use the
Tivoli Decision Support for z/OS CICS Performance feature to explore those
issues and concerns.
– Chapter 4, “Using the CICS Partitioning feature” describes how to use the
CICS Partitioning feature and provides descriptions of the supplied data
tables.
v Use Part II, ″Reference″ for a detailed description of the CICS Performance
feature:
– Chapter 5, “Data flow and Tivoli Decision Support for z/OS objects”
describes the flow of data from log record to report (or list record), showing
Tivoli Decision Support for z/OS definitions. It also provides a simple
explanation of the supported logs, their structure, and the common fields and
conditions associated with each log. It shows how the CICS Performance
feature maps log data into tables.
– Chapter 6, “Data tables, lookup tables, and control tables” describes the
supplied data tables and updates, including columns and expressions. It
contains similar descriptions of lookup tables and control tables.
– Chapter 7, “Reports” contains examples of the CICS Performance feature
reports and shows where the data comes from.
v Use Part III, ″Appendixes″ as a reference for obtaining support for IBM software
products.
A glossary and index follow the appendix.
Publications
This section lists publications in the Tivoli Decision Support for z/OS library and
any other related documents. It also describes how to access Tivoli publications
online, how to order Tivoli publications, and how to submit comments on Tivoli
publications.
x
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Tivoli Decision Support for z/OS library
Tivoli Decision Support for z/OS library
The following documents are available in the Tivoli Decision Support for z/OS
library:
v Administration Guide and Reference, SH19-6816
Provides information about initializing the Tivoli Decision Support for z/OS
database and customizing and administering Tivoli Decision Support for z/OS.
v AS/400 System Performance Feature Guide and Reference, SH19-4019
Provides information for administrators and users about collecting and reporting
performance data generated by AS/400® systems.
v CICS Performance Feature Guide and Reference, SH19-6820
Provides information for administrators and users about collecting and reporting
performance data generated by Customer Information and Control System
(CICS).
v Distributed Systems Performance Feature Guide and Reference, SH19-4018
Provides information for administrators and users about collecting and reporting
performance data generated by operating systems and applications running on a
workstation.
v Guide to Reporting, SH19-6842
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.
v IMS Performance Feature Guide and Reference, SH19-6825
Provides information for administrators and users about collecting and reporting
performance data generated by Information Management System (IMS™).
v Language Guide and Reference, SH19-6817
Provides information for administrators, performance analysts, and
programmers who are responsible for maintaining system log data and reports.
v Messages and Problem Determination, SH19-6902
Provides information to help operators and system programmers understand,
interpret, and respond to Tivoli Decision Support for z/OS messages and codes.
v Monitoring Agent Guide, SC23-7968
Enables administrators and users to view their collected and summarized Tivoli
Decision Support for z/OS data from within the Tivoli Enterprise Portal
graphical user interface.
v Network Performance Feature Installation and Administration, SH19-6901
Provides information for network analysts or programmers who are responsible
for setting up the network reporting environment.
v Network Performance Feature Reference, SH19-6822
Provides reference information for network analysts or programmers who use
the Network Performance feature.
v Network Performance Feature Reports, SH19-6821
Provides information for network analysts or programmers who use the
Network Performance feature reports.
v Resource Accounting for z/OS, SH19-4495
Provides information for users who want to use Tivoli Decision Support for
z/OS to collect and report performance data generated by Resource Accounting
for z/OS.
v System Performance Feature Guide, SH19-6818
Preface
xi
Tivoli Decision Support for z/OS library
Provides information for performance analysts and system programmers who
are responsible for meeting the service-level objectives established in your
organization.
v System Performance Feature Reference Volume I, SH19-6819
Provides information for administrators and users with a variety of backgrounds
who want to use Tivoli Decision Support for z/OS to analyze z/OS, z/VM®,
zLinux, and their subsystems, performance data.
v System Performance Feature Reference Volume II, SH19-4494
Provides information for administrators and users with a variety of backgrounds
who want to use Tivoli Decision Support for z/OS to analyze z/OS, z/VM,
zLinux, and their subsystems, performance data.
v Usage and Accounting Collector User Guide, SC23-7966
Provides information about the functions and features of the Usage and
Accounting Collector.
v IBM Online Library z/OS Software Products Collection Kit, SK3T-4270
CD containing all z/OS documentation.
Accessing terminology online
The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available, in English only,
at the following Web site:
http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm
The IBM Terminology Web site consolidates the terminology from IBM product
libraries in one convenient location. You can access the Terminology Web site at the
following Web address:
http://www.ibm.com/ibm/terminology
Using LookAt to look up message explanations
LookAt is an online facility that lets you look up explanations for most of the IBM
messages you encounter, as well as for some system abends (an abnormal end of a
task) and codes. Using LookAt to find information is faster than a conventional
search because in most cases LookAt goes directly to the message explanation.
You can use LookAt from the following locations to find IBM message
explanations from z/OS elements and features, z/VM, VSE/ESA™, and Clusters
for AIX® and Linux®:
v The internet. You can access IBM message explanations directly from the LookAt
Web site at:
http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/
v Your z/OS TSO/E host system. You can install code on your z/OS systems to
access IBM message explanations, using LookAt from a TSO/E command line
(for example, TSO/E prompt, ISPF, or z/OS UNIX® System Services running
OMVS).
v Your Microsoft® Windows® workstation. You can install code to access IBM
message explanations on the (SK3T-4269), using LookAt from a Microsoft
Windows DOS command line.
v Your wireless handheld device. You can use the LookAt Mobile Edition with a
handheld device that has wireless access and an Internet browser (for example,
xii
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Using LookAt to look up message explanations
Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera for
Linux handheld devices.) Link to the LookAt Mobile Edition from the LookAt
Web site.
You can obtain code to install LookAt on your host system or Microsoft Windows
workstation from:
v A CD in the z/OS Collection, (SK3T-4269)
v The z/OS and Software Products DVD Collection, (SK3T-4271)
v The LookAt Web site (click Download and then select the platform, release,
collection, and location that suit your needs). More information is available in
the LOOKAT.ME files available during the download process.
Accessing publications online
IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:
http://www.ibm.com/software/tivoli/library/
Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click the Tivoli Decision Support for
z/OS link to access the product library at the Tivoli software information center.
Note: If you print PDF documents on other than letter-sized paper, set the option
in the File ” Print window that allows Adobe® Reader to print letter-sized
pages on your local paper.
Ordering publications
You can order many Tivoli publications online at the following Web site:
http://www.elink.ibmlink.ibm.com/publications/servlet/pbi.wss
You can also order by telephone by calling one of these numbers:
v In the United States: 800-879-2755
v In Canada: 800-426-4968
In other countries, contact your software account representative to order Tivoli
publications.
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, see the Accessibility Appendix in the Administration
Guide and Reference.
Preface
xiii
Tivoli technical training
Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:
http://www.ibm.com/software/tivoli/education/
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:
v Searching knowledge bases: You can search across a large collection of known
problems and workarounds, Technotes, and other information.
v Obtaining fixes: You can locate the latest fixes that are already available for your
product.
v 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 “Support
information,” on page 377.
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:
v MVS, OS/390®, and z/OS.
v VM and z/VM.
Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v 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)
v Column headings in a table
v Keywords and parameters in text
Italic
v
v
v
v
Citations (titles of books, diskettes, and CDs)
Words defined in text
Emphasis of words (words as words)
Letters as letters
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
xiv
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Typeface conventions
v Examples and code examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options
Except for editorial changes, updates to this edition are marked with a vertical bar
to the left of the change.
Changes in this edition
This edition is an update to the previous edition of the same book. No technical
changes have been added for this edition.
Preface
xv
Changes in this edition
xvi
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Part 1. CICS performance feature Guide
Chapter 1. Introducing the CICS Performance
feature . . . . . . . . . . . . . . . . 3
Implementing performance management . . . . . 3
Defining performance objectives . . . . . . . . 4
Collecting performance data . . . . . . . . . 7
Chapter 2. Implementing the CICS Performance
feature . . . . . . . . . . . . . . . . 9
Planning the implementation process . . . . . . 9
Considering which components to install . . . . 10
Evaluating the CICS monitoring component . . 13
1. Basic subcomponent . . . . . . . . 13
2. DBCTL subcomponent . . . . . . . . 13
3. DL/I subcomponent . . . . . . . . 13
4. Basic application analysis subcomponent . 13
5. DBCTL application analysis subcomponent 13
6. DL/I application analysis subcomponent
13
7. CICS/MVS subcomponent (global +
accounting) . . . . . . . . . . . . 14
8. Basic transaction subcomponent . . . . 14
9. DBCTL transaction subcomponent . . . . 14
10. DL/I transaction subcomponent . . . . 14
11. Basic application user subcomponent . . 14
12. DBCTL application user subcomponent . . 14
13. DL/I application user subcomponent . . 14
14. CICS TS transaction resources
subcomponent . . . . . . . . . . . 14
15. CICS TS enterprise Java beans
subcomponent . . . . . . . . . . . 14
16. CICS Resource Manager Interface
subcomponent . . . . . . . . . . . 15
Evaluating the CICS OMEGAMON monitoring
component . . . . . . . . . . . . . 15
1. File and Database subcomponent . . . . 15
2. File and Database Application
subcomponent . . . . . . . . . . . 15
3. File and Database Transaction
subcomponent . . . . . . . . . . . 15
4. File and Database Application User
subcomponent . . . . . . . . . . . 15
5. File and Database Detailed Usage
subcomponent . . . . . . . . . . . 15
Evaluating the CICS statistics component . . . 16
Evaluating the CICS transaction and unit-of-work
analysis component. . . . . . . . . . . 16
Making input data available . . . . . . . . . 16
Verifying CICS/ESA and CICS/TS requirements 16
CICS/ESA and CICS/TS CMF requirements
16
CICS/ESA and CICS/TS statistics
requirements . . . . . . . . . . . . 17
Verifying CICS/MVS requirements . . . . . 17
Verifying OMEGAMON XE for CICS
requirements . . . . . . . . . . . . . 18
Optimizing data collection . . . . . . . . 19
Defining the operating environment . . . . . . 19
Installing the components . . . . . . . . . 20
© Copyright IBM Corp. 1994, 2009
Updating the lookup tables . . . .
Updating CICS_TIMEZONES . .
Updating CICS_LOOKUP_APPL .
Updating CICS_LOOKUP_SYSTEM
Updating other lookup tables . .
Testing the installation. . . . . .
Putting the feature into production .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
23
24
24
25
26
26
26
.
.
.
.
.
.
.
.
.
27
27
28
29
29
32
32
34
35
.
.
.
.
.
36
37
37
38
38
Chapter 4. Using the CICS Partitioning feature
Considering which components to install . . . .
Evaluating the CICS monitoring component . .
1. Basic subcomponent . . . . . . . .
2. DBCTL subcomponent . . . . . . . .
3. DL/I subcomponent . . . . . . . .
4. Basic application analysis subcomponent .
5. DBCTL application analysis subcomponent
6. DL/I application analysis subcomponent
7. CICS/MVS subcomponent (global +
accounting) . . . . . . . . . . . .
8. CICS TS Transaction Resources
subcomponent . . . . . . . . . . .
9. CICS TS Enterprise Java Beans
subcomponent . . . . . . . . . . .
10. CICS Resource Manager Interface
subcomponent . . . . . . . . . . .
Evaluating the CICS statistics component . . .
Evaluating the CICS transaction and unit-of-work
analysis component. . . . . . . . . . .
How the CICS Partitioning feature processes CMF
data . . . . . . . . . . . . . . . . .
Data tables in the CICS Partitioning feature . . .
Naming standard for CICS Partitioning tables . .
Tables in the CICS monitoring component . . .
Tables in the CICS statistics component . . . .
Tables in the CICS transaction and unit-of-work
analysis component. . . . . . . . . . .
Environment restrictions . . . . . . . . . .
Customization considerations . . . . . . . .
41
41
42
43
43
43
43
43
43
Chapter 3. Monitoring CICS Performance . .
Monitoring availability . . . . . . . . .
Monitoring CICS resource availability . . .
Monitoring file and data base usage . . . . .
Monitoring response time . . . . . . . .
Monitoring resource use . . . . . . . . .
Monitoring processor use . . . . . . . .
Monitoring storage use . . . . . . . .
Monitoring volumes and throughput . . . . .
Interpreting combined CICS and DB2 performance
data . . . . . . . . . . . . . . . .
Monitoring exception and incident data . . . .
Monitoring SYSEVENT data . . . . . . . .
Understanding CICS unit-of-work reporting . .
Examining MRO and ISC characteristics . . .
43
43
44
44
44
44
44
46
47
47
47
48
48
49
1
2
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 1. Introducing the CICS Performance feature
IBM Tivoli Decision Support for z/OS (hereafter referred to as Tivoli Decision
Support for z/OS) is a reporting system that collects performance data logged by
computer systems, summarizes the data, and presents it in a variety of forms.
Tivoli Decision Support for z/OS consists of a base product and several optional
features that are used in systems management.
The Tivoli Decision Support for z/OS base includes:
v Interactive System Productivity Facility (ISPF) host reporting and administration
dialogs
v Log collector
v Log and record definitions for all records used by the features
Each feature provides:
v Update definitions for DATABASE 2 (DB2®) tables
v Table definitions
v Report definitions
The Tivoli Decision Support for z/OS database stores all reporting data, which
comes from several sources. For example, logs from System Management Facilities
(SMF), Resource Management Facility (RMF™), Customer Information and Control
System (CICS), and Information Management System (IMS) can be consolidated
into a single report. If you install all components of all features and set system and
subsystem data-recording parameters as recommended for each feature, you can
ensure a steady supply of data about the operation of the entire DP center.
This chapter offers suggestions on establishing performance objectives and
service-level agreements, and it also describes the CICS Performance feature’s role
in the Tivoli Decision Support for z/OS environment.
Tivoli Decision Support for z/OS assists you in performance management and
service-level management of various computer systems. The CICS Performance
feature provides reports for your use in analyzing the performance of CICS/ESA,
CICS/MVS, and CICS/TS. This section prepares you for using Tivoli Decision
Support for z/OS in practical systems analysis.
Implementing performance management
As a performance analyst, your responsibility is to satisfy users’ requirements. To
perform your duties, for example, you might:
1. Define performance objectives.
2. Gather performance data.
3. Create reports from the performance data.
Analyze performance reports to see if your objectives have been met.
Determine major constraints in the system.
Gather detailed performance data about suspected constraints.
Decide where you can afford to make trade-offs, and which resources can bear
an additional load.
8. Tune the system to improve performance.
4.
5.
6.
7.
© Copyright IBM Corp. 1994, 2009
3
Implementing performance management
9. Verify the removal of performance constraints.
Figure 1 shows the cycle of performance management.
Understand the performance objectives
Follow a measurement and evaluation plan
to monitor the system including:
— Objectives
— Resource contention
— Predictions
No
Were the performance objectives met?
Identify major resolvable
resource contention
Yes
Continue monitoring the system as planned
Devise a tuning strategy that:
— Minimizes resource use
— Expands system capacity
Identify the variables
Predict the effects
Is the proposed change
cost-effective?
No
Yes
Make the change
Figure 1. Performance-management cycle
Defining performance objectives
Before you can analyze the performance of any computing system, you must
establish a measurable criteria for performance. The purpose of performance
objectives is twofold:
v To state what is expected of the system in specific terms for each workload
category (for example, trivial versus nontrivial transactions) at distinct time
periods (for example, prime shift, off-shift, and peak periods within each shift)
v To understand and document the resources required to meet the objectives
From the nature of these two goals, establishing performance objectives is an
iterative process. Expect to update your performance objectives as the workload
changes, as resource requirements change, and as turnaround and response time
requirements change. Detailed performance objectives and detailed analysis of
4
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Defining performance objectives
system performance make such changes noticeable. They help you identify
solutions to performance problems that arise because of the changing nature of the
system workload.
Performance objectives should be realistic, in line with your budget,
understandable, and measurable. Objectives used at many organizations include:
v Acceptable response time (a duration within which some percentage of all
applications have completed)
v Average throughput levels (the total number of transactions completed within a
given time)
v System availability criteria, including mean time to failure and the durations of
down times
Such objectives define the workload for the system and determine the
requirements for data processing resources: processor speed, storage amounts,
additional software, and so on.
Presumably, users will have input to performance objectives. A mutual agreement
on acceptable performance, between the data processing and user groups in an
organization, is often formalized and called a service-level agreement. Service-level
agreements can include expectations of query response time, the transaction
throughput per day, hour, or minute, and schedules provided for batch jobs. They
list criteria for determining whether or not the system performs adequately.
Each user group may require a different level of service. If so, formalize a
service-level agreement with each user group and establish service criteria for that
user group.
Follow these steps to define performance objectives:
1. Define the terms in which to specify objectives.
The basic types of performance objectives are:
v User-oriented objectives, which reflect the way an end user would rate the
services provided by the system. These include:
– Response time for interactive work
– Turnaround time for batch work
v System-oriented objectives, which reflect the workload supported by the
system. These include:
– Batch throughput
– Interactive transaction rate
– Number of concurrent interactive users
2. Decide how to measure the objectives.
When choosing the terms in which to define your objectives, also determine
how to measure and report performance in relation to your objectives.
For user-oriented objectives, note any differences between measured objectives
and what a user sees. Times reported by measurement tools are usually
system-oriented elapsed times that do not include such delays as job output
distribution and network time.
3. Document the current workload (categories and amount) and consider:
v
v
v
v
Priority
Different time periods during which objectives and priorities vary
Resource requirements
Types of user groups (and machines) with varying objectives
Chapter 1. Introducing the CICS Performance feature
5
Defining performance objectives
v The applicable service-level agreement for the user or user group
v How to track and report each service-level agreement (for example, by
department or by user group)
You document workload categories to distinguish work for different resource
requirements, different objectives, different priorities, and so on.
Also define factors for each level of each workload category. For example,
determine factors for batch, TSO, CICS, IMS, and other subsystems. Within
each subsystem, define even more factors: batch work divided into job classes;
TSO, CICS, and IMS divided into types of transactions; all categories divided
by peak hours and off-shifts.
4. Set objectives for each workload category.
Use your documentation to state objectives for a percentage of the transactions
in a class. For example, you could state, “90% of all CICS transactions should
receive a three-second response time; 85% of all jobs in class A should receive a
one-hour turnaround time.”
While stating your objectives in these terms, also state objectives for the
remaining percentage of transactions. For example, state performance objectives
for the remaining 10% of all CICS transactions and the remaining 15% of all
jobs in class A. Set objectives for 100% of the work in the system.
Note: When setting user-oriented objectives, be sure to consider any time the
user sees that is not reflected in the measurement of the objective. For
example, if trivial transactions require a four-second response time, you
might set the objective to three seconds to account for network delays
not reflected in response-time measurements.
5. Measure and document resources used by each workload category.
To measure the resources used by different workload categories, choose the
means by which to measure resource consumption. For example, measure and
document service units, seconds, number of events, and so on.
Essentially, you want to identify the amounts of processor, storage, and I/O
resources required for each workload category. This resource data further
defines the workload categories; from this data, you can set resource limits for
each category (for example, one processor minute for each job in job class X).
6. Measure resources used against objectives.
If measured objectives meet defined objectives, simply monitor system
performance. If measured objectives do not meet defined objectives, analyze the
system to identify performance constraints and potential resource trade-offs.
Table 1 summarizes the basic items in an initial service-level agreement.
Table 1. Sample performance objectives in a service-level agreement
System type
Transactions per minute
Internal response time
CICSA
100
5 seconds
CICSB
200
5 seconds
TSO
—
—
TSOC
—
—
In the sample, you promise CICSA users a five-second response time, provided
that the load is less than 100 transactions per minute. You also promise CICSB
users a five-second response time. Because CICSB users do more profitable work,
the agreed limit is 200 transactions per minute.
6
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Defining performance objectives
This sample agreement is simple; a real agreement would probably specify groups
of transactions rather than whole CICS regions, percentiles rather than averages for
response time, and terminal rather than internal response time.
Remember that certain qualifications exist. For example, if users submit more
work, it runs, but with increased response time. Also, this agreement is valid only
for transactions already in production. This restriction prevents users from adding
more work to the batch applications under the same service-level agreement.
You can refine the service-level agreement over time. You can include objectives for
such items as system availability, reliability, and security. But the main point is to
identify measurable objectives.
For more detailed information about defining performance objectives and
formalizing them in a service-level agreement, refer to the CICS Performance Guide.
Collecting performance data
Before you can analyze data to understand CICS characteristics, you must first
collect the data. All IBM systems and subsystems provide data on how well they
perform.
To produce usable information from data and present only needed data to users,
you use several products. These products gather performance and management
data and write that data to records. You customize these products to gather only
the data needed to write the necessary records to the specific logs. Customizing the
products helps organize the information, create the required reports, and reduce
the performance impact.
Tivoli Decision Support for z/OS and the CICS Performance feature collect from
SMF records only the data required to meet CICS users’ needs, combine that data
with more data (called environment data), and present the data in reports. Figure 2
on page 8 illustrates how data is organized for presentation in Tivoli Decision
Support for z/OS reports.
Chapter 1. Introducing the CICS Performance feature
7
Collecting performance data
Figure 2. Organizing and presenting system performance data
The key to successful implementation of Tivoli Decision Support for z/OS is
knowing:
v The information and resources on which you want to report and how to perform
customization to select them
v The way you want to organize, set objectives for, and process the data (used
later to define the environment)
Note: The process of entering and maintaining environment data is called
administration. Tivoli Decision Support for z/OS provides an administration
dialog for maintaining resource information. Refer to the Administration
Guide and Reference for information on how to use the administration dialog.
8
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 2. Implementing the CICS Performance feature
This chapter describes how to plan for and set up the CICS Performance feature. It
supplements the procedure in the Administration Guide and Reference for installing a
component with information specific to the CICS Performance feature.
Planning the implementation process
Before installing the CICS Performance feature, you must follow these steps to plan
the implementation process:
1. Describe users’ tasks. Then determine what data the CICS Performance feature
must gather to help users accomplish those tasks.
2. Determine which components you must install to meet the users’ needs.
3. Determine the administration tasks you must perform for the selected
components and make any decisions required by these tasks. These tasks help
you customize Tivoli Decision Support for z/OS and the CICS Performance
feature to work efficiently and effectively with your computer system.
4. For each selected component, determine the tasks you must perform to
customize the supported products to work with Tivoli Decision Support for
z/OS and with the CICS Performance feature.
If this is your first exercise in implementation planning, follow all these steps to
ensure that the CICS Performance feature’s implementation is consistent. If you are
reading this chapter in preparation for modifying your system, you might not need
to perform all of these tasks.
Use the planning process to prepare for these main customization tasks:
v Customizing CICS/MVS, CICS/ESA and CICS/TS to gather the performance
data that is written to SMF and other log files. You customize these products to
generate the data required by the components you install.
v Defining environment data, which is all the information (besides the input data)
that the CICS Performance feature needs to create reports. Environment data
controls the data-collection process and provides more information in the
reports.
Figure 3 illustrates the overall process for implementing the CICS Performance
feature.
© Copyright IBM Corp. 1994, 2009
9
Considering which components to install
Figure 3. Implementation process for the CICS Performance feature
Considering which components to install
Your most critical planning task is determining what kind of information users
need from the CICS Performance feature. For example, users may be interested
only in system resource availability or transaction response time. Installing only
those parts of the feature needed to meet user requirements ensures that the
feature benefits users while it minimizes the performance impact caused by data
collection and interpretation activities.
10
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Considering which components to install
The CICS Performance feature uses these information categories for selecting the
information for reports:
Performance
Response time, resource use, and volumes and throughput for CICS-related
activity affect performance. Generally, performance is stated as response
time: the elapsed time to process a single user interaction with known
characteristics, such as a simple inquiry or update.
Response time can be regarded as:
v Internal response time excluding transmission delay (for example, a
CICS pseudoconversational task life)
v Terminal response time as perceived by the user
Exceptions and incidents
Exceptions and incidents are events that exceed limits for:
v A service-level agreement
v Installation standards
Exceptions also include events that do not affect general CICS availability
but do affect transaction and CICS resources. You will most likely monitor
exceptions for these purposes:
v To detect causes of system downtime
v To identify user groups or transactions with excessive exceptions
An incident is an exception that indicates a more serious limit condition.
As explained in “Monitoring exception and incident data” on page 37, you
should investigate and correct incidents.
Although Tivoli Decision Support for z/OS can analyze data and produce reports
for all of these information categories, you might not need all that data. Figure 4
on page 12 shows that the CICS Performance feature is divided into four
components. The CICS monitoring component is divided further into 16
subcomponents. The CICS OMEGAMON® monitoring component is divided
further into 5 subcomponents. Components and subcomponents provide support
for specific operating systems, subsystems, and licensed programs.
Chapter 2. Implementing the CICS Performance feature
11
Considering which components to install
Figure 4. CICS Performance feature structure
Consider carefully which components to install. Components are groups of Tivoli
Decision Support for z/OS objects (for example, predefined update definitions, data
tables, and reports). If you find that you need reports from a component that you
have not installed, you must install that component and then wait several days or
weeks until enough data has been collected to create reports. However, if you
install more components than you need, Tivoli Decision Support for z/OS collects
needless data, which takes up disk space and uses processor time.
Note: You cannot uninstall an individual subcomponent. As described in the
Administration Guide and Reference, you must uninstall a component, then
reinstall it, selecting only those subcomponents you need.
At this point, you might find it helpful to examine the predefined reports for each
subcomponent. For more information, see “Chapter 7, “Reports.”
12
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Considering which components to install
Evaluating the CICS monitoring component
The CICS monitoring facility (CMF) provides the performance data for the CICS
monitoring component. Figure 4 on page 12 shows the subcomponents contained
in this component.
Notes:
1. Subcomponents 1–3 summarize data by transaction, subcomponents 4–6
summarize data by application, subcomponents 8–10 summarize data by
transaction and user, and subcomponents 11–13 summarize data by application
and user.
2. To make efficient use of the application analysis subcomponents
(subcomponents 4, 5, and 6), you must update the CICS_LOOKUP_APPL
table. For more information, see “Updating CICS_LOOKUP_APPL” on page 24.
1. Basic subcomponent
This first subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize, by transaction, basic data gathered by CMF. Consider
using this subcomponent as a starting point.
2. DBCTL subcomponent
Database control (DBCTL) is a DL/I interface that uses an address space separate
from CICS. It is available only for CICS/ESA and CICS/TS. If you run DBCTL,
consider installing this subcomponent. It summarizes data by transaction. Its tables
contain the DBCTL monitoring fields. (You must verify the presence of these fields
in the performance monitoring record, as described in “Making input data
available” on page 16.)
3. DL/I subcomponent
This subcomponent processes data from the local interface to a DL/I database. If
you run DL/I, consider installing this subcomponent. It summarizes data by
transaction. Available for CICS/MVS, CICS/ESA, and CICS/TS, its tables contain
the DL/I monitoring fields. (As with the DBCTL subcomponent, verify the
presence of the DL/I fields in the performance monitoring record, as described in
“Making input data available” on page 16.)
4. Basic application analysis subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize transaction data by application. See “Updating the lookup
tables” on page 23 for information on the customization needed to use this
subcomponent.
5. DBCTL application analysis subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize DBCTL transaction data by application. For the CICS
Performance feature to summarize transaction data by application, you must use
the customization procedure in “Updating the lookup tables” on page 23.
6. DL/I application analysis subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize DL/I transaction data by application. Again, you must use
the customization procedure in “Updating the lookup tables” on page 23 for the
CICS Performance feature to successfully summarize transaction data by
application.
Chapter 2. Implementing the CICS Performance feature
13
Considering which components to install
7. CICS/MVS subcomponent (global + accounting)
Only CICS/MVS users should consider installing this global and accounting
subcomponent. Its tables contain the Tivoli Decision Support for z/OS objects
necessary to summarize global and accounting data only for CICS Version 2.
8. Basic transaction subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize, by transaction and user, basic data gathered by CMF.
9. DBCTL transaction subcomponent
Database control (DBCTL) is a DL/I interface that uses an address space separate
from CICS. It is available only for CICS/ESA and CICS/TS. If you run DBCTL,
consider installing this subcomponent. It summarizes data by transaction and user.
Its tables contain the DBCTL monitoring fields. (You must verify the presence of
these fields in the performance monitoring record, as described in “Making input
data available” on page 16.)
10. DL/I transaction subcomponent
This subcomponent processes data from the local interface to a DL/I database. If
you run DL/I, consider installing this subcomponent. It summarizes data by
transaction and user. Available for both CICS/MVS, CICS/ESA, and CICS/TS, its
tables contain the DL/I monitoring fields. (As with the DBCTL subcomponent,
verify the presence of the DL/I fields in the performance monitoring record, as
described in “Making input data available” on page 16.)
11. Basic application user subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize transaction data by application and user. See “Updating
the lookup tables” on page 23 for information on the customization needed to use
this subcomponent.
12. DBCTL application user subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize DBCTL transaction data by application and user. For the
CICS Performance feature to summarize transaction data by application and user,
you must use the customization procedure in “Updating the lookup tables” on
page 23.
13. DL/I application user subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize DL/I transaction data by application and user. Again, you
must use the customization procedure in “Updating the lookup tables” on page 23
for the CICS Performance feature to successfully summarize transaction data by
application and user.
14. CICS TS transaction resources subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to collect data on transaction resources from SMF_110_1 class 5 record.
15. CICS TS enterprise Java™ beans subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to collect enterprise bean-related data from SMF_110_1 class 3
monitoring record.
14
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Considering which components to install
16. CICS Resource Manager Interface subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize by transaction Resource Management Interface data if this
option is enabled in the Monitoring Control Table (MCT).
Evaluating the CICS OMEGAMON monitoring component
OMEGAMON XE for CICS provides the performance data for the CICS
OMEGAMON monitoring component. Figure 4 on page 12 shows the
subcomponents contained in this component. Tivoli Decision Support for z/OS
Version 1.8.0 supports OMEGAMON XE for CICS from Version 4.1.
Notes:
1. Subcomponent 1 summarizes data by transaction and user, subcomponent 2
summarizes data by application, subcomponent 3 summarizes data by
transaction, subcomponent 4 summarizes data by application and user, and
subcomponent 5 summarizes data by transaction.
2. To make efficient use of the application analysis subcomponents
(subcomponents 2 and 4), you must update the CICS_LOOKUP_APPL table.
For more information, see “Updating CICS_LOOKUP_APPL” on page 24. You
must verify the presence of the OMEGAMON fields in the performance
monitoring record, as described in “Making input data available” on page 16.
1. File and Database subcomponent
This subcomponent processes file and database usage information from the data
OMEGAMON XE for CICS appends to the SMF type 110 record. It summarizes the
data by transaction and user.
2. File and Database Application subcomponent
This subcomponent processes file and database usage information from the data
OMEGAMON XE for CICS appends to the SMF type 110 record. It summarizes the
data by application.
3. File and Database Transaction subcomponent
This subcomponent processes file and database usage information from the data
OMEGAMON XE for CICS appends to the SMF type 110 record. It summarizes the
data by transaction.
4. File and Database Application User subcomponent
This subcomponent processes file and database usage information from the data
OMEGAMON XE for CICS appends to the SMF type 110 record. It summarizes the
data by application and user.
5. File and Database Detailed Usage subcomponent
This subcomponent processes file and database usage information from the SMF
type 112 subtype 203 record, created by OMEGAMON XE for CICS. It summarizes
the data by transaction.
Chapter 2. Implementing the CICS Performance feature
15
Considering which components to install
Evaluating the CICS statistics component
Statistics, supported only for CICS/ESA and CICS/TS, are a tool for monitoring a
CICS system; they collect information on the CICS system as a whole, without
regard to tasks. Consider installing this component if you are interested in these
types of statistics (written to SMF data sets by the CICS statistics domain):
v Interval
v End-of-day
v Requested
v Unsolicited
For information about statistics, refer to the appropriate CICS Performance Guide.
Evaluating the CICS transaction and unit-of-work analysis
component
The CICS transaction and unit-of-work analysis component collects data about a
transaction as it migrates from one CICS region (or processor complex) to another
and back, letting you determine the total resource requirements of the combined
transaction as a unit of work.
Note: Unit-of-work data collection generates intensive processing, which
significantly increases collection time.
If you install this component, collect its data with a separate collect job, and for a
limited time (15 minutes should be sufficient). Do not include this component’s
table in your normal collect job. Otherwise, data collection takes too long to
complete and results in a table that is too large to manage. For more information,
see “Optimizing data collection” on page 19.
Making input data available
The CICS Performance feature uses CICS monitoring facility (CMF) and CICS
statistics to generate data. For CICS/MVS, CICS/ESA and CICS/TS, verify that
you have suitable values in the system initialization table (SIT) and in the
monitoring control table (MCT). For CICS/MVS only, verify that you have suitable
values in the journaling control table (JCT).
Verifying CICS/ESA and CICS/TS requirements
Tivoli Decision Support for z/OS supports CICS/ESA and CICS/TS performance,
statistics, and exception data recorded through SMF.
CICS/ESA and CICS/TS CMF requirements
DFHSIT (the system initialization table)
Specify these operands:
v MN=ON enables CMF recording.
v MNPER=ON generates performance data.
v MNEXC=ON generates exception data.
In the DFHSIT, code MNCONV=YES to separate reporting for each
terminal interaction of a conversational transaction. If MNCONV=NO, the
response time for these transactions includes operator think time, which
distorts average values.
Also, specifying MNEVE=ON in the DFHSIT generates SYSEVENT data.
Although not supported by the CICS Performance feature, SYSEVENT data
is a useful performance-analysis tool and can be collected by the System
16
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Making input data available
Performance feature. Refer to the appropriate CICS System Definition Guide
for information about defining DFHSIT. Refer to the System Performance
Feature Guide for information on using the System Performance feature for
performance analysis.
As an alternative to revising the SIT, you can control CMF dynamically by
using either master-terminal transaction commands or
system-programming commands.
Refer to the appropriate CICS CICS-Supplied Transactions for descriptions of
these applicable master-terminal transaction commands:
v CEMT SET MONITOR ON PERF
v CEMT SET MONITOR ON EXCEPT
v CEMT SET MONITOR ON EVENT
Refer to the appropriate CICS System Programming Reference for descriptions
of the applicable SP™ commands.
DFHMCT (the monitoring control table)
Code the TYPE=INITIAL instruction with the operand CPU=YES if you
need processor time measurements. (Note that CPU=YES is not required
for CICS V4.1 and above.) There is a small processing overhead but, if you
do not code this, the CPU time columns are zero in the CICS101, CICS403,
and CICS404 reports.
Code the TYPE=INITIAL instruction with the operand CONV=YES if you
want separate reporting for each terminal interaction of a conversational
transaction. If CONV=NO, the response time for these transactions
includes operator think time, which distorts average values.
If you run a database manager (either DBCTL or DL/I) and have chosen to
install a subcomponent that contains their monitoring fields, check that
these fields are present in the MCT.
If you want to record all system-defined performance data (no exclusions)
and if you have no user-defined event monitoring points (EMPs), then you
do not have to define DFHMCT for either CICS/ESA or CICS/TS. If you
choose not to define DFHMCT, however, two defaults are active: CPU=NO
and CONV=NO.
CICS/ESA and CICS/TS statistics requirements
In the DFHSIT macro, specify a STATRCD=ON operand to record interval and
unsolicited statistics. To provide enough statistical data for meaningful reporting,
use the default statistics interval of three hours. You can dynamically turn on or off
requested and unsolicited statistics data by using either CEMT or SP commands.
Refer to the appropriate CICS CICS-Supplied Transactions for a description of the
CEMT command CEMT SET STATISTICS. Refer to the appropriate CICS System
Programming Reference for a description of the SP command EXEC CICS SET
STATISTICS.
CICS/ESA and CICS/TS record statistics data at the end-of-day expiry time and at
shutdown, regardless of settings that control requested and unsolicited statistics
data. Refer to the appropriate CICS Performance Guide for details of CICS statistics.
Verifying CICS/MVS requirements
DFHSIT (the system initialization table)
Specify these operands:
v MCT=xx enables use of the monitoring control table, where xx represents
the MCT suffix.
Chapter 2. Implementing the CICS Performance feature
17
Making input data available
v MONITOR=(ACC,PER,EXC) enables monitoring of accounting,
performance, and exception data.
In the DFHSIT, code MNCONV=YES to separate reporting for each
terminal interaction of a conversational transaction. If MNCONV=NO, the
response time for these transactions includes operator think time, which
distorts average values.
To generate the most detailed Tivoli Decision Support for z/OS reports,
code DFHSIT to continuously record CICS monitoring data to the SMF log.
Refer to CICS/MVS Resource Definition (Macro) for information about
defining DFHSIT.
As an alternative to revising the SIT, you can control CMF dynamically by
using the CSTT transaction. Refer to CICS/MVS CICS-Supplied Transactions
for a description of the CSTT transaction.
DFHMCT (the monitoring control table)
Define separate TYPE=RECORD entries for each of these classes of
monitoring data:
v CLASS=ACCOUNT enables recording of accounting data.
v CLASS=EXCEPTION enables recording of exception data.
v CLASS=PERFORMANCE enables recording of transaction performance
data.
You can control whether CMF uses separate journals for each class, or
whether it records some combination of classes into one journal.
If you run DL/I, and have chosen to install a subcomponent that contains
its monitoring fields, check that these fields are present in the MCT.
Refer to the CICS/MVS Resource Definition (Macro) for information about
defining DFHMCT.
DFHPPT and DFHPCT
Monitoring entries are required in the CICS system definition (CSD) file
(online resource definitions) or in the processing program table (PPT) and
the program control table (PCT) (macro definitions). To determine how to
control CMF when using online resource definitions, refer to the CICS/MVS
Operations Guide and CICS/MVS Resource Definition (Online). To determine
how to control CMF when using macro resource definitions, refer to the
CICS/MVS Operations Guide and CICS/MVS Resource Definition (Macro).
DFHJCL (journaling control table)
Specify these operands:
v FORMAT=SMF records data in SMF type 110 record format.
v JTYPE=SMF writes journal buffers to the SMF log.
Refer to CICS/MVS Resource Definition (Macro) for information about
defining DFHJCT.
For information about the data provided in the accounting, performance, and
exception class records, refer to the CICS/MVS Performance Guide and the
CICS/MVS Customization Guide.
Verifying OMEGAMON XE for CICS requirements
If you want to record the OMEGAMON XE for CICS performance data, you have
to define those event monitoring points in the MCT. For more information on
18
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Making input data available
defining the MCT, see the OMEGAMON XE for CICS on z/OS Version 4.1
Information Center. Tivoli Decision Support for z/OS Version 1.8.0 supports
OMEGAMON XE for CICS Version 4.1.
Optimizing data collection
Your first task in optimizing data collection is to install only the components and
subcomponents that meet your needs. Use the information in “Considering which
components to install” on page 10 to evaluate components and subcomponents.
The Administration Guide and Reference describes how to optimize Tivoli Decision
Support for z/OS data collection by specifying only the needed tables in the
INCLUDE (or EXCLUDE) clauses of the COLLECT statement. The example in
Figure 5 shows how to selectively include data tables supplied with the CICS
Performance feature.
//JOBCARD
//COLLECT EXEC PGM=DRLPLC,
// PARM=('SYSTEM=DB2A',
//
'SYSPREFIX=DRLSYS',
//
'SHOWINPUT=YES')
//STEPLIB DD DISP=SHR,DSN=DRLxxx.LOAD.LIBRARY
//DRLLOG DD DISP=SHR,DSN=XXX.CICS33.LOG1
LOG DATA SET
//DRLDUMP DD SYSOUT=*,DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760)
//DRLOUT DD SYSOUT=*,DCB=(RECFM=F,LRECL=132)
//DRLNDICT DD DISP=OLD,DSN=XXX.CICS.NODICT.RECORDS.LOG
//DRLIN
DD *
SET PREFIX
=
'DRL'
;
COLLECT
SMF
INCLUDE
DRL.EXCEPTION_T,
DRL.CICS_DBCTL_TRAN_D,
DRL.CICS_DBCTL_TRAN_W,
DRL.CICS_DBCTL_USR_D,
DRL.CICS_DBCTL_USR_H,
DRL.CICS_DBCTL_USR_W,
DRL.CICS_DLI_TRAN_D,
DRL.CICS_DLI_TRAN_W,
DRL.CICS_DLI_USR_D,
DRL.CICS_DLI_USR_H,
DRL.CICS_DLI_USR_W,
DRL.CICS_A_BASIC_H,
DRL.CICS_A_BASIC_W,
DRL.CICS_A_DBCTL_H,
DRL.CICS_A_DBCTL_W,
DRL.CICS_A_DBCTL_USR_H,
DRL.CICS_A_DBCTL_USR_W,
DRL.CICS_A_DLI_H,
...
DRL.CICS_S_TRANSIENT_T
REPROCESS
;
/*
Figure 5. Sample COLLECT job with an INCLUDE clause
See “How Tivoli Decision Support for z/OS processes dictionary data” on page 66
for the line:
//DRLNDICT DD DISP=OLD,DSN=XXX.CICS.NODICT.RECORDS.LOG
Defining the operating environment
To organize the system data collected from SMF and other logs, you must define
the operating environment to Tivoli Decision Support for z/OS. This process
(described in the Administration Guide and Reference) occurs for any component.
Tables contain the environment data, and Tivoli Decision Support for z/OS uses
these tables when it processes data and creates reports.
Chapter 2. Implementing the CICS Performance feature
19
Installing the components
Installing the components
After the system programmer has successfully installed the Tivoli Decision Support
for z/OS base and features, you can choose whether to load any feature
components and subcomponents. Tivoli Decision Support for z/OS installs the
necessary log and record definitions, record procedures, and updates definitions to
Tivoli Decision Support for z/OS system tables. Tivoli Decision Support for z/OS
also installs the predefined tables (described in “Chapter 6, “Data tables, lookup
tables, and control tables”) and reports (described in “Chapter 7, “Reports”).
Each component and subcomponent of the CICS Performance feature is optional.
All Tivoli Decision Support for z/OS features, components, and subcomponents
install the same way. Using the administration dialog, you select which
components of the CICS Performance feature to install.
Perform these steps:
1. From the Tivoli Decision Support for z/OS Administration window (Figure 6),
select 2. Components and press Enter.
Other Utilities Help
-------------------------------------------------------------------------Tivoli Decision Support for z/OS Administration
Select one of the following. Then press Enter.
2_ 1.
2.
3.
4.
5.
System
Components
Logs
Tables
Reports
Command ===> ______________________________________________________________
F1=Help
F2=Split
F3=Exit
F9=Swap
F10=Actions F12=Cancel
Figure 6. Tivoli Decision Support for z/OS Administration window
Tivoli Decision Support for z/OS displays the Components window (Figure 7
on page 21).
20
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Installing the components
Component Space Other Help
--------------------------------------------------------------------------Components
Row 1 to 22 of 74
Command ===> _______________________________________________________________
Select one or more components. Then press Enter to Open component.
/ Components
_ z/OS Performance Management (MVSPM) Component
_ z/OS System (MVS) Component
_ z/OS Availability Component
_ z/OS Interval Job/Step Accounting Component
_ z/VM Performance Component
/ CICS Monitoring Component
_ CICS Monitoring Partitioned Component
_ CICS OMEGAMON Monitoring Component
_ CICS Statistics Component
_ CICS Statistics Partitioned Component
_ CICS Tran&UOW Analysis Partitioning Component
_ CICS Transaction and UOW Analysis Component
_ Data Set Component
_ DB2 Component
_ DFSMS Set Component
_ DFSMS/RMM Component
_ EREP Component
_ HTTP Server for z/OS (ICSS) Component
_ IMS 10.1 CSQ Collect Component
_ IMS 10.1 Log Records Component
_ IMS 7.1 Collect Component
_ IMS 7.1 CSQ Collect Component
F1=Help
F2=Split
F3=Exit
F5=New
F8=Fwd
F9=Swap
F10=Actions F12=Cancel
Status
Date
Installed 2007-08-01
Installed 2007-08-01
F6=Install
F7=Bkwd
Figure 7. Components window
2. From the Components window, select the component to install (here, the CICS
monitoring component) and press F6.
Because the CICS monitoring component contains subcomponents, Tivoli
Decision Support for z/OS displays the CICSMON Component Parts window
(Figure 8 on page 22).
Chapter 2. Implementing the CICS Performance feature
21
Installing the components
Component Space Other Help
------------------------------------------------------------------------------|
CICSMON Component Parts
Row 1 to 13 of 16 |
|Command ===> _____________________________________________________________
|
|
|
|Select the parts of the component you want to install. Then press Enter.
|
|
|
| / Component Part
Status
Date
|
| / 1 Basic Subcomponent
|
| _ 2 DBCTL Subcomponent
|
| _ 3 DL/I Subcomponent
|
| _ 4 Basic Application Analysis Subcomponent
|
| _ 5 DBCTL Application Analysis Subcomponent
|
| _ 6 DL/I Application Analysis Subcomponent
|
| _ 7 CICS/MVS Global and Accounting Subcomponent
|
| / 8 Basic Transaction Subcomponent
|
| _ 9 DBCTL Transaction Subcomponent
|
| _ 10 DL/I Transaction Subcomponent
|
| _ 11 Basic Application User Subcomponent
|
| _ 12 DBCTL Application User Subcomponent
|
| _ 13 DL/I Application User Subcomponent
|
| F1=Help
F2=Split
F7=Bkwd
F8=Fwd
F9=Swap
F12=Cancel
|
------------------------------------------------------------------------------DFSMS/RMM Component
EREP Component
HTTP Server for z/OS (ICSS) Component
IMS 10.1 CSQ Collect Component
IMS 10.1 Log Records Component
IMS 7.1 Collect Component
IMS 7.1 CSQ Collect Component
F1=Help
F2=Split
F3=Exit
F5=New
F6=Install
F7=Bkwd
F8=Fwd
F9=Swap
F10=Actions F12=Cancel
Figure 8. CICSMON Component Parts window
3. Select the subcomponents to install and press Enter to display the Installation
Options window (Figure 9 on page 23).
Start with subcomponent 1. Then test it and install more subcomponents as
required.
22
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Installing the components
Component Space Other Help
---------------------------------------------------------------------------|
CICSMON Component Parts
ROW 1 TO 13 of 13
| -------------------------------------------------------------| S|
Installation Options
| Enter.
| |
|
| /| Select one of the following. Then press Enter.
|Date
| /|
|
| _|
__ 1. Online
|
| _|
2. Batch
|
| _|
|
| _| F1=Help
F2=Split
F6=Objects F9=Swap
F12=Cancel
|
| _-------------------------------------------------------------| _ 7 CICS/MVS subcomponent (global + accounting)
|
| / 8 Basic Transaction subcomponent
| _ 9 DBCTL Transaction subcomponent
| _ 10 DL/I Transaction subcomponent
| _ 11 Basic Application User subcomponent
| _ 12 DBCTL Application User subcomponent
| _ 13 DL/I Application User subcomponent
| ***************************** BOTTOM OF DATA ****************************
| Command ===> ____________________________________________________________|
| F1=Help
F2=Split
F7=Bkwd
F8=Fwd
F9=Swap
F12=Cancel
---------------------------------------------------------------------------F8=Fwd
F9=Swap
F10=Actions F12=Cancel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Figure 9. Installation Options window
4. Using the component-installation procedure in the Administration Guide and
Reference, specify whether to install the subcomponent online or in batch mode.
Installation of the CICS Performance feature can result in a lot of output, so it
is recommended that you install CICS components in batch.
v If you specify online installation, Tivoli Decision Support for z/OS displays
the Lookup Tables window. (See “Updating the lookup tables” for more
information.)
– To edit a lookup table using ISPF edit, select a table and press Enter.
– If the lookup table is wider than 255 characters, you must use the QMF™
table editor:
- 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).
v If you specify batch mode, Tivoli Decision Support for z/OS starts an ISPF
edit session, from which you can edit and submit the installation JCL. Batch
installation messages identify the lookup tables that require editing. (See
“Updating the lookup tables” for more information.)
When you have finished editing lookup tables, installation continues. After
installation is complete, Tivoli Decision Support for z/OS returns to the
Components window, and the Status field indicates that the component is
installed.
Updating the lookup tables
To accurately analyze performance data from your system, group the data by user
groups, workload types, project groups, and so on. Each installation has different
criteria for grouping the data. All components and subcomponents of the CICS
Performance feature include lookup tables that you can customize to specify the
groupings you want reflected in your reports.
Chapter 2. Implementing the CICS Performance feature
23
Updating the lookup tables
To decide how you want data grouped, develop a performance and service-level
strategy using the information in “Defining performance objectives” on page 4.
After developing your strategy, use the administration dialog to modify the lookup
tables for each subcomponent to implement your strategy. You can edit tables
using either the ISPF editor or the QMF table editor.
Note: As the needs of your organization change, so will your service-level strategy.
You might need to update the lookup tables periodically to reflect these
changes.
With the CICS Performance feature, customization involves updating the
CICS_TIMEZONES, CICS_LOOKUP_APPL and CICS_LOOKUP_SYSTEM lookup
tables.
Updating CICS_TIMEZONES
This table can be filled in through the Tivoli Decision Support for z/OS dialogs.
For more information about customizing the lookup tables through the dialogs,
refer to the Administration Guide and Reference.
Another way to fill in this table is with statements similar to those shown in
Figure 10.
SQL INSERT INTO &PREFIX.CICS_TIMEZONES
(MVS_SYSTEM_ID, TIMEOFF)
VALUES (('MVS1', -1))
SQL INSERT INTO &PREFIX.CICS_TIMEZONES
(MVS_SYSTEM_ID, TIMEOFF)
VALUES (('MVS2', 1))
SQL INSERT INTO &PREFIX.CICS_TIMEZONES
(MVS_SYSTEM_ID, TIMEOFF)
VALUES (('MVS3', 0))
Figure 10. Sample fill in for the CICS_TIMEZONES lookup table
For MVS1, the local time is calculated by subtracting one hour from the GMT time
read on the record. For MVS2, the local time is calculated by adding one hour to
the GMT time read on the record. For MVS3, the time is left unchanged.
Updating CICS_LOOKUP_APPL
Decide whether you require reports by CICS transaction or by both CICS
transaction and CICS application. To enable reporting on CICS applications, update
the CICS_LOOKUP_APPL table to identify application components; otherwise,
your reports will not show CICS application data.
For example, a simple way to fill the CICS_LOOKUP_APPL table is to first fill the
CICS_TRANSACTION_D table with valid data by collecting a log. If your
transactions have a generic naming standard for your order-entry application (such
as OE01, OE02, OE03, and so on), you can update the CICS_LOOKUP_APPL table
with the SQL statement shown in Figure 11 on page 25.
24
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Updating the lookup tables
INSERT INTO CICS_LOOKUP_APPL
(MVS_SYSTEM_ID,
CICS_SYSTEM_ID,
APPLICATION_NAME,
TRANSACTION_ID,
TRAN_RESP_BND1_SEC, TRAN_RESP_BND2_SEC, TRAN_RESP_BND3_SEC,
TRAN_RESP_BND4_SEC,
APPL_RESP_BND1_SEC, APPL_RESP_BND2_SEC, APPL_RESP_BND3_SEC,
APPL_RESP_BND4_SEC)
SELECT DISTINCT
MVS_SYSTEM_ID,
CICS_SYSTEM_ID,
'ORDER_ENTRY',
--application name (variable)
TRANSACTION_ID,
1,2,5,10,1,2,5,10
--response time boundaries (defaults)
FROM CICS_TRANSACTION_D
WHERE TRANSACTION_ID LIKE 'OE%'
--generic transaction identifier (variable)
Figure 11. Sample update to the CICS_LOOKUP_APPL lookup table
Note: For other applications, you can repeat the statements shown in Figure 11
and just change both the application name and the generic transaction
identifier.
If you decide that you require reports by both CICS transaction and CICS
application, you must install at least one of these application analysis
subcomponents:
v Subcomponent 4, basic application analysis
v Subcomponent 5, DBCTL application analysis
v Subcomponent 6, DL/I application analysis
As described in “Evaluating the CICS monitoring component” on page 13,
subcomponents that summarize data by transaction are prerequisites for their
corresponding subcomponents that summarize data by application. The example in
Figure 12 shows update definition code that uses the table for application analysis
subcomponents.
APPLICATION_NAME
= VALUE(LOOKUP APPLICATION_NAME
IN &PREFIX.CICS_LOOKUP_APPL
WHERE MVS_SYSTEM_ID LIKE
MVS_SYSTEM_ID
AND CICS_SYSTEM_ID LIKE
CICS_SYSTEM_ID
AND TRANSACTION_ID LIKE
TRANSACTION_ID,
'OTHER'))
Figure 12. Update definition supplied in subcomponent 4, basic application analysis
This summarizes all transactions that do not match under the ‘OTHER’ application.
For information about using LIKE in a COLLECT statement, refer to the Language
Guide and Reference.
Note: The example in Figure 12 can be modified to look only for exact matches
(with some improvement in performance) by exchanging LIKE for equal
signs (=).
Updating CICS_LOOKUP_SYSTEM
This table can be used to group CICS systems. You can then create reports that
report on groups of CICS systems, specifying a group name, such as
PRODUCTION. Update CICS_LOOKUP_SYSTEM with statements similar to those
Chapter 2. Implementing the CICS Performance feature
25
Updating the lookup tables
shown in Figure 13.
APPLICATION_NAME
= VALUE(LOOKUP APPLICATION_NAME
IN &PREFIX.CICS_LOOKUP_APPL
WHERE MVS_SYSTEM_ID LIKE
MVS_SYSTEM_ID
AND CICS_SYSTEM_ID LIKE
CICS_SYSTEM_ID
AND TRANSACTION_ID LIKE
TRANSACTION_ID,
'OTHER'))
Figure 13. Sample update to the CICS_LOOKUP_SYSTEM lookup table
CICS_LOOKUP_SYSTEM is not used in the supplied tables and reports.
For more information about customizing lookup tables, refer to the Administration
Guide and Reference.
Updating other lookup tables
If your system also has the System Performance feature installed, you can cause
Tivoli Decision Support for z/OS to collect data regarding CICS region activity by
updating the MVS_WORKLOAD_TYPE table. This information can prove helpful
when you need reports on CICS availability. For more information, refer to the
System Performance Feature Reference Volume 1.
Testing the installation
Before starting the daily use of the CICS Performance feature, run a few tests to
ensure that the installation was successful. This step verifies that Tivoli Decision
Support for z/OS is collecting the right data, storing the data correctly, and using
the proper data to create reports. Testing the installation also confirms that the
lookup tables contain appropriate values.
Refer to the Administration Guide and Reference for the steps involved in testing
component installation.
Putting the feature into production
After you run the tests and verify that the installation is successful, you can put
the CICS Performance feature and its components into production.
Figure 14 shows the daily steps involved in using Tivoli Decision Support for
z/OS.
(SMF data only)
Switch
SMF
data sets
Run
COLLECT
job
Perform
database
maintenance
Create
reports
Figure 14. Daily steps involved in using Tivoli Decision Support for z/OS
You can run reports in batch, after setting batch parameters for each report using
the administration dialog.
For detailed information about these steps, refer to the Administration Guide and
Reference.
26
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 3. Monitoring CICS Performance
To understand performance data, you must first understand the work CICS
performs at your installation. Analyze the work by its basic building blocks:
transactions. Group the transactions into categories of similar resource or user
requirements and describe each category’s characteristics. Understand the workload
that CICS performs for each transaction. Also, understand the volume of
transactions expected during any given period. Tivoli Decision Support for z/OS
can show you various types of data for the transactions currently processed by
CICS.
Tivoli Decision Support for z/OS feature components and subcomponents include
lookup tables that you can customize to specify the groupings you want reflected
in your reports. For more information, see “Updating the lookup tables” on page
23.
A service-level agreement for a CICS user group defines commitments in several
areas of quantifiable CICS-related resources and services. As described in
“Considering which components to install” on page 10, CICS service commitments
belong to one of these areas:
v Availability
v Performance
v Exceptions and incidents
This chapter describes certain issues and concerns associated with systems
management and how you can use the CICS Performance feature to explore those
issues and concerns.
Monitoring availability
CICS, in the SMF logs, provides availability information for the overall subsystem,
as well as the connection to DB2. This information is collected by Tivoli Decision
Support for z/OS in the CICS_AVAIL_T_,_D,_W tables (see pages 133 and 134 for
details). The CICS_AVAIL_RES lookup table needs to be customized with the name
of the resources (CICS regions and DB2 connections) to be monitored. In addition
to the above specific data, other considerations and measurements can be
performed as follows.
Users of CICS applications depend on the availability of several types of resources:
v Central site hardware and the operating system environment in which the CICS
region runs
v Network hardware, such as communication controllers, teleprocessing lines, and
terminals through which users access the CICS region
v CICS region
v Application programs and data
Application programs can be distributed among several CICS regions. More than
one set of such resource types might exist, all of which must be available to satisfy
application requirements.
The information provided by CICS and MVS limits the accuracy with which Tivoli
Decision Support for z/OS can report availability. A process of deduction can yield
© Copyright IBM Corp. 1994, 2009
27
Monitoring availability
some helpful analysis of CICS availability. If CICS uses a resource, that resource
must have been available. Records and messages indicating that CICS used a
resource tell you that the resource was available at that time. But, if a resource is
not used for a known period, it is not necessarily unavailable.
You can define dependencies between resources by specifying MVS subsystem
resource type, name, and availability objectives in the common lookup table
AVAILABILITY_PARM and the MVS lookup table MVS_WORKLOAD_TYPE.
You can create reports that show CICS region and resource availability.
Monitoring CICS resource availability
Although CICS keeps status information about its resources in its internal control
tables, this information is not usually available externally. CICS writes an exception
for line and terminal out-of-service information to destination CSMT. To ensure
complete data capture for CICS/MVS, run CSTT AUT at CICS termination (for
example, through the shutdown PLT).
CMF performance class records, CICS/ESA and CICS/TS statistics show
transaction types and terminals used within any selected time interval. These
records contain usage counts for all CICS resources identified in the CICS control
tables where you define your system and tailor it to your environment, as
described in Chapter 2, “Implementing the CICS Performance feature,” on page 9.
Notes:
1. When you infer resource availability from usage in this way, carefully choose
resources to monitor. Resources must be active often enough to make it
unlikely that they are inactive during a monitoring interval. Otherwise, zero
use falsely designates unavailability.
2. When creating reports to show CICS resource availability, compare reporting
periods for resources required by more than one CICS region. Tivoli Decision
Support for z/OS can correctly report CICS resource availability when you
logically combine information. For example:
v Distributed applications, either multiregion operation (MRO) or intersystem
communication (ISC), need resources in two or more connected CICS regions.
The availability of each resource may be inferred from its use in each system.
The availability of the application can only be developed by combining
availability information and determining that the application was available in
every CICS region that supplies resources.
v VTAM® terminals may be shared between CICS regions. The availability of a
terminal may be inferred from its use by any subsystem. A global view of the
availability of the terminal can be developed by finding it active in any one
of the connected systems. (It cannot be available in all systems at the same
time.)
3. CICS uses an extended recovery facility (XRF) to reduce the duration of
unplanned outages, thereby allowing a higher level of CICS availability. The
main source of CICS information for XRF is the CICS XRF Guide. For a detailed
analysis of XRF and VTAM performance effects, refer to the CICS Performance
Guide .
28
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Monitoring file and data base usage
Monitoring file and data base usage
OMEGAMON XE for CICS writes information on file and data base usage to SMF
type 110 records as well as to SMF type 112 subtype 203 records. These records
contain counts and elapsed times for commands issued by transactions against
various file and database types. Figure 15 shows a Tivoli Decision Support for
z/OS sample report. This report can be used to determine transaction averages on
DB2 request counts, DB2 request response times, DB2 wait counts, and DB2 wait
elapsed times.
OMEGAMON transaction DB2 averages, hourly
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
DATE: '2007-06-07'
HOUR
---20
TRANSACTION
ID
REQUEST COUNT REQUEST RESPONSE TIME DB2 WAIT COUNT DB2 WAIT TIME
----------- ------------- --------------------- -------------- ------------AMG1
1446
5.118E-03
684
3.136E-06
Tivoli Decision Support: CICSOMEG007
Figure 15. CICS Application Response Times, Detail report
Monitoring response time
Tivoli Decision Support for z/OS reporting methods show CICS response as
internal response time, that is the amount of time from the recording of a transaction
request to its processing termination. Internal response time does not measure how
long the message took to get from the terminal operator, through a communication
controller, across a communication line, through another communication controller,
through the communication access method, and finally through any delays before
a channel program enqueued the request to a CICS region. It also does not account
for any delay before the terminal regains control, finds the message, and requests
CICS services. Figure 16 shows the elements of CICS internal response time. (For
details about the response-time elements, refer to the description of SNA
transaction flows in the appropriate CICS Performance Guide.)
S
T
A
R
T
Response time
Suspend time
Dispatch time
Service time
F
I
N
I
S
H
Figure 16. CICS internal response-time elements
CICS response-time reports show only the CICS application internal response
times. As described in the , the Network Performance Feature generates reports
that show the total, end-to-end average response time (operator transit time) for
VTAM applications (for example, a CICS region) on an individual logical-unit (LU)
basis. The operator transit time consists of the host transit time and the network
transit time, which are also shown in the Network Performance Feature reports.
Using these reports, you can isolate a response-time problem either to the network
or to CICS and act on it accordingly. Should the problem be in CICS, you can use
CICS Performance feature reports to identify the application causing the
response-time degradation.
Chapter 3. Monitoring CICS Performance
29
Monitoring response time
For example, the CICS Application Response Times, Overview report (in Figure 17)
shows average internal response times for applications defined in the
CICS_LOOKUP_APPL lookup table. It compares actual response times to response
times established in the service-level agreement. The applications shown are those
with the most frequent transactions.
Figure 17. CICS Application Response Times, Overview report
Tivoli Decision Support for z/OS can also show trends in response time for a
particular workload. The CICS Application Response Times, Trend report (in
Figure 18 on page 31) contains weekly average internal response times for
applications defined in the CICS_LOOKUP_APPL lookup table.
30
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Monitoring response time
x
x
x
x
+
+
+
+
+
+
x
Figure 18. CICS Application Response Times, Trend report
Tivoli Decision Support for z/OS uses service time and suspend time when it
calculates the information contained in the CICS Application Response Times,
Detail report (in Figure 19).
CICS Application Response Times, Detail
MVS system ='MVSB' CICS system ='FGAIZ3'
Date: 2000-05-10
Average Average
Application
Tran elapsed CPU
name
count (sec) (sec)
----------------------- -------- ------OTHER
507
6.964 0.000
SYSTEM
120
2.439 0.000
=========
627
Average
disp
(sec)
------0.000
0.000
Average
disp
wait
(sec)
------0.064
0.058
Average
suspend
(sec)
------0.307
0.201
Average
program
load
(sec)
------0.025
0.077
Average
TD IO
wait
(sec)
------0.001
0.000
Average
TS IO
wait
(sec)
------0.023
0.011
Average
TC IO
wait
(sec)
------0.403
0.002
Average
FC IO
wait
(sec)
------0.000
0.000
Average
JC IO
wait
(sec)
------0.678
1.921
Average
MRO
wait
(sec)
------0.069
0.001
Average
except
wait
(sec)
------6.657
2.237
Tivoli Decision Support for z/OS Report: CICS403
Figure 19. CICS Application Response Times, Detail report
Response times depend on the speed of the processor and on the nature of the
application. The CPU time is zero if CPU=YES is not specified in the MCT.
Suspend time is the time a task must wait for resources. Because processor service
time is but a fraction of a second, the processor usage is generally acceptable, even
at high processor utilization levels. However, look for the symptoms of resource
contention: growing suspend and exception wait times.
Observe consistency among response times. Sharp variations indicate erratic
behavior. The typical way in which response times in a system deteriorate with
increasing transaction rate is gradual at first, then suddenly rapid. A typical curve
appears in Figure 20 on page 32. It shows a sharp change when, suddenly, the
response time increases dramatically for a relatively small increase in transaction
rate.
Chapter 3. Monitoring CICS Performance
31
Monitoring response time
Figure 20. Example of deteriorating response time due to increased workload
Response time is the main performance factor to track when measuring service
levels in CICS regions. Because interactive workload is usually variable, you
should collect data from periods of peak activity (volume of transactions) to get a
true picture of system activity. Activity peaks can differ among individual users or
among localized groups of terminals. Examples of this difference are peak activity
levels among different departments or on different teleprocessing lines. Refer to the
CICS Performance Guide for information about response-time measurement
techniques (for example, full-load measurement and single-transaction
measurement).
Monitoring resource use
Poor response time usually indicates inefficient use of either the processor or
storage (or both). This section describes how Tivoli Decision Support for
z/OS-supplied reports can help you isolate a resource as the cause of a CICS
performance problem.
Monitoring processor use
Tivoli Decision Support for z/OS supplies a CICS Application CPU Utilization,
Trend report (in Figure 21 on page 33) that shows weekly averages of CPU use for
the timespan you specify.
32
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Monitoring resource use
x
x
+
x
x
+
+
x
+
+
x
+
Figure 21. CICS Application CPU Utilization, Trend report
If both the CICS Performance feature’s statistics component and the System
Performance feature’s MVS component are installed and active, these reports are
available for analyzing transaction rates and processor use by CICS region:
v The CICS Transaction Processor Utilization, Monthly report (in Figure 22 on
page 34) shows monthly averages for the dates you specify.
v The CICS Transaction Processor Utilization, Daily report shows daily averages
for the dates you specify.
These reports have the advantage that they do not need CMF data. Statistics incur
less processing overhead.
Chapter 3. Monitoring CICS Performance
33
Monitoring resource use
Figure 22. CICS Transaction Processor Utilization, Monthly report
Monitoring storage use
Storage stress occurs when CICS is short of dynamic storage or extended dynamic
storage. It can indicate:
v Resource constraints, causing tasks to remain in storage longer than necessary
v Too many tasks in storage, overwhelming available free storage
v Poorly designed applications and programs, requiring unreasonable amounts of
storage
Symptoms of storage stress include:
v Poor response times
v Short-on-storage (SOS) conditions
v Heavy paging activity
v Dramatic increase in I/O activity on DFHRPL program libraries
v Program compression (applicable only to CICS/MVS)
Tivoli Decision Support for z/OS produces several reports that can help identify
storage stress. For example, the CICS Dynamic Storage (DSA) Usage report (in
Figure 23 on page 35) shows pagepool usage.
34
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Monitoring resource use
CICS Dynamic Storage (DSA) Usage
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
Free
Free
Largest
Pagepool
DSA
Cushion
storage storage
free
name
(bytes) (bytes)
(bytes) (pct)
area
Getmains Freemains
-------- --------- -------- --------- ------- --------- -------- --------CDSA
1048576
65536
802816
76
765952
3695
3620
ECDSA
8388608
262144
7667712
91
7667712
8946
7252
ERDSA
3145728
262144
1302528
41
1290240
204
3
EUDSA
8388608
262144
8388608
100
8388608
1
1
UDSA
4194304
65536
4186112
99
4182016
6
4
Tivoli Decision Support for z/OS Report: CICS809
Figure 23. Dynamic Storage (DSA) Usage report
CICS/ESA and CICS/TS differ from CICS/MVS in its defenses against stress.
CICS/MVS compresses programs (deleting all nonresident, not-in-storage
programs) when it issues a GETMAIN that does not successfully complete.
CICS/ESA and CICS/TS dynamically manage incremental and progressive
program compression as free storage decreases, removing least-recently-used
programs from storage. CICS/ESA also slows dispatching of new tasks
incrementally and progressively as free storage diminishes. The overhead of a full
program compression is avoided, if possible, by CICS/ESA.
Monitoring volumes and throughput
CICS/ESA and CICS/TS use MVS subtasks to fast load programs from DASD to
MVS library lookaside dataspaces in extended storage. This process practically
eliminates DASD I/O for critical programs. Paging from DASD increases demands
on processor resource, but paging from library lookaside areas has almost no effect
on processing performance.
Because CICS/ESA and CICS/TS use an MVS subtask to page and because an
MVS page-in causes a MVS task to halt execution, the number of page-ins is a
performance concern. Page-outs are not a concern because page-outs are scheduled
to occur during lulls in CICS processing. If you suspect that a performance
problem is related to excessive paging, you can use Tivoli Decision Support for
z/OS to monitor page-ins from data that RMF creates and then writes to SMF.
Consider controlling CICS throughput either by using MXT, AMXT, and CMXT in
CICS or by using the DL/I CMAXTSK specification in the DLZACT. Fewer
concurrent transactions require less central storage, cause less paging, and process
faster than a lot of transactions.
The degree of sensitivity of CICS regions to paging from DASD depends on the
transaction rate, the processor loading, and the average internal lifetime of the
CICS tasks. An ongoing, hour-on-hour acceptable rate can easily increase to
unacceptable levels during peak processing.
Chapter 3. Monitoring CICS Performance
35
Monitoring volumes and throughput
CICS Transaction Performance, Detail
MVS ID ='IPO2' CICS ID ='CFGTV1 '
Date: '2000-03-19' to '2000-03-20'
Tran
Tran
ID
count
------------QUIT
7916
CRTE
1760
AP00
1750
PM94
1369
VCS1
737
PM80
666
CESN
618
SU01
487
...
GC11
1
DM08
1
=========
20359
Avg
Avg
resp
CPU
time
time
(sec)
(sec)
--------- -------0.085
0.017
4.847
0.004
0.184
0.036
0.086
0.012
0.073
0.008
1.053
0.155
8.800
0.001
0.441
0.062
0.341
0.028
0.014
0.002
Prog
load
reqs
(avg)
----0
0
0
0
2
1
0
4
1
0
Program
Prog
FC
storage Getmains Getmains
loads calls Excepbytes
< 16 MB > 16 MB
(avg) (avg) tions
(max)
(avg)
(avg)
----- ----- ------ ------------ -------- -------0
18
0
74344
22
0
0
0
0
210176
1
0
0
8
0
309800
66
0
0
6
0
130096
24
0
0
7
0
81200
14
0
0
62
0
104568
583
0
0
0
0
41608
0
0
0
126
0
177536
38
0
0
0
2
0
0
0
37048
5040
============
309800
10
3
0
0
Tivoli Decision Support for z/OS Report: CICS101
Figure 24. CICS Transaction Performance, Detail report
The best indicator of a transaction’s performance is its response. For each
transaction ID, the CICS Transaction Performance, Detail report (in Figure 24)
shows the total transaction count and the average response time.
Use this report to start verifying that you are meeting service-level objectives. First,
verify that the values for average response time are acceptable. Then check that the
transaction rates do not exceed agreed-to limits. If a transaction is not receiving the
appropriate level of service, you must determine the cause of the delay.
Interpreting combined CICS and DB2 performance data
For each CICS task, CICS generates an LU6.2 unit-of-work ID. DB2 also creates an
LU6.2 unit-of-work ID. Figure 25, shows that Tivoli Decision Support for z/OS can
use the DB2 accounting token to correlate CICS records with DB2 records for the
same task.
DB2 accounting record
PLAN
TOKEN
GET PAGE SELECT
GRANT
CICS performance-monitoring record
TRAN
USERID
NETNAME
UOWID
TCIOWT
Figure 25. Correlating a CICS performance-monitoring record with a DB2 accounting record
36
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Interpreting combined CICS and DB2 performance data
Tivoli Decision Support for z/OS’s ability to match the NETNAME and UOWID
fields in a CICS record to the TOKEN field in a DB2 record lets you create reports
that show the DB2 activity caused by a CICS transaction.
Monitoring exception and incident data
An exception is an event that you should monitor. An exception appears in a report
only if it has occurred; reports do not show null counts. A single exception need
not be a cause for alarm. An incident is defined as an exception with severity 1, 2,
or 3.
The CICS Performance feature updates the EXCEPTION_T table for these incidents
and exceptions:
v Wait for storage
v Wait for main temporary storage
v Wait for a file string
v Wait for a file buffer
v Wait for an auxiliary temporary storage string
v Wait for an auxiliary temporary storage buffer
v Transaction ABEND
v System ABEND
v Storage violations
v Short-of-storage conditions
v VTAM request rejections
v I/O errors on auxiliary temporary storage
v I/O errors on the intrapartition transient data set
v Autoinstall errors
v MXT reached
v DTB overflow
v Link errors for IRC and ISC
v Journal buffer-full conditions
v CREAD and CWRITE fails (data space problems)
v Local shared pool (LSR) string waits (from A08BKTSW)
v Waits for a buffer in the LSR pool (from A09TBW)
v Errors writing to SMF
v No space on transient-data data set (from A11ANOSP)
v Waits for a transient-data string (from A11STNWT)
v Waits for a transient-data buffer (from A11ATNWT)
v Transaction restarts (from A02ATRCT)
v Maximum number of tasks in a class reached (CMXT) (from A15MXTM)
v Transmission errors (from A06TETE or AUSTETE)
Use the CICS001 (CICS Exceptions) and CICS002 (CICS Incidents) reports to report
on these events.
Monitoring SYSEVENT data
SYSEVENT data is a special type of transaction timing information. If the
SYSEVENT option is used, CICS issues a SYSEVENT macro at the end of each
transaction. For each transaction, this macro records:
v Transaction ID
v Associated terminal ID
v Elapsed time
By using CICS monitoring facility (CMF) with MVS System Resource Manager
(SRM), you can monitor transaction rates and internal response times without
Chapter 3. Monitoring CICS Performance
37
Monitoring SYSEVENT data
incurring the overhead of running the full CMF and associated reporting. This
approach is especially useful when you require only transaction statistics, rather
than the detailed information that CMF produces.
Refer to the CICS Performance Guide for information about this SRM macro and its
invocation.
Understanding CICS unit-of-work reporting
In a CICS multiple region operation (MRO) or intersystem communication (ISC)
environment, the available measurement data presents opportunities for tracing a
transaction as it migrates from one region (or processor complex) to another and
back. This measurement data lets you determine the total resource requirements of
the combined transaction as a unit of work, without having to separately analyze
the component transactions in each region. The ability to combine the component
transactions of an MRO or ISC series makes possible precise resource accounting
and chargeback, and capacity and performance analysis.
CICS monitoring facility (CMF) contains fields designed to allow association of
transactions executing in different regions in an MRO or ISC relationship.
Examining MRO and ISC characteristics
The use of MRO and ISC is often a solution to a variety of CICS system problems
and constraints. Spreading CICS activity across several discrete CICS address
spaces can provide such benefits as relief for virtual storage constraints, increased
availability, performance improvements, added security, and easier maintenance.
Although these benefits outweigh any disadvantages of using MRO and ISC, there
is one consequence of this technology. Transaction activity is more difficult to trace,
because CICS monitors write transaction performance records for each of the
MRO/ISC component transactions. For one typical unit of work, a record is written
for the terminal-owning region (TOR), the application-owning region (AOR), and
the file-owning region (FOR). Also, the data for the independent regions may be
written to different SMF data sets.
MRO-related transactions running in multiple regions can have different
transaction IDs. The most obvious examples are function-shipping transactions.
Transaction IDs for requests for file, DL/I, and other services are generated by
CICS. The first three characters of the transaction IDs for these mirror transactions
are CSM.
Two data fields allow tracing of MRO and ISC activity as transactions migrate
from one region to another: unit-of-work ID (UOWID) and network name
(NETNAME). When a transaction is initiated through a terminal, CICS establishes
values for these fields reflecting the region and transaction of origin, and these
values get picked up and assigned to the corresponding fields in the performance
monitor record written for that transaction. When this local transaction causes one
or more remote transactions to be initiated, the values for UOWID and NETNAME
are passed through the remote link and assigned to the performance monitor
records written for the remote transaction(s) in their respective regions.
The UOWID is an eight-byte field whose value is derived from the system
time-of-day clock. The value in the UOWID is a copy of the TOD clock value, with
the high-order byte chopped off. CICS uses the low-order two bytes for what it
38
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Understanding CICS unit-of-work reporting
calls a period count and, according to the CICS Customization Guide its value
depends on synchpoint activity. Therefore, it can change during the life of a
transaction.
The NETNAME value is used to identify the region of origin for MRO and ISC
transactions. For MRO, the NETNAME value is taken from the terminal control
table (TCT) of the region of origination. For ISC transactions, the NETNAME is
networkID.LUname and can be up to 17 characters long. The NETNAME obtained
from the TCT for MRO is not the same as the name by which the region is known
to VTAM, that is the VTAM APPLID.
The CICS UOW Response Times report (in Figure 26) shows an example of how
Tivoli Decision Support for z/OS presents CICS unit-of-work response times.
CICS UOW Response Times
Time: '09.59.00' to '10.00.00'
Date: 2000-03-10
Adjusted
UOW
start
Tran
time
ID
-------- ---09.59.25 OP22
OP22
CICS
ID
-------CICSPROD
CICSPRDC
UOW Response
Program tran
time
name
count (sec)
-------- ----- -------DFHCRP
2
0.436
OEPCPI22
09.59.26 AP63 CICSPRDE APPM00
AP63 CICSPROD DFHCRP
2
0.045
09.59.26 ARUS CICSPROD DFHCRP
CSM5 CICSPRDB DFHMIR
ARUS CICSPRDC AR49000
3
0.158
09.59.26 CSM5 CICSPRDB DFHMIR
GCS6 CICSPROD GCSCPS20
2
0.068
09.59.27 CSM5
CSM5
MQ01
MQ01
4
0.639
CICSPRDB
CICSPRDB
CICSPROD
CICSPRDD
DFHMIR
DFHMIR
DFHCRP
CMQ001
...
Tivoli Decision Support for z/OS Report: CICS902
Figure 26. CICS UOW Response Times report
Chapter 3. Monitoring CICS Performance
39
40
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 4. Using the CICS Partitioning feature
This chapter describes the CICS Partitioning feature.
The CICS Partitioning feature enables customers that have a multiple z/OS
environment to perform a parallel collection of data produced by CICS on different
z/OS systems. This parallel collection provides an improvement in the total
collection time for large amounts of CICS data running on different z/OS systems.
The CICS Partitioning feature uses partitioned DB2 tablespaces. The use of
partitioned tablespaces enables you to update in parallel the same tables, provided
that the data belongs to different partitions. Thus the DB2 tablespaces, tables and
indexes have been implemented to allow the possibility of addressing data,
produced on different z/OS systems (that is, having different MVS_SYSTEM_IDs),
to different partitions.
Considering which components to install
Figure 27 shows that the CICS Partitioning feature is divided into three
components. The CICS monitoring component is divided further into nine
subcomponents. Components and subcomponents provide support for specific
operating systems, subsystems, and licensed programs.
© Copyright IBM Corp. 1994, 2009
41
Considering which components to install
Figure 27. CICS Partitioning feature structure
Consider carefully which components to install. Components are groups of Tivoli
Decision Support for z/OS objects (for example, predefined update definitions, data
tables, and reports). If you find that you need reports from a component that you
have not installed, you must install that component and then wait several days or
weeks until enough data has been collected to create reports. However, if you
install more components than you need, Tivoli Decision Support for z/OS collects
needless data, which takes up disk space and uses processor time.
Note: You cannot uninstall an individual subcomponent. You must uninstall a
component, then reinstall it, selecting only those subcomponents you need.
Refer to the Administration Guide and Reference for details.
At this point, you might find it helpful to examine the predefined reports for each
subcomponent. For more information, see Chapter 7, “Reports.”
Evaluating the CICS monitoring component
The CICS monitoring facility (CMF) provides the performance data for the CICS
monitoring component. Figure 27 on page 42 shows that this component is the
only CICS Performance feature component that contains subcomponents.
42
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Considering which components to install
Notes:
1. Subcomponents 1 through 3 summarize data by transaction, and
subcomponents 4 through 6 further summarize data by application.
2. To make efficient use of the application analysis subcomponents
(subcomponents 4, 5, and 6), you must update the CICS_LOOKUP_APPL
table. For more information, see “Updating CICS_LOOKUP_APPL” on page 24.
1. Basic subcomponent
This first subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize, by transaction, basic data gathered by CMF. Consider
using this subcomponent as a starting point.
2. DBCTL subcomponent
Database control (DBCTL), is a DL/I interface that uses an address space separate
from CICS. It is available only for CICS/ESA and CICS/TS. If you run DBCTL,
consider installing this subcomponent. It summarizes data by transaction. Its tables
contain the DBCTL monitoring fields. (You must verify the presence of these fields
in the performance monitoring record, as described in “Making input data
available” on page 16.)
3. DL/I subcomponent
This subcomponent processes data from the local interface to a DL/I database. If
you run DL/I, consider installing this subcomponent. It summarizes data by
transaction. Available for CICS/MVS, CICS/ESA, and CICS/TS, its tables contain
the DL/I monitoring fields. (As with the DBCTL subcomponent, verify the
presence of the DL/I fields in the performance monitoring record, as described in
“Making input data available” on page 16.)
4. Basic application analysis subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize transaction data by application. See “Updating the lookup
tables” on page 23 for information on the customization needed to use this
subcomponent.
5. DBCTL application analysis subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize DBCTL transaction data by application. For the CICS
Performance feature to summarize transaction data by application, you must use
the customization procedure in “Updating the lookup tables” on page 23.
6. DL/I application analysis subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize DL/I transaction data by application. Again, you must use
the customization procedure in “Updating the lookup tables” on page 23 for the
CICS Performance feature to successfully summarize transaction data by
application.
7. CICS/MVS subcomponent (global + accounting)
Only CICS/MVS users should consider installing this global and accounting
subcomponent. Its tables contain the Tivoli Decision Support for z/OS objects
necessary to summarize global and accounting data only for CICS Version 2.
8. CICS TS Transaction Resources subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to collect data on transaction resources from SMF_110_1 class 5 record.
Chapter 4. Using the CICS Partitioning feature
43
Considering which components to install
9. CICS TS Enterprise Java Beans subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to collect enterprise bean-related data from SMF_110_1 class 3
monitoring record.
10. CICS Resource Manager Interface subcomponent
This subcomponent contains the Tivoli Decision Support for z/OS objects
necessary to summarize by transaction Resource Management Interface data if this
option is enabled in the Monitoring Control Table (MCT).
Evaluating the CICS statistics component
Statistics, supported only for CICS/ESA and CICS/TS, are a tool for monitoring a
CICS system; they collect information on the CICS system as a whole, without
regard to tasks. Consider installing this component if you are interested in these
types of statistics (written to SMF data sets by the CICS statistics domain):
v Interval
v End-of-day
v Requested
v Unsolicited
For information about statistics, refer to the appropriate CICS Performance Guide.
Evaluating the CICS transaction and unit-of-work analysis
component
The CICS transaction and unit-of-work analysis component collects data about a
transaction as it migrates from one CICS region (or processor complex) to another
and back, letting you determine the total resource requirements of the combined
transaction as a unit of work.
Note: Unit-of-work data collection generates intensive processing, which
significantly increases collection time.
If you install this component, collect its data with a separate collect job, and for a
limited time (15 minutes should be sufficient). Do not include this component’s
table in your normal collect job. Otherwise, data collection takes too much time to
complete and results in a table that is too large to manage. For more information,
see “Optimizing data collection” on page 19.
How the CICS Partitioning feature processes CMF data
The data sections of the following CMF records consist of records of identical
format that relate to one of these monitoring classes:
v Dictionary data (class 1)
v Accounting data (class 2) for CICS/MVS only
v Performance data (class 3)
v Exception data (class 4)
Dictionary data describes fields in CMF-generated performance data sections. CICS
writes a new dictionary record whenever performance monitoring is activated. The
DRL2CICS record procedure updates the CICS_DICTIONARY table with any new
dictionary records. As it processes a CMF record, Tivoli Decision Support for z/OS
loads into memory SMF log dictionary records and any dictionary records stored
in CICS_DICTIONARY.
44
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
How CICS Partitioning processes CMF data
Figure 28. How CMF performance records are processed by the CICS Partitioning feature
Tivoli Decision Support for z/OS uses the most recently generated dictionary
section (that matches the MVS system ID, CICS system ID, and class values) to
resolve field values in each performance record. As shown in Figure 28, DRL2CICS
creates a common transaction performance record (SMF_CICS_T) from the CICS
transaction performance records.
The log collector uses the DRL2CICS record procedure to map field values for data
in accounting, performance, and exception records to intermediate records mapped
by these record definitions:
SMF_CICS_A
Maps accounting records that Tivoli Decision
Support for z/OS generates from CICS/MVS
accounting records
SMF_CICS_T
Maps transaction performance records that Tivoli
Decision Support for z/OS generates from
CICS/MVS, CICS/ESA, and CICS/TS performance
records
SMF_CICS_E2
Maps exception records that Tivoli Decision
Support for z/OS generates from CICS/MVS
exception records
Chapter 4. Using the CICS Partitioning feature
45
How CICS Partitioning processes CMF data
The CICS/ESA or CICS/TS exception data section is a single, fixed-length record,
mapped by the SMF_110_E record definition. Update definitions store exception
data in the Tivoli Decision Support for z/OS common table EXCEPTION_T, but
some rows in this table are also created from exceptional conditions in CICS/ESA
or CICS/TS statistics records.
Tivoli Decision Support for z/OS stores data in DB2 columns that correspond to
most fields found in CICS performance data. If you need to add fields to CMF
performance records, remember to update the Tivoli Decision Support for z/OS
CICS_FIELD control table with your fields, and add fields in the SMF_CICS_T
record definition with the offset and length that you specify in CICS_FIELD. The
CICS_FIELD table is loaded using the SQL statements in the
DRLxxx.SDRLDEFS(DRLTCIFI) member. Use this member as a template for
additional entries. The SMF_CICS_T record definition is in the
DRLxxx.SDRLDEFS(DRLRS110) member. For more information about SMF records
and data fields that CMF produces for CICS refer to the appropriate CICS
Customization Guide.
The log collector uses the DRL4CICS record procedure to map field values for data
in transaction resource monitoring records (class 5). The output record to map
these fields is SMF_CICS_TR.
Figure 29. How CICS/TS transaction resource records are processed by the CICS
Partitioning feature
Data tables in the CICS Partitioning feature
The data tables for the CICS Partitioning feature are the same as the data tables for
the CICS Performance feature. The only difference is in the name, which has a P
added to the end, for the CICS Partitioning feature. For example, the CICS
Performance data table CICS_S_AUTO_TER_T is the same as the CICS Partitioning
data table CICS_S_AUTO_TERM_TP.
For a description of the tables that belong to the CICS Partitioning feature, refer to
the description of the data tables that belong to the non-partitioning feature in
Chapter 6, “Data tables, lookup tables, and control tables,” on page 69. For more
details about the data table naming convention, refer to “Naming standard for
CICS Partitioning tables” on page 47.
46
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Data tables in the CICS Partitioning feature
Note: The CICS_EXCEPTION_T data table has the same name in the CICS
Performance and CICS Partitioning features.
Naming standard for CICS Partitioning tables
The names of the CICS Partitioning feature tables use this format:
CICS_prefix_content_suffix
Where:
v prefix identifies the component or subcomponent type (for example, S for the
statistics component and A for the application analysis subcomponents). Table
names for subcomponent 1, the basic subcomponent, do not contain prefixes;
table names for the remaining six subcomponents do contain a prefix.
v content is a description (for example, CICS_TRANSACTIO for
subcomponent 1’s partitioned CICS transaction statistics).
v suffix indicates the summarization level of the data in the table (for example,
CICS_TRANSACTIO_DP for partitioned CICS transaction statistics summarized
by day).
A table name can have these summarization-level suffixes:
_TP
The table holds nonsummarized, partitioned data (timestamped data).
_HP
The table holds partitioned data summarized by hour (hourly data).
_DP
The table holds partitioned data summarized by day (daily data).
_WP The table holds partitioned data summarized by week (weekly data).
_MP The table holds partitioned data summarized by month (monthly data).
Tables in the CICS monitoring component
As described in “Evaluating the CICS monitoring component” on page 42, the
CICS monitoring component is the only CICS Partitioning feature component that
contains subcomponents. This section groups data tables for the CICS monitoring
component by these subcomponents:
1.
2.
3.
4.
5.
6.
Basic subcomponent
DBCTL subcomponent
DL/I subcomponent
Basic application analysis subcomponent
DBCTL application analysis subcomponent
DL/I application analysis subcomponent
7. CICS/MVS subcomponent (global + accounting)
8. CICS TS Transaction Resources subcomponent
9. CICS TS Enterprise Java Beans subcomponent
Subcomponents 1 and 4 are based on the transaction data, and the tables are
almost the same, differing only in their key structure.
Tables in the CICS statistics component
As described in “Evaluating the CICS statistics component” on page 44, the CICS
Partitioning feature supports statistics only for CICS/ESA and CICS/TS. If you
install the CICS statistics component, Tivoli Decision Support for z/OS loads into
its system tables the data tables described in Chapter 6, “Data tables, lookup tables,
and control tables,” on page 69.
Chapter 4. Using the CICS Partitioning feature
47
Data tables in the CICS Partitioning feature
Tables in the CICS transaction and unit-of-work analysis
component
As described in “Evaluating the CICS transaction and unit-of-work analysis
component” on page 44, if you install the CICS transaction and unit-of-work
analysis component, Tivoli Decision Support for z/OS loads into its system tables
the data table and view tables described in Chapter 6, “Data tables, lookup tables,
and control tables,” on page 69.
If you install this component, use a separate collection job for it. In the daily CICS
collection job, exclude the data table provided with this component. Otherwise,
data collection takes too much time to complete and results in a table that is too
large to manage. For more information, see “Optimizing data collection” on page
19.
Environment restrictions
Consider the following restrictions are:
v The CICS Partitioning feature can be installed only if DB2 Version 4 or later is
installed. This is because TYPE 2 indexes are used in the INDEX definition.
v Different log datasets have to be supplied for each collect job. The log datasets
collected by each collect job must contain only the CICS records produced by the
MVS system that are to be inserted in a single partition. If this does not occur,
the records for collection can be filtered through a condition in the COLLECT
statement:
COLLECT SMF WHERE SMFFRTY=110 AND
SMFSID='JSYS'
1^ condition
2^ condition
The 1^ condition selects only CICS records. The 2^ condition selects only records
with JSYS in the MVS system ID. Thus only CICS records having JSYS in the
MVS_SYSTEM_ID (SMFSID) have to be collected. The records with different
MVS system IDs, to be stored in different partitions, must be collected by
separate jobs.
Another method to avoid the processing of data other than CICS data is to
exclude tables belonging to components different from CICS partitioning, if
installed. This can be obtained through the EXCLUDE clause (or INCLUDE on
CICS table to fill in) in the COLLECT statement:
COLLECT SMF
WHERE SMFFRTY=110 AND
SMFSID='JSYS'
EXCLUDE tables
INCLUDE tables
Note: These rules must be correctly maintained to avoid contention problems.
v A new parameter has been added in the COLLECT statement. This parameter
must be specified when collecting on CICS partitioned components to avoid
timeout problems due to contentions. It must not be specified when collecting
on nonpartitioned components to avoid performance degradation.
An example of the COLLECT statement is:
COLLECT SMF
WHERE SMFSID='JSYS'
EXCLUDE tables
INCLUDE tables
REPROCESS
PARTITION
COMMIT AFTER BUFFER FULL BUFFER SIZE 500000;
v The MERGE clause cannot be used with the CICS Partitioning feature.
48
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Customization considerations
Customization considerations
All the tables are defined in a partitioned tablespace and have a partitioned index
except the CICS_FIELD. The following steps have to be added to the normal
installation of the Tivoli Decision Support for z/OS:
1. Predefine the storage groups (as many as there are partitions) as follows:
v If you are installing the Tivoli Decision Support for z/OS for the first time,
initialize the DB2 database by performing Step 3 of the installation procedure
(see the Administration Guide and Reference), that is, run the DRLJDBIP job
after running the DRLJDBIN job.
v If you have already run DRLJDBIN in another environment, you have only
to run DRLJDBIP. This job contains the SQL statements that are needed to
create the storage groups for the CICS Partitioning feature (with as many
partitions as needed, four as default):
CREATE STOGROUP STOGRx
VOLUMES (VOLSTOGRx1, VOLSTOGRx, ...)
VCAT CATALOG-NAME;
GRANT USE OF STOGROUP STOGRx TO DRL, DRLSYS WITH GRANT OPTION;
Note: If you need more (or less) than four partitions, you have to customize
the DRLJDBIP job accordingly.
2. If you are migrating from a previous release environment, before installing the
components, perform UPDATE SYSTEM TABLES (from the System Tables
window).
If you are installing Tivoli Decision Support for z/OS for the first time, perform
CREATE SYSTEM Tables.
3. Use the two modules DRLJDICT and DRLJEXCP, supplied with the product,
to partition the two tables CICS_DICTIONARY and EXCEPTION_T.
If you are installing the Tivoli Decision Support for z/OS for the first time, run
the DRLJDICT job after creating the system tables. If, when you are going to
install the CICS Partitioning feature, you have already installed some
components that include the EXCEPTION_T table (that is, the EXCEPTION_T
table results already installed), run the DRLJEXCP job.
If you are migrating from a previous release environment, perform UPDATE
SYSTEM TABLES and then run these two jobs.
In any case, DRLJEXCP has to be run only if the EXCEPTION_T table has
already been created, that is, if any component that includes it has been
installed.
The modules contain the SQL statements that are needed to create partitioned
tablespaces for the two tables, to unload the data already present, to create the
new tables and the Type 2 partitioned indexes, and to reload the data. After
running these statements, the OLD DEFINITIONS will be lost and the table
will be partitioned. The CICS_DICTIONARY table will be in common with the
old CICS monitoring component, if any. The EXCEPTION_T table will be in
common with all the other components that originally included it.
Chapter 4. Using the CICS Partitioning feature
49
Customization considerations
4. Before installing the components, customize the definitions of the tablespaces
for the number of partitions that you need and specify the PRIQTY and
SECQTY for each partition as follows in the following sample, properly
customizable by the user:
SQL CREATE TABLESPACE DRLSPS11
IN &DATABASE.
NUMPARTS 4
(PART 1 USING STOGROUP STOGR1
PRIQTY 2000
SECQTY 1000,
PART 2 USING STOGROUP STOGR2
PRIQTY 2000
SECQTY 1000,
PART 3 USING STOGROUP STOGR3
PRIQTY 2000
SECQTY 1000,
PART 4 USING STOGROUP STOGR4
PRIQTY 2000
SECQTY 1000)
LOCKSIZE PAGE
CLOSE NO;
Most table spaces for the CICS Partitioning Feature have LOCKSIZE ANY set
by default. Anyway, administrators may consider to use of LOCKSIZE PAGE.
If you need more (or less) partitions, add (or delete) one PART block for each
partition from the tablespace definitions and change the NUMPARTS
parameter.
If you change the number of partitions, you have to modify the INDEX
definitions accordingly.
After customizing the tablespace definitions, you have to customize the INDEX
definitions so as to set the highest value of the partition key for each partition.
This is so as to have one partition for each MVS ID data that you want to
collect separately. In the supplied definitions, the partition key is the
MVS_SYSTEM_ID key and, according to the value of this key, the partitions
have their boundaries as follows:
SQL CREATE TYPE2 UNIQUE INDEX &PREFIX.CICSTRANUSR_HP_IX
ON &PREFIX.CICS_TRAN_USR_HP
(MVS_SYSTEM_ID,
DATE,
PERIOD_NAME,
TIME, CICS_SYSTEM_ID,
TRANSACTION_ID, USER_ID)
CLUSTER
(PART 1 VALUES(BZZZ')
USING STOGROUP STOGR1
PRIQTY 2000
SECQTY 1000,
PART 2 VALUES(CZZZ')
USING STOGROUP STOGR2
PRIQTY 2000
SECQTY 1000,
PART 3 VALUES(JZZZ')
USING STOGROUP STOGR3
PRIQTY 2000
SECQTY 1000,
PART 4 VALUES(ZZZZ')
USING STOGROUP STOGR4
PRIQTY 2000
SECQTY 1000);
The string specified in the VALUES parameter defines the maximum value of
the keys that will be stored in the partition.
5. Start the installation with the components that you need.
50
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Part 2. CICS performance feature Reference
Chapter 5. Data flow and Tivoli Decision Support
for z/OS objects . . . . . . . . . . . .
Tivoli Decision Support for z/OS data flow: an
overview . . . . . . . . . . . . . . .
Record processing by the CICS Performance feature
How Tivoli Decision Support for z/OS processes
CMF data . . . . . . . . . . . . . . .
How Tivoli Decision Support for z/OS processes
dictionary data . . . . . . . . . . . .
Using the DFHMNDUP utility . . . . . .
Using the DRL1CIEX utility . . . . . . .
How Tivoli Decision Support for z/OS processes
CICS data records . . . . . . . . . . .
How Tivoli Decision Support for z/OS processes
CICS/ESA statistics. . . . . . . . . . .
55
55
58
62
66
67
67
67
68
Chapter 6. Data tables, lookup tables, and
control tables . . . . . . . . . . . . . 69
Naming standard for CICS Performance tables . . 69
Table descriptions . . . . . . . . . . . . 70
Tables in the CICS monitoring component . . . . 70
1. Basic subcomponent data tables . . . . . 71
CICS_TRAN_USR_H, _D, _W . . . . . . 71
CICSBTS_TRAN_USR_H, _D, _W . . . . . 72
CICSCHN_TRAN_USR_H, _D, _W . . . . 73
CICSDOC_TRAN_USR_H, _D, _W . . . . 74
CICSWEB_TRAN_USR_H, _D, _W . . . . 75
Common fields for subcomponents 1, 4, 8, and
11 . . . . . . . . . . . . . . . 76
Common fields for the business transaction
service (BTS) . . . . . . . . . . . . 89
Common fields for the Channel and Container
usage for data transfer (CHN) . . . . . . 90
Common fields for the document handler
(DOC) . . . . . . . . . . . . . . 92
Common fields for the Web interface (WEB)
92
2. DBCTL subcomponent . . . . . . . . . 94
CICS_DBCTL_USR_H, _D, _W . . . . . . 94
3. DL/I subcomponent . . . . . . . . . 96
CICS_DLI_USR_H, _D, _W . . . . . . . 96
4. Basic application analysis subcomponent . . 97
CICS_A_BASIC_H, _W . . . . . . . . 97
CICSBTS_A_BASIC_H, _W . . . . . . . 98
CICSCHN_A_BASIC_H, _W . . . . . . . 98
CICSDOC_A_BASIC_H, _W . . . . . . . 99
CICSWEB_A_BASIC_H, _W . . . . . . 100
5. DBCTL application analysis subcomponent
100
CICS_A_DBCTL_H, _W . . . . . . . . 100
6. DL/I application analysis subcomponent . . 102
CICS_A_DLI_H, _W . . . . . . . . . 102
7. CICS/MVS subcomponent (global +
accounting) . . . . . . . . . . . . . 103
CICS_M_ACCOUNT_H, _D, _W, _M . . . 103
8. Basic transaction subcomponent . . . . . 104
CICS_TRANSACTION_H, _D, _W . . . . 104
CICSBTS_TRANSACT_H, _D, _W . . . . 105
© Copyright IBM Corp. 1994, 2009
CICSCHN_TRANSACT_H, _D, _W . . . .
CICSDOC_TRANSACT_H, _D, _W . . . .
CICSWEB_TRANSACT_H, _D, _W . . . .
9. DBCTL transaction subcomponent . . . .
CICS_DBCTL_TRAN_H, _D, _W . . . . .
10. DL/I transaction subcomponent . . . . .
CICS_DLI_TRAN_H, _D, _W . . . . . .
11. Basic application user subcomponent . . .
CICS_A_USR_H, _W . . . . . . . . .
CICSBTS_A_USR_H, _W. . . . . . . .
CICSCHN_A_USR_H, _W . . . . . . .
CICSDOC_A_USR_H, _W . . . . . . .
CICSWEB_A_USR_H, _W . . . . . . .
12. DBCTL application user subcomponent . .
CICS_A_DBCTL_USR_H,_W . . . . . .
13. DL/I application user subcomponent . . .
CICS_A_DLI_USR_H, _W . . . . . . .
14. CICS TS Transaction Resources
subcomponent . . . . . . . . . . . .
CICS_FILE_TRAN_H, _D, _W . . . . . .
CICS_QUEUE_TRAN_H, _D, _W . . . . .
15. CICS TS Enterprise Java Beans
subcomponent . . . . . . . . . . . .
CICS_BEAN_REQ_H, _D, _W . . . . . .
16. CICS Resource Manager Interface
subcomponent . . . . . . . . . . . .
CICS_RMI_PERF_T . . . . . . . . .
CICS_RMI_PERF_H . . . . . . . . .
CICS_RMI_PERF_D . . . . . . . . .
Tables in the CICS OMEGAMON monitoring
component . . . . . . . . . . . . . .
1. File and Database subcomponent data tables
CICS_O_FL_H, _D, _W . . . . . . . .
2. File and Database Application subcomponent
data tables . . . . . . . . . . . . .
CICS_O_A_FL_H,_D,_W . . . . . . .
3. File and Database Transaction subcomponent
data tables . . . . . . . . . . . . .
CICS_O_TRAN_FL_ H,_D,_W . . . . . .
4. File and Database Application User
subcomponent data tables . . . . . . . .
CICS_O_A_USR_FL_ H,_D,_W . . . . .
5. File and Database Detailed usage
subcomponent data tables . . . . . . . .
CICS_O_FL_DTL_H, _D, _W . . . . . .
Tables in the CICS statistics component. . . . .
CICS_AVAIL_T . . . . . . . . . . . .
CICS_AVAIL_D,_W . . . . . . . . . .
CICS_MVSTCB_D . . . . . . . . . . .
CICS_MVSTCB_H . . . . . . . . . . .
CICS_MVSTCB_RES_D . . . . . . . . .
CICS_MVSTCB_RES_H . . . . . . . . .
CICS_PIPELINE_T . . . . . . . . . .
CICS_DOCT_RES_D . . . . . . . . . .
CICS_DOCT_RES_H . . . . . . . . . .
CICS_S_AUTO_TERM_T . . . . . . . .
106
106
107
107
108
109
109
111
111
111
112
113
113
114
114
116
116
117
118
119
120
120
121
121
122
123
124
124
125
127
127
127
127
128
128
129
129
133
133
134
135
135
136
137
137
138
139
140
51
CICS_S_AUTO_TERM_D
CICS_S_CFDT_GREQ_T .
CICS_S_CFDT_GREQ_D.
CICS_S_CFDT_SERV_T .
CICS_S_CFDT_SERV_D .
CICS_S_CFDT_STOR_T .
CICS_S_CFDT_TBAC_T .
CICS_S_CFDT_TBAC_D .
CICS_S_DB2CONN_T .
CICS_S_DB2CONN_D .
CICS_S_DB2ENTRY_T .
CICS_S_DB2ENTRY_D .
CICS_S_DBCTL_T . . .
CICS_S_DBCTL_D. . .
CICS_S_DISPATCH_T .
CICS_S_DISPATCH_D .
CICS_S_DLI_T . . . .
CICS_S_DLI_D . . . .
CICS_S_DSPOOL_T . .
CICS_S_DSPOOL_D . .
CICS_S_DUMP_T . . .
CICS_S_DUMP_D . . .
CICS_S_ENQUE_MGR_T
CICS_S_ENQUE_MGR_D
CICS_S_ENTBEANS_T,_D
CICS_S_FEPI_T. . . .
CICS_S_FEPI_D . . .
CICS_S_FILE_T. . . .
CICS_S_FILE_D . . .
CICS_S_GLB_TCPIP_T .
CICS_S_GLB_TCPIP_D .
CICS_S_GLBURIMAP_T.
CICS_S_GLBURIMAP_D
CICS_S_GLOBAL_T . .
CICS_S_GLOBAL_D . .
CICS_S_INTERCOM_T .
CICS_S_INTERCOM_D .
CICS_S_JOURNAL_T. .
CICS_S_JOURNAL_T2 .
CICS_S_JOURNAL_D .
CICS_S_JOURNAL_D2 .
CICS_S_JVM_PROF_T,_D
CICS_S_JVM_PROG_T,_D
CICS_S_JVMPOOL_T,_D
CICS_S_LOGSTREAM_T
CICS_S_LOGSTREAM_D
CICS_S_LSR_POOL_T .
CICS_S_LSR_POOL_D .
CICS_S_LSRP_FILE_T .
CICS_S_LSRP_FILE_D .
CICS_SMD_SUBP_D . .
CICS_SMD_SUBP_H . .
CICS_S_MONITOR_T .
CICS_S_MONITOR_D .
CICS_S_NC_LSTRUC_T .
CICS_S_NC_LSTRUC_D.
CICS_S_NCS_STOR_T .
CICS_S_PIPELINE_T . .
CICS_S_PROGRAM_T .
CICS_S_PROGRAM_D .
CICS_S_RECOV_MGR_T
52
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
142
143
144
145
147
150
150
151
152
155
157
159
160
162
162
164
166
167
169
170
171
172
172
174
175
176
178
179
182
184
185
186
188
189
193
197
202
207
207
208
209
210
211
212
213
214
215
217
219
220
221
222
222
224
225
226
227
228
228
230
232
CICS_S_RECOV_MGR_D . .
CICS_S_STOR_DOM_T . . .
CICS_S_STOR_DOM_D . . .
CICS_S_STOR_DSA_T . . .
CICS_S_STOR_DSA_D . . .
CICS_S_STOR_TASK_T . . .
CICS_S_STOR_TASK_D . . .
CICS_S_TCLASS_T . . . .
CICS_S_TCLASS_D . . . .
CICS_S_TCPIP_T . . . . .
CICS_S_TCPIP_D . . . . .
CICS_S_TERMINAL_T . . .
CICS_S_TERMINAL_D . . .
CICS_S_TRAN_T . . . . .
CICS_S_TRAN_D, _M . . .
CICS_S_TRANSIENT_T . . .
CICS_S_TRANSIENT_D . . .
CICS_S_TS_BPOOL_T . . .
CICS_S_TS_BPOOL_D . . .
CICS_S_TS_CF_T . . . . .
CICS_S_TS_CF_D . . . . .
CICS_S_TS_STOR_T . . . .
CICS_S_TS_STOR_D . . . .
CICS_S_URIMAP_T . . . .
CICS_S_WEBSERV_T . . . .
CICS_TCPIP_CONN_D . . .
CICS_TCPIP_CONN_H . . .
Tables in the CICS transaction and
analysis component . . . . .
CICS_T_TRAN_T . . . . .
CICSBTS_T_TRAN_T . . . .
CICSCHN_T_TRAN_T . . .
CICSDOC_T_TRAN_T . . .
CICSWEB_T_TRAN_T . . .
CICS_T_UOW_TV1 . . . .
CICS_T_UOW_TV2 . . . .
CICS_WMQ_CONN_D . . .
CICS_WMQ_CONN_H . . .
Lookup tables . . . . . . .
CICS_AVAIL_RES . . . . .
Example of table contents .
CICS_LOOKUP_APPL . . .
CICS_LOOKUP_SYSTEM . .
CICS_OMEG_FIELD . . . .
CICS_TIMEZONES . . . .
Control tables . . . . . . .
CICS_DICTIONARY . . . .
CICS_FIELD. . . . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
unit-of-work
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
Chapter 7. Reports . . . . . . . . . .
Report format and general description . . . .
Report ID . . . . . . . . . . . .
Report group . . . . . . . . . . .
Source . . . . . . . . . . . . . .
Attributes . . . . . . . . . . . .
Variables . . . . . . . . . . . . .
Reports in the CICS monitoring component . .
CICS Transaction Performance, Detail . . .
CICS Transaction Channel Performance, Detail
CICS Application Channel Performance, Detail
CICS Application Response Times, Overview
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
233
235
236
236
239
241
242
243
244
245
247
248
250
251
252
253
255
257
258
259
261
263
264
265
266
267
269
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
270
270
284
286
288
290
291
291
292
293
294
294
295
295
296
296
299
299
299
300
.
.
.
.
.
.
.
.
.
301
301
301
301
301
302
302
302
302
304
305
307
CICS Application Response Times, Trend . . .
CICS Application Response Times, Detail . . .
CICS Application CPU Utilization, Trend . . .
CICS Application I/O Wait Times, Detail . . .
CICS Application Main Response Times, Detail
CICS Application Wait Times, Detail. . . . .
CICS Application DLI Call Utilization, Trend
CICS/MVS CMF Transaction Statistics . . . .
CICS Transaction Processor Utilization, Daily
CICS Transaction Processor Utilization, Monthly
CICS Transactions Resources Details, Daily . .
CICS Enterprise Java Beans Details, Daily . . .
Reports in the CICS OMEGAMON monitoring
component . . . . . . . . . . . . . .
CICS OMEGAMON database/file total requests,
hourly . . . . . . . . . . . . . . .
CICS OMEGAMON database/file total
commands, hourly . . . . . . . . . .
CICS OMEGAMON database/file avg request
response, daily . . . . . . . . . . . .
CICS OMEGAMON database/file avg
command response, daily . . . . . . . .
CICS OMEGAMON transaction database/file
requests, daily . . . . . . . . . . . .
CICS OMEGAMON transaction database/file
commands, daily . . . . . . . . . . .
CICS OMEGAMON transaction DB2 averages,
hourly . . . . . . . . . . . . . . .
Reports in the CICS statistics component . . . .
CICS Global Loader . . . . . . . . . .
CICS Global Temporary Storage . . . . . .
CICS Global VTAM . . . . . . . . . .
CICS Global DTB . . . . . . . . . . .
CICS Global IRC Batch . . . . . . . . .
CICS Transaction Usage . . . . . . . . .
CICS Program Usage . . . . . . . . . .
CICS Dynamic Storage (DSA) Usage . . . .
CICS File Statistics . . . . . . . . . .
CICS ISC/IRC Function Shipping by Connection
CICS ISC/IRC Global . . . . . . . . .
CICS ISC/IRC Mode Entries . . . . . . .
CICS ISC/IRC System Entries by Connection
CICS TS Recovery Manager . . . . . . .
CICS TS Enqueue Manager . . . . . . . .
CICS TS Logstreams . . . . . . . . . .
CICS DB2 Connection: TCB Statistics . . . .
CICS DB2 Connection: Buffer Pool Statistics . .
CICS DB2 Connection: Command Statistics . .
CICS DB2 Entries: Resource Info . . . . . .
CICS DB2 Entries: Request Statistics . . . . .
CICS DB2 Entries: Performance Statistics . . .
CICS Shared TS queue server: Buffer Pool
Statistics . . . . . . . . . . . . . .
CICS Shared TS queue server: Storage Statistics
CICS TCP/IP Global statistics . . . . . . .
CICS TCP/IP Service Statistics . . . . . .
CICS TCP/IP Service Requests Statistics . . .
CICS TCP/IP Service Requests: Daily Trend . .
CICS CFDT Server Statistics . . . . . . .
CICS CFDT Storage Statistics . . . . . . .
CICS NC Storage Statistics . . . . . . . .
308
309
311
312
314
316
317
318
319
319
320
321
322
322
CICS URIMAP Global statistics . . . . . .
CICS URIMAP Resource statistics . . . . .
CICS JVM Profile Statistics, Daily. . . . . .
CICS Transaction Processor Utilization, Daily
CICS Transaction Processor Utilization, Monthly
CICS Availability Reports . . . . . . . .
CICS_DB2 Connection Availability, Daily
Overview report . . . . . . . . . .
CICS Subsystem Availability, Daily Trend
report . . . . . . . . . . . . . .
Reports in the CICS transaction and unit-of-work
analysis component . . . . . . . . . . .
CICS UOW Response Times . . . . . . .
Reports common to all components . . . . . .
CICS Exceptions . . . . . . . . . . .
CICS Incidents . . . . . . . . . . . .
362
363
365
366
367
368
368
368
369
369
371
371
372
323
324
324
325
326
327
328
328
329
330
331
332
333
334
335
336
337
338
339
341
342
343
345
346
347
349
350
351
352
353
355
356
357
358
359
360
361
361
Part 2.Part II - References
53
54
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 5. Data flow and Tivoli Decision Support for z/OS
objects
As described in Part I, ″Guide″, Tivoli Decision Support for z/OS loads objects into
its system tables when a feature component is installed. These objects (for example,
log and record definitions, record procedures, and update definitions) are needed
for data collection. At the same time, Tivoli Decision Support for z/OS loads the
predefined tables and reports associated with that feature component.
After you update the lookup tables, Tivoli Decision Support for z/OS and its
features collect data from log records. This data is restricted to that required to
meet users’ needs. Tivoli Decision Support for z/OS combines this data with
information that you provide for presentation in reports. For more details about
updating lookup tables, see Chapter 2, “Implementing the CICS Performance
feature,” on page 9.
This chapter describes the flow of data from log record to report (or list record),
showing Tivoli Decision Support for z/OS definitions. It also provides a simple
explanation of the supported logs, their structure, and the common fields and
conditions associated with each log. It shows how the CICS Performance feature
maps log data into tables.
Tivoli Decision Support for z/OS data flow: an overview
Input for the Tivoli Decision Support for z/OS database consists of sequential log
data sets, such as SMF and DCOLLECT system logs. Tivoli Decision Support for
z/OS processes data collected from the input logs, summarizes and stores the data
in the Tivoli Decision Support for z/OS database, and creates reports based on that
data.
Figure 30 on page 56 is an overview of the flow of data from the SMF log into
Tivoli Decision Support for z/OS.
© Copyright IBM Corp. 1994, 2009
55
Tivoli Decision Support for z/OS data flow: an overview
Figure 30. Overview of data flow from SMF log into Tivoli Decision Support for z/OS
The Tivoli Decision Support for z/OS data flow (see Figure 31 on page 57) follows
these steps:
1. The operating system or licensed program writes data to sequential log data
sets. These data sets are the input to Tivoli Decision Support for z/OS.
2. The COLLECT function reads data from the log data sets.
3. Tivoli Decision Support for z/OS uses record definitions to map the data from
log data sets. Using record definitions, extracts only the data it needs from the
log to create Tivoli Decision Support for z/OS-internal records.
4. In some cases, Tivoli Decision Support for z/OS uses a record procedure to
reformat the data mapped by record definitions. Record procedures are used to
add more data and to combine data from several records. Update definitions
define which tables need data from the records.
5. When data is reformatted by a record procedure, Tivoli Decision Support for
z/OS uses a second record definition to map the new data.
6. Tivoli Decision Support for z/OS stores the data in data tables. Update
definitions instruct it where to store the data. At the same time, it uses lookup
tables as input to data tables. The lookup tables contain user-defined
information that defines an organization’s operating environment. The lookup
tables then convert data or add user-defined data to the tables. Some tables
contain summarized information from another table. (For example, one table
56
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Tivoli Decision Support for z/OS data flow: an overview
might contain hourly data summarized from weekly data in another table.)
Update definitions also define the summarized tables.
7. Tivoli Decision Support for z/OS creates reports with the data from the data
tables. In some cases, it uses additional data from lookup tables when creating
the reports.
Figure 31. Overview of data flow within Tivoli Decision Support for z/OS
For more information about collecting data, refer to the Administration Guide and
Reference.
Chapter 5. Data flow and Tivoli Decision Support for z/OS objects
57
Record processing by the CICS Performance feature
Record processing by the CICS Performance feature
CICS records data in SMF type 110 records. These data sections follow the SMF
header and descriptor. Each SMF type 110 record contains only data sections of the
same CICS version, record subtype, and record class. For CICS/MVS, the record
has another level of detail within a class: the type of record.
OMEGAMON XE for CICS appends information to the SMF type 110 (CICS
Performance) record. The following is a list of all the OMEGAMON CICS sections,
which can be appended to the SMF type 110 record:
v OMEGBSC (OMEGAMON Basic section, which can be split into multiple
subsections)
v OMEGDB2 (DB2)
v OMEGDLI (DL/I)
v CANMQ (MQ)
v CANWLMSC (Workload Manager)
v CANUE1 (User Event)
v OMEGCICS (CICS Performance Analyser)
The OMEGAMON CICS Monitoring component collects data from the following
OMEGAMON XE for CICS sections:
v OMEGBSC
v OMEGDB2
v OMEGDLI
v CANMQ
v CANUE1 (User Event)
OMEGAMON XE for CICS records data in SMF type 112 subtype 203 records.
These records contain counts and elapsed times for each type of file or database
command that a transaction issues.
The following is a list of all the possible file and database types in the SMF112
subtype 203 record:
v VSAM
v DL/I
v MQ
v ADABAS
v
v
v
v
SUPRA
DATACOM
IDMS
UE1 (user event)
The log collector initiates SMF record processing according to CICS record
definitions. The log collector uses these record definitions to map data in the SMF
log. It selects the appropriate definition according to the type of data recorded by
CICS. Table 2 on page 59 shows the record definitions used by the log collector.
58
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Record processing by the CICS Performance feature
Table 2. Record definitions for mapping data in the SMF log
Record definition
Description
Source
Dictionary
record?
SMF_110_1
CICS/ESA and CICS/TS performance CMF
Yes
SMF_110_1_5
CICS/TS transaction resources
CMF
No
SMF_110_2
CICS/ESA and CICS/TS statistics
Statistics
No
SMF_110_3
CICS/TS data sharing statistics
Statistics
No
SMF_110_4
CICS/TS coupling facility statistics
Statistics
No
SMF_110_5
CICS/TS named counter sequence
server statistics
Statistics
No
SMF_110_C
CICS/TS 3.2+ Compressed record
CMF
Yes
SMF_110_E
CICS/ESA and CICS/TS exceptions
CMF
No
SMF_110_0_V2
CICS/MVS accounting, performance,
and exceptions
CMF
Yes
SMF_112_203_C
CICS file and data base usage
compressed record
OMEGAMON No
XE for CICS
SMF_112_203
CICS file and data base usage
Record
procedure
DRL2OMEG
No
CICS/ESA generates a dictionary record only for its CMF-generated performance
data; CICS/MVS generates a dictionary record for all of its CMF-generated data.
CICS uses dictionary records to describe the format, length, and field titles in these
CICS CMF-generated data records. The dictionary record will also indicate whether
any of the OMEGAMON XE for CICS sections are added to the SMF type 110
performance record.
The CICS Performance feature uses these record procedures:
DRL2CICS
This handles the CMF data that uses a dictionary for field mapping. It also
processes and stores the dictionary records themselves. It writes records for
which there is no dictionary to the DRLNDICT dataset, so you must
include a DD statement for this dataset in the collect step.
DRL4CICS
This splits CMF class 5 records by transaction resource record, creating
simpler output records that are mapped by further record definitions.
DRL2CIST
This splits the CICS/ESA and CICS/TS statistics records by ID, creating
small output records that are mapped by further record definitions.
DRL2COMP
This handles Compressed SMF record data sections and expands them
using the standard z/OS Compression/Expansion routine CSRCESRV. The
output record is SMF_110_1.
DRL2OMEG
This handles compressed SMF type 112 subtype 203 records and expands
them using the standard z/OS Compression/Expansion routine
CSRCESRV. The output record is SMF_112_203.
Chapter 5. Data flow and Tivoli Decision Support for z/OS objects
59
Record processing by the CICS Performance feature
With the CICS Performance feature installed, Tivoli Decision Support for z/OS has
system table information that lets the log collector:
v Map the different subtypes and classes of SMF records through its record
definitions
v Create intermediate records of various types through its record procedures
v Store data in tables through its update definitions
60
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Record processing by the CICS Performance feature
Figure 32 on page 61 shows an overview of the flow of data from CICS into Tivoli
Decision Support for z/OS tables and reports.
Figure 32. Data flow from CICS into Tivoli Decision Support for z/OS tables and reports
The log collector uses log and record definitions, record procedures, and update
definitions to move data from SMF type 110 and 112 records into Tivoli Decision
Support for z/OS tables. The log collector uses record definitions to identify SMF
type 110 and 112 records and to map its data according to the CICS version that
produced the record, the record subtype, and the record class.
When the log collector finds the SMF type 110 or 112 record, it uses CICS
Performance feature record definitions to map the data for further processing.
Some record definitions cause the log collector to use record procedures that create
intermediate records.
Record procedure DRL2OMEG expands compressed SMF type 112 subtype 203
records.
Chapter 5. Data flow and Tivoli Decision Support for z/OS objects
61
How Tivoli Decision Support for z/OS processes CMF data
How Tivoli Decision Support for z/OS processes CMF data
The data sections of the following CMF records consist of records of identical
format that relate to one of these monitoring classes:
v Dictionary data (class 1)
v Accounting data (class 2) for CICS/MVS only
v Performance data (class 3)
v Exception data (class 4)
Dictionary data describes fields in CMF-generated performance data sections. CICS
writes a new dictionary record whenever performance monitoring is activated. The
DRL2CICS record procedure updates the CICS_DICTIONARY table with any new
dictionary records. As it processes a CMF record, Tivoli Decision Support for z/OS
loads into memory SMF log dictionary records and any dictionary records stored
in CICS_DICTIONARY.
Tivoli Decision Support for z/OS uses the most recently generated dictionary
section (that matches the MVS system ID, CICS system ID, and class values) to
resolve field values in each performance record. As shown in Figure 33 on page 63,
DRL2CICS creates a common transaction performance record (SMF_CICS_T) from
the CICS transaction performance records.
62
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
How Tivoli Decision Support for z/OS processes CMF data
Figure 33. How CMF performance records are processed
Chapter 5. Data flow and Tivoli Decision Support for z/OS objects
63
How Tivoli Decision Support for z/OS processes CMF data
The log collector uses the DRL2CICS record procedure to map field values for data
in accounting, performance, and exception records to intermediate records mapped
by these record definitions:
SMF_CICS_A
Maps accounting records that Tivoli Decision
Support for z/OS generates from CICS/MVS
accounting records
SMF_CICS_T
Maps transaction performance records that Tivoli
Decision Support for z/OS generates from
CICS/MVS, CICS/ESA, and CICS/TS performance
records
SMF_CICS_E2
Maps exception records that Tivoli Decision
Support for z/OS generates from CICS/MVS
exception records
The CICS/ESA or CICS/TS exception data section is a single, fixed-length record,
mapped by the SMF_110_E record definition. Update definitions store exception
data in the Tivoli Decision Support for z/OS common table EXCEPTION_T, but
some rows in this table are also created from exceptional conditions in CICS/ESA
and CICS/TS statistics records.
Tivoli Decision Support for z/OS stores data in DB2 columns that correspond to
most fields found in CICS performance data. If you need to add fields to CMF
performance records, remember to update the Tivoli Decision Support for z/OS
CICS_FIELD control table with your fields, and add fields in the SMF_CICS_T
record definition with the offset and length that you specify in CICS_FIELD. The
CICS_FIELD table is loaded using the SQL statements in the DRLxxx.SDRLDEFS
(DRLTCIFI) member. Use this member as a template for additional entries. The
SMF_CICS_T record definition is in the DRLxxx.SDRLDEFS (DRLRS110) member.
For more information about SMF records and data fields that CMF produces for
CICS refer to the CICS/ESA Customization Guide or the CICS/MVS Customization
Guide.
The log collector uses the DRL4CICS record procedure to map field values for data
in transaction resource monitoring records (class 5). The output record to map
these fields is SMF_CICS_TR.
64
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
How Tivoli Decision Support for z/OS processes CMF data
Figure 34. How CICS/TS transaction resource records are processed by the CICS
Performance feature
Chapter 5. Data flow and Tivoli Decision Support for z/OS objects
65
How Tivoli Decision Support for z/OS processes CMF data
How Tivoli Decision Support for z/OS processes dictionary
data
Any monitoring utility program that processes performance data, including Tivoli
Decision Support for z/OS, needs the dictionary record that relates to the data
being processed before it can analyze the data. Normally, this is not a problem,
because Tivoli Decision Support for z/OS stores dictionary records in the database.
Once Tivoli Decision Support for z/OS has read a valid dictionary record for a
CICS system, it does not need another one until the CMF field mapping changes,
which may be when you apply service to the CICS system.
If you have just applied service or migrated from an earlier release, Tivoli Decision
Support for z/OS needs the new dictionary record before it can analyze the
records. It will normally appear before any CMF records in the log, but if you are
not collecting the first log for the changed CICS system, follow this procedure:
1. Make sure that there is a valid dictionary record somewhere in the log files,
even if it is not at the beginning of the first log. CMF writes one when it is
turned on, so you can force CMF to write one by turning off CMF logging, and
then turning it on again. For CICS/ESA and CIC/TS only, you can run
DFHMNDUP, as described in “Using the DFHMNDUP utility” on page 67, to
generate a dictionary record.
For CICS/MVS, you can run DRL1CIEX to extract the dictionary, as described
in “Using the DRL1CIEX utility” on page 67.
2. Make sure that the collect JCL has a DRLNDICT DD statement. Allocate a file
with LRECL=32754, BLKSIZE=32760, and RECFM=VB. Concatenate your log
files. Start with the output file from DFHMNDUP or DRL1CIEX, if any, and
then the other log files starting with the oldest.
3. Collect the data. If the DRL2CICS record procedure encounters a CMF record
for which there is no dictionary, it writes the record to the DRLNDICT data set.
When it has read all the log records, it lists the CICS systems with missing
dictionary records, and marks those systems where the dictionary record was
found later in the log and stored.
4. Check the output messages (DRLOUT). The following messages are written to
DRLOUT if Tivoli Decision Support for z/OS finds monitoring records without
a valid dictionary (in either the logs or in the CICS_DICTIONARY table):
DRL2111W 25 CICS monitoring records written to dataset
DEGEER.CICSOUT because matching dictionaries
could not initially be found:
DRL2112I MVS system | CICS applid |
Number| Found
DRL2113I -----------|-------------|----------|-----DRL2114I ECHO
| VMCPC1
|
19| Yes
DRL2114I S38X
| ECIC
|
3| Yes
DRL2114I S38X
| FCIC
|
3| Yes
DRL2113I -----------|-------------|----------|-----DRL2115I Total
|
25
Found = Yes indicates that a matching dictionary record was found later in the
log.
5. If you do not get these messages, Tivoli Decision Support for z/OS found the
dictionaries that it needed. If you get these messages, and Found=Yes for some
of the systems, rerun collect with the DRLNDICT data set as the new input log
data set. This will collect the data for the systems that had Found=Yes. Provide
a new output DRLNDICT data set for this collect job.
66
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
How Tivoli Decision Support for z/OS processes CMF data
Using the DFHMNDUP utility
CICS/ESA and CICS/TS provide a monitoring dictionary utility program
(DFHMNDUP) that writes a dictionary record to a sequential data set, which is
specified on a DD statement with a ddname of SYSUT4. You can then concatenate
this data set ahead of your log data sets when you collect data with Tivoli Decision
Support for z/OS. For the DFHMNDUP program to generate the correct dictionary
record for the performance data you will process, use the JCL shown in Figure 35.
//SMFMNDUP JOB (accounting information),CLASS=A,
//
MSGCLASS=A,USER=userid,PASSWORD=password,NOTIFY=userid
//***************************************************************
//*
Create new dictionary record and output to SYSUT4
*
//***************************************************************
//MNDUP
EXEC PGM=DFHMNDUP
//STEPLIB DD DSN=CICS330.SDFHLOAD,DISP=SHR
//
DD DSN=mct.table.loadlib,DISP=SHR
//SYSUT4 DD DSN=CICS330.applid.MNDUPREC,DISP=(NEW,CATLG),
//
UNIT=SYSDA,SPACE=(TRK,(1,1))
//SYSPRINT DD SYSOUT=A
//SYSUDUMP DD SYSOUT=A
//SYSIN
DD *
MCT=NO
(the suffix of your monitoring control table)
SYSID=MVSA
(your MVS system ID)
GAPPLID=DBDCCICS (your CICS generic VTAM APPLID)
Figure 35. Sample JCL to run the monitoring dictionary utility (DFHMNDUP)
For more detailed information on the DFHMNDUP program, refer to the CICS
Operations Guide.
Using the DRL1CIEX utility
For CICS/MVS, you can run DRL1CIEX to extract the dictionary from the log to a
separate data set. You can then concatenate this data set ahead of your log data
sets when you collect data with Tivoli Decision Support for z/OS. Sample JCL for
DRL1CIEX is in DRLxxx.SDRLCNTL (DRLJCIEX). The JCL comment statements
contain more information about the utility.
How Tivoli Decision Support for z/OS processes CICS data
records
Tivoli Decision Support for z/OS stores data in DB2 columns that correspond to
most fields found in CICS CMF-generated records. For more information about
SMF records and fields that CICS produces, refer to the CICS Customization Guide.
Tivoli Decision Support for z/OS inserts data into tables by following update
definitions that indicate where to store CICS/ESA-specific data, CICS/MVS-specific
data, and common CICS data. For more information about the tables that the log
collector updates, see Chapter 6, “Data tables, lookup tables, and control tables,”
on page 69.
As Tivoli Decision Support for z/OS generates reports, it selects data from
appropriate tables. It extracts data from CICS-specific tables. If you request
information about transactions, tasks, applications, or users that might involve
both CICS/ESA and CICS/MVS systems, the feature extracts data from those
CICS-specific tables and from tables created from common performance records.
For more information about the reports that the CICS Performance feature
provides, see Chapter 7, “Reports,” on page 301.
Chapter 5. Data flow and Tivoli Decision Support for z/OS objects
67
How Tivoli Decision Support for z/OS processes CMF data
How Tivoli Decision Support for z/OS processes CICS/ESA
statistics
Tivoli Decision Support for z/OS uses the record definition SMF_110_2 to map
CICS/ESA and CICS/TS statistics records, SMF_110_3 to map CICS/TS data
sharing statistics records, SMF_110_4 to map CICS/TS coupling facility statistics,
and SMF_110_5 to map counter sequence server statistics reports, in the SMF log.
The DRL2CIST record procedure creates intermediate records according to the
statistics ID. The log collector then uses update definitions to update tables that
contain CICS/ESA statistics data.
Tivoli Decision Support for z/OS stores data in DB2 columns that correspond to
most fields found in CICS/ESA statistics data. For more information about SMF
records and data fields in CICS/ESA statistics, refer to the CICS/ESA Performance
Guide and to the CICS/ESA Customization Guide.
68
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 6. Data tables, lookup tables, and control tables
The Tivoli Decision Support for z/OS database is a collection of DB2 tables, where
each table contains a fixed number of columns. The number of rows in each table
varies with time, due to rows added by the collect function and database
maintenance.
The process of entering data into the tables consists of several stages. The data
from the log is first summarized in one table. Then, the contents of that table are
summarized into another table, and so on. An update definition specifies how data
from one source (a record type or table) is entered into one target (always a table).
When the Tivoli Decision Support for z/OS collect function collects records from
the various logs supported, it stores the data in tables. Each component uses
several tables.
This chapter describes the data tables, lookup tables, and control tables used by the
CICS Performance feature. It includes an explanation of the naming standard used.
For descriptions of common data tables used by the CICS Performance feature and
other Tivoli Decision Support for z/OS features, refer to the Administration Guide
and Reference.
Naming standard for CICS Performance tables
The names of CICS Performance feature tables use this format:
CICS_prefix_content_suffix
Where:
v prefix identifies the component or subcomponent type (for example, S for the
statistics component and A for the application analysis subcomponents). Table
names for subcomponent 1 and subcomponent 8, the basic subcomponents, do
not contain prefixes; table names for the remaining 12 subcomponents do
contain a prefix.
v content is a description (for example, CICS_TRANSACTION for
subcomponent 1’s CICS transaction statistics).
v suffix indicates the summarization level of the data in the table (for example,
CICS_TRANSACTION_D for CICS transaction statistics summarized by day).
A table name can have these summarization-level suffixes:
_T
The table holds nonsummarized data (timestamped data)
_H
The table holds data summarized by hour (hourly data)
_D
The table holds data summarized by day (daily data)
_W
The table holds data summarized by week (weekly data)
_M
The table holds data summarized by month (monthly)
Lookup tables and control tables do not have a suffix; control tables also do not
have a prefix.
Notes:
1. The same tables referring to the non-partitioning feature can also be referred
to the partitioning feature when a P is added to the end of the name of the
table. For example, if you want to analize the table CICS_S_AUTO_TER_TP,
look at the table CICS_S_AUTO_TERM_T.
© Copyright IBM Corp. 1994, 2009
69
Naming standard for CICS Performance tables
2. The CICS_EXCEPTION_T data table has the same name in the CICS
Performance and CICS Partitioning feature.
Table descriptions
Each table description includes information about the table, a description of each
of the key columns, and a description of each of the data columns:
v Key columns are marked like this: K. They are sorted in the sequence they
appear in the table.
v Data columns follow the last key column and are sorted in alphabetic order with
the underscore ignored.
The descriptions of most key columns and data columns contain references to the
fields from which they are derived in the SMF record (for example, “From
SMFMNSID”) or the CICS record (for example, “From DISPWTT”). For an
explanation of such fields, refer to the applicable product documentation.
For each component and subcomponent, the tables appear in alphabetic order, with
underscores and suffixes ignored.
Tables with similar contents (that is, tables with the same name but with different
suffixes) are described under one heading. For example, the heading
“CICS_TRANSACTION_D, _W” covers two similar tables:
CICS_TRANSACTION_D and CICS_TRANSACTION_W. Except for the DATE
column, the contents of these tables are identical. Differences that exist in the
contents of similar tables are explained in the column descriptions.
Tables in the CICS monitoring component
As described in “Evaluating the CICS monitoring component” on page 13, the
CICS monitoring component contains subcomponents. This section groups data
tables for the CICS monitoring component by these subcomponents:
1. Basic subcomponent
2. DBCTL subcomponent
3. DL/I subcomponent
4. Basic application analysis subcomponent
5. DBCTL application analysis subcomponent
6. DL/I application analysis subcomponent
7. CICS/MVS subcomponent (global + accounting)
8. Basic transaction subcomponent
9. DBCTL transaction subcomponent
10. DL/I transaction subcomponent
11. Basic application user subcomponent
12. DBCTL application user subcomponent
13. DL/I application user subcomponent
14. CICS TS transaction resources subcomponent
15. CICS TS enterprise Java beans subcomponent
16. CICS Resource Manager Interface subcomponent
Subcomponents 1 and 4 are based on the transaction data, and the tables are
almost the same, differing only in their key structure. In the table layouts that
follow, the common fields are placed in a separate section.
70
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic subcomponent data tables
1. Basic subcomponent data tables
The data tables described in this section are for the basic subcomponent, which
summarizes (by transaction and user) basic data gathered by the CICS monitoring
facility (CMF).
CICS_TRAN_USR_H, _D, _W
These tables provide CICS transaction data, grouped by user ID and transaction
ID. They contain information from CICS performance class monitoring records
from CICS/ESA and CICS/TS (SMF 110, subtype 1) and CICS/MVS (SMF 110,
subtype 0).
The default retention periods for these tables are:
7 days for CICS_TRAN_USR_H
30 days for CICS_TRAN_USR_D
565 days for CICS_TRAN_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID
for a task created as the result of receiving an ATTACH
request across an MRO or APPC link with attach-time security.
From USERID.
Remaining fields
See “Common fields for subcomponents 1, 4, 8, and 11” on
page 76.
Chapter 6. Data tables, lookup tables, and control tables
71
Basic subcomponent data tables
CICSBTS_TRAN_USR_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions,
grouped by user ID and transaction ID. They contain information from CICS
performance class monitoring records from CICS/TS (SMF 110, subtype 1) related
to the business transaction service (BTS).
The default retention periods for these tables are:
7 days for CICSBTS_TRAN_USR_H
30 days for CICSBTS_TRAN_USR_D
565 days for CICSBTS_TRAN_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
72
See “Common fields for the business transaction service (BTS)”
on page 89.
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic subcomponent data tables
CICSCHN_TRAN_USR_H, _D, _W
These tables provide hourly, daily and weekly statistics related to the use of
channels and containers for data transfer between programs. They contain
information from CICS performance class monitoring records from CICS/TS (SMF
110, subtype 1) grouped by user ID and transaction ID.
The default retention periods are:
7 days for CICSCHN_TRAN_USR_H
30 days for CICSCHN_TRAN_USR_D
365 days for CICSCHN_TRAN_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
Used only in CICSCHN_TRAN_USR_H. The hour when the
performance records were initialised. From START. (For _H
table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
Remaining fields
See “Common fields for the Channel and Container usage for
data transfer (CHN)” on page 90.
Chapter 6. Data tables, lookup tables, and control tables
73
Basic subcomponent data tables
CICSDOC_TRAN_USR_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions,
grouped by user ID and transaction ID. They contain information from CICS
performance class monitoring records from CICS/TS (SMF 110, subtype 1) related
to the document handler.
The default retention periods for these tables are:
7 days for CICSDOC_TRAN_USR_H
30 days for CICSDOC_TRAN_USR_D
565 days for CICSDOC_TRAN_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
74
See “Common fields for the document handler (DOC)” on page
92.
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic subcomponent data tables
CICSWEB_TRAN_USR_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions,
grouped by user ID and transaction ID. They contain information from CICS
performance class monitoring records from CICS/TS (SMF 110, subtype 1) related
to the Web interface activity.
The default retention periods for these tables are:
7 days for CICSWEB_TRAN_USR_H
30 days for CICSWEB_TRAN_USR_D
565 days for CICSWEB_TRAN_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
See “Common fields for the Web interface (WEB)” on page 92.
Chapter 6. Data tables, lookup tables, and control tables
75
Common fields for subcomponents 1, 4, 8, 11
Common fields for subcomponents 1, 4, 8, and 11
This table shows the fields that come after the key columns.
Column name
Key columns
Data type
Description
See under the table heading.
K
BMS_INPUTS
FLOAT
Number of BMS IN requests. This is the number of RECEIVE
MAP requests that incurred a terminal I/O. This is the sum
of BMSINCT.
BMS_MAP_REQUESTS
FLOAT
Number of BMS MAP requests. This is the number of
RECEIVE MAP requests that did not incur a terminal I/O,
added to the number of RECEIVE MAP FROM requests. This
is the sum of BMSMAPCT.
BMS_OUTPUTS
FLOAT
Number of BMS OUT requests. This is the number of SEND
MAP requests. This is the sum of BMSOUTCT.
BMS_REQUESTS_TOTAL
FLOAT
Total number of BMS requests. This is the sum of
BMSTOTCT.
BRIDGE_TRANS_ID
FLOAT
3270 Bridge transaction identification. From BRDGTRAN.
CFDTWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for CF data table I/O.
From CFDTWAIT.
CFDTWAIT_COUNT
FLOAT
Number of times that the user task waited for CF data table
I/O. From CFDTWAIT.
CHARS_IN_ALT_LU62
FLOAT
Number of characters received from the alternate terminal
facility by the user task for LUTYPE6.2 (APPC) sessions. This
is the sum of TCC62IN2.
CHARS_INPUT_ALT
FLOAT
Number of characters received from the LUTYPE6.1 alternate
terminal. This is the sum of TCCHRIN2.
CHARS_INPUT_PRIME
FLOAT
Number of characters received from the principal terminal.
This is the sum of TCCHRIN1.
CHARS_OUT_ALT_LU62
FLOAT
Number of characters sent to the alternate terminal facility
by the user task for LUTYPE6.2 (APPC) sessions. This is the
sum of TCC62OU2.
CHARS_OUTPUT_ALT
FLOAT
Number of characters sent to the LUTYPE6.1 alternate
terminal. This is the sum of TCCHROU2.
CHARS_OUTPUT_PRIME
FLOAT
Number of characters sent to the principal terminal. This is
the sum of TCCHROU1.
CHARS_PRIME_TOTAL
FLOAT
Total number of characters to and from the principal
terminal. This is the sum of TCCHRIN1 + TCCHROU1.
CPU_MAX_SEC
FLOAT
Maximum CPU time used during one transaction, in seconds.
This is the maximum of USRCPUT.
CPU_MIN_SEC
FLOAT
Minimum CPU time used during one transaction, in seconds.
This is the minimum of USRCPUT.
CPU_SUM_SEC
FLOAT
CPU time, in seconds. This is the sum of USRCPUT.
DB2_REQS_COUNT
FLOAT
Number of DB2 (EXEC SQL IFI) requests issued by the user
task. From DB2REQCT.
DB2CONWT_CLOCK
FLOAT
Elapsed time that the user task waited for a CICS DB2
subtask to become available. From DB2CONWT.
DB2CONWT_COUNT
FLOAT
Number of times that the user task waited for a CICS DB2
subtask to become available. From DB2CONWT.
DB2RDYQW_CLOCK
FLOAT
Elapsed time that the user task waited for a DB2 thread to
become available. From DB2RDYQW.
76
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
DB2RDYQW_COUNT
FLOAT
Number of times that the user task waited for a DB2 thread
to become available. From DB2RDYQW.
DB2WAIT_CLOCK
FLOAT
Elapsed time that the user task waited for DB2 to service the
DB2 EXEC SQL and IFI requests. From DB2WAIT.
DB2WAIT_COUNT
FLOAT
Number of times that the user task waited for DB2 to service
the DB2 EXEC SQL and IFI requests. From DB2WAIT.
DECRYPT_BYTES
FLOAT
Number of bytes decrypted by the secure sockets layer for
the user task. From SOBYDECT.
DISP_TCB_HWM
FLOAT
The peak number of CICS open TCBs (in TCB modes H8, J8,
J9, L8, or S8) that have been allocated to the user task. From
DSTCBHWM.
DISPATCH_COUNT
FLOAT
Number of times that tasks were dispatched. This is the sum
of USRDISPT.
DISPATCH_DELAY_SEC
FLOAT
Time waiting for the first dispatch, in seconds. This is a
subset of SUSPEND_SEC. This is the sum of DSPDELAY.
DISPATCH_SEC
FLOAT
Elapsed time that tasks were dispatched, in seconds. This is
the sum of USRDISPT.
DISPATCH_WAITS
FLOAT
Number of times that tasks were waiting for redispatch. This
is valid for CICS V3 and later. This is the sum of DISPWTT.
DISPATCH_WAIT_SEC
FLOAT
Time that tasks were waiting for redispatch, in seconds. This
is valid for CICS V3 and later. This is the sum of DISPWTT.
DSMMSC_CLOCK
FLOAT
The elapsed time which the user task spent waiting because
no TCB was available, and none could be created due to
MVS storage constraints. From DSMMSC_CLOCK.
DSMMSC_COUNT
FLOAT
The number of times that the user task waited because no
TCB was available, and none could be created due to MVS
storage constraints. From DSMMSC_COUNT.
DSTCBM_CLOCK
FLOAT
The elapsed time which the user task spent in TCB mismatch
waits, that is, waiting because there was no available TCB
matching the request, but there was at least one
non-matching free TCB. From DSTCBM_CLOCK.
DSTCBM_COUNT
FLOAT
The number of times that the user task waited due to TCB
mismatch, because there was no available TCB matching the
request, but there was at least one non-matching free TCB.
From DSTCBM_COUNT.
ENCRYPT_BYTES
FLOAT
Number of bytes encrypted by the secure sockets layer for
the user task. From SOBYENCT.
ENQ_WAITS
FLOAT
Number of CICS Task Control ENQ waits. This is the sum of
ENQDELAY.
ENQ_WAIT_SEC
FLOAT
Time waiting for CICS Task Control ENQ, in seconds. This is
the sum of ENQDELAY.
EXCEPTIONS
FLOAT
Number of exception conditions. This is valid for CICS V3
and later. This is the sum of EXWTTIME.
EXCEPTION_WAIT_SEC
FLOAT
Exception wait time, in seconds. This is valid for CICS V3
and later. This is the sum of EXWTTIME.
FC_ACCESS_METHODS
FLOAT
Number of file control access method calls. Not incremented
if the request is function shipped. This is the sum of
FCAMCT.
Chapter 6. Data tables, lookup tables, and control tables
77
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
FC_ADD_REQUESTS
FLOAT
Number of file control ADD requests. Incremented even if
the request is function shipped. This is the sum of
FCADDCT.
FC_BROWSE_REQUESTS
FLOAT
Number of file control BROWSE requests. Incremented even
if the request is function shipped. This is the sum of
FCBRWCT.
FC_DELETE_REQUESTS
FLOAT
Number of file control DELETE requests. Incremented even if
the request is function shipped. This is the sum of FCDELCT.
FC_GET_REQUESTS
FLOAT
Number of file control GET requests. Incremented even if the
request is function shipped. This is the sum of FCGETCT.
FC_IO_WAITS
FLOAT
Number of file control I/O waits. This is the sum of
FCIOWTT.
FC_IO_WAIT_SEC
FLOAT
File control I/O wait time, in seconds. This is the sum of
FCIOWTT.
FC_PUT_REQUESTS
FLOAT
Number of file control PUT requests. Incremented even if the
request is function shipped. This is the sum of FCPUTCT.
FC_REQUESTS_TOTAL
FLOAT
Total number of file control requests. Incremented even if the
request is function shipped. This is the sum of FCTOTCT.
FE_ALLOC_COUNT
FLOAT
Number of conversations allocated by the user task. This
number is incremented for each FEPI ALLOCATE POOL or
FEPI CONVERSE POOL. This is the sum of SZALLOCT.
FE_ALLOC_TIMEOUT
FLOAT
Number of times the user task timed out while waiting to
allocate a conversation. This is the sum of SZALLCTO.
FE_CHARS_RECEIVED
FLOAT
Number of characters received through FEPI by the user
task. This is the sum of SZCHRIN.
FE_CHARS_SENT
FLOAT
Number of characters sent through FEPI by the user task.
This is the sum of SZCHROUT.
FE_RECEIVE_REQ
FLOAT
Number of FEPI RECEIVE requests made by the user task.
This number is also incremented for each FEPI CONVERSE
request. This is the sum of SZRCVCT.
FE_RECEIVE_TIMEOUT
FLOAT
Number of times the user task timed out while waiting to
receive data. This is the sum of SZRCVTO.
FE_REQUESTS_TOTAL
FLOAT
Total number of all FEPI API and SPI requests made by the
user task. This is the sum of SZTOTCT.
FE_SEND_REQUESTS
FLOAT
Number of FEPI SEND requests made by the user task. This
number is also incremented for each FEPI CONVERSE
request. This is the sum of SZSENDCT.
FE_START_REQUESTS
FLOAT
Number of FEPI START requests made by the user task. This
is the sum of SZSTRTCT.
FE_WAITS
FLOAT
Number of times that the user task waited for FEPI services.
This is the sum of SZWAIT.
FE_WAIT_SEC
FLOAT
Time that the user task waited for all FEPI services, in
seconds. This is the sum of SZWAIT.
GETMAINS_CDSA
FLOAT
Number of user-storage GETMAIN requests below the 16MB
line, in the CDSA. This is the sum of SCCGETCT.
GETMAINS_ECDSA
FLOAT
Number of user-storage GETMAIN requests above the 16MB
line, in the ECDSA. This is the sum of SCCGETCTE.
GETMAINS_EUDSA
FLOAT
Number of user-storage GETMAIN requests above the 16MB
line, in the EUDSA. This is the sum of SCUGETCTE.
78
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
GETMAINS_UDSA
FLOAT
Number of user-storage GETMAIN requests below the 16MB
line, in the UDSA. This is the sum of SCUGETCT.
GNQDELAY_CLOCK
FLOAT
Elapsed time that the user task waited for a CICS task
control global enqueue. From GNQDELAY.
GNQDELAY_COUNT
FLOAT
Number of times that the user task waited for a CICS task
control global enqueue. From GNQDELAY.
GVUPWAIT_CLOCK
FLOAT
Elapsed time that the user task waited as the result of
relinquishing control to another task. From GVUPWAIT.
GVUPWAIT_COUNT
FLOAT
Number of times that the user task waited as the result of
relinquishing control to another task. From GVUPWAIT.
ICDELAY_CLOCK
FLOAT
Elapsed time that the user task waited the result from EXEC
CICS DELAY or RETRIEVE command. From ICDELAY.
ICDELAY_COUNT
FLOAT
Number of times that the user task waited the result from
EXEC CICS DELAY or RETRIEVE command. From
ICDELAYT.
IC_START_REQUESTS
FLOAT
Number of interval control START or INITIATE requests.
This is the sum of ICPUINCT.
ICTOT_REQS
FLOAT
Total number of Interval Control Start, Cancel, Delay and
Retrieve requests issued by the user task. From ICTOTCT.
IMS_REQS_COUNT
FLOAT
Number of IMS (DBCTL) requests issued by the user task.
From IMSREQCT.
IMSWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for DBCTL to service
the IMS requests issued by the user task. From IMSWAIT.
IMSWAIT_COUNT
FLOAT
Number of times that the user task waited for DBCTL to
service the IMS requests issued by the user task. From
IMSWAIT.
|
|
ISIOWTT_CLOCK
The elapsed time the user task waited for control at this end
of an (IPIC) connection. From ISIOWTT.
|
|
ISIOWTT_COUNT
The number of times the user task waited for control at this
end of an (IPIC) connection. From ISIOWTT.
J8CPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on each
CICS J8 TCB. From J8CPUT.
J8CPUT_COUNT
FLOAT
Number of times that the user task was dispatched on each
CICS J8 TCB. From J8CPUT.
J9CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS J9
mode TCB. From J9CPUT_CLOCK.
J9CPUT_COUNT
FLOAT
The number of times that the user task was dispatched by
the CICS dispatcher domain on a CICS J9 mode TCB. From
J9CPUT_COUNT.
JAVA_OO_REQS
FLOAT
Total number of CICS OO foundation class requests (JCICS)
issued by the user task. From CFCAPICT.
JC_IO_WAITS
FLOAT
Number of journal control I/O waits. This is the sum of
JCIOWTT.
JC_IO_WAIT_SEC
FLOAT
Journal control I/O wait time, in seconds. This is the sum of
JCIOWTT.
JC_OUTPUT_REQUESTS
FLOAT
Number of journal control output requests. This is the sum
of JCPUWRCT.
JVMITI_CLOCK
FLOAT
JVM elapsed time, initialize - clock. From JVMITI_CLOCK.
Chapter 6. Data tables, lookup tables, and control tables
79
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
JVMITI_COUNT
FLOAT
JVM elapsed time, initialize - count. From JVMITI_COUNT.
JVMRTI_CLOCK
FLOAT
JVM elapsed time, reset - clock. From JVMRTI_CLOCK.
JVMRTI_COUNT
FLOAT
JVM elapsed time, reset - count. From JVMRTI_COUNT.
JVMSUSP_CLOCK
FLOAT
Elapsed time that the task was suspended by the CICS
dispatcher while running in the CICS JVM. From JVMSUSP.
JVMSUSP_COUNT
FLOAT
Number of times that the task was suspended by the CICS
dispatcher while running in the CICS JVM. From JVMSUSP.
JVMTIME_CLOCK
FLOAT
Elapsed time that was spent in the CICS JVM by the user.
From JVMTIME.
JVMTIME_COUNT
FLOAT
Number of times that were spent in the CICS JVM by the
user. From JVMTIME.
KY8DIS_CLOCK
FLOAT
User task key 8 mode dispatch time - clock. idd:break>From
KY8DIS_CLOCK.
KY8DIS_COUNT
FLOAT
User task key 8 mode dispatch time - count. idd:break>From
KY8DIS_COUNT.
KY8CPU_CLOCK
FLOAT
User task key 8 mode CPU time - clock. idd:break>From
KY8CPU_CLOCK.
KY8CPU_COUNT
FLOAT
User task key 8 mode CPU time - count. idd:break>From
KY8CPU_COUNT.
KY9_COUNT
FLOAT
The number of times the user task was dispatched by the
CICS dispatcher on a CICS key 9 mode TCB. From
KY9_COUNT.
KY9CPU_CLOCK
FLOAT
Processor time during which the user task was dispatched by
the CICS dispatcher on a CICS key 9 mode TCB. From
KY9CPU_CLOCK.
KY9DIS_CLOCK
FLOAT
The total elapsed time during which the user task was
dispatched by the CICS dispatcher on a CICS key 9 mode
TCB. From KY9DIS_CLOCK.
L8CPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on each
CICS L8 TCB. From L8CPUT.
L8CPUT_COUNT
FLOAT
Number of times that the user task was dispatched on each
CICS L8 TCB. From L8CPUT.
L9CPUT_CLOCK
FLOAT
Processor time during which the user task was dispatched by
the CICS dispatcher domain on a CICS L9 mode TCB. When
a transaction invokes an OPENAPI application program
defined with EXECKEY= USER, it is allocated and uses a
CICS L9 mode TCB. From L9CPUT.
L9CPUT_COUNT
FLOAT
Number of times the user task was dispatched by the CICS
dispatcher domain on a CICS L9 mode TCB. This field is
related to XPlink support. From L9CPUT.
LINK_URM_REQS
FLOAT
Number of program LINK URM requests issued by the user
task. This is the sum of PLCURMCT.
LMDELAY_CLOCK
FLOAT
Elapsed time that the user task waited to acquire a lock on a
resource. From LMDELAY.
LMDELAY_COUNT
FLOAT
Number of times that the user task waited to acquire a lock
on a resource. From LMDELAY.
LOGGER_WRITE_COUNT
FLOAT
Number of CICS logger write requests issued by the user
task. This is the sum of LOGWRTCT.
80
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
LU61_IO_WAITS
FLOAT
Number of waits for I/O on a LUTYPE6.1 connection or
session. Includes waits for conversations across LUTYPE6.1
connections, but not waits due to LUTYPE6.1 syncpoint
flows. This is the sum of LU61WTT.
LU61_IO_WAIT_SEC
FLOAT
I/O wait time for a LUTYPE6.1 connection or session, in
seconds. Includes wait time for conversations across
LUTYPE6.1 connections, but not waits due to LUTYPE6.1
syncpoint flows. This is the sum of LU61WTT.
LU62_IO_WAITS
FLOAT
Number of waits for I/O on a LUTYPE6.2 (APPC)
connection or session. Includes waits for conversations across
LUTYPE6.2 (APPC) connections, but not waits due to
LUTYPE6.2 (APPC) syncpoint flows. This is the sum of
LU62WTT.
LU62_IO_WAIT_SEC
FLOAT
I/O wait time for a LUTYPE6.2 (APPC) connection or
session, in seconds. Includes wait time for conversations
across LUTYPE6.2 (APPC) connections, but not waits due to
LUTYPE6.2 (APPC) syncpoint flows. This is the sum of
LU62WTT.
MAXJTD_CLOCK
FLOAT
Max JVM TCB delay time - clock. idd:break>From
MAXJTD_CLOCK.
MAXJTD_COUNT
FLOAT
Max JVM TCB delay time - count. idd:break>From
MAXJTD_COUNT.
MAXHTD_CLOCK
FLOAT
Max hot-pooling TCB delay time - clock. idd:break>From
MAXHTD_CLOCK.
MAXHTD_COUNT
FLOAT
Max hot-pooling TCB delay time - count. idd:break>From
MAXHTD_COUNT.
MAXOTDLY_CLOCK
FLOAT
Elapsed time that the user task waited to obtain a CICS open
TCB, because the region had reached the limit set by
MAXOPENTCBS parameter. From MAXOTDLY.
MAXOTDLY_COUNT
FLOAT
Number of times that the user task waited to obtain a CICS
open TCB, because the region had reached the limit set by
MAXOPENTCBS parameter. From MAXOTDLY.
MAXSSLTCBS_COUNT
FLOAT
Number of times the CICS system reached the limit set by
the system initialization parameter MAXXPTCBS. From
MAXXTDLY.
MAXXPTCBS_COUNT
FLOAT
Number of times the CICS system reached the limit set by
the system initialization parameter MAXSSLTCBS. From
MAXSTDLY.
MRO_WAITS
FLOAT
Number of times that tasks waited for control at this end of
an MRO link. This is the sum of IRIOWTT.
MRO_WAIT_SEC
FLOAT
Time that tasks waited for control at this end of an MRO
link, in seconds. This is the sum of IRIOWTT.
MSCPUT_CLOCK
FLOAT
Total processor time that the user task was dispatched on
each CICS TCB. From MSDISPT.
MSCPUT_COUNT
FLOAT
Number of times that the user task was dispatched on each
CICS TCB. From MSDISPT.
MSDISPT_CLOCK
FLOAT
Total elapsed time that the user task was dispatched on each
CICS TCB. From MSDISPT.
MSDISPT_COUNT
FLOAT
Number of times that the user task was dispatched on each
CICS TCB. From MSDISPT.
Chapter 6. Data tables, lookup tables, and control tables
81
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
MSGS_IN_ALT_LU62
FLOAT
Number of messages received from the alternate terminal
facility by the user task for LUTYPE6.2 (APPC) sessions. This
is the sum of TCM62IN2.
MSGS_INPUT_ALT
FLOAT
Number of messages received from the LUTYPE6.1 alternate
terminal. This is the sum of TCMSGIN2.
MSGS_INPUT_PRIME
FLOAT
Number of messages received from the principal terminal.
This is the sum of TCMSGIN1.
MSGS_OUT_ALT_LU62
FLOAT
Number of messages sent to the alternate terminal facility by
the user task for LUTYPE6.2 (APPC) sessions. This is the
sum of TCM62OU2.
MSGS_OUTPUT_ALT
FLOAT
Number of messages sent to the LUTYPE6.1 alternate
terminal. This is the sum of TCMSGOU2.
MSGS_OUTPUT_PRIME
FLOAT
Number of messages sent to the principal terminal. This is
the sum of TCMSGOU1.
MXT_DELAY_SEC
FLOAT
Time waiting for the first dispatch caused by MXT limits
being reached, in seconds. This is the sum of MXTDELAY.
NET_ID
CHAR(8)
Network ID. From NETID.
NO_CHAR_RCV
FLOAT
Number of characters received. From SOCHRIN.
NO_CHAR_RCV_IN
FLOAT
Number of characters received inbound. From SOCHRIN1.
NO_CHAR_SEND
FLOAT
Number of characters sent. From SOCHROUT.
NO_CHAR_SND_IN
FLOAT
Number of characters sent inbound. From SOMSROU1.
NO_CRT_P_SOCK
FLOAT
Number of create persistent socket requests. From
SOCNPSCT.
NO_CRT_NP_SOCK
FLOAT
Number of create non-persistent socket requests. From
SOCPSCT
NO_EXT_CERTIF
FLOAT
Number of extract TCP/IP and certificate requests. From
SOEXTRCT.
NO_IN_SOCKET
FLOAT
Number of inbound socket send requests. From SOMSGOU1.
NO_INBO_RCV
FLOAT
Number of inbound socket receive requests. From
SOMSGIN1.
NON_PERS_SOCK
FLOAT
Persistent socket hwm. From SONPSHWM.
NO_SOCKET_RCV
FLOAT
Number of socket receive requests. From SORCVCT.
NO_SOCKET_SND
FLOAT
Number of socket send requests. From SOSENDCT.
OTSIND_CLOCK
FLOAT
OTS indoubt wait time - clock. From OTSIND_CLOCK.
OTSIND_COUNT
FLOAT
OTS indoubt wait time - count. From OTSIND_COUNT.
OTS_TRANS_ID
CHAR(128)
OTS transaction ID. From OTSTID.
PAGEINS
FLOAT
Number of virtual storage page-ins. For CICS V2 only. This is
the sum of PAGINCT.
PERF_REC_COUNT
FLOAT
Number of performance class record written by the CICS
Monitoring Facility (CMF) for the user task. Sum of
PERRECNT.
PERSISTE_SOCK
FLOAT
Non-persistent socket hwm. From SOPSHWM.
PGM_COMPRESS
FLOAT
Number of program compressions. For CICS V2 only. This is
the sum of PCCMPRTM.
PGM_COMPRESS_SEC
FLOAT
Time, in seconds, that the task spent in program
compression. For CICS V2 only. This is the sum of
PCCMPRTM.
82
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
PGM_DTL_COUNT
FLOAT
Number of distributed program LINK requests issued by the
user task. From PCDPLCT.
PGM_LINK_REQUESTS
FLOAT
Number of program LINK requests. This is the sum of
PCLINKCT.
PGM_LOAD_REQUESTS
FLOAT
Number of program LOAD requests. This is the sum of
PCLOADCT.
PGM_LOADS
FLOAT
Number of program library fetches. This is the sum of
PCLOADTM.
PGM_LOAD_SEC
FLOAT
Time that tasks waited for program library (DFHRPL)
fetches, in seconds. This is the sum of PCLOADTM.
PGM_XCTL_REQUESTS
FLOAT
Number of program XCTL (transfer control) requests. This is
the sum of PCXCTLCT.
PORT_NUMBER
FLOAT
Port number being used for this TCP/IP service. From
PORTNUM.
PTPWAI_CLOCK
FLOAT
Partner wait time - clock. From PTPWAI_CLOCK.
PTPWAI_COUNT
FLOAT
Partner wait time - count. From PTPWAI_COUNT.
QRCPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on the CICS
QR TCB. From QRCPUT.
QRCPUT_COUNT
FLOAT
Number of times that the user task was dispatched on the
CICS QR TCB. From QRCPUT.
QRDISPT_CLOCK
FLOAT
Elapsed time that the user task was dispatched on the CICS
QR TCB. From QRDISPT.
QRDISPT_COUNT
FLOAT
Number of times that the user task was dispatched on the
CICS QR TCB. From QRDISPT.
QRMODDLY_CLOCK
FLOAT
Elapsed time that the user task waited for a redispatch on
the CICS QR TCB. From QRMODDLY.
QRMODDLY_COUNT
FLOAT
Number of times that the user task waited for a redispatch
on the CICS QR TCB. From QRMODDLY.
RECORDS
FLOAT
Total number of performance class monitoring records. This
is the number of log records summarized.
RECOVERY_MGR_UOW
CHAR(8)
Identifier of the logical unit of work (unit of recovery) for
this task. Unit-of-recovery values are used to synchronize
recovery operations among CICS and other resource
managers, such as IMS and DB2. From RMUOWID.
REDISPATC_COUNT
FLOAT
Number of times that the user task was re-dispatched after a
CICS Dispatcher change TCB mode request. From
DSCHMDLY.
REDISPATC_WAIT_SEC
FLOAT
The elapsed time, in seconds, the user task waited for
re-dispatch after a CICS Dispatcher change-TCB mode
request was issued by or on behalf of the user task. This field
is related to Internet Security and is a subset of
SUSPEND_SEC. From DSCHMDLY.
RESPONSE_MAX_SEC
FLOAT
Peak task response time, in seconds. This is the maximum of
STOP - START.
RESPONSE_MIN_SEC
FLOAT
Minimum task response time, in seconds. This is the
minimum of STOP - START.
RESPONSE_SUM_SEC
FLOAT
Total response time for all tasks, in seconds. This is the sum
of STOP - START.
Chapter 6. Data tables, lookup tables, and control tables
83
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
|
|
RLS_MAX_SEC
Maximum CPU time used during one transaction, in seconds.
This is the maximum of RLSCPUT.
|
|
RLS_MIN_SEC
Minimum CPU time used during one transaction, in seconds.
This is the the minimum of RLSCPUT.
|
RLS_SUM_SEC
CPU time, in seconds. This is the sum of RLSCPUT.
RLSWAIT_CLOCK
FLOAT
Elapsed time during which the user task waited for RLS file
I/O. This is from RLSWAIT.
RLSWAIT_COUNT
FLOAT
Number of times that the user task was waiting for RLS file
I/O. This is the sum of RLSWAIT.
RLUNAME
CHAR(8)
VTAM logical unit name. From RLUNAME.
RMI_COUNT
FLOAT
Number of times that the user task was in the Resource
Manager Interface (RMI). This is the sum of RMITIME.
RMI_SEC
FLOAT
Time spent in the Resource Manager Interface (RMI), in
seconds. This is the sum of RMITIME.
RMI_SUSPENDS
FLOAT
Number of times that the task was suspended while in the
Resource Manager Interface (RMI). This is a subset of
SUSPENDS and RMI_COUNT. This is the sum of RMISUSP.
RMI_SUSPEND_SEC
FLOAT
Time the task was suspended by the dispatcher while in the
Resource Manager Interface (RMI), in seconds. This is a
subset of SUSPEND_SEC and RMI_SEC. This is the sum of
RMISUSP.
RODISP_CLOCK
FLOAT
User task RO mode dispatch time - clock. From
RODISP_CLOCK.
RODISP_COUNT
FLOAT
User task RO mode dispatch time - count. From
RODISP_COUNT.
ROCPUT_CLOCK
FLOAT
User task RO mode CPU time - clock. From
ROCPUT_CLOCK.
ROCPUT_COUNT
FLOAT
User task RO mode CPU time - count. From
ROCPUT_COUNT.
RQPWAI_CLOCK
FLOAT
Request processor wait time - clock. From RQPWAI_CLOCK.
RQPWAI_COUNT
FLOAT
Request processor wait time - count. From
RQPWAI_COUNT.
RQRWAI_CLOCK
FLOAT
Request receiver wait time - clock. From RQRWAI_CLOCK.
RQRWAI_COUNT
FLOAT
Request receiver wait time - count. From RQRWAI_COUNT.
RRMSWAIT_CLOCK
FLOAT
Elapsed time that the user task waited in doubt using
resource recovery services for EXCI. From RRMSWAIT.
RRMSWAIT_COUNT
FLOAT
Number of times that the user task waited in doubt using
resource recovery services for EXCI. From RRMSWAIT.
RUNTRWTT_CLOCK
FLOAT
Elapsed time that the user task waited for completion of a
transaction that executed as the result of a CICS BTS run
process or run activity. From RUNTRWTT.
RUNTRWTT_COUNT
FLOAT
Number of times that the user task waited for completion of
a transaction that executed as the result of a CICS BTS run
process or run activity. From RUNTRWTT.
S8CPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on each
CICS S8 TCB. From S8CPUT.
S8CPUT_COUNT
FLOAT
Number of times that the user task was dispatched on each
CICS S8 TCB. From S8CPUT.
84
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
SHR24_BYTE_COUNT
FLOAT
Number of bytes of shared storage GETMAINed by the user
task below the 16MB line, in the CDSA or SDSA. This is the
sum of SC24GSHR.
SHR24_FREEM_COUNT
FLOAT
Number of bytes of shared storage FREEMAINed by the user
task below the 16MB line, in the CDSA or SDSA. This is the
sum of SC24FSHR.
SHR24_GETM_COUNT
FLOAT
Number of storage GETMAIN requests issued by the user
task for shared storage below the 16MB line, in the CDSA or
SDSA. This is the sum of SC24SGCT.
SHR31_BYTE_COUNT
FLOAT
Number of bytes of shared storage GETMAINed by the user
task above the 16MB line, in the ECDSA or ESDSA. This is
the sum of SC31GSHR.
SHR31_FREEM_COUNT
FLOAT
Number of bytes of shared storage FREEMAINed by the user
task above the 16MB line, in the ECDSA or ESDSA. This is
the sum of SC31FSHR.
SHR31_GETM_COUNT
FLOAT
Number of storage GETMAIN requests issued by the user
task for shared storage above the 16MB line, in the ECDSA
or ESDSA. This is the sum of SC31SGCT.
SOIOWTT_CLOCK
FLOAT
Elapsed time that the user task waited for SOCKETS I/O.
From SOIOWTT.
SOIOWTT_COUNT
FLOAT
Number of times that the user task waited for SOCKETS
I/O. From SOIOWTT.
SOOIOW_CLOCK
FLOAT
Outbound socket I/O wait time - clock. From
SOOIOW_CLOCK.
SOOIOW_COUNT
FLOAT
Outbound socket I/O wait time - count. From
SOOIOW_COUNT.
SRVSYWTT_CLOCK
FLOAT
Elapsed time that the user task waited for a CF data table to
process syncpoint requests. From SRVSYWT.
SRVSYWTT_COUNT
FLOAT
Number of times that the user task waited for a CF data
table to process syncpoint requests. From SRVSYWT.
SSLTCB_WAIT_SEC
FLOAT
The elapsed time, in seconds, in which the user task waited
to obtain a CICS SSL TCB (S8 mode), because the CICS
system had reached the limit set by the system initialization
parameter MAXSSLTCBS. This field is related to Internet
Security. From MAXSTDLY.
STORAGE_CDSA_MAX
FLOAT
Peak user storage allocated below the 16MB line in the CICS
dynamic storage area (CDSA), in bytes. This is the maximum
of SC24CHWM.
STORAGE_ECDSA_MAX
FLOAT
Peak user storage allocated above the 16MB line in the
extended CICS dynamic storage area (ECDSA), in bytes. This
is the maximum of SC31CHWM.
STORAGE_EUDSA_MAX
FLOAT
Peak user storage allocated above the 16MB line in the
extended user dynamic storage area (EUDSA), in bytes. This
is the maximum of SCUSRHWME.
STORAGE_OCC_CDSA
FLOAT
Storage occupancy below the 16MB line in the CDSA, in
kilobyte-seconds. This measures the area under the curve of
storage in use against elapsed time. This is the sum of
SC24COCC.
Chapter 6. Data tables, lookup tables, and control tables
85
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
STORAGE_OCC_ECDSA
FLOAT
Storage occupancy above the 16MB line in the ECDSA, in
kilobyte-seconds. This measures the area under the curve of
storage in use against elapsed time. This is the sum of
SC31COCC.
STORAGE_OCC_EUDSA
FLOAT
Storage occupancy above the 16MB line in the EUDSA, in
kilobyte-seconds. This measures the area under the curve of
storage in use against elapsed time. This is the sum of
SCUSRSTGE.
STORAGE_OCC_UDSA
FLOAT
Storage occupancy below the 16MB line in the UDSA, in
kilobyte-seconds. This measures the area under the curve of
storage in use against elapsed time. This is the sum of
SCUSRSTG.
STORAGE_PGM_A16M
FLOAT
Peak program storage above the 16MB line, in bytes. This
includes ECDSA, EUDSA, and ERDSA. This is the maximum
of PC31AHWM.
STORAGE_PGM_B16M
FLOAT
Peak program storage below the 16MB line, in bytes. This
includes CDSA and UDSA. This is the maximum of
PC24BHWM.
STORAGE_PGM_CDSA
FLOAT
Peak program storage below the 16MB line in the CICS
dynamic storage area (CDSA), in bytes. This is the maximum
of PC24CHWM.
STORAGE_PGM_ECDSA
FLOAT
Peak program storage above the 16MB line in the extended
CICS dynamic storage area (ECDSA), in bytes. This is the
maximum of PC31CHWM.
STORAGE_PGM_ERDSA
FLOAT
Peak program storage above the 16MB line in the extended
read-only dynamic storage area (ERDSA), in bytes. This is
the maximum of PC31RHWM.
STORAGE_PGM_ESDSA
FLOAT
Peak program storage above the 16MB line in the extended
shared dynamic storage area (ESDSA). This is a subset of
STORAGE_PGM_A16M. This is the maximum of
PC31SHWM.
STORAGE_PGM_EUDSA
FLOAT
Peak program storage above the 16MB line in the extended
user dynamic storage area (EUDSA), in bytes. This is the
maximum of PC31UHWM.
STORAGE_PGM_RDSA
FLOAT
Peak program storage below the 16MB line in the read-only
dynamic storage area (RDSA). This is a subset of
STORAGE_PGM_B16M. This is the maximum of
PC24RHWM.
STORAGE_PGM_SDSA
FLOAT
Peak program storage below the 16MB line in the shared
dynamic storage area (SDSA). This is a subset of
STORAGE_PGM_B16M. This is the maximum of
PC24SHWM.
STORAGE_PGM_TOTAL
FLOAT
Peak program storage both above and below the 16MB line,
in bytes. This is the maximum of PCSTGHWM.
STORAGE_PGM_UDSA
FLOAT
Peak program storage below the 16MB line in the user
dynamic storage area (UDSA), in bytes. This is the maximum
of PC24UHWM.
STORAGE_TIOA_MAX
FLOAT
Peak terminal storage allocated to the terminal for one
transaction, in bytes. This is the maximum of TCSTG.
STORAGE_TIOA_SUM
FLOAT
Terminal storage allocated to the terminal associated with
this transaction, if applicable, in bytes. This is the sum of
TCSTG.
86
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
STORAGE_UDSA_MAX
FLOAT
Peak user storage allocated below the 16MB line in the user
dynamic storage area (UDSA), in bytes. This is the maximum
of SCUSRHWM.
SUSPENDS
FLOAT
Number of times tasks were suspended. This is the sum of
SUSPTIME.
SUSPEND_SEC
FLOAT
Total elapsed time, in seconds, that tasks were suspended by
the dispatcher. This is the sum of SUSPTIME.
SYNCDLY_CLOCK
FLOAT
Elapsed time that the user task waited for a SYNC request to
be issued by its parent transaction. From SYNCDLY.
SYNCDLY_COUNT
FLOAT
Number of times that the user task waited for a SYNC
request to be issued by its parent transaction. From
SYNCDLY.
SYNCPOINT_REQUESTS
FLOAT
Number of SYNCPOINT requests. This is the sum of
SPSYNCCT.
SYNCTIME_CLOCK
FLOAT
Total elapsed time that the user task was dispatched and was
processing Syncpoint requests. This is from SYNCTIME.
SYNCTIME_COUNT
FLOAT
Number of times that the user task was dispatched and was
processing Syncpoint requests. This is the sum of
SYNCTIME.
TC_ALLOCATE_REQ
FLOAT
Number of TCTTE ALLOCATE requests issued by tasks for
APPC, LUTYPE6.1, and IRC sessions. This is the sum of
TCALLOCT.
TC_IO_WAITS
FLOAT
Number of terminal control I/O waits. This includes
LUTYPE6.1 communication waits for CICS V3 data. (See
LU61_IO_WAITS for CICS V4 and later.) This is the sum of
TCIOWTT.
TC_IO_WAIT_SEC
FLOAT
Terminal control I/O wait time, in seconds. This includes
LUTYPE6.1 communication wait time for CICS V3 data. (See
LU61_IO_WAIT_SEC for CICS V4 and later.) This is the sum
of TCIOWTT.
TCB_ATTACH_COUNT
FLOAT
Number of CICS TCBs attached by the user task. From
TCBATTCT.
TCB_CHANGE_MODES
FLOAT
Number of CICS change-TCB modes issued by the user task.
From CHMODECT.
TCLSNAME_DELAY_SEC
FLOAT
Time waiting for the first dispatch caused by transaction
class limits being reached, in seconds. This is the sum of
TCLDELAY.
TCP_SERVICE
CHAR(8)
Name of the CP/IP service. From TCPSRVCE.
TD_GET_REQUESTS
FLOAT
Number of transient data GET requests. This is the sum of
TDGETCT.
TD_IO_WAITS
FLOAT
Number of transient data I/O waits. This is valid for CICS
V3 and later. This is the sum of TDIOWTT.
TD_IO_WAIT_SEC
FLOAT
Transient data I/O wait time, in seconds. This is valid for
CICS V3 and later. This is the sum of TDIOWTT.
TD_PURGE_REQUESTS
FLOAT
Number of transient data PURGE requests. This is the sum
of TDTPURCT.
TD_PUT_REQUESTS
FLOAT
Number of transient data PUT requests. This is the sum of
TDPUTCT.
TD_REQUESTS_TOTAL
FLOAT
Total number of transient data requests. This is the sum of
TDTOTCT.
Chapter 6. Data tables, lookup tables, and control tables
87
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
TOT_NO_SOCKET
FLOAT
Total number of socket requests. From SOTOTCT.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE = T indicating task termination. This is valid for CICS
V3 and later. See RECORDS for earlier versions of CICS.
TRANSACTION_FLAG
CHAR(8)
Transaction flags. A string of 64 bits used for signalling the
transaction definition and status information. From
TRANFLAG.
TRANS_FACILITY_NAM
CHAR(8)
Transaction facility name. From FCTYNAME.
TERM_CONNECT_NAME
CHAR(4)
Terminal session connection name. From TERMCNNM.
TERM_INFO
CHAR(4)
Terminal or session information for this tasks principal
facility as identified in the TERM field id 002. This field is
null if the task is not associated with a terminal or session.
From TERMINFO.
TS_AUX_PUT_REQ
FLOAT
Number of auxiliary temporary storage PUT requests. This is
the sum of TSPUTACT.
TS_GET_REQUESTS
FLOAT
Number of temporary storage GET requests. This is the sum
of TSGETCT.
TS_IO_WAITS
FLOAT
Number of temporary storage I/O waits. This is the sum of
TSIOWTT.
TS_IO_WAIT_SEC
FLOAT
Temporary storage I/O wait time, in seconds. This is the sum
of TSIOWTT.
TS_MAIN_PUT_REQ
FLOAT
Number of main temporary storage PUT requests. This is the
sum of TSPUTMCT.
TS_REQUESTS_TOTAL
FLOAT
Total number of temporary storage requests. This is the sum
of TSTOTCT.
TSSHWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for the completion of
an asynchronous shared temporary storage request to a
temporary storage data server. From TSSHWAIT.
TSSHWAIT_COUNT
FLOAT
Number of times that the user task waited for the completion
of an asynchronous shared temporary storage request to a
temporary storage data server. From TSSHWAIT.
|
|
WMQGETWT_CLOCK
The elapsed time the user task waited for WebSphere MQ to
service the user tasks GETWAIT request. From WMQGETWT.
|
|
|
WMQGETWT_COUNT
The number of times the user task waited for WebSphere MQ
to service the user tasks GETWAIT request. From
WMQGETWT.
WORKLOAD_REPCLASS
CHAR(8)
MVS Workload Manager (WLM) report class for this
transaction. This field is null if the transaction was
WLM-classified in another CICS region. From RPTCLASS.
WORKLOAD_SERVCLASS
CHAR(8)
MVS Workload Manager (WLM) service class for this
transaction. This field is null if the transaction was
WLM-classified in another CICS region. From SRVCLASS.
WTCEWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for one or more Event
Control Blocks (ECBs) or the completion of an event. From
WTEXWAIT.
WTCEWAIT_COUNT
FLOAT
Number of times that the user task waited for one or more
ECBs or the completion of an event. From WTEXWAIT.
WTEXWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for one or more ECBs,
passed to CICS by the user task. From WTEXWAIT.
88
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for subcomponents 1, 4, 8, 11
Column name
Data type
Description
WTEXWAIT_COUNT
FLOAT
Number of times that the user task waited for one or more
ECBs, passed to CICS by the user task. From WTEXWAIT.
X8CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS X8
mode TCB. When a transaction invokes a C or C++ program
that was compiled with the XPLINK option, and that is
defined with EXECKEY= CICS, it is allocated and uses a
CICS X8 mode TCB. From X8CPUT.
X8CPUT_COUNT
FLOAT
Number of times the user task was dispatched by the CICS
dispatcher domain on a CICS X8 mode TCB. This field is
related to XPlink support. From X8CPUT.
X9CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS X9
mode TCB. When a transaction invokes a C or C++ program
that was compiled with the XPLINK option, and that is
defined with EXECKEY= USER, it is allocated and uses a
CICS X9 mode TCB. From X9CPUT.
X9CPUT_COUNT
FLOAT
Number of times the user task was dispatched by the CICS
dispatcher domain on a CICS X9 mode TCB. This field is
related to XPlink support. From X9CPUT.
XPTCBS_WAIT_SEC
FLOAT
The elapsed time, in seconds, in which the user task waited
to obtain a CICS XP TCB (C8 or X9 mode), because the CICS
system had reached the limit set by the system parameter
MAXXPTCBS. From MAXXTDLY.
Common fields for the business transaction service (BTS)
This table shows the fields that come after the key columns.
Column name
Key columns
Data type
Description
See under the table heading.
K
BTS_ACQUIRE_REQS
FLOAT
Number of CICS BTS acquire process or acquire activity
requests issued by the user task. From BAACQACT.
BTS_DEFACT_COUNT
FLOAT
Number of CICS BTS define activity requests issued by the
user task. From BADACTCT.
BTS_DEFPRC_COUNT
FLOAT
Number of CICS BTS define process requests issued by the
user task. From BADPROCT.
BTS_DELETE_COUNT
FLOAT
Number of CICS BTS delete process or delete activity
requests issued by the user task. From BADCPACT.
BTS_DGPACT_CONTAI
FLOAT
Number of CICS BTS delete, get, or put container requests
for activity data containers issued by the user task. From
BAACDCCT.
BTS_DGPPROC_CONTAI
FLOAT
Number of CICS BTS delete, get, or put container requests
for process data containers issued by the user task. From
BAPRDCCT.
BTS_LINK_COUNT
FLOAT
Number of CICS BTS link process or link activity requests
that the user task issued. From BALKPACT.
BTS_RESET_COUNT
FLOAT
Number of CICS BTS reset process or reset activity requests
issued by the user task. From BARSPACT.
BTS_RESUME_COUNT
FLOAT
Number of CICS BTS resume process or resume activity
requests issued by the user task. From BARMPACT.
Chapter 6. Data tables, lookup tables, and control tables
89
Common fields for the business transaction service
Column name
Data type
Description
BTS_RETR_COUNT
FLOAT
Number of CICS BTS retrieve-reattach event requests issued
by the user task. From BADFIECT.
BTS_RUN_ASYNC_COUNT
FLOAT
Number of CICS BTS run process or run activity requests
that the user task made to execute a child process or activity
asynchronously. From BARASYCT.
BTS_RUN_SYNC_COUNT
FLOAT
Number of CICS BTS run process or run activity requests
that the user task made to execute a child process or activity
synchronously. From BARSYNCT.
BTS_SUSPEND_COUNT
FLOAT
Number of CICS BTS suspend process or suspend activity
requests issued by the user task. From BASUPACT.
BTS_TIMEREV_REQS
FLOAT
Number of CICS BTS timer-associated event requests issued
by the user task. From BATIAECT.
BTS_TOT_REQS
FLOAT
Number of CICS BTS acquire process and acquire activity
requests issued by the user task. From BATOTACT.
BTS_TOTACT_CONTAI
FLOAT
Total number of CICS BTS process or activity container
requests issued by the user task. From BATOTCCT.
BTS_TOTEVENT_REQS
FLOAT
Total number of CICS BTS event requests issued by the user
task. From BATOTECT.
RECORDS
FLOAT
Total number of performance class monitoring records. This
is the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS
V3 and later. For earlier versions of CICS, see the column
RECORDS in this table.
Common fields for the Channel and Container usage for data
transfer (CHN)
This table shows the fields that come after the key columns.
Column name
Data type
Description
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination.
START_CHAN_LREQS
FLOAT
Total number of local interval control START requests, with
the CHANNEL option, issued by the user task. From
ICSTACCT.
LREQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all the
locally-executed START CHANNEL requests issued by the
user task. This total includes the length of any headers to the
data. From ICSTACDL.
START_CHAN_RREQS
FLOAT
Total number of interval control START CHANNEL requests,
to be executed on remote systems, issued by the user task.
From ICSTRCCT.
RREQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all the
remotely-executed START CHANNEL requests issued by the
user task. This total includes the length of any headers to the
data. From ICSTRCDL.
90
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for the Channel and Container usage for data transfer
Column name
Data type
Description
DPL_REQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all the
distributed program link (DPL) requests, with the CHANNEL
option, issued by the user task. This total includes the length
of any headers to the data. From PCDLCSDL.
DPLRET_REQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all DPL
RETURN CHANNEL commands issued by the user task. This
total includes the length of any headers to the data. From
PCDLCRDL.
LINK_CHAN_REQS
FLOAT
Number of local program LINK requests, with the CHANNEL
option, issued by the user task. From PCLNKCCT.
XCTL_CHAN_REQS
FLOAT
Number of program XCTL requests issued with the
CHANNEL option by the user task. From PCXCLCCT.
DPL_CHAN_REQS
FLOAT
Number of program distributed program link (DPL) requests
issued with the CHANNEL option by the user task. From
PCDPLCCT.
RET_CHAN_REQS
FLOAT
Number of remote pseudoconversational RETURN requests,
with the CHANNEL option, issued by the user task. From
PCRTNCCT.
RET_CHAN_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all the
remote pseudoconversational RETURN CHANNEL commands
issued by the user task. This total includes the length of any
headers to the data. From PCRTNCDL.
CHAN_CONTAIN_REQS
FLOAT
Number of CICS requests for channel containers issued by the
user task. From PGTOTCCT.
CHAN_BRWCONT_REQS
FLOAT
Number of CICS browse requests for channel containers
issued by the user task. From PGBRWCCT.
CHAN_GETCONT_REQS
FLOAT
Number of GET CONTAINER requests for channel containers
issued by the user task. From PGGETCCT.
CHAN_PUTCONT_REQS
FLOAT
Number of PUT CONTAINER requests for channel containers
issued by the user task. From PGPUTCCT.
CHAN_MOVCONT_REQS
FLOAT
Number of MOVE CONTAINER requests for channel
containers issued by the user task. From PGMOVCCT.
CHAN_GETCONT_BYTES
FLOAT
The total length, in bytes, of the data in the containers of all
the GET CONTAINER CHANNEL commands issued by the
user task. From PGGETCDL.
CHAN_PUTCONT_BYTES
FLOAT
CHANNEL commands issued by the user task. From
PGPUTCDL.
CHAN_MOVEPUT_CONT
FLOAT
The number of containers created by MOVE and PUT
CONTAINER requests for channel containers issued by the
user task. From PGCRECCT.
Chapter 6. Data tables, lookup tables, and control tables
91
Common fields for the document handler
Common fields for the document handler (DOC)
This table shows the fields that come after the key columns.
Column name
Data type
Key columns
Description
See under the table heading.
K
DOCHND_CRT_COUNT
FLOAT
Number of document handler CREATE requests issued by the
user task. From DHCRECT.
DOCHND_INS_COUNT
FLOAT
Number of document handler INSERT requests issued by the
user task. From DHINSCT.
DOCHND_RETR_COUNT
FLOAT
Number of document handler RETRIEVE requests issued by
the user task. From DHRETCT.
DOCHND_SET_COUNT
FLOAT
Number of document handler SET requests issued by the user
task. From DHSETCT.
DOCHND_TOT_COUNT
FLOAT
Number of document handler requests issued by the user
task. From DHTOTCT.
DOCHND_TOTCREDOCL
FLOAT
Number of all documents created by the user task. From
DHTOTDCL.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS
V3 and later. For earlier versions of CICS, see the column
RECORDS in this table.
Common fields for the Web interface (WEB)
This table shows the fields that come after the key columns.
Column name
Key columns
Data type
Description
See under the table heading.
K
BEANTOT_REQ_NUM
FLOAT
The total of beans occurred. From EJBTOTCT.
NO_WEB_BROWSE
FLOAT
Number of WEB browse requests. From WBBRWCT.
NO_WEB_EXTRACT
FLOAT
Number of WEB extract requests. From WBEXTRCT.
NO_WEB_READ
FLOAT
Number of WEB read requests. From WBREADCT.
NO_WEB_WRITE
FLOAT
Number of WEB write requests. From WBWRITCT.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS
V3 and later. For earlier versions of CICS, see the column
RECORDS in this table.
WEB_CHARS_RECEIVED
FLOAT
Number of characters received by the CICS Web interface
RECEIVE requests issued by the user task. From WBCHRIN.
WEB_CHARS_SENT
FLOAT
Number of characters sent by the CICS Web interface SEND
requests issued by the user task. From WBRCHROUT.
WEBH_BROWSE_REQS
FLOAT
Number of CICS Web support BROWSE HTTPHEADER
requests (STARTBROWSE, READNEXT, and ENDBROWSE)
issued by the user task when CICS is an HTTP client. From
WBBRWOCT.
92
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Common fields for the Web interface
Column name
Data type
Description
WEBH_BYTES_RECV
FLOAT
Number of bytes received by the RECEIVE and CONVERSE
requests issued by the user task when CICS is an HTTP client.
From WBCHRIN1.
WEBH_BYTES_SENT
FLOAT
Number of bytes sent by the SEND and CONVERSE requests
issued by the user task when CICS is an HTTP client. From
WBCHROU1.
WEBH_INVOKEWS_REQS
FLOAT
Number of CICS INVOKE WEBSERVICE requests issued by
the user task. From WBIWBSCT.
WEBH_PARSEURL_REQS
FLOAT
Number of PARSE URL requests issued by the user task. From
WBPARSCT.
WEBH_READ_REQS
FLOAT
Number of WEB READ HTTPHEADER requests issued by the
user task when CICS is an HTTP client. From WBREDOCT.
WEBH_READTEM_BYTES
FLOAT
Total length, in bytes, of the data read from the repository in
temporary storage by the user task. From WBREPRDL.
WEBH_RECV_REQS
FLOAT
Number of WEB RECEIVE and CONVERSE requests issued
by the user task when CICS is an HTTP client. From
WBRCVIN1.
WEBH_SEND_REQS
FLOAT
Number of WEB SEND and CONVERSE requests issued by
the user task when CICS is an HTTP client. From
WBSNDOU1.
WEBH_WRITTEM_BYTES
FLOAT
Total length, in bytes, of the data written to the repository in
temporary storage by the user task. From WBREPWDL.
WEBH_WRITE_REQS
FLOAT
Number of WEB WRITE HTTPHEADER requests issued by
the user task when CICS is an HTTP client. From
WBWRTOCT.
WEB_RECV_REQS
FLOAT
Number of CICS Web interface RECEIVE requests issued by
the user task. From WBRCVCT.
WEB_REPOREAD_REQS
FLOAT
Number of reads from repository in shared temporary storage
issued by the user task. From WBREPRCT.
WEB_REPOWRITE_REQS
FLOAT
Number of writes in shared temporary storage issued by the
user task. From WBREPWCT.
WEB_SEND_REQS
FLOAT
Number of CICS Web interface SEND requests issued by the
user task. From WBSENDCT.
WEB_TOT_REQS
FLOAT
Number of CICS Web interface requests issued by the user
task. From WBTOTCT.
Chapter 6. Data tables, lookup tables, and control tables
93
DBCTL subcomponent data tables
2. DBCTL subcomponent
The data tables described in this section are for the database control (DBCTL)
subcomponent, which summarizes (by transaction and user) DBCTL data gathered
by the CICS monitoring facility (CMF). These tables contain the DBCTL monitoring
fields.
CICS_DBCTL_USR_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions. They
contain information from the DBCTL fields in the performance class monitoring
record.
The default retention periods for these tables are:
7 days for CICS_DBCTL_USR_H
30 days for CICS_DBCTL_USR_D
565 days for CICS_DBCTL_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
USER_ID
K
CHAR(8)
User ID. From USERID.
TRANSACTION_ID
K
CHAR(8)
Transaction identifier. From TRAN.
PSB_NAME
K
CHAR(8)
Name of the PSB. From DBCTL_NPSB.
DEDB_CALL_CNT
INTEGER
Number of Data Entry Data Base (DEDB) calls. This is the sum
of DBCTL_DECL.
DEDB_READ_CNT
INTEGER
Number of Data Entry Data Base (DEDB) read requests. This is
the sum of DBCTL_DERD.
DLI_CALL_CNT
INTEGER
Number of DL/I requests. This is the sum of DBCTL_TOTC.
DLI_DEL_CALL_CNT
INTEGER
Number of DL/I Delete requests. This is the sum of
DBCTL_DLET.
DLI_GHN_CALL_CNT
INTEGER
Number of DL/I Get Hold Next (GHN) requests. This is the
sum of DBCTL_GHN.
DLI_GHNP_CALL_CNT
INTEGER
Number of DL/I Get Hold Next within Parent (GHNP)
requests. This is the sum of DBCTL_GHNP.
DLI_GHU_CALL_CNT
INTEGER
Number of DL/I Get Hold Unique (GHU) requests. This is the
sum of DBCTL_GHU.
DLI_GN_CALL_CNT
INTEGER
Number of DL/I Get Next (GN) requests. This is the sum of
DBCTL_GN.
DLI_GNP_CALL_CNT
INTEGER
Number of DL/I Get Next within Parent (GNP) requests. This
is the sum of DBCTL_GNP.
DLI_GU_CALL_CNT
INTEGER
Number of DL/I Get Unique (GU) requests. This is the sum of
DBCTL_GU1.
94
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DBCTL subcomponent data tables
Column name
Data type
Description
DLI_INS_CALL_CNT
INTEGER
Number of DL/I Insert requests. This is the sum of
DBCTL_ISRT.
DLI_IO_CNT
INTEGER
DL/I I/O count. Accounting data from the PST (PSTACCT).
This is the sum of DBCTL_DBIO.
DLI_IO_TIME_USEC
FLOAT
DL/I I/O time, in microseconds. This is the sum of
DBCTL_TMIO.
DLI_REP_CALL_CNT
INTEGER
Number of DL/I Replace requests. This is the sum of
DBCTL_REPL.
EXL_DEQ_CNT
INTEGER
Number of exclusive dequeues. This is the sum of
DBCTL_EXDQ.
EXL_ENQ_CNT
INTEGER
Number of exclusive enqueues. This is the sum of
DBCTL_EXEQ.
FASTPATH_RESERV
INTEGER
Reserved for Fast Path.
INTENCON_WAIT_USEC
FLOAT
Wait time for intent conflict, in microseconds. In a PSB
schedule, when an intent conflict is detected, the schedule
request must wait. This is the sum of DBCTL_INTC.
OVERFLOW_BUFF_CNT
INTEGER
Number of overflow buffers used. This is the sum of
DBCTL_OVFN.
PGM_ISO_LOCK_USEC
FLOAT
Time spent in Program Isolation (PI) locking, in microseconds.
This is the sum of DBCTL_TLOC.
POOLSPAC_WAIT_USEC
FLOAT
Wait time for pool space, in microseconds. In a PSB schedule,
when the pool space is insufficient for PSB/DMB blocks, the
schedule request must wait. This is the sum of DBCTL_POOL.
RECORDS
INTEGER
Total number of performance class monitoring records. This is
the number of log records summarized.
SCHED_PROCESS_USEC
FLOAT
Time to schedule the PSB, in microseconds. This is the sum of
DBCTL_SCHT.
TEST_DEQ_CNT
INTEGER
Number of test dequeues. This is the sum of DBCTL_TSDQ.
TEST_ENQ_CNT
INTEGER
Number of test enqueues. This is the sum of DBCTL_TENQ.
THREAD_CPU_SEC
FLOAT
Thread CPU time, in seconds.
UNIT_WORK_CONT_CNT
INTEGER
Number of unit-of-work contentions. Sum of DBCTL_UOWC.
UPD_DEQ_CNT
INTEGER
Number of update dequeues. This is the sum of
DBCTL_UPDQ.
UPD_ENQ_CNT
INTEGER
Number of update enqueues. This is the sum of
DBCTL_UENQ.
WAIT_DEDB_BUFF_CNT
INTEGER
Number of waits for a Data Entry Data Base (DEDB) buffer.
This is the sum of DBCTL_BFWT.
WAIT_EXL_ENQ_CNT
INTEGER
Number of waits for exclusive enqueues. This is the sum of
DBCTL_WEXQ.
WAIT_TEST_ENQ_CNT
INTEGER
Number of waits for test enqueues. This is the sum of
DBCTL_WTEQ.
WAIT_UPD_ENQ_CNT
INTEGER
Number of waits for update enqueues. This is the sum of
DBCTL_WUEQ.
Chapter 6. Data tables, lookup tables, and control tables
95
DL/I subcomponent data tables
3. DL/I subcomponent
The data tables described in this section are for the Data Language/I (DL/I)
subcomponent, which summarizes (by transaction and user) DL/I data gathered
by the CICS monitoring facility (CMF). These tables contain the DL/I monitoring
fields.
CICS_DLI_USR_H, _D, _W
These tables provide statistics on CICS transactions, grouped by user ID. They
contain information from the DL/I fields in the performance class monitoring
record.
The default retention periods for these tables are:
7 days for CICS_DLI_USR_H
30 days for CICS_DLI_USR_D
565 days for CICS_DLI_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Derived from fields SMFMNSID, SMFMNDTE and
SMFSMNME using the PERIOD function.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID
for a task created as the result of receiving an ATTACH
request across an MRO or APPC link with attach-time security.
From USERID.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
CALL_CNT
INTEGER
Number of DL/I calls. This is the sum of DLI_CLK3_COUNT.
CALL_ELAPS_SEC
FLOAT
Elapsed time for DL/I calls, in seconds. From
DLI_CLK3_CLOCK.
DELETE_CALL_CNT
INTEGER
Number of DELETE requests. This is the sum of DLI_DELETE.
GET_HOLD_NEXT_CNT
INTEGER
Number of Get Hold Next (GHN) requests. This is the sum of
DLI_GETHN.
GET_HOLD_NEXTP_CNT
INTEGER
Number of Get Hold Next within Parent (GHNP) requests.
This is the sum of DLI_GETGHNP.
GET_HOLD_UNIQ_CNT
INTEGER
Number of Get Hold Unique (GHU) requests. This is the sum
of DLI_GETHU.
GET_NEXT_PAR_CNT
INTEGER
Number of Get Next within Parent (GNP) requests. This is the
sum of DLI_GETNP.
GET_NEXT_REQ_CNT
INTEGER
Number of Get Next (GN) requests. This is the sum of
DLI_GETN.
GET_UNIQ_REQ_CNT
INTEGER
Number of Get Unique (GU) requests. This is the sum of
DLI_GETU.
INSERT_CALL_CNT
INTEGER
Number of Insert requests. This is the sum of DLI_INSERT.
IO_WAIT_CNT
INTEGER
Number of DL/I I/O waits. This is the sum of
DLI_CLK4_COUNT.
96
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DL/I subcomponent data tables
Column name
Data type
Description
IO_WAIT_TIME
FLOAT
DL/I I/O wait time, in seconds. From DLI_CLK4_CLOCK.
PSB_SCHED_ACT_CNT
INTEGER
Number of PSB terminations. This is the sum of
DLI_CLK2_COUNT.
PSB_SCHED_ACT_SEC
FLOAT
Time that a PSB was scheduled, in seconds. This is measured
from completion of the schedule request to termination. From
DLI_CLK2_CLOCK.
PSB_SCHED_REQ_CNT
INTEGER
Number of PSB schedule requests. This is the sum of
DLI_CLK1_COUNT.
PSB_SCHED_REQ_SEC
FLOAT
Time to service PSB schedule requests, in seconds. From
DLI_CLK1_CLOCK.
RECORDS
INTEGER
Number of performance class monitoring records. This is the
number of log records summarized.
REPLACE_CALL_CNT
INTEGER
Number of Replace requests. This is the sum of
DLI_REPLACE.
4. Basic application analysis subcomponent
The data tables described in this section are for the basic application analysis
subcomponent, which summarizes CMF-gathered transaction data by application.
CICS_A_BASIC_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
application name. They contain information from CICS performance class
monitoring records from CICS/ESA and CICS/TS (SMF 110, subtype 1) and
CICS/MVS (SMF 110, subtype 0).
The default retention periods for these tables are:
14 days for CICS_A_BASIC_H
565 days for CICS_A_BASIC_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This
is normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals
according to operator shift or to separate peak and other
periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the
CICS_LOOKUP_APPL lookup table.
FLOAT
Response-time objective for this application. This is from
APPL_RESP_BND1_SEC in the CICS_LOOKUP_APPL
lookup table.
RESPONSE_OBJ_SEC
Remaining fields
See “Common fields for subcomponents 1, 4, 8, and 11” on
page 76.
Chapter 6. Data tables, lookup tables, and control tables
97
Basic application analysis subcomponent data tables
CICSBTS_A_BASIC_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
application name. They contain information from CICS performance class
monitoring records from CICS/TS (SMF 110, subtype 1) related to the business
transaction service (BTS).
The default retention periods for these tables are:
14 days for CICSBTS_A_BASIC_H
565 days for CICSBTS_A_BASIC_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column RECORDS
in this table.
Remaining fields
See “Common fields for the business transaction service (BTS)”
on page 89.
CICSCHN_A_BASIC_H, _W
These tables provide hourly and weekly statistics related to the use of channels
and containers for data transfer between programs. They contain information from
CICS performance class monitoring records from CICS/TS (SMF 110, subtype 1)
grouped by application name.
The default retention periods are:
14 days for CICSCHN_A_BASIC_H
365 days for CICSCHN_A_BASIC_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
98
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic application analysis subcomponent data tables
Column name
Data type
Description
TIME
K
TIME
Used only in CICSCHN_A_BASIC_H. The hour when the
performance records were initialised. From START. (For _H
table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
Remaining fields
See “Common fields for the Channel and Container usage for
data transfer (CHN)” on page 90.
CICSDOC_A_BASIC_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
application name. They contain information from CICS performance class
monitoring records from CICS/TS (SMF 110, subtype 1) related to the document
handler.
The default retention periods for these tables are:
14 days for CICSDOC_A_BASIC_H
565 days for CICSDOC_A_BASIC_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
See “Common fields for the document handler (DOC)” on page
92.
Chapter 6. Data tables, lookup tables, and control tables
99
Basic application analysis subcomponent data tables
CICSWEB_A_BASIC_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
application name. They contain information from CICS performance class
monitoring records from CICS/TS (SMF 110, subtype 1) related to the Web
interface activity.
The default retention periods for these tables are:
14 days for CICSWEB_A_BASIC_H
565 days for CICSWEB_A_BASIC_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
See “Common fields for the Web interface (WEB)” on page 92.
5. DBCTL application analysis subcomponent
The data tables described in this section are for the DBCTL application analysis
subcomponent, which summarizes CMF-gathered transaction data by application.
CICS_A_DBCTL_H, _W
These tables provide hourly and weekly statistics on CICS transactions. They
contain information from the DBCTL fields in the performance class monitoring
record.
The default retention periods for these tables are:
30 days for CICS_A_DBCTL_H
565 days for CICS_A_DBCTL_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
100
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DBCTL application analysis subcomponent data tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF is
used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
PSB_NAME
K
CHAR(8)
Name of the PSB. From DBCTL_NPSB.
DEDB_CALL_CNT
INTEGER
Number of Data Entry Data Base (DEDB) calls. This is the sum
of DBCTL_DECL.
DEDB_READ_CNT
INTEGER
Number of Data Entry Data Base (DEDB) read requests. This is
the sum of DBCTL_DERD.
DLI_CALL_CNT
INTEGER
Number of DL/I requests. This is the sum of DBCTL_TOTC.
DLI_DEL_CALL_CNT
INTEGER
Number of DL/I Delete requests. This is the sum of
DBCTL_DLET.
DLI_GHN_CALL_CNT
INTEGER
Number of DL/I Get Hold Next (GHN) requests. This is the
sum of DBCTL_GHN.
DLI_GHNP_CALL_CNT
INTEGER
Number of DL/I Get Hold Next within Parent (GHNP)
requests. This is the sum of DBCTL_GHNP.
DLI_GHU_CALL_CNT
INTEGER
Number of DL/I Get Hold Unique (GHU) requests. This is the
sum of DBCTL_GHU.
DLI_GN_CALL_CNT
INTEGER
Number of DL/I Get Next (GN) requests. This is the sum of
DBCTL_GN.
DLI_GNP_CALL_CNT
INTEGER
Number of DL/I Get Next within Parent (GNP) requests. This
is the sum of DBCTL_GNP.
DLI_GU_CALL_CNT
INTEGER
Number of DL/I Get Unique (GU) requests. This is the sum of
DBCTL_GU1.
DLI_INS_CALL_CNT
INTEGER
Number of DL/I Insert requests. This is the sum of
DBCTL_ISRT.
DLI_IO_CNT
INTEGER
DL/I I/O count. Accounting data from the PST (PSTACCT).
This is the sum of DBCTL_DBIO.
DLI_IO_TIME_USEC
FLOAT
DL/I I/O time, in microseconds. This is the sum of
DBCTL_TMIO.
DLI_REP_CALL_CNT
INTEGER
Number of DL/I Replace requests. This is the sum of
DBCTL_REPL.
EXL_DEQ_CNT
INTEGER
Number of exclusive dequeues. This is the sum of
DBCTL_EXDQ.
EXL_ENQ_CNT
INTEGER
Number of exclusive enqueues. This is the sum of
DBCTL_EXEQ.
FASTPATH_RESERV
INTEGER
Reserved for Fast Path.
INTENCON_WAIT_USEC
FLOAT
Wait time for intent conflict, in microseconds. In a PSB
schedule, when an intent conflict is detected, the schedule
request must wait. This is the sum of DBCTL_INTC.
OVERFLOW_BUFF_CNT
INTEGER
Number of overflow buffers used. This is the sum of
DBCTL_OVFN.
PGM_ISO_LOCK_USEC
FLOAT
Time spent in Program Isolation (PI) locking, in microseconds.
This is the sum of DBCTL_TLOC.
Chapter 6. Data tables, lookup tables, and control tables
101
DBCTL application analysis subcomponent data tables
Column name
Data type
Description
POOLSPAC_WAIT_USEC
FLOAT
Wait time for pool space, in microseconds. In a PSB schedule,
when the pool space is insufficient for PSB/DMB blocks, the
schedule request must wait. This is the sum of DBCTL_POOL.
RECORDS
INTEGER
Total number of performance class monitoring records. This is
the number of log records summarized.
SCHED_PROCESS_USEC
FLOAT
Time to schedule the PSB, in microseconds. This is the sum of
DBCTL_SCHT.
TEST_DEQ_CNT
INTEGER
Number of test dequeues. This is the sum of DBCTL_TSDQ.
TEST_ENQ_CNT
INTEGER
Number of test enqueues. This is the sum of DBCTL_TENQ.
THREAD_CPU_SEC
FLOAT
Thread CPU time, in seconds. This is the sum of
DBCTL_CTM1.
UNIT_WORK_CONT_CNT
INTEGER
Number of unit-of-work contentions. Sum of DBCTL_UOWC.
UPD_DEQ_CNT
INTEGER
Number of update dequeues. This is the sum of
DBCTL_UPDQ.
UPD_ENQ_CNT
INTEGER
Number of update enqueues. This is the sum of
DBCTL_UENQ.
WAIT_DEDB_BUFF_CNT
INTEGER
Number of waits for a Data Entry Data Base (DEDB) buffer.
This is the sum of DBCTL_BFWT.
WAIT_EXL_ENQ_CNT
INTEGER
Number of waits for exclusive enqueues. This is the sum of
DBCTL_WEXQ.
WAIT_TEST_ENQ_CNT
INTEGER
Number of waits for test enqueues. This is the sum of
DBCTL_WTEQ.
WAIT_UPD_ENQ_CNT
INTEGER
Number of waits for update enqueues. This is the sum of
DBCTL_WUEQ.
6. DL/I application analysis subcomponent
The data tables described in this section are for the DL/I application analysis
subcomponent, which summarizes CMF-gathered transaction data by application.
CICS_A_DLI_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
application name. They contain information from the DL/I fields in the
performance class monitoring record.
The default retention periods for these tables are:
30 days for CICS_A_DLI_H
565 days for CICS_A_DLI_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Derived from fields SMFMNSID, SMFMNDTE and
SMFSMNME using the PERIOD function.
TIME
K
TIME
Ttime when the transaction was started. It applies only to the
_H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
102
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DL/I application analysis subcomponent data tables
Column name
Data type
Description
CHAR(18)
Application name. From the CICS_LOOKUP_APPL lookup
table.
CALL_CNT
INTEGER
Number of DL/I calls. This is the sum of DLI_CLK3_COUNT.
CALL_ELAPS_SEC
FLOAT
Elapsed time for DL/I calls, in seconds. From
DLI_CLK3_CLOCK.
DELETE_CALL_CNT
INTEGER
Number of Delete requests. This is the sum of DLI_DELETE.
GET_HOLD_NEXT_CNT
INTEGER
Number of Get Hold Next (GHN) requests. This is the sum of
DLI_GETHN.
GET_HOLD_NEXTP_CNT
INTEGER
Number of Get Hold Next within Parent (GHNP) requests.
This is the sum of DLI_GETGHNP.
GET_HOLD_UNIQ_CNT
INTEGER
Number of Get Hold Unique (GHU) requests. This is the sum
of DLI_GETHU.
GET_NEXT_PAR_CNT
INTEGER
Number of Get Next within Parent (GNP) requests. This is the
sum of DLI_GETNP.
GET_NEXT_REQ_CNT
INTEGER
Number of Get Next (GN) requests. This is the sum of
DLI_GETN.
GET_UNIQ_REQ_CNT
INTEGER
Number of Get Unique (GU) requests. This is the sum of
DLI_GETU.
INSERT_CALL_CNT
INTEGER
Number of Insert requests. This is the sum of DLI_INSERT.
IO_WAIT_CNT
INTEGER
Number of DL/I I/O waits. This is the sum of
DLI_CLK4_COUNT.
IO_WAIT_TIME
FLOAT
DL/I I/O wait time, in seconds. From DLI_CLK4_CLOCK.
PSB_SCHED_ACT_CNT
INTEGER
Number of PSB terminations. This is the sum of
DLI_CLK2_COUNT.
PSB_SCHED_ACT_SEC
FLOAT
Time that a PSB was scheduled, in seconds. This is measured
from completion of the schedule request to termination. From
DLI_CLK2_CLOCK.
PSB_SCHED_REQ_CNT
INTEGER
Number of PSB schedule requests. This is the sum of
DLI_CLK1_COUNT.
PSB_SCHED_REQ_SEC
FLOAT
Time to service PSB schedule requests, in seconds. From
DLI_CLK1_CLOCK.
RECORDS
INTEGER
Number of performance class monitoring records. This is the
number of log records summarized.
REPLACE_CALL_CNT
INTEGER
Number of Replace requests. This is the sum of
DLI_REPLACE.
APPLICATION_NAME
K
7. CICS/MVS subcomponent (global + accounting)
The data tables described in this section are for the CICS/MVS subcomponent
(global + accounting). These tables contain the Tivoli Decision Support for z/OS
objects necessary to summarize global and accounting data only for CICS/MVS
Version 2.
CICS_M_ACCOUNT_H, _D, _W, _M
These tables provide accounting statistics on CICS transactions. They use data from
accounting class monitoring records from CICS/MVS Version 2 (SMF 110,
subtype 0).
The default retention periods for these tables are:
Chapter 6. Data tables, lookup tables, and control tables
103
CICS/MVS subcomponent data tables
7 days for CICS_M_ACCOUNT_H
30 days for CICS_M_ACCOUNT_D
565 days for CICS_M_ACCOUNT_W
565 days for CICS_M_ACCOUNT_M
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Derived from fields SMFMNSID, SMFMNDTE and
SMFSMNME using the PERIOD function.
TIME
K
SMALLINT
Time when the transaction was started. It applies only to the
_H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
TERMINAL_ID
K
CHAR(4)
Terminal identifier. From TERM.
TRANSACTION_TYPE
K
CHAR(4)
Transaction type. From T.
USER_ID
K
CHAR(8)
User ID related to the transaction. From USERID.
ABENDS
INTEGER
Number of transactions that abended. From ABENDS.
END_TIME_LATEST
TIMESTAMP
Most recent task-detach time. From STOP.
MESSAGES_INPUT
INTEGER
Number of input messages. From MSGIN.
RECORDS
INTEGER
Number of accounting class monitoring records. This is the
number of log records summarized. From START.
RESPONSE_MAX_SEC
INTEGER
Maximum task response time, in seconds. This is the
maximum of STOP−START.
RESPONSE_MIN_SEC
INTEGER
Minimum task response time, in seconds. This is the minimum
of STOP−START.
RESPONSE_SUM_SEC
INTEGER
Summarized task response time, in seconds. Calculated as
STOP−START.
START_TIME_EARLIES
TIMESTAMP
Earliest task-start time. From START.
TRANSACTIONS
INTEGER
Number of transactions identified. From OCCURS.
USERS
INTEGER
Number of users. From UCOUNT.
8. Basic transaction subcomponent
The data tables described in this section are for the basic transaction
subcomponent, which summarizes (by transaction) basic data by the CICS
monitoring facility (CMF).
CICS_TRANSACTION_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions. They
contain information from CICS performance class monitoring records from
CICS/ESA and CICS/TS (SMF 110, subtype 1) and CICS/MVS (SMF 110,
subtype 0).
The default retention periods for these tables are:
7 days for CICS_TRANSACTION_H
30 days for CICS_TRANSACTION_D
104
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic transaction subcomponent data tables
565 days for CICS_TRANSACTION_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is normally
the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the PERIOD_PLAN
table. Use it to group time intervals according to operator shift or to
separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It applies
only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is used
when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
Remaining fields
See “Common fields for subcomponents 1, 4, 8, and 11” on page 76.
CICSBTS_TRANSACT_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions,
grouped by transaction ID. They contain information from CICS performance class
monitoring records from CICS/TS (SMF 110, subtype 1) related to the business
transaction service (BTS).
The default retention periods for these tables are:
7 days for CICSBTS_TRANSACT_H
30 days for CICSBTS_TRANSACT_D
565 days for CICSBTS_TRANSACT_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals
according to operator shift or to separate peak and other
periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that
is used when requesting a session with this CICS system.
From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS
V3 and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
See “Common fields for the business transaction service
(BTS)” on page 89.
Chapter 6. Data tables, lookup tables, and control tables
105
Basic transaction subcomponent data tables
CICSCHN_TRANSACT_H, _D, _W
These tables provide hourly, daily and weekly statistics related to the use of
channels and containers for data transfer between programs. They contain
information from CICS performance class monitoring records from CICS/TS (SMF
110, subtype 1) grouped by transaction ID.
The default retention periods are:
7 days for CICSCHN_TRANSACT_H
30 days for CICSCHN_TRANSACT_D
365 days for CICSCHN_TRANSACT_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
Used only in CICSCHN_TRANSACT_H. The hour when the
performance records were initialised. From START. (For _H
table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
Remaining fields
See “Common fields for the Channel and Container usage for
data transfer (CHN)” on page 90.
CICSDOC_TRANSACT_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions,
grouped by transaction ID. They contain information from CICS performance class
monitoring records from CICS/TS (SMF 110, subtype 1) related to the document
handler.
The default retention periods for these tables are:
7 days for CICSDOC_TRANSACT_H
30 days for CICSDOC_TRANSACT_D
565 days for CICSDOC_TRANSACT_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
106
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic transaction subcomponent data tables
Column name
Data type
Description
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column
RECORDS in this table.
Remaining fields
See “Common fields for the document handler (DOC)” on page
92.
CICSWEB_TRANSACT_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions,
grouped by transaction ID. They contain information from CICS performance class
monitoring records from CICS/TS (SMF 110, subtype 1) related to the Web
interface activity.
The default retention periods for these tables are:
7 days for CICSWEB_TRANSACT_H
30 days for CICSWEB_TRANSACT_D
565 days for CICSWEB_TRANSACT_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This
is normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals
according to operator shift or to separate peak and other
periods.
TIME
K
TIME
The hour when the performance records were initialized.
It applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN.
RECORDS
FLOAT
Total number of performance class monitoring records.
This is the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records
with RTYPE=T indicating task termination. This is valid
for CICS V3 and later. For earlier versions of CICS, see
the column RECORDS in this table.
Remaining fields
See “Common fields for the Web interface (WEB)” on
page 92.
9. DBCTL transaction subcomponent
The data tables described in this section are for the DBCTL transaction
subcomponent, which summarizes (by transaction) DBCTL data gathered by the
CICS monitoring facility (CMF). These tables contain the DBCTL monitoring fields.
Chapter 6. Data tables, lookup tables, and control tables
107
DBCTL transaction subcomponent data tables
CICS_DBCTL_TRAN_H, _D, _W
These tables provide hourly, daily, and weekly statistics on CICS transactions. They
contain information from the DBCTL fields in the performance class monitoring
record.
The default retention periods for these tables are:
7 days for CICS_DBCTL_TRAN_H
30 days for CICS_DBCTL_TRAN_D
565 days for CICS_DBCTL_TRAN_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF is
used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
PSB_NAME
K
CHAR(8)
Name of the PSB. From DBCTL_NPSB.
DEDB_CALL_CNT
INTEGER
Number of Data Entry Data Base (DEDB) calls. This is the sum
of DBCTL_DECL.
DEDB_READ_CNT
INTEGER
Number of Data Entry Data Base (DEDB) read requests. This is
the sum of DBCTL_DERD.
DLI_CALL_CNT
INTEGER
Number of DL/I requests. This is the sum of DBCTL_TOTC.
DLI_DEL_CALL_CNT
INTEGER
Number of DL/I Delete requests. This is the sum of
DBCTL_DLET.
DLI_GHN_CALL_CNT
INTEGER
Number of DL/I Get Hold Next (GHN) requests. This is the
sum of DBCTL_GHN.
DLI_GHNP_CALL_CNT
INTEGER
Number of DL/I Get Hold Next within Parent (GHNP)
requests. This is the sum of DBCTL_GHNP.
DLI_GHU_CALL_CNT
INTEGER
Number of DL/I Get Hold Unique (GHU) requests. This is the
sum of DBCTL_GHU.
DLI_GN_CALL_CNT
INTEGER
Number of DL/I Get Next (GN) requests. This is the sum of
DBCTL_GN.
DLI_GNP_CALL_CNT
INTEGER
Number of DL/I Get Next within Parent (GNP) requests. This
is the sum of DBCTL_GNP.
DLI_GU_CALL_CNT
INTEGER
Number of DL/I Get Unique (GU) requests. This is the sum of
DBCTL_GU1.
DLI_INS_CALL_CNT
INTEGER
Number of DL/I Insert requests. This is the sum of
DBCTL_ISRT.
DLI_IO_CNT
INTEGER
DL/I I/O count. Accounting data from the PST (PSTACCT).
This is the sum of DBCTL_DBIO.
DLI_IO_TIME_USEC
FLOAT
DL/I I/O time, in microseconds. This is the sum of
DBCTL_TMIO.
108
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DBCTL transaction subcomponent data tables
Column name
Data type
Description
DLI_REP_CALL_CNT
INTEGER
Number of DL/I Replace requests. This is the sum of
DBCTL_REPL.
EXL_DEQ_CNT
INTEGER
Number of exclusive dequeues. This is the sum of
DBCTL_EXDQ.
EXL_ENQ_CNT
INTEGER
Number of exclusive enqueues. This is the sum of
DBCTL_EXEQ.
FASTPATH_RESERV
INTEGER
Reserved for Fast Path.
INTENCON_WAIT_USEC
FLOAT
Wait time for intent conflict, in microseconds. In a PSB
schedule, when an intent conflict is detected, the schedule
request must wait. This is the sum of DBCTL_INTC.
OVERFLOW_BUFF_CNT
INTEGER
Number of overflow buffers used. This is the sum of
DBCTL_OVFN.
PGM_ISO_LOCK_USEC
FLOAT
Time spent in Program Isolation (PI) locking, in microseconds.
This is the sum of DBCTL_TLOC.
POOLSPAC_WAIT_USEC
FLOAT
Wait time for pool space, in microseconds. In a PSB schedule,
when the pool space is insufficient for PSB/DMB blocks, the
schedule request must wait. This is the sum of DBCTL_POOL.
RECORDS
INTEGER
Total number of performance class monitoring records. This is
the number of log records summarized.
SCHED_PROCESS_USEC
FLOAT
Time to schedule the PSB, in microseconds. This is the sum of
DBCTL_SCHT.
TEST_DEQ_CNT
INTEGER
Number of test dequeues. This is the sum of DBCTL_TSDQ.
TEST_ENQ_CNT
INTEGER
Number of test enqueues. This is the sum of DBCTL_TENQ.
THREAD_CPU_SEC
FLOAT
Thread CPU time, in seconds.
UNIT_WORK_CONT_CNT
INTEGER
Number of unit-of-work contentions. Sum of DBCTL_UOWC.
UPD_DEQ_CNT
INTEGER
Number of update dequeues. This is the sum of
DBCTL_UPDQ.
UPD_ENQ_CNT
INTEGER
Number of update enqueues. This is the sum of
DBCTL_UENQ.
WAIT_DEDB_BUFF_CNT
INTEGER
Number of waits for a Data Entry Data Base (DEDB) buffer.
This is the sum of DBCTL_BFWT.
WAIT_EXL_ENQ_CNT
INTEGER
Number of waits for exclusive enqueues. This is the sum of
DBCTL_WEXQ.
WAIT_TEST_ENQ_CNT
INTEGER
Number of waits for test enqueues. This is the sum of
DBCTL_WTEQ.
WAIT_UPD_ENQ_CNT
INTEGER
Number of waits for update enqueues. This is the sum of
DBCTL_WUEQ.
10. DL/I transaction subcomponent
The data tables described in this section are for the DL/I transaction
subcomponent, which summarizes (by transaction) DL/I data gathered by the
CICS monitoring facility (CMF). These tables contain the DL/I monitoring fields.
CICS_DLI_TRAN_H, _D, _W
This table provides hourly, daily and weekly statistics on CICS transactions. It
contains information from the DL/I fields in the performance class monitoring
record.
Chapter 6. Data tables, lookup tables, and control tables
109
DL/I transaction subcomponent data tables
The default retention periods for these tables are:
7 days for CICS_DLI_TRAN_H
30 days for CICS_DLI_TRAN_D
565 days for CICS_DLI_TRAN_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Derived from fields SMFMNSID, SMFMNDTE and
SMFSMNME using the PERIOD function.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
CALL_CNT
INTEGER
Number of DL/I calls. This is the sum of DLI_CLK3_COUNT.
CALL_ELAPS_SEC
FLOAT
Elapsed time for DL/I calls, in seconds. From
DLI_CLK3_CLOCK.
DELETE_CALL_CNT
INTEGER
Number of Delete requests. This is the sum of DLI_DELETE.
GET_HOLD_NEXT_CNT
INTEGER
Number of Get Hold Next (GHN) requests. This is the sum of
DLI_GETHN.
GET_HOLD_NEXTP_CNT
INTEGER
Number of Get Hold Next within Parent (GHNP) requests.
This is the sum of DLI_GETGHNP.
GET_HOLD_UNIQ_CNT
INTEGER
Number of Get Hold Unique (GHU) requests. This is the sum
of DLI_GETHU.
GET_NEXT_PAR_CNT
INTEGER
Number of Get Next within Parent (GNP) requests. This is the
sum of DLI_GETNP.
GET_NEXT_REQ_CNT
INTEGER
Number of Get Next (GN) requests. This is the sum of
DLI_GETN.
GET_UNIQ_REQ_CNT
INTEGER
Number of Get Unique (GU) requests. This is the sum of
DLI_GETU.
INSERT_CALL_CNT
INTEGER
Number of Insert requests. This is the sum of DLI_INSERT.
IO_WAIT_CNT
INTEGER
Number of DL/I I/O waits. This is the sum of
DLI_CLK4_COUNT.
IO_WAIT_TIME
FLOAT
DL/I I/O wait time, in seconds. From DLI_CLK4_CLOCK.
PSB_SCHED_ACT_CNT
INTEGER
Number of PSB terminations. This is the sum of
DLI_CLK2_COUNT.
PSB_SCHED_ACT_SEC
FLOAT
Time that a PSB was scheduled, in seconds. This is measured
from completion of the schedule request to termination. From
DLI_CLK2_CLOCK.
PSB_SCHED_REQ_CNT
INTEGER
Number of PSB schedule requests. This is the sum of
DLI_CLK1_COUNT.
PSB_SCHED_REQ_SEC
FLOAT
Time to service PSB schedule requests, in seconds. From
DLI_CLK1_CLOCK.
RECORDS
INTEGER
Number of performance class monitoring records. This is the
number of log records summarized.
110
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DL/I transaction subcomponent data tables
Column name
Data type
Description
REPLACE_CALL_CNT
INTEGER
Number of Replace requests. This is the sum of
DLI_REPLACE.
11. Basic application user subcomponent
The data tables described in this section are for the Basic application user
subcomponent, which summarizes CMF-gathered transaction data by application
and user.
CICS_A_USR_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
user ID and application name. They contain information from CICS performance
class monitoring records from CICS/ESA and CICS/TS (SMF 110, subtype 1) and
CICS/MVS (SMF 110, subtype 0).
The default retention periods for these tables are:
14 days for CICS_A_USR_H
565 days for CICS_A_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It applies
only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is used
when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for a
task created as the result of receiving an ATTACH request across an
MRO or APPC link with attach-time security. From USERID.
Remaining fields
See “Common fields for subcomponents 1, 4, 8, and 11” on page 76.
CICSBTS_A_USR_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
user ID and application name. They contain information from CICS performance
class monitoring records from CICS/TS (SMF 110, subtype 1) related to the
business transaction service (BTS).
The default retention periods for these tables are:
14 days for CICSBTS_A_USR_H
565 days for CICSBTS_A_USR_W
Chapter 6. Data tables, lookup tables, and control tables
111
Basic application user subcomponent data tables
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for a
task created as the result of receiving an ATTACH request across
an MRO or APPC link with attach-time security. From USERID.
RECORDS
FLOAT
Total number of performance class monitoring records. This is the
number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column RECORDS
in this table.
Remaining fields
See “Common fields for the business transaction service (BTS)”
on page 89.
CICSCHN_A_USR_H, _W
These tables provide hourly and weekly statistics related to the use of channels
and containers for data transfer between programs. They contain information from
CICS performance class monitoring records from CICS/TS (SMF 110, subtype 1)
grouped by user ID and application name.
The default retention periods for these tables are:
14 days for CICSCHN_A_USR_H
365 days for CICSCHN_A_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
Used only in CICSCHN_A_USR_H. The hour when the
performance records were initialized. From START. (For _H table
only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
112
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Basic application user subcomponent data tables
Column name
USER_ID
K
Data type
Description
CHAR(8)
User ID at task creation. This can also be the remote user ID for a
task created as the result of receiving an ATTACH request across
an MRO or APPC link with attach-time security. From USERID.
Remaining fields
See “Common fields for the Channel and Container usage for data
transfer (CHN)” on page 90.
CICSDOC_A_USR_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
user ID and application name. They contain information from CICS performance
class monitoring records from CICS/TS (SMF 110, subtype 1) related to the
document handler.
The default retention periods for these tables are:
14 days for CICSDOC_A_USR_H
565 days for CICSDOC_A_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for a
task created as the result of receiving an ATTACH request across
an MRO or APPC link with attach-time security. From USERID.
RECORDS
FLOAT
Total number of performance class monitoring records. This is the
number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column RECORDS
in this table.
Remaining fields
See “Common fields for the document handler (DOC)” on page
92.
CICSWEB_A_USR_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
user ID and application name. They contain information from CICS performance
class monitoring records from CICS/TS (SMF 110, subtype 1) related to the Web
interface activity.
The default retention periods for these tables are:
14 days for CICSWEB_A_USR_H
565 days for CICSWEB_A_USR_W
Chapter 6. Data tables, lookup tables, and control tables
113
Basic application user subcomponent data tables
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according to
operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
APPLICATION_NAME
K
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RECORDS
FLOAT
Total number of performance class monitoring records. This is
the number of log records summarized.
TRANSACTION_COUNT
FLOAT
Total number of performance class monitoring records with
RTYPE=T indicating task termination. This is valid for CICS V3
and later. For earlier versions of CICS, see the column RECORDS
in this table.
Remaining fields
See “Common fields for the Web interface (WEB)” on page 92.
12. DBCTL application user subcomponent
The data tables described in this section are for the DBCTL application user
subcomponent, which summarizes CMF-gathered transaction data by application
and user.
CICS_A_DBCTL_USR_H,_W
These tables provide hourly and weekly statistics on CICS transactions. They
contain information from the DBCTL fields in the performance class monitoring
record.
The default retention periods for these tables are:
30 days for CICS_A_DBCTL_USR_H
565 days for CICS_A_DBCTL_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
The hour when the performance records were initialized. It
applies only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the system ID. From SMFMNSID.
114
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DBCTL application user subcomponent data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID
for a task created as the result of receiving an ATTACH
request across an MRO or APPC link with attach-time security.
From USERID.
APPLICATION_NAME
K
CHAR(18)
Application name. From CICS_LOOKUP_APPL lookup table.
PSB_NAME
K
CHAR(8)
Name of the PSB. From DBCTL_NPSB.
DEDB_CALL_CNT
INTEGER
Number of Data Entry Data Base (DEDB) calls. This is the
sum of DBCTL_DECL.
DEDB_READ_CNT
INTEGER
Number of Data Entry Data Base (DEDB) read requests. This
is the sum of DBCTL_DERD.
DLI_CALL_CNT
INTEGER
Number of DL/I requests. This is the sum of DBCTL_TOTC.
DLI_DEL_CALL_CNT
INTEGER
Number of DL/I Delete requests. This is the sum of
DBCTL_DLET.
DLI_GHN_CALL_CNT
INTEGER
Number of DL/I Get Hold Next (GHN) requests. This is the
sum of DBCTL_GHN.
DLI_GHNP_CALL_CNT
INTEGER
Number of DL/I Get Hold Next within Parent (GHNP)
requests. This is the sum of DBCTL_GHNP.
DLI_GHU_CALL_CNT
INTEGER
Number of DL/I Get Hold Unique (GHU) requests. This is the
sum of DBCTL_GHU.
DLI_GN_CALL_CNT
INTEGER
Number of DL/I Get Next (GN) requests. This is the sum of
DBCTL_GN.
DLI_GNP_CALL_CNT
INTEGER
Number of DL/I Get Next within Parent (GNP) requests. This
is the sum of DBCTL_GNP.
DLI_GU_CALL_CNT
INTEGER
Number of DL/I Get Unique (GU) requests. This is the sum of
DBCTL_GU1.
DLI_INS_CALL_CNT
INTEGER
Number of DL/I Insert requests. This is the sum of
DBCTL_ISRT.
DLI_IO_CNT
INTEGER
DL/I I/O count. Accounting data from the PST (PSTACCT).
This is the sum of DBCTL_DBIO.
DLI_IO_TIME_USEC
FLOAT
DL/I I/O time, in microseconds. This is the sum of
DBCTL_TMIO.
DLI_REP_CALL_CNT
INTEGER
Number of DL/I Replace requests. This is the sum of
DBCTL_REPL.
EXL_DEQ_CNT
INTEGER
Number of exclusive dequeues. This is the sum of
DBCTL_EXDQ.
EXL_ENQ_CNT
INTEGER
Number of exclusive enqueues. This is the sum of
DBCTL_EXEQ.
FASTPATH_RESERV
INTEGER
Reserved for Fast Path.
INTENCON_WAIT_USEC
FLOAT
Wait time for intent conflict, in microseconds. In a PSB
schedule, when an intent conflict is detected, the schedule
request must wait. This is the sum of DBCTL_INTC.
OVERFLOW_BUFF_CNT
INTEGER
Number of overflow buffers used. This is the sum of
DBCTL_OVFN.
Chapter 6. Data tables, lookup tables, and control tables
115
DBCTL application user subcomponent data tables
Column name
Data type
Description
PGM_ISO_LOCK_USEC
FLOAT
Time spent in Program Isolation (PI) locking, in microseconds.
This is the sum of DBCTL_TLOC.
POOLSPAC_WAIT_USEC
FLOAT
Wait time for pool space, in microseconds. In a PSB schedule,
when the pool space is insufficient for PSB/DMB blocks, the
schedule request must wait. This is the sum of DBCTL_POOL.
RECORDS
INTEGER
Total number of performance class monitoring records. This is
the number of log records summarized.
SCHED_PROCESS_USEC
FLOAT
Time to schedule the PSB, in microseconds. This is the sum of
DBCTL_SCHT.
TEST_DEQ_CNT
INTEGER
Number of test dequeues. This is the sum of DBCTL_TSDQ.
TEST_ENQ_CNT
INTEGER
Number of test enqueues. This is the sum of DBCTL_TENQ.
THREAD_CPU_SEC
FLOAT
Thread CPU time, in seconds. From DBCTL_CTM1.
UNIT_WORK_CONT_CNT
INTEGER
Number of unit-of-work contentions. Sum of DBCTL_UOWC.
UPD_DEQ_CNT
INTEGER
Number of update dequeues. This is the sum of
DBCTL_UPDQ.
UPD_ENQ_CNT
INTEGER
Number of update enqueues. This is the sum of
DBCTL_UENQ.
WAIT_DEDB_BUFF_CNT
INTEGER
Number of waits for a Data Entry Data Base (DEDB) buffer.
This is the sum of DBCTL_BFWT.
WAIT_EXL_ENQ_CNT
INTEGER
Number of waits for exclusive enqueues. This is the sum of
DBCTL_WEXQ.
WAIT_TEST_ENQ_CNT
INTEGER
Number of waits for test enqueues. This is the sum of
DBCTL_WTEQ.
WAIT_UPD_ENQ_CNT
INTEGER
Number of waits for update enqueues. This is the sum of
DBCTL_WUEQ.
13. DL/I application user subcomponent
The data tables described in this section are for the DL/I application user
subcomponent, which summarizes CMF-gathered transaction data by application
and user.
CICS_A_DLI_USR_H, _W
These tables provide hourly and weekly statistics on CICS transactions, grouped by
application name and user ID. They contain information from the DL/I fields in
the performance class monitoring record.
The default retention periods for these tables are:
30 days for CICS_A_DLI_USR_H
565 days for CICS_A_DLI_USR_W
Column name
Data type
Description
DATE
K
DATE
Date when the transaction was started. From START.
PERIOD_NAME
K
CHAR(8)
Derived from fields SMFMNSID, SMFMNDTE and
SMFSMNME using the PERIOD function.
TIME
K
TIME
Time when the transaction was started. It applies only to the
_H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
116
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DL/I application user subcomponent data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system. When XRF
is used, the two systems have the same generic but different
specific IDs. From SMFMNPRN.
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID
for a task created as the result of receiving an ATTACH
request across an MRO or APPC link with attach-time security.
From USERID.
APPLICATION_NAME
K
CHAR(18)
Application name. From CICS_LOOKUP_APPL lookup table.
CALL_CNT
INTEGER
Number of DL/I calls. This is the sum of DLI_CLK3_COUNT.
CALL_ELAPS_SEC
FLOAT
Elapsed time for DL/I calls, in seconds. From
DLI_CLK3_CLOCK.
DELETE_CALL_CNT
INTEGER
Number of Delete requests. This is the sum of DLI_DELETE.
GET_HOLD_NEXT_CNT
INTEGER
Number of Get Hold Next (GHN) requests. This is the sum of
DLI_GETHN.
GET_HOLD_NEXTP_CNT
INTEGER
Number of Get Hold Next within Parent (GHNP) requests.
This is the sum of DLI_GETGHNP.
GET_HOLD_UNIQ_CNT
INTEGER
Number of Get Hold Unique (GHU) requests. This is the sum
of DLI_GETHU.
GET_NEXT_PAR_CNT
INTEGER
Number of Get Next within Parent (GNP) requests. This is the
sum of DLI_GETNP.
GET_NEXT_REQ_CNT
INTEGER
Number of Get Next (GN) requests. This is the sum of
DLI_GETN.
GET_UNIQ_REQ_CNT
INTEGER
Number of Get Unique (GU) requests. This is the sum of
DLI_GETU.
INSERT_CALL_CNT
INTEGER
Number of Insert requests. This is the sum of DLI_INSERT.
IO_WAIT_CNT
INTEGER
Number of DL/I I/O waits. This is the sum of
DLI_CLK4_COUNT.
IO_WAIT_TIME
FLOAT
DL/I I/O wait time, in seconds. From DLI_CLK4_CLOCK.
PSB_SCHED_ACT_CNT
INTEGER
Number of PSB terminations. This is the sum of
DLI_CLK2_COUNT.
PSB_SCHED_ACT_SEC
FLOAT
Time that a PSB was scheduled, in seconds. This is measured
from completion of the schedule request to termination. From
DLI_CLK2_CLOCK.
PSB_SCHED_REQ_CNT
INTEGER
Number of PSB schedule requests. This is the sum of
DLI_CLK1_COUNT.
PSB_SCHED_REQ_SEC
FLOAT
Time to service PSB schedule requests, in seconds. From
DLI_CLK1_CLOCK.
RECORDS
INTEGER
Number of performance class monitoring records. This is the
number of log records summarized.
REPLACE_CALL_CNT
INTEGER
Number of Replace requests. This is the sum of
DLI_REPLACE.
14. CICS TS Transaction Resources subcomponent
The data tables described in this section provide transaction resource data coming
from class 5 CMF records.
Chapter 6. Data tables, lookup tables, and control tables
117
CICS TS Transaction Resources data tables
CICS_FILE_TRAN_H, _D, _W
These tables provide file resource data grouped by transaction ID. The data is from
the CICS transaction resource class monitoring records (SMF 110, subtype 1).
The default retention periods for these tables are:
7 days for CICS_FILE_TRAN_H
30 days for CICS_FILE_TRAN_D
565 days for CICS_FILE_TRAN_W
Column name
Data type
Description
DATE
K
DATE
Date when the record was written to SMF. From SMFMNDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFMNSID,
SMFMNDTE, and SMFMNTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the record was written to SMF. It applies only to
the _H table. From SMFMNTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction ID. From MNRTRAID.
FILE_NAME
K
CHAR(8)
File name. From MNRFLNME.
CFDT_IOWAIT_CLOCK
FLOAT
The elapsed time in which the user task waited for a data table
access request to the coupling facility data table server to
complete for this file. From MNRCFDTT_CLOCK.
FILE_ACCMETH_COUNT
FLOAT
The number of times that the user task invoked file
access-method interfaces. From MNRFLAM_COUNT.
FILE_ADD_CLOCK
FLOAT
The elapsed time that the user task waited for completion of
ADD requests for this file. From MNRFLADD_CLOCK.
FILE_ADD_COUNT
FLOAT
The number of ADD requests issued against this file. From
MNRFLADD_COUNT.
FILE_BRW_CLOCK
FLOAT
The elapsed time that the user task waited for completion of
BROWSE requests for this file. From MNRFLBRW_CLOCK.
FILE_BRW_COUNT
FLOAT
The number of BROWSE requests issued against this file. From
MNRFLBRW_COUNT.
FILE_DEL_CLOCK
FLOAT
The elapsed time that the user task waited for completion of
DELETE requests for this file. From MNRFLDEL_CLOCK.
FILE_DEL_COUNT
FLOAT
The number of DELETE requests issued against this file. From
MNRFLDEL_COUNT.
FILE_GET_CLOCK
FLOAT
The elapsed time that the user task waited for completion of
GET requests for this file. From MNRFLGET_CLOCK.
FILE_GET_COUNT
FLOAT
The number of GET requests issued against this file. From
MNRFLGET_COUNT.
FILE_IOWAIT_CLOCK
FLOAT
The total I/O wait time on this file. From
MNRIOWTM_CLOCK.
FILE_PUT_CLOCK
FLOAT
The elapsed time that the user task waited for completion of
PUT requests for this file. From MNRFLPUT_CLOCK.
FILE_PUT_COUNT
FLOAT
The number of PUT requests issued against this file. From
MNRFLPUT_COUNT.
118
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS TS Transaction Resources data tables
Column name
Data type
Description
FILE_TOT_CLOCK
FLOAT
The elapsed time that the user task waited for completion of all
requests for this file. From MNRFLTOT_CLOCK.
FILE_TOT_COUNT
FLOAT
The number of all requests issued against this file. From
MNRFLTOT_COUNT.
RLS_IOWAIT_CLOCK
FLOAT
The elapsed time in which the user task waited for RLS file
I/O on this file. From MNRRLSWT_CLOCK.
CICS_QUEUE_TRAN_H, _D, _W
These tables provide temporary storage queue resource data grouped by
transaction ID. They gather information from the CICS transaction resource class
monitoring records (SMF 110, subtype 1).
The default retention periods for these tables are:
7 days for CICS_QUEUE_TRAN_H
30 days for CICS_QUEUE_TRAN_D
565 days for QUEUE_FILE_TRAN_W
Column name
Data type
Description
DATE
K
DATE
Date when the record was written to SMF. From
SMFMNDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFMNSID, SMFMNDTE, and SMFMNTME from the
record as parameters in the PERIOD function.
TIME
K
TIME
Time when the record was written to SMF. It applies only
to the _H table. From SMFMNTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction ID. From MNRTRAID.
TSQUEUE_NAME
K
CHAR(16)
The name of the temporary storage queue. From
MNRTSQNM.
TSQUEUE_GET_CLOCK
FLOAT
The elapsed time that the user task waited for completion
of GET requests for this temporary storage queue. From
MNRTSQGT_CLOCK.
TSQUEUE_GET_COUNT
FLOAT
The number of GET requests issued against the
temporary storage queue. From MNRTSQGT_COUNT.
TSQUEUE_PUT_CLOCK
FLOAT
The elapsed time that the user task waited for completion
of PUT requests to auxiliary temporary storage for this
temporary storage queue. From MNRTSQPA_CLOCK.
TSQUEUE_PUT_COUNT
FLOAT
The number of PUT requests to auxiliary temporary
storage issued against the temporary storage queue. From
MNRTSQPA_COUNT.
TSQUEUE_MAIN_CLOCK
FLOAT
The elapsed time that the user task waited for completion
of PUT requests to main temporary storage for this
temporary storage queue. From MNRTSQPM_CLOCK.
TSQUEUE_MAIN_COUNT
FLOAT
The number of PUT requests tomain temporary storage
issued against the temporary storage queue. From
MNRTSQPM_COUNT.
Chapter 6. Data tables, lookup tables, and control tables
119
CICS TS Transaction Resources data tables
Column name
Data type
Description
TSQUEUE_TOT_CLOCK
FLOAT
The elapsed time that the user task waited for completion
of all requests for this temporary storage queue. From
MNRTSQTO_CLOCK.
TSQUEUE_TOT_COUNT
FLOAT
The number of all requests issued against the temporary
storage queue. From MNRTSQTO_COUNT.
TSQUEUE_GETIT_LEN
FLOAT
The total length of all items obtained from this temporary
storage queue. From MNRGETIT.
TSQUEUE_PUTAUX_LEN
FLOAT
The total length of all items written to the auxiliary
temporary storage queue. From MNRPUTAX.
TSQUEUE_MAIN_LEN
FLOAT
The total length of all items written to the main
temporary storage queue. From MNRPUTMN.
TSQUEUE_IOWT_CLOCK
FLOAT
The total I/O wait time on this temporary storage queue.
From MNRIOWAT_CLOCK.
SHQUEUE_IOWT_CLOCK
FLOAT
The total I/O wait time on the shared temporary storage
queue. From MNRSHWAT_CLOCK.
15. CICS TS Enterprise Java Beans subcomponent
The data table described in this section provides enterprise bean-related data
coming from class 3 CMF records. Data is summarized by CORBA server name.
CICS_BEAN_REQ_H, _D, _W
These tables provide enterprise bean-related data grouped by CORBA server. The
data is from CICS performance class monitoring records (SMF 110, subtype 1).
The default retention periods for these tables are:
7 days for CICS_BEAN_REQ_H
30 days for CICS_BEAN_REQ_D
565 days for CICS_BEAN_REQ_W
Column name
Data type
Description
DATE
K
DATE
Date when the performance records were initialized. This is
normally the task start date. From START.
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
K
TIME
Hour when the performance records were initialized. It applies
only to the _H table. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
CORBASER_NAME
K
CHAR(4)
The CorbaServer for which this request processor instance is
handling requests. From CBSRVRNM.
BEANACT_REQ_NUM
FLOAT
The number of bean activations that have occurred in this
request processor. From EJBSACCT.
BEANPAS_REQ_NUM
FLOAT
The number of bean passivations that have occurred in this
request processor. From EJBSPACT.
BEANCRE_REQ_NUM
FLOAT
The number of bean creation calls that have occurred in this
request processor. From EJBCRECT.
120
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS TS Enterprise Java Beans data tables
Column name
Data type
Description
BEANREM_REQ_NUM
FLOAT
The number of bean removal calls that have occurred in this
request processor. From EJBREMCT.
BEANMET_REQ_NUM
FLOAT
The number of bean method calls that have occurred in this
request processor. From EJBMTHCT.
BEANTOT_REQ_NUM
FLOAT
Total beans that have occurred in this request processor. From
EJBTOTCT.
16. CICS Resource Manager Interface subcomponent
The data table described in this section provides Resource Manager Interface (RMI)
data coming from CICS performance class monitoring records, and is grouped by
transaction ID.
The default retention periods are:
7 days for CICS_RMI_PERF_T
7 days for CICS_RMI_PERF_H
45 days for CICS_RMI_PERF_D
CICS_RMI_PERF_T
Column name
Data type
Description
DATETIME
K
TIMESTAMP
Date and Time of the transaction
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN
USER_ID
K
CHAR(8)
User ID at task creation.This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RMI_SEC
FLOAT
Time spent in the Resource Manager Interface (RMI), in
seconds. This is the sum of RMITIME.
RMI_COUNT
FLOAT
Number of times that the user task was in the Resource
Manager Interface (RMI). This is the sum of RMITIME.
RMI_SUSPEND_SEC
FLOAT
Number of times that the task was suspended while in the
Resource Manager Interface (RMI). This is a subset of
SUSPENDS and RMI_COUNT. This is the sum of RMISUSP.
RMITOTAL_CLOCK
FLOAT
The total elapsed time spent in the CICS Resource Manager
Interface
RMITOTAL_COUNT
FLOAT
Count of RMI calls. From RMITOTAL.
RMIOTHER_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for resource
manager requests other than DB2, DBCTL, EXEC DLI,
WebSphere® MQ, CICSPlex® SM, and CICS TCP/IP socket
requests.
RMIOTHER_COUNT
FLOAT
Count of other RMI calls. From RMIOTHER
Chapter 6. Data tables, lookup tables, and control tables
121
CICS TS Enterprise Java Beans data tables
Column name
Data type
Description
RMIDB2_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI forDB2 requests
RMIDB2_COUNT
FLOAT
Count of DB2 RMI calls. From RMIDB2
RMIDBCTL_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for DBCTL
requests
RMIDBCTL_COUNT
FLOAT
Count of DBCTL RMI calls. From RMIDBCTL
RMIEXDLI_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for EXEC DLI
requests
RMIEXDLI_COUNT
FLOAT
Count of DLI RMI calls. From RMIDLI
RMIMQM_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for WebSphere
MQ requests
RMIMQM_COUNT
FLOAT
Count of MQM RMI calls. From RMIMQM
RMICPSM_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for CICSPlex SM
requests
RMICPSM_COUNT
FLOAT
Count of CPSM RMI calls. From RMICPSM
RMITCPIP_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for CICS TCP/IP
socket requests
RMITCPIP_COUNT
FLOAT
Count of TCPIP RMI calls. From RMITCPIP
CICS_RMI_PERF_H
Column name
Data type
Description
DATE
K
DATE
Date of the transaction
TIME
K
TIME
Hour of the transaction
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RMI_SEC
FLOAT
Time spent in the Resource Manager Interface (RMI), in
seconds. This is the sum of RMITIME.
RMI_COUNT
FLOAT
Number of times that the user task was in the Resource
Manager Interface (RMI). This is the sum of RMITIME.
RMI_SUSPEND_SEC
FLOAT
Number of times that the task was suspended while in the
Resource Manager Interface (RMI). This is a subset of
SUSPENDS and RMI_COUNT. This is the sum of RMISUSP.
RMITOTAL_CLOCK
FLOAT
The total elapsed time spent in the CICS Resource Manager
Interface
RMITOTAL_COUNT
FLOAT
Count of RMI calls. From RMITOTAL.
122
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS TS Enterprise Java Beans data tables
Column name
Data type
Description
RMIOTHER_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for resource
manager requests other than DB2, DBCTL, EXEC DLI,
WebSphere MQ, CICSPlex SM, and CICS TCP/IP socket
requests.
RMIOTHER_COUNT
FLOAT
Count of other RMI calls. From RMIOTHER
RMIDB2_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for DB2 requests
RMIDB2_COUNT
FLOAT
Count of DB2 RMI calls. From RMIDB2
RMIDBCTL_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for DBCTL
requests
RMIDBCTL_COUNT
FLOAT
Count of DBCTL RMI calls. From RMIDBCTL
RMIEXDLI_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for EXEC DLI
requests
RMIEXDLI_COUNT
FLOAT
Count of DLI RMI calls. From RMIDLI
RMIMQM_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for WebSphere
MQ requests
RMIMQM_COUNT
FLOAT
Count of MQM RMI calls. From RMIMQM
RMICPSM_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for CICSPlex SM
requests
RMICPSM_COUNT
FLOAT
Count of CPSM RMI calls. From RMICPSM
RMITCPIP_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for CICS TCP/IP
socket requests
RMITCPIP_COUNT
FLOAT
Count of TCPIP RMI calls. From RMITCPIP
CICS_RMI_PERF_D
Column name
Data type
Description
DATE
K
DATE
Day of the transaction
PERIOD_NAME
K
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFMNSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction name. From TRAN
USER_ID
K
CHAR(8)
User ID at task creation. This can also be the remote user ID for
a task created as the result of receiving an ATTACH request
across an MRO or APPC link with attach-time security. From
USERID.
RMI_SEC
FLOAT
Time spent in the Resource Manager Interface (RMI), in
seconds. This is the sum of RMITIME
RMI_COUNT
FLOAT
Number of times that the user task was in the Resource
Manager Interface (RMI). This is the sum of RMITIME.
RMI_SUSPEND_SEC
FLOAT
Number of times that the task was suspended while in the
Resource Manager Interface (RMI). This is a subset of
SUSPENDS and RMI_COUNT. This is the sum of RMISUSP.
RMITOTAL_CLOCK
FLOAT
The total elapsed time spent in the CICS Resource Manager
Interface
Chapter 6. Data tables, lookup tables, and control tables
123
CICS TS Enterprise Java Beans data tables
Column name
Data type
Description
RMITOTAL_COUNT
FLOAT
Count of RMI calls. From RMITOTAL.
RMIOTHER_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for resource
manager requests other than DB2, DBCTL, EXEC DLI,
WebSphere MQ, CICSPlex SM, and CICS TCP/IP socket
requests.
RMIOTHER_COUNT
FLOAT
Count of other RMI calls. From RMIOTHER
RMIDB2_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for DB2 requests
RMIDB2_COUNT
FLOAT
Count of DB2 RMI calls. From RMIDB2
RMIDBCTL_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for DBCTL
requests
RMIDBCTL_COUNT
FLOAT
Count of DBCTL RMI calls. From RMIDBCTL
RMIEXDLI_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for EXEC DLI
requests
RMIEXDLI_COUNT
FLOAT
Count of DLI RMI calls. From RMIDLI
RMIMQM_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for WebSphere
MQ requests
RMIMQM_COUNT
FLOAT
Count of MQM RMI calls. From RMIMQM
RMICPSM_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for CICSPlex SM
requests
RMICPSM_COUNT
FLOAT
Count of CPSM RMI calls. From RMICPSM
RMITCPIP_CLOCK
FLOAT
The total elapsed time spent in the CICS RMI for CICS TCP/IP
socket requests
RMITCPIP_COUNT
FLOAT
Count of TCPIP RMI calls. From RMITCPIP
Tables in the CICS OMEGAMON monitoring component
As described in “Evaluating the CICS OMEGAMON monitoring component” on
page 15, this component contains subcomponents. This section groups data tables
for the CICS OMEGAMON monitoring component by these subcomponents:
1. File and Database Subcomponent
2. File and Database Application Subcomponent
3. File and Database Transaction Subcomponent
4. File and Database Application User Subcomponent
5. File and Database Detailed Usage Subcomponent
Tables in subcomponents 1, 2, 3 and 4 contain the same information, differing only
in their key structure.
1. File and Database subcomponent data tables
The data tables described in this section are for the file and database
subcomponent, which summarizes basic file and database usage information, as
appended by OMEGAMON XE for CICS to the SMF type 110 record. The data is
summarized by transaction and user, similar to the tables of the Basic
subcomponent of the CICS Monitoring component.
124
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
File and Database subcomponent data tables
CICS_O_FL_H, _D, _W
These tables provide file and database usage information from SMF type 110
subtype 1 records, as appended by OMEGAMON. The data is grouped by user
and transaction.
The default retention periods for these tables are:
7 days for CICS_O_FL_ H
30 days for CICS_O_FL_ D
565 days for CICS_O_FL_ W
Column Name
Key
Data Type
Comment
DATE
k
DATE(4)
Date when the records were initialized. This is normally the
task start date. From SMF110DTE.
PERIOD_NAME
k
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
k
TIME(4)
The hour when the performance records were initialized. It
applies only to the _H table. From SMF110TME.
MVS_SYSTEM_ID
k
CHAR(4)
MVS system ID. This is the SMF system ID. From SMF110SID.
CICS_SYSTEM_ID
k
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMF110PRN.
TRANSACTION_ID
k
CHAR(4)
Transaction name
USER_ID
k
CHAR(8)
User ID at task creation. This can also be the remote user ID
for a task created as the result of receiving an ATTACH
request across an MRO or APPC link with attach-time security.
From USERID.
FILE_DB_ TYPE
k
CHAR(10)
File or Database TYPE. Please refer to Table 3 on page 126 for
possible values.
FILE_DB_ACTION
k
CHAR(3)
File or Database Action. Please refer to Table 3 on page 126 for
possible values.
CLOCK
FLOAT(8)
Elapsed Time for File or Database Action.
COUNT
FLOAT(8)
Number of file or database actions.
FILE_DB_TYPE and FILE_DB_ACTION combinations: Table 3 on page 126 lists
the possible combinations of FILE_DB_TYPE and FILE_DB_ACTION, as processed
by Tivoli Decision Support for z/OS:
Chapter 6. Data tables, lookup tables, and control tables
125
File and Database subcomponent data tables
Table 3. FILE_DB_TYPE and FILE_DB_ACTION combinations
FILE_DB_TYPE
FILE_DB_ACTION
Description
DB2
OPN
OPEN CURSOR
CLO
CLOSE CURSOR
FET
FETCH
SEL
SELECT
INS
INSERT
UPD
UPDATE
DEL
DELETE
PRE
PRERARE
DES
DESCRIBE
EXE
EXECUTE
EXI
EXECUTE IMMEDIATE
MIS
MISCELLANEOUS
DATACOM
TOT
TOTAL
SUPRA
TOT
TOTAL
ADABAS
TOT
TOTAL
IDMS
TOT
TOTAL
VSAM
TOT
TOTAL
DLI
SCH
SCHEDULE THE PCB
TER
TERMINATE THE PCB
GU
GET UNIQUE
GN
GET NEXT
GNP
GET NEXT IN PARENT
GHU
GET HOLD UNIQUE
GHN
GET HOLD NEXT
GHP
GET HOLD NEXT IN PARENT
INS
INSERT
DEL
DELETE
REP
REPLACE
TOT
TOTAL
F1
FUNCTION1
F2
FUNCTION2
F3
FUNCTION3
F4
FUNCTION4
F5
FUNCTION5
F6
FUNCTION6
F7
FUNCTION7
F8
FUNCTION8
F9
FUNCTION9
F10
FUNCTION10
MQ
126
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
File and Database Application subcomponent data tables
2. File and Database Application subcomponent data tables
The data tables described in this section are for the file and database application
subcomponent, which summarizes basic file and database usage information, as
appended by OMEGAMON XE for CICS to the SMF type 110 record. The data is
summarized by application, similar to the data in the tables of the Basic
Application analysis subcomponent of the CICS Monitoring component
CICS_O_A_FL_H,_D,_W
These tables provide file and database usage information from SMF type 110
subtype 1 records, as appended by OMEGAMON. The data is grouped by
application name.
The default retention periods for these tables are:
7 days for CICS_O_A_FL_ H
30 days for CICS_O_A_FL_ D
565 days for CICS_O_A_FL_ W
Column Name
Key
Data Type
Comment
DATE
k
DATE(4)
Date when the records were initialized. This is normally the
task start date. From SMF110DTE.
PERIOD_NAME
k
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
k
TIME(4)
The hour when the performance records were initialized. It
applies only to the _H table. From SMF110TME.
MVS_SYSTEM_ID
k
CHAR(4)
MVS system ID. This is the SMF system ID. From SMF110SID.
CICS_SYSTEM_ID
k
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMF110PRN.
APPLICATION_NAME
k
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
FILE_DB_ TYPE
k
CHAR(10)
File or Database TYPE. Please refer to Table 3 on page 126 for
possible values.
FILE_DB_ACTION
k
CHAR(3)
File or Database Action. Please refer to Table 3 on page 126 for
possible values.
CLOCK
FLOAT(8)
Elapsed Time for File or Database Action.
COUNT
FLOAT(8)
Number of file or database actions.
3. File and Database Transaction subcomponent data tables
The data tables described in this section are for the file and database transaction
subcomponent, which summarizes basic file and database usage information, as
appended by OMEGAMON XE for CICS to the SMF type 110 record. The data is
summarized by transaction, similar to the data in the tables of the Basic
Transaction subcomponent of the CICS Monitoring component.
CICS_O_TRAN_FL_ H,_D,_W
These tables provide file and database usage information from SMF type 110
subtype 1 records, as appended by OMEGAMON. The data is grouped by
transaction ID.
The default retention periods for these tables are:
7 days for CICS_O_TRAN_FL_ H
Chapter 6. Data tables, lookup tables, and control tables
127
File and Database Transaction subcomponent data tables
30 days for CICS_O_TRAN_FL_ D
565 days for CICS_O_TRAN_FL_ W
Column Name
Key
Data Type
Comment
DATE
k
DATE(4)
Date when the records were initialized. This is normally the
task start date. From SMF110DTE.
PERIOD_NAME
k
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
k
TIME(4)
The hour when the performance records were initialized. It
applies only to the _H table. From SMF110TME.
MVS_SYSTEM_ID
k
CHAR(4)
MVS system ID. This is the SMF system ID. From SMF110SID.
CICS_SYSTEM_ID
k
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMF110PRN.
TRANSACTION_ID
k
CHAR(4)
Transaction name.
FILE_DB_ TYPE
k
CHAR(10)
File or Database TYPE. Please refer to Table 3 on page 126 for
possible values.
FILE_DB_ACTION
k
CHAR(3)
File or Database Action. Please refer to Table 3 on page 126 for
possible values.
CLOCK
FLOAT(8)
Elapsed Time for File or Database Action.
COUNT
FLOAT(8)
Number of file or database actions.
4. File and Database Application User subcomponent data
tables
The data tables described in this section are for the file and database application
user subcomponent, which summarizes basic file and database usage information,
as appended by OMEGAMON XE for CICS to the SMF type 110 record.
The data is summarized by application and user, similar to the data in the tables of
the Basic Application User subcomponent of the CICS Monitoring component.
CICS_O_A_USR_FL_ H,_D,_W
These tables provide file and database usage information from SMF type 110
subtype 1 records, as appended by OMEGAMON. The data is grouped by
application name and user ID.
The default retention periods for these tables are:
7 days for CICS_O_A_USR_FL_ H
30 days for CICS_O_A_USR_FL_ D
565 days for CICS_O_A_USR_FL_ W
Column Name
Key
Data Type
Comment
DATE
k
DATE(4)
Date when the records were initialized. This is normally the
task start date. From SMF110DTE.
PERIOD_NAME
k
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
k
TIME(4)
The hour when the performance records were initialized. It
applies only to the _H table. From SMF110TME.
MVS_SYSTEM_ID
k
CHAR(4)
MVS system ID. This is the SMF system ID. From SMF110SID.
128
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
File and Database Application User subcomponent data tables
Column Name
Key
Data Type
Comment
CICS_SYSTEM_ID
k
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMF110PRN.
APPLICATION_NAME
k
CHAR(18)
Application name. This comes from the CICS_LOOKUP_APPL
lookup table.
USER_ID
k
CHAR(8)
User ID at task creation. This can also be the remote user ID
for a task created as the result of receiving an ATTACH
request across an MRO or APPC link with attach-time security.
From USERID.
FILE_DB_ TYPE
k
CHAR(10)
File or Database TYPE. Please refer to Table 3 on page 126 for
possible values.
FILE_DB_ACTION
k
CHAR(3)
File or Database Action. Please refer to Table 3 on page 126 for
possible values.
CLOCK
FLOAT(8)
Elapsed Time for File or Database Action.
COUNT
FLOAT(8)
Number of file or database actions.
5. File and Database Detailed usage subcomponent data
tables
The data tables described in this section are for the file and database detailed
usage subcomponent, which summarizes file and database usage information, from
the SMF type 112 subtype 203 records, created by OMEGAMON XE for CICS.
These tables contain counts and elapsed times for each type of file or database
command that a transaction issues.
CICS_O_FL_DTL_H, _D, _W
These tables provide detailed file and database usage information from the
OMEGAMON CICS SMF records (type 112, subtype 203). The data is grouped by
transaction ID.
The default retention periods for these tables are:
7 days for CICS_O_FL_DTL_ H
30 days for CICS_ O_FL_DTL _ D
565 days for CICS_ O_FL_DTL _ W
Column Name
Key
Data Type
Comment
DATE
k
DATE(4)
Date when the records were initialized. This is normally the
task start date. From SMF112DTE.
PERIOD_NAME
k
CHAR(8)
Time period. This is the name that you define in the
PERIOD_PLAN table. Use it to group time intervals according
to operator shift or to separate peak and other periods.
TIME
k
TIME(4)
The hour when the performance records were initialized. It
applies only to the _H table. From SMF112TME.
MVS_SYSTEM_ID
k
CHAR(4)
MVS system ID. This is the SMF system ID. From SMF112SID.
CICS_SYSTEM_ID
k
CHAR(8)
CICS generic APPLID. From SMF112GAPL.
TRANSACTION_NAME
k
CHAR(18)
Transaction name. From TRAN.
FILE_DB_ TYPE
k
CHAR(10)
File or Database TYPE. Please refer to Table 4 on page 130 for
possible values.
FILE_DB_ SUBTYPE
k
CHAR(6)
File or Database Subtype. Please refer to Table 4 on page 130
for possible values.
Chapter 6. Data tables, lookup tables, and control tables
129
File and Database Detailed usage subcomponent data tables
Column Name
Key
Data Type
Comment
FILE_DB_ NAME
k
CHAR(48)
File or Database Name. From D_FILE_NAME.
FILE_DB_ACTION
k
CHAR(3)
File or Database Action. This value is derived using the
CICS_OMEG_FIELD lookup table. Please refer to Table 5 on
page 131 for possible values.
CLOCK
FLOAT(8)
Elapsed Time for File or Database Action. Calculated as
SUM(D_CLOCK/625E2).
COUNT
FLOAT(8)
Number of file or database actions. Calculated as
SUM(D_COUNT).
FILE_DB_TYPE and FILE_DB_SUBTYPE combinations: Table 4 lists the possible
combinations of FILE_DB_TYPE and FILE_DB_SUBTYPE, as processed by Tivoli
Decision Support for z/OS:
Table 4. FILE_DB_TYPE and FILE_DB_SUBTYPE combinations
FILE_DB_TYPE
FILE_DB_SUBTYPE
VSAM
N/A
DLI
PSB
DBD
IDMS
RECORD
AREA
SET
NONAME
ADABAS
N/A
SUPRA
N/A
DATACOM
N/A
MQ
N/A
USEREVT
N/A
FILE_DB_TYPE and FILE_DB_ACTION combinations: Table 5 on page 131 lists
the possible combinations of FILE_DB_TYPE and FILE_DB_ACTION, as processed
by Tivoli Decision Support for z/OS:
130
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
File and Database Detailed usage subcomponent data tables
Table 5. FILE_DB_TYPE and FILE_DB_ACTION combinations
FILE_DB_TYPE
FILE_DB_ACTION
Description
DLI
SCH
SCHEDULE THE PCB
TER
TERMINATE THE PCB
GU
GET UNIQUE
GN
GET NEXT
GNP
GET NEXT IN PARENT
GHU
GET HOLD UNIQUE
GHN
GET HOLD NEXT
GHP
GET HOLD NEXT IN PARENT
INS
INSERT
DEL
DELETE
REP
REPLACE
ISN
PROCESS ISN
SEA
SEARCH
RRE
READ RECORD
RFI
READ FIELD
RDE
READ DESCRIPTOR
HOL
HOLD
ADD
ADD
UPD
UPDATE
DEL
DELETE
REL
RELEASE
REA
READ
WRI
WRITE
UPD
UPDATE
DEL
DELETE
BRO
BROWSE
MIS
MISCELLANEOUS
ADD
ADD
DEL
DELETE
FIN
FIND
REA
READ
WRI
WRITE
ADABAS
VSAM
SUPRA
Chapter 6. Data tables, lookup tables, and control tables
131
File and Database Detailed usage subcomponent data tables
Table 5. FILE_DB_TYPE and FILE_DB_ACTION combinations (continued)
FILE_DB_TYPE
FILE_DB_ACTION
Description
DATACOM
ADD
ADD
CNT
COUNT
DEL
DELETE
GN
GET NEXT
GS
GET SET
LSP
LOCATE SPECIFIC
REA
READ
REL
RELEASE
SEL
SELECT
SSE
SELECT SET
UPD
UPDATE
BIN
BIND RECORD
GFO
GET/FIND/OBTAIN
AR
ACCEPT/RETURN
KEE
KEEP
STO
STORE RECORD
MOD
MODIFY
ERP
ERASE PERM
ERS
ERASE SELECT
ERA
ERASE ALL
ERU
ERASE UNQUAL
CON
CONNECT/DISCONNECT
REA
READY AREA
IFS
IF SET
OPN
OPEN
CLO
CLOSE
GET
GET
PUT
PUT
PU1
PU1
INQ
INQUIRE
SET
SET
MIS
MISCELLANEOUS
IDMS
MQ
132
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
File and Database Detailed usage subcomponent data tables
Table 5. FILE_DB_TYPE and FILE_DB_ACTION combinations (continued)
FILE_DB_TYPE
FILE_DB_ACTION
Description
USEREVT
F1
FUNCTION1
F2
FUNCTION2
F3
FUNCTION3
F4
FUNCTION4
F5
FUNCTION5
F6
FUNCTION6
F7
FUNCTION7
F8
FUNCTION8
F9
FUNCTION9
F10
FUNCTION10
Tables in the CICS statistics component
As described in “Evaluating the CICS statistics component” on page 16, the CICS
Performance feature supports statistics only for CICS/ESA and CICS/TS. If you
install the CICS statistics component, Tivoli Decision Support for z/OS loads into
its system tables the data tables described in this section.
CICS_AVAIL_T
This table provides detailed availability data about the CICS subsystem and
CICS-DB2 Connection. The data comes from different CICS records. It is updated
by the lookup table “CICS_AVAIL_RES” on page 294.
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is from the SMFSTSID field in the SMF
record.
CICS_SYSTEM_ID
K
CHAR(8)
The CICS subsystem ID. This is from the SMFSTPRN field in
the SMF record.
RESOURCE_NAME
K
CHAR(18)
Resource Name. This is from the RESOURCE_TARGET_NM
or from RESOURCE_SOURCE_NM into CICS_AVAIL_RES
lookup table.
RESOURCE_TYPE
K
CHAR(8)
Resource Type. Possible values are: CICSSYS (CICS System),
DB2CONN (CICS-DB2 Connection).
Chapter 6. Data tables, lookup tables, and control tables
133
CICS statistics component data tables
Column name
INTERVAL_TYPE
K
Data type
Description
CHAR(3)
Interval type. Possible values are:
v ===
v !==
v ==!
v ===!
v !=!
v XXX
v !XX
v XX!
v !X!
where:
START_TIME
=
Indicates that the resource is up
X
Indicates that the resource is down
!
Indicates an interval start or end
blank
Means that the status is unknown
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 intervals
with a start time within this range appears, the two interval
are merged.
K
CICS_AVAIL_D,_W
These tables provide daily and weekly statistics on the availability of CICS
subsystem CICS-DB2 Connection. They contain consolidated data from the
CICS_AVAIL_T table.
The default retention periods for these tables are:
CICS_AVAIL_D
45 days
CICS_AVAIL_W
365 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.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is from the MVS_SYSTEM_ID collect
parameter.
CICS_SYSTEM_ID
K
CHAR(8)
The CICS subsystem ID.
RESOURCE_NAME
K
CHAR(18)
Resource Name.
RESOURCE_TYPE
K
CHAR(8)
Resource Type. Possible values are: CICSSYS (CICS System),
DB2CONN (CICS-DB2 Connection).
MEASURED_ HOURS
FLOAT
Number of hours measured.
AVAIL_OBJ_PCT
DECIMAL(4, 1)
Availability objective for the resource, in percent. This is
from the column AVAIL_OBJ_PCT in the CICS_AVAIL_RES
lookup table. This value should be compared with the actual
availability, which is calculated as: 100*UP_IN_SCHEDULE/
SCHEDULE_HOURS.
134
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
SCHEDULE_HOURS
FLOAT
Number of hours the resource is scheduled to be up.
STARTS
SMALLINT
Number of times the resource was started.
STOPS
SMALLINT
Number of times the resource was stopped.
STARTS_IN_SCHEDULE
SMALLINT
Number of times the resource was started within the
schedule.
STOPS_IN_SCHEDULE
SMALLINT
Number of times the resource was stopped within the
schedule.
UP_HOURS
FLOAT
Number of hours the resource was up.
UP_IN_SCHEDULE
FLOAT
Number of hours the resource was up within the schedule.
CICS_MVSTCB_D
This table provides hourly MVS TCB Global statistics from CICS TS (SMF 110,
subtype 2). This maps the CICS DFHDSTDS macro.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
DST_CT_CICSTCB
INTEGER
Current number of CICS TCBs. From DSTDS_CTCB_COUNT.
DST_CPU_CICSTCB
FLOAT
So far for currently attach. From DSTDS_CTCB_CPU.
DST_PRIV_BEL16M
FLOAT
Private stg below 16M. From DSTDS_CTCB_SB.
DST_PRIV_OVA16M
FLOAT
Private stg above 16M. From DSTDS_CTCB_SA.
DST_CT_NONCICSTCB
INTEGER
Curr number of non-CICS TCB. From DSTDS_NCTCB_COUNT.
DST_CPU_NONCICSTCB
INTEGER
So far for currently attach. From DSTDS_NCTCB_CPU.
DST_NCTCB_BEL16M
FLOAT
Private stg below 16M. From DSTDS_NCTCB_SB.
DST_NCTCB_OVA16M
FLOAT
Private stg above 16M. From DSTDS_NCTCB_SA.
DST_CTCB_BEL_USE
FLOAT
<16M in use. From DSTDS_CTCB_SB_IN.
DST_CTCB_OVA_USE
FLOAT
>16M in use. From DSTDS_CTCB_SA_IN.
DST_NCTCB_BEL_USE
FLOAT
<16M in use. From DSTDS_NCTCB_SB_IN.
DST_NCTCB_OVA_USE
FLOAT
>16M in use. From DSTDS_NCTCB_SA_IN.
CICS_MVSTCB_H
This table provides hourly MVS TCB Global statistics from CICS TS (SMF 110,
subtype 2). This maps the CICS DFHDSTDS macro.
The default retention period for this table is 7 days.
Chapter 6. Data tables, lookup tables, and control tables
135
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
DST_CT_CICSTCB
INTEGER
Current number of CICS TCBs. From DSTDS_CTCB_COUNT.
DST_CPU_CICSTCB
FLOAT
So far for currently attach. From DSTDS_CTCB_CPU.
DST_PRIV_BEL16M
FLOAT
Private stg below 16M. From DSTDS_CTCB_SB.
DST_PRIV_OVA16M
FLOAT
Private stg above 16M. From DSTDS_CTCB_SA.
DST_CT_NONCICSTCB
INTEGER
Curr number of non-CICS TCB. From DSTDS_NCTCB_COUNT.
DST_CPU_NONCICSTCB
INTEGER
So far for currently attach. From DSTDS_NCTCB_CPU.
DST_NCTCB_BEL16M
FLOAT
Private stg below 16M. From DSTDS_NCTCB_SB.
DST_NCTCB_OVA16M
FLOAT
Private stg above 16M. From DSTDS_NCTCB_SA.
DST_CTCB_BEL_USE
FLOAT
<16M in use. From DSTDS_CTCB_SB_IN.
DST_CTCB_OVA_USE
FLOAT
>16M in use. From DSTDS_CTCB_SA_IN.
DST_NCTCB_BEL_USE
FLOAT
<16M in use. From DSTDS_NCTCB_SB_IN.
DST_NCTCB_OVA_USE
FLOAT
>16M in use. From DSTDS_NCTCB_SA_IN.
CICS_MVSTCB_RES_D
This table provides daily MVS TCB Resource statistics from CICS TS (SMF 110,
subtype 2). This maps the CICS DFHDSRDS macro.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
DSR_TCB_NAME
K
CHAR(8)
Initial prog or QR, RO etc. From DSRDS_TCB_NAME.
DSR_TCB_ADDRESS
CHAR(8)
Address of MVS TCB. From DSRDS_TCB_ADDR.
DSR_TCB_TYPE
CHAR(1)
“C” for CICS,“N” for non CICS. From DSRDS_TCB_TYPE
DSR_TCB_CICS_TASK
INTEGER
CICS task number or 0. From DSRDS_TCB_CICS_TSK.
DSR_TCB_MOTHER
CHAR(8)
Address of mother TCB. From DSRDS_TCB_MOTHER.
136
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DSR_TCB_SISTER
CHAR(8)
Address of sister TCB. From DSRDS_TCB_SISTER.
DSR_TCB_DAUGHTER
CHAR(8)
Address of daughter TCB. From DSRDS_TCB_DAUGHTER.
DSR_TCB_CPU
FLOAT
Total CPU time so far. From DSRDS_TCB_CPU.
DSR_TCB_STOR_B16M
FLOAT
Private storage below 16M. From DSRDS_TCB_SB.
DSR_TCB_STOR_A16M
FLOAT
Private storage above 16M. From DSRDS_TCB_SA.
DSR_TCB_INST_B16M
FLOAT
Below 16M in use. From DSRDS_TCB_SB_IN.
DSR_TCB_INST_A16M
FLOAT
Above 16M in use. From DSRDS_TCB_SA_IN.
CICS_MVSTCB_RES_H
This table provides hourly MVS TCB Resource statistics from CICS TS (SMF 110,
subtype 2). This maps the CICS DFHDSRDS macro.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
DSR_TCB_NAME
K
CHAR(8)
Initial prog or QR, RO etc. From DSRDS_TCB_NAME.
DSR_TCB_ADDRESS
CHAR(8)
Address of MVS TCB. From DSRDS_TCB_ADDR.
DSR_TCB_TYPE
CHAR(1)
“C”for CICS,“N” for non CICS. From DSRDS_TCB_TYPE
DSR_TCB_CICS_TASK
INTEGER
CICS task number or 0. From DSRDS_TCB_CICS_TSK.
DSR_TCB_MOTHER
CHAR(8)
Address of mother TCB. From DSRDS_TCB_MOTHER.
DSR_TCB_SISTER
CHAR(8)
Address of sister TCB. From DSRDS_TCB_SISTER.
DSR_TCB_DAUGHTER
CHAR(8)
Address of daughter TCB. From DSRDS_TCB_DAUGHTER.
DSR_TCB_CPU
FLOAT
Total CPU time so far. From DSRDS_TCB_CPU.
DSR_TCB_STOR_B16M
FLOAT
Private storage below 16M. From DSRDS_TCB_SB.
DSR_TCB_STOR_A16M
FLOAT
Private storage above 16M. From DSRDS_TCB_SA.
DSR_TCB_INST_B16M
FLOAT
Below 16M in use. From DSRDS_TCB_SB_IN.
DSR_TCB_INST_A16M
FLOAT
Above 16M in use. From DSRDS_TCB_SA_IN.
CICS_PIPELINE_T
This table It provides detailed statistics for PIPELINE. It contains data from CICS
statistics records (SMF 110,subtype 2, stid 105). For CICS/TS V3.1 and later, it takes
information from the DFHPIRDS CICS dsect.
The default retention period for this table is 7 days.
Chapter 6. Data tables, lookup tables, and control tables
137
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PIPELINE_NAME
K
CHAR(8)
The name of the pipeline resource definition. From PIRPIPNM.
CONFIG_FILE
VARCHAR
The name of the HFS file (254) that provides information about
the message handlers and their configuration. From PIRCONF.
SHELF_DIRECTORY
VARCHAR
The fully qualified name of (254) the shelf directory for the
pipeline definition. From PIRSHDIR
WSDIR_PICKUP_DIR
VARCHAR
The fully qualified name of (254) the Web service binding
directory (also known as the pickup directory). From
PIRWSDIR
PIPELINE_USE_COUNT
FLOAT
The number of times this pipeline resource defs was used to
install a Web service or to process a Web service request. From
PIRUSECNT
PIPELINE_MODE
CHAR(10)
Pipeline Mode.
CICS_DOCT_RES_D
This is a new table. It provides daily DocTemplate resource statistics from CICS TS
3.2 (SMF 110, subtype 2). This maps the CICS DFHDHDDS macro.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
DT_DOCTEMPL_NAME
K
CHAR(8)
Doctemplate name. From DHD_DOCT_NAME.
DT_TEMPLATE_TYPE
CHAR(10)
Doctemplate type. From DHD_TEMPLATE_TYPE.
DT_APPEND_CRLF
CHAR(1)
Doctemplate append crlf. From DHD_APPEND_CRLF.
DT_TEMPLATE_CONT
CHAR(6)
Doctemplate contents. From DHD_TEMPLATE_CONT.
DT_TEMPLATE_NAME
CHAR(48)
Doctemplate template name. From DHD_TEMPLATE_NAME.
DT_TEMPL_EPROG
CHAR(8)
Template exit program name. From DHD_TEMPL_EPROG.
DT_TEMPL_FILENME
CHAR(8)
Template file name. From DHD_TEMPL_FILENME.
138
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DT_TEMPL_PROGNME
CHAR(8)
Template program name. From DHD_TEMPL_PROGNME.
DT_TEMPL_PDSMEM
CHAR(8)
Template PDS member. From DHD_TEMPL_PDSMEM.
DT_TEMPL_PDSDDNME
CHAR(8)
Template PDS ddname. From DHD_TEMPL_PDSDDNME.
DT_TEMPL_PDSDSNME
CHAR(44)
Template PDS dsname. From DHD_TEMPL_PDSDSNME.
DT_TEMPL_TDQNAME
CHAR(4)
Template tdqueue name. From DHD_TEMPL_TDQNAME.
DT_TEMPL_TSQNAME
CHAR(16)
Template tsqueue name. From DHD_TEMPL_TSQNAME.
DT_TEMPL_HFSFILE
CHAR(254)
Template hfsfile name. From DHD_TEMPL_HFSFILE.
DT_TEMPL_CACHE_SZ
INTEGER
Template cache size. From DHD_TEMPL_CACHE_SZ.
DT_TEMPL_USE_CT
INTEGER
Template use count. From DHD_TEMPL_USE_CT.
DT_TEMPL_NEWCOPY
INTEGER
Template newcopy count. From DHD_TEMPL_NEWCOPY.
DT_TEMPL_READ_CT
INTEGER
Template read count. From DHD_TEMPL_READ_CT.
DT_TEMPL_CACHEUSE
INTEGER
Template cache copy used. From DHD_TEMPL_CACHEUSE.
DT_TEMPL_CACHEDEL
INTEGER
Template cache deleted. From DHD_TEMPL_CACHEDEL.
CICS_DOCT_RES_H
This table provides hourly DocTemplate resource statistics from CICS TS 3.2 (SMF
110, subtype 2). This maps the CICS DFHDHDDS macro.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
DT_DOCTEMPL_NAME
K
CHAR(8)
Doctemplate name. From DHD_DOCT_NAME.
DT_TEMPLATE_TYPE
CHAR(10)
Doctemplate type. From DHD_TEMPLATE_TYPE.
DT_APPEND_CRLF
CHAR(1)
Doctemplate append crlf. From DHD_APPEND_CRLF.
DT_TEMPLATE_CONT
CHAR(6)
Doctemplate contents. From DHD_TEMPLATE_CONT.
DT_TEMPLATE_NAME
CHAR(48)
Doctemplate template name. From DHD_TEMPLATE_NAME.
DT_TEMPL_EPROG
CHAR(8)
Template exit program name. From DHD_TEMPL_EPROG.
DT_TEMPL_FILENME
CHAR(8)
Template file name. From DHD_TEMPL_FILENME.
DT_TEMPL_PROGNME
CHAR(8)
Template program name. From DHD_TEMPL_PROGNME.
DT_TEMPL_PDSMEM
CHAR(8)
Template PDS member. From DHD_TEMPL_PDSMEM.
DT_TEMPL_PDSDDNME
CHAR(8)
Template PDS ddname. From DHD_TEMPL_PDSDDNME.
DT_TEMPL_PDSDSNME
CHAR(44)
Template PDS dsname. From DHD_TEMPL_PDSDSNME.
DT_TEMPL_TDQNAME
CHAR(4)
Template tdqueue name. From DHD_TEMPL_TDQNAME.
Chapter 6. Data tables, lookup tables, and control tables
139
CICS statistics component data tables
Column name
Data type
Description
DT_TEMPL_TSQNAME
CHAR(16)
Template tsqueue name. From DHD_TEMPL_TSQNAME.
DT_TEMPL_HFSFILE
CHAR(254)
Template hfsfile name. From DHD_TEMPL_HFSFILE.
DT_TEMPL_CACHE_SZ
INTEGER
Template cache size. From DHD_TEMPL_CACHE_SZ.
DT_TEMPL_USE_CT
INTEGER
Template use count. From DHD_TEMPL_USE_CT.
DT_TEMPL_NEWCOPY
INTEGER
Template newcopy count. From DHD_TEMPL_NEWCOPY.
DT_TEMPL_READ_CT
INTEGER
Template read count. From DHD_TEMPL_READ_CT.
DT_TEMPL_CACHEUSE
INTEGER
Template cache copy used. From DHD_TEMPL_CACHEUSE.
DT_TEMPL_CACHEDEL
INTEGER
Template cache deleted. From DHD_TEMPL_CACHEDEL.
CICS_S_AUTO_TERM_T
This table provides detailed statistics data on CICS systems. It contains data from
CICS autoinstalled terminal records from CICS statistics records (SMF 110,
subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
AUTOINSTALL_ATT
INTEGER
Number of eligible autoinstall attempts made. From
A04VADAT.
DELETIONS
INTEGER
Number of deletions of terminal entries. From A04VADLO.
IDLE_CUR_CNT
INTEGER
Current idle count. CICS V4 and later. From A04CIDCT.
IDLE_CUR_TIME
TIME
Time (hh:mm:ss) that all current remote terminal definitions
have been idle awaiting reuse. CICS V4 and later. From
A04CIDLE.
IDLE_CUR_TIME_MAX
TIME
Maximum time (hh:mm:ss) that a currently idle shipped
terminal definition has been idle during the recording period.
CICS V4 and later. From A04CMAXI.
IDLE_MAX_TIME
TIME
Maximum time (hh:mm:ss) that a previously idle shipped
terminal definition had been idle during the recording period.
CICS V4 and later. From A04TMAXI.
IDLE_TOTAL_CNT
INTEGER
Total number of times that all previously used remote
terminal definitions had been idle awaiting reuse. Does not
include remote terminal definitions currently idle awaiting
reuse. CICS V4 and later. From A04TIDCT.
140
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
IDLE_TOTAL_TIME
TIME
Total time (hh:mm:ss) that all previously used remote terminal
definitions had been idle awaiting reuse. Does not include
remote terminal definitions currently idle awaiting reuse. CICS
V4 and later. From A04TIDLE.
INTERVAL_EXP_CNT
INTEGER
Number of times the remote delete interval
(REM_DEL_DELAY) expired since the start of the recording
period. CICS V4 and later. From A04TIEXP.
QUEUED_LOGONS
INTEGER
Number of attempts that waited for deletion. From
A04VADQT.
QUEUED_LOGONS_PEAK
INTEGER
Highest number of logons that waited for deletion. From
A04VADQK.
QUEUED_PEAK_COUNT
INTEGER
Number of times the peak number of waiting logons was
reached. From A04VADQX.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REJECTED_ATTEMPTS
INTEGER
Number of eligible autoinstall attempts rejected. From
A04VADRJ.
REM_DEL_DELAY
TIME
Time delay (hh:mm:ss) between invocations of the timeout
delete transaction that removes redundant shipped terminal
definitions. Set by the DSHIPINT SIT-parameter, or by a
subsequent SET DELETSHIPPED command. CICS V4 and
later. From A04RDINT.
REM_DEL_DELETES
INTEGER
Number of shipped terminal definitions deleted from this
region because of pre-CICS/ESA 4.1 remote delete
instructions, since the start of the recording period. CICS V4
and later. From A04RDDEL.
REM_DEL_IDLE
TIME
Minimum time (hh:mm:ss) that an inactive shipped terminal
definition must remain installed in this region, before it
becomes eligible for removal by the CICS timeout delete
transaction. CICS V4 and later. From A04RDIDL.
REM_DEL_ISSUED
INTEGER
Number of pre-CICS/ESA 4.1 remote delete instructions
issued by this region since the start of the recording period.
CICS V4 and later. From A04RDISS.
REM_DEL_REC_CNT
INTEGER
Number of pre-CICS/ESA 4.1 remote delete instructions
received by this region since the start of the recording period.
CICS V4 and later. From A04RDREC.
REM_TERM_BUILDS
INTEGER
Number of shipped remote terminal definitions installed at
the start of the recording period, plus the number built during
the recording period. CICS V4 and later. From A04SKBLT.
REM_TERM_DELETES
INTEGER
Number of shipped remote terminal definitions deleted
during the recording period by the TIMEOUT transaction.
CICS V4 and later. From A04SKDEL.
REM_TERM_INSTALLS
INTEGER
Number of shipped remote terminal definitions currently
installed in this region. CICS V4 and later. From A04SKINS.
SETLOGON_HOLD
INTEGER
Number of times the SETLOGON HOLD command was
issued. From A04VADSH.
Chapter 6. Data tables, lookup tables, and control tables
141
CICS statistics component data tables
Column name
Data type
Description
TERM_CREATE_PEAK
INTEGER
Peak number of attempts to create terminal entries. From
A04VADPK.
TERM_PEAK_COUNT
INTEGER
Number of peak attempts reached. From A04VADPX.
CICS_S_AUTO_TERM_D
This table provides daily statistics on CICS autoinstalled terminals. It contains
consolidated data from the CICS_S_AUTO_TERM_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
AUTOINSTALL_ATT
INTEGER
Number of eligible autoinstall attempts made. From
A04VADAT.
DELETIONS
INTEGER
Number of deletions of terminal entries. From A04VADLO.
IDLE_MAX_TIME
TIME
Maximum time (hh:mm:ss) that a previously idle shipped
terminal definition had been idle during the recording period.
CICS V4 and later. From A04TMAXI.
IDLE_TOTAL_CNT
INTEGER
Total number of times that all previously used remote
terminal definitions had been idle awaiting reuse. Does not
include remote terminal definitions currently idle awaiting
reuse. CICS V4 and later. From A04TIDCT.
INTERVAL_EXP_CNT
INTEGER
Number of times the remote delete interval
(REM_DEL_DELAY) expired since the start of the recording
period. CICS V4 and later. From A04TIEXP.
QUEUED_LOGONS
INTEGER
Number of attempts that waited for deletion. From
A04VADQT.
QUEUED_LOGONS_PEAK
INTEGER
Highest number of logons that waited for deletion. From
A04VADQK.
QUEUED_PEAK_COUNT
INTEGER
Number of times the peak number of waiting logons was
reached. From A04VADQX.
REJECTED_ATTEMPTS
INTEGER
Number of eligible autoinstall attempts rejected. From
A04VADRJ.
REM_DEL_DELETES
INTEGER
Number of shipped terminal definitions deleted from this
region because of pre-CICS/ESA 4.1 remote delete
instructions, since the start of the recording period. CICS V4
and later. From A04RDDEL.
REM_DEL_ISSUED
INTEGER
Number of pre-CICS/ESA 4.1 remote delete instructions
issued by this region since the start of the recording period.
CICS V4 and later. From A04RDISS.
142
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
REM_DEL_REC_CNT
INTEGER
Number of pre-CICS/ESA 4.1 remote delete instructions
received by this region since the start of the recording period.
CICS V4 and later. From A04RDREC.
REM_TERM_BUILDS
INTEGER
Number of shipped remote terminal definitions installed at
the start of the recording period, plus the number built during
the recording period. CICS V4 and later. From A04SKBLT.
REM_TERM_DELETES
INTEGER
Number of shipped remote terminal definitions deleted
during the recording period by the TIMEOUT transaction.
CICS V4 and later. From A04SKDEL.
SETLOGON_HOLD
INTEGER
Number of times the SETLOGON HOLD command was
issued. From A04VADSH.
TERM_CREATE_PEAK
INTEGER
Peak number of attempts to create terminal entries. From
A04VADPK.
TERM_PEAK_COUNT
INTEGER
Number of peak attempts reached. From A04VADPX.
CICS_S_CFDT_GREQ_T
This table provides detailed Coupling Facility table server requests statistics. Total
table control request statistics for all tables are supplied. For CICS/TS V1.3 and
later, this maps the DFHCFS8K record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
CF_GBACKOUT_UOW
FLOAT
Number of units of work backed out. From S8SPBACK.
CF_GCOMMIT_UOW
FLOAT
Number of units of work committed. From S8SPCOMM.
CF_GCLOSE_TAB
FLOAT
Number of successful CLOSE requests for the table. From
S8OCCLOS.
CF_GDEL_MULT
FLOAT
Number of multiple (generic) delete requests. From
S8RQDELM.
CF_GDELETE
FLOAT
Number of DELETE requests. From S8RQDELE.
CF_GDELETE_TAB
FLOAT
Number of times a table was deleted. From S8OCDELE.
CF_GEXTR_STATS
FLOAT
Number of extract table statistics. From S8OCSTAT.
CF_GINQUIRE
FLOAT
Number of INQUIRE table requests. From S8IQINQU.
CF_GINQUIRE_UOW
FLOAT
Number of units of work INQUIRE requests. From
S8SPINQU.
Chapter 6. Data tables, lookup tables, and control tables
143
CICS statistics component data tables
Column name
Data type
Description
CF_GLOAD
FLOAT
Number of records written by initial load requests. From
S8RQLOAD.
CF_GOPEN_TAB
FLOAT
Number of successful OPEN requests for the table. From
S8SOCOPEN.
CF_GPOINT
FLOAT
Number of POINT requests. From S8RQPOIN.
CF_GPREPARE
FLOAT
Number of units of work prepared. From S8SPPREP.
CF_GREAD
FLOAT
Number of READ requests (including those for update).
From S8RQREAD.
CF_GREAD_DEL
FLOAT
Number of combined READ and DELETE requests. From
S8RQRDDL.
CF_GRESTART_UOW
FLOAT
Number of times that the connections were restarted. From
S8SPREST.
CF_GRETLOCK_UOW
FLOAT
Number of units of work whose locks are retained. From
S8PRETA.
CF_GRETURN_HIGH
FLOAT
Number of requests for current highest key. From
S8RQHIGH.
CF_GREWRITES
FLOAT
Number of REWRITE requests. From S8RQREWR.
CF_GSET_ATTR
FLOAT
Number of times new table status was set. From S8OCSET.
CF_GUNLOCK
FLOAT
Number of UNLOCK requests. From S8RQUNLK.
CF_GWRITES
FLOAT
Number of WRITE requests for new records. From
S8RQWRIT.
CICS_S_CFDT_GREQ_D
This table provides daily Coupling Facility table server requests statistics. Total
table control request statistics for all tables are supplied. For CICS/TS V1.3 and
later, this maps the DFHCFS8K record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
CF_GBACKOUT_UOW
FLOAT
Number of units of work backed out. From S8SPBACK.
CF_GCOMMIT_UOW
FLOAT
Number of units of work committed. From S8SPCOMM.
CF_GCLOSE_TAB
FLOAT
Number of successful CLOSE requests for the table. From
S8OCCLOS.
CF_GDEL_MULT
FLOAT
Number of multiple (generic) delete requests. From
S8RQDELM.
CF_GDELETE
FLOAT
Number of DELETE requests. From S8RQDELE.
144
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CF_GDELETE_TAB
FLOAT
Number of times a table was deleted. From S8OCDELE.
CF_GEXTR_STATS
FLOAT
Number of extract table statistics. From S8OCSTAT.
CF_GINQUIRE
FLOAT
Number of INQUIRE table requests. From S8IQINQU.
CF_GINQUIRE_UOW
FLOAT
Number of INQUIRE table requests. From S8SPINQU.
CF_GLOAD
FLOAT
Number of records written by initial load requests. From
S8RQLOAD.
CF_GOPEN_TAB
FLOAT
Number of successful OPEN requests for the table. From
S8SOCOPEN.
CF_GPOINT
FLOAT
Number of POINT requests. From S8RQPOIN.
CF_GPREPARE
FLOAT
Number of units of work prepared. From S8SPPREP.
CF_GREAD
FLOAT
Number of READ requests (including those for update).
From S8RQREAD.
CF_GREAD_DEL
FLOAT
Number of combined READ and DELETE requests. From
S8RQRDDL.
CF_GRESTART_UOW
FLOAT
Number of times that the connections were restarted. From
S8SPREST.
CF_GRETLOCK_UOW
FLOAT
Number of units of work whose locks are retained. From
S8PRETA.
CF_GRETURN_HIGH
FLOAT
Number of requests for current highest key. From
S8RQHIGH.
CF_GREWRITES
FLOAT
Number of REWRITE requests. From S8RQREWR.
CF_GSET_ATTR
FLOAT
Number of times new table status was set. From S8OCSET.
CF_GUNLOCK
FLOAT
Number of UNLOCK requests. From S8RQUNLK.
CF_GWRITES
FLOAT
Number of WRITE requests for new records. From
S8RQWRIT.
CICS_S_CFDT_SERV_T
This table provides detailed Coupling Facility data tables list structure. For
CICS/TS V1.3 and later, this maps the DFHCFS6K record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
CF_LISTSTRUC_NAME
K
CHAR(16)
Full name of the list structure. From S6NAME.
Chapter 6. Data tables, lookup tables, and control tables
145
CICS statistics component data tables
Column name
Data type
Description
CHAR(16)
Name of the connection to the list structure. From
S6CNNAME.
CF_ALLOC_SIZE
FLOAT
Current allocated size of the list structure. From S6SIZE.
CF_ALLOC_SIZE_MAX
FLOAT
Maximum size to which the structure could be altered.
From S6SIZEMX.
CF_ASYNC_REQS
FLOAT
Number of requests completion was asynchronous. From
S6ASYCT.
CF_AUTH_MISMATCH
FLOAT
Number of times a list authority comparison failed,
mismatch caused by table status update. From S6RSP5CT.
CF_BUFF_SHORT
FLOAT
Number of times that entry data was larger than the input
buffer length, which normally results in a retry with a
larger buffer. From S6RSP2CT.
CF_CNTLIST_HEAD
FLOAT
Maximum number of list headers in the structure could be
altered. From S6HDRSCT.
CF_CREATE_LIST
FLOAT
Number of times a new data list was created. From
S6CRLCT.
CF_DATAEL_MAX
FLOAT
Maximum element size per entry (for 32 KB). From
S6ELEMLN.
CF_DATAEL_SIZE
FLOAT
Data element size as fullword. From S6ELEMLN.
CF_DEL_APPL_ENTR
FLOAT
Number of delete APPLID entries. From S6DLACT.
CF_DEL_UOW_ENTRY
FLOAT
Number of unit of work list deletes. From S6DLUCT.
CF_DELETE_DATAIT
FLOAT
Number of data entry deletes. From S6DLDCT.
CF_DELETE_LIST
FLOAT
Number of times a data list was deleted for reuse. From
S6DLLCT.
CF_DELTBIX_ENTRY
FLOAT
Number of table index deletes. From S6DLICT.
CF_ELEMFREE_MIN
FLOAT
Lowest number of free elements. From S6ELEMLO.
CF_ELEMRET_MAX
FLOAT
Maximum elements returned by IXLCONN. From
S6ELEMMX.
CF_ELEMUSE_MAX
FLOAT
Highest number of elements in use. From S6ELEMHI.
CF_ELSIDE_ENTRY
FLOAT
Element side of entry element ratio. From S6ELEMPE.
CF_ENT_APPLID_MAX
FLOAT
Highest entries on APPLID list. From S6APPLHI.
CF_ENT_FRELST_MAX
FLOAT
Highest entries on the free list. From S6FREEHI.
CF_ENT_TABIND_MAX
FLOAT
Highest entries on the free list. From S6INDXHI.
CF_ENT_UOWLST_MAX
FLOAT
Highest entries in unit of work list. From S6UOWLST.
CF_ENT_USELST_MAX
FLOAT
Highest entries on used list. From S6USEDHI.
CF_ENTRSIDE_ENTRY
FLOAT
Entry side of entry element ratio. From S6ELEMPE.
CF_ENTRYFREE_MIN
FLOAT
Lowest number of entries in use. From S6ENTRLO.
CF_ENTRYRET_MAX
FLOAT
Maximum entries returned by IXLCONN. From
S6ENTRMX.
CF_ENTRYUSE_MAX
FLOAT
Highest number of entries in use. From S6ENTRHI.
CF_INQR_DATALST
FLOAT
Number of inquiries on data list. From S6INLCT.
CF_LIST_HEAD_MAX
FLOAT
Headers used for Control List. From S6HDRS.
CF_LIST_OUTSPACE
FLOAT
Number of times the list structure became full. From
S6RSP7CT.
CF_CONNECT_NAME
146
K
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CF_MAXLIST_REACH
FLOAT
Number of times a table reached the maximum number of
items causing the relevant list to be marked as full. From
S6RSP6CT.
CF_MODIFY_LIST
FLOAT
Number of times that data list controls were modified.
From S6MDLCT.
CF_NOMATCH_FOUND
FLOAT
Number of entries not found (table or item). From
S6RSP3CT.
CF_NOMATCH_VERS
FLOAT
Number of times a version check failed for an entry being
updated, indicating that another task had updated it first.
From S6RSP4CT.
CF_NORMAL_RESP
FLOAT
Number of normal responses. From S6RSP1CT.
CF_OTHER_ERROR
FLOAT
Number of times some other error codes were returned by
IXLLIST.
CF_READ_APPL_ENTR
FLOAT
Number of read APPLID entries. From S6RDACT.
CF_READ_DATAIT
FLOAT
Number of data entry reads. From S6RDDCT.
CF_READ_MSGQUEUE
FLOAT
Number of lock release messages read by this server. From
S6RDMCT.
CF_READ_UOW_ENTRY
FLOAT
Number of unit of work list reads. From S6WRDUCT.
CF_READTBIX_ENTRY
FLOAT
Number of table index reads. From S6RDICT.
CF_REREAD_FULL
FLOAT
Number of reread entries for full data length. From
S6RRLCT.
CF_REWRT_APPL_ENTR
FLOAT
Number of rewrite APPLID entries. From S6RWACT.
CF_REWRT_DATAIT
FLOAT
Number of data entry rewrites. From S6RWDCT.
CF_REWRT_UOW_ENTRY
FLOAT
Number of unit of work list rewrites. From S6RWUCT.
CF_REWRTTBIX_ENTRY
FLOAT
Number of table index writes to update table status. From
S6RWICT.
CF_SMR_STR_UNAVAIL
FLOAT
Structure temporarily unavailable, during system-managed
rebuild. From S6RSP9CT
CF_TBLDATA_HEAD
FLOAT
Headers available for table data. From S6HDRSCD.
CF_WRITE_APPL_ENTR
FLOAT
Number of write APPLID entries. From S6WRACT.
CF_WRITE_DATAIT
FLOAT
Number of data entry writes. From S6WRDCT.
CF_WRITE_UOW_ENTRY
FLOAT
Number of unit of work list writes. From S6WRUCT.
CF_WRITE_MSGQUEUE
FLOAT
Number of lock release messages sent by this server. From
S6RDMCT.
CF_WRITETBIX_ENTRY
FLOAT
Number of table index writes to create new tables. From
S6WRICT.
CICS_S_CFDT_SERV_D
This table provides daily Coupling Facility data tables list structure. For CICS/TS
V1.3 and later, this maps the DFHCFS6K record.
The default retention period for this table is 30 days.
Column name
DATE
K
Data type
Description
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
Chapter 6. Data tables, lookup tables, and control tables
147
CICS statistics component data tables
Column name
Data type
Description
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
CF_LISTSTRUC_NAME
K
CHAR(16)
Full name of the list structure. From S6NAME.
CF_CONNECT_NAME
K
CHAR(16)
Name of the connection to the list structure. From
S6CNNAME.
CF_ALLOC_SIZE
FLOAT
Current allocated size of the list structure. From S6SIZE.
CF_ALLOC_SIZE_MAX
FLOAT
Maximum size to which the structure could be altered.
From S6SIZEMX.
CF_ASYNC_REQS
FLOAT
Number of requests for which completion was
asynchronous. From S6ASYCT.
CF_AUTH_MISMATCH
FLOAT
Number of times a list authority comparison failed,
mismatch caused by table status update. From S6RSP5CT.
CF_BUFF_SHORT
FLOAT
Number of times that entry data was larger than the input
buffer length, which normally results in a retry with a
larger buffer. From S6RSP2CT.
CF_CNTLIST_HEAD
FLOAT
Maximum number of list headers in the structure could be
altered. From S6HDRSCT.
CF_CREATE_LIST
FLOAT
Number of times a new data list was created. From
S6CRLCT.
CF_DATAEL_MAX
FLOAT
Maximum elements per entry (for 32 KB). From
S6ELEMLN.
CF_DATAEL_SIZE
FLOAT
Data element size as fullword. From S6ELEMLN.
CF_DEL_APPL_ENTR
FLOAT
Number of delete APPLID entries. From S6DLACT.
CF_DEL_UOW_ENTRY
FLOAT
Number of unit of work list deletes. From S6DLUCT.
CF_DELETE_DATAIT
FLOAT
Number of data entries deletes. From S6DLDCT.
CF_DELETE_LIST
FLOAT
Number of times a data list was deleted for reuse. From
S6DLLCT.
CF_DELTBIX_ENTRY
FLOAT
Number of table index deletes. From S6DLICT.
CF_ELEMFREE_MIN
FLOAT
Lowest number of free elements. From S6ELEMLO.
CF_ELEMRET_MAX
FLOAT
Maximum elements returned by IXLCONN. From
S6ELEMMX.
CF_ELEMUSE_MAX
FLOAT
Highest number of elements in use. From S6ELEMHI.
CF_ELSIDE_ENTRY
FLOAT
Element side of entry element ratio. From S6ELEMPE.
CF_ENT_APPLID_MAX
FLOAT
Highest entries on APPLID list. From S6APPLHI.
CF_ENT_FRELST_MAX
FLOAT
Highest entries on free list. From S6FREEHI.
CF_ENT_TABIND_MAX
FLOAT
Highest entries on free list. From S6INDXHI.
CF_ENT_UOWLST_MAX
FLOAT
Highest entries in unit of work list. From S6UOWLST.
CF_ENT_USELST_MAX
FLOAT
Highest entries on used list. From S6USEDHI.
CF_ENTRSIDE_ENTRY
FLOAT
Entry side of entry element ratio. From S6ELEMPE.
CF_ENTRYFREE_MIN
FLOAT
Lowest number of entries in use. From S6ENTRLO.
148
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CF_ENTRYRET_MAX
FLOAT
Maximum entries returned by IXLCONN. From
S6ENTRMX.
CF_ENTRYUSE_MAX
FLOAT
Highest number of entries in use. From S6ENTRHI.
CF_INQR_DATALST
FLOAT
Number of inquiries on data list. From S6INLCT.
CF_LIST_HEAD_MAX
FLOAT
Headers used for Control List. From S6HDRS.
CF_LIST_OUTSPACE
FLOAT
Number of times the list structure became full. From
S6RSP7CT.
CF_MAXLIST_REACH
FLOAT
Number of times a table reached the maximum number of
items causing the relevant list to be marked as full. From
S6RSP6CT.
CF_MODIFY_LIST
FLOAT
Number of times that data list controls were modified.
From S6MDLCT.
CF_NOMATCH_FOUND
FLOAT
Number of entries not found (table or item). From
S6RSP3CT.
CF_NOMATCH_VERS
FLOAT
Number of times a version check failed for an entry being
updated, indicating that another task had updated it first.
From S6RSP4CT.
CF_NORMAL_RESP
FLOAT
Number of normal responses. From S6RSP1CT.
CF_OTHER_ERROR
FLOAT
Number of times some other error codes were returned by
IXLLIST.
CF_READ_APPL_ENTR
FLOAT
Number of read APPLID entries. From S6RDACT.
CF_READ_DATAIT
FLOAT
Number of data entry reads. From S6RDDCT.
CF_READ_MSGQUEUE
FLOAT
Number of lock release messages read by this server. From
S6RDMCT.
CF_READ_UOW_ENTRY
FLOAT
Number of unit of work list reads. From S6WRDUCT.
CF_READTBIX_ENTRY
FLOAT
Number of table index reads. From S6RDICT.
CF_REREAD_FULL
FLOAT
Number of reread entries for full data length. From
S6RRLCT.
CF_REWRT_APPL_ENTR
FLOAT
Number of rewrite APPLID entries. From S6RWACT.
CF_REWRT_DATAIT
FLOAT
Number of data entry rewrites. From S6RWDCT.
CF_REWRT_UOW_ENTRY
FLOAT
Number of unit of work list rewrites. From S6RWUCT.
CF_REWRTTBIX_ENTRY
FLOAT
Number of table index writes to update table status. From
S6RWICT.
CF_SMR_STR_UNAVAIL
FLOAT
Structure temporarily unavailable, during system-managed
rebuild. From S6RSP9CT
CF_TBLDATA_HEAD
FLOAT
Headers available for Table Data. From S6HDRSCD.
CF_WRITE_APPL_ENTR
FLOAT
Number of write APPLID entries. From S6WRACT.
CF_WRITE_DATAIT
FLOAT
Number of data entry writes. From S6WRDCT.
CF_WRITE_UOW_ENTRY
FLOAT
Number of unit of work list writes. From S6WRUCT.
CF_WRITE_MSGQUEUE
FLOAT
Number of lock release messages sent by this server. From
S6RDMCT.
CF_WRITETBIX_ENTRY
FLOAT
Number of table index writes to create new tables. From
S6WRICT.
Chapter 6. Data tables, lookup tables, and control tables
149
CICS statistics component data tables
CICS_S_CFDT_STOR_T
This table provides detailed Coupling Facility data table storage statistics. For
CICS/TS V1.3 and later, this maps the DFHCFS9K record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
CF_STORPOOL
K
CHAR(8)
Name of the storage pool AXMPGANY or AXMPGLOW.
From S9ANYNAM or S9LOWNAM.
CF_ADDRESS
FLOAT
Address of the storage pool area. From S9ANYPTR or
S9LOWPTR.
CF_COMPRESS
FLOAT
Number of compress (defragmentation) attempts. From
S9ANYRQC or S9LOWRQC.
CF_FREE_REQS
FLOAT
Number of storage FREE requests. From S9ANYRQS or
S9LOWRQS.
CF_FREEPAGE_LOW
FLOAT
Lowest number of free pages (since reset). From S9ANYLO
or S9LOWLO.
CF_GET
FLOAT
Number of storage GET requests. From S9ANYRQG or
S9LOWRQG.
CF_GET_FAILED
FLOAT
Number of GET requests that failed to obtain storage. From
S9ANYRQF or S9LOWRQF.
CF_PAGES_FREE
FLOAT
Number of free pages in the storage pool. From S9ANYFR or
S9LOWFR.
CF_PAGES_TOT
FLOAT
Total number of pages in the storage pool. From S9ANYMX
or S9LOWMX.
CF_PAGES_USED
FLOAT
Number of used pages in the storage pool. From S9ANYUS
or S9LOWUS.
CF_SIZE
FLOAT
Size of the storage pool. From S9ANYSIZ or S9LOWSIZ.
CICS_S_CFDT_TBAC_T
This table provides detailed Coupling Facility table accesses statistics. For CICS/TS
V1.3 and later, this maps the DFHCFS7K record.
The default retention period for this table is 7 days.
Column name
DATE
150
K
Data type
Description
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
CF_TABLE_NAME
K
CHAR(16)
Table name padded with spaces. From S7TABLE.
CF_CLOSE_TAB
FLOAT
Number of successful CLOSE requests for the table. From
S7OCCLOS.
CF_DEL_MULT
FLOAT
Number of multiple (generic) DELETE requests. From
S7RQDELM.
CF_DELETE
FLOAT
Number of DELETE requests. From S7RQDELE.
CF_DELETE_TAB
FLOAT
Number of times the table with the name specified was
deleted. From S7OCDELE.
CF_EXTR_STATS
FLOAT
Number of extract table statistics. From S7OCSTAT.
CF_LOAD
FLOAT
Number of records written by initial load requests. From
S7RQLOAD.
CF_OPEN_TAB
FLOAT
Number of extract table statistics. From S7OCOPEN.
CF_POINT
FLOAT
Number of POINT requests. From S7RQPOIN.
CF_READ
FLOAT
Number of combined READ and DELETE requests. From
S7RQRDDL.
CF_READ_DEL
FLOAT
Number of READ requests (including those for UPDATE).
From S7RQREAD.
CF_RETURN_HIGH
FLOAT
Number of requests for the current highest key. From
S7RQHIGH.
CF_READ
FLOAT
Number of READ requests (including those for UPDATE).
From S7RQREAD.
CF_REWRITES
FLOAT
Number of REWRITE requests. From S7RQREWR.
CF_UNLOCK
FLOAT
Number of UNLOCK requests. From S7RQUNLK.
CF_WRITES
FLOAT
Number of WRITE requests for new records. From
S7RQWRIT.
CICS_S_CFDT_TBAC_D
This table provides daily Coupling Facility table accesses statistics. For CICS/TS
V1.3 and later, this maps the DFHCFS7K record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
Chapter 6. Data tables, lookup tables, and control tables
151
CICS statistics component data tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
CF_TABLE_NAME
K
CHAR(16)
Table name padded with spaces. From S7TABLE.
CF_CLOSE_TAB
FLOAT
Number of successful CLOSE requests for the table. From
S7OCCLOS.
CF_DEL_MULT
FLOAT
Number of multiple (generic) DELETE requests. From
S7RQDELM.
CF_DELETE
FLOAT
Number of DELETE requests. From S7RQDELE.
CF_DELETE_TAB
FLOAT
Number of times the table with the name specified was
deleted. From S7OCDELE.
CF_EXTR_STATS
FLOAT
Number of extract table statistics. From S7OCSTAT.
CF_LOAD
FLOAT
Number of records written by initial load requests. From
S7RQLOAD.
CF_OPEN_TAB
FLOAT
Number of extract table statistics. From S7OCOPEN.
CF_POINT
FLOAT
Number of POINT requests. From S7RQPOIN.
CF_READ
FLOAT
Number of combined READ and DELETE requests. From
S7RQRDDL.
CF_READ_DEL
FLOAT
Number of READ requests (including those for UPDATE).
From S7RQREAD.
CF_RETURN_HIGH
FLOAT
Number of requests for the current highest key. From
S7RQHIGH.
CF_READ
FLOAT
Number of READ requests (including those for UPDATE).
From S7RQREAD.
CF_REWRITES
FLOAT
Number of REWRITE requests. From S7RQREWR.
CF_UNLOCK
FLOAT
Number of UNLOCK requests. From S7RQUNLK.
CF_WRITES
FLOAT
Number of WRITE requests for new records. From
S7RQWRIT.
CICS_S_DB2CONN_T
This table provides detailed CICS/DB2 global statistics. For CICS/TS V1.2 and
later, this maps the DFHD2GDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
152
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
DB2_CONN_NAME
K
CHAR(8)
Name of the installed DB2CONN. From DB2CONNM.
DB2_SYSID
K
CHAR(4)
Name of the DB2 subsystem to which the CICS-DB2
attachment is connected or will connect. From DB2SYSID.
DB2_RELEASE
K
CHAR(4)
Version and release level of the DB2 subsystem to which
CICS is currently connected. From DB2RLS.
DB2_GMT_CONN_TIME
TIMESTAMP
GMT when CICS connected to DB2 (STCK). From
DB2GCONN.
DB2_LOC_CONN_TIME
TIMESTAMP
Local time when CICS connected to DB2. From
DB2LCONN.
DB2_GMT_DISC_TIME
TIMESTAMP
GMT when CICS disconnected from DB2 (STCK). From
DB2GDISC.
DB2_LOC_DISC_TIME
TIMESTAMP
Local time when CICS disconnected from DB2. From
DB2LDISC.
DB2_PART_SIGNON
FLOAT
Number of partial signons. From DB2POPSI.
DB2_TCB_LIMIT
FLOAT
Maximum number of subtask TCBs that can be attached to
service DB2 requests. From DB2MXTCB.
DB2_TCB_CURRENT
FLOAT
Current number of subtask TCBs that are attached to
service DB2 requests. From DB2CRTCB.
DB2_TCB_HWM
FLOAT
Peak number of subtask TCBs that are attached to service
DB2 requests. From DB2HWMTC.
DB2_TCB_FREE
FLOAT
Current number of subtask TCBs without a DB2 thread.
From DB2FREET.
DB2_TCB_READYQ_CUR
FLOAT
Number of CICS tasks that are queued waiting for a DB2
subtask TCB to become available. From DB2QUTCB.
DB2_TCB_READYQ_HWM
FLOAT
Peak number of CICS tasks that are queued waiting for a
DB2 subtask TCB to become available. From DB2RQUHW.
DB2_POOL_PLAN_NAME
CHAR(8)
Name of the plan being used for the pool. If a dynamic
plan exit is being used for the pool, this field is null. From
DB2POPNM.
DB2_POOL_PLEX_NAME
CHAR(8)
Name of the dynamic plan exit to be used for the pool. If a
static plan is being used for the pool, this field contains
nulls. From DB2POPEX.
DB2_POOL_AUTHID
CHAR(8)
Static ID that is to be used for DB2 security checking of
pool threads. If an Authtype is being used for pool
threads, this field contains nulls. From DB2POAUI.
DB2_POOL_AUTHTYPE
CHAR(8)
Type of ID that is to be used for DB2 security checking of
pool threads. If an Authtype is being used for pool
threads, this field contains nulls. From DB2POAUT.
DB2_POOL_ACCNTREC
CHAR(4)
Maximum frequency of DB2 accounting records that are to
be used for transactions using pool threads. From
DB2POACC.
DB2_POOL_THRWAIT
CHAR(4)
Specifies whether transactions should wait for a pool
thread or should be abended if the number of active pool
threads exceeds the pool thread limit. From DB2POTHW.
DB2_POOL_PRIORITY
CHAR(8)
Priority of the pool thread subtasks relative to the CICS
main task. From DB2POPRI.
Chapter 6. Data tables, lookup tables, and control tables
153
CICS statistics component data tables
Column name
Data type
Description
DB2_POOL_CALLS
FLOAT
Number of SQL calls that are made using pool threads.
From DB2POCAL.
DB2_POOL_SIGNONS
FLOAT
Number of DB2 signons that are performed for pool
threads. From DB2POSIG.
DB2_POOL_COMMITS
FLOAT
Number of 2-phase commits that are performed for UOWs
using pool threads. From DB2POCOM.
DB2_POOL_ABORTS
FLOAT
Number of UOWs (using pool threads) that were rolled
back. From DB2POABO.
DB2_POOL_SINGLE_PH
FLOAT
Number of UOWs (using pool threads) that used
single-phase commit, either because they were R/O UOWs
or because DB2 was the only recoverable resource updated
in the UOWs. From DB2POSPH.
DB2_POOL_THR_REUSE
FLOAT
Number of times that CICS transactions, using the pool,
reused an existing DB2 thread. From DB2POTHR.
DB2_POOL_THR_TERM
FLOAT
Number of terminate thread requests made to DB2 for pool
threads. From DB2POTHT.
DB2_POOL_THR_WAITS
FLOAT
Number of times that all available threads in the pool were
busy and a transaction had to wait for a thread to become
available. From DB2POTHW.
DB2_POOL_THR_LIMIT
FLOAT
Current maximum number of pool threads that are
allowed. From DB2POTHM.
DB2_POOL_THR_CUR
FLOAT
Current number of active pool threads. From DB2POTHC.
DB2_POOL_THR_HWM
FLOAT
Peak number of active pool threads. From DB2POTHH.
DB2_POOL_TASK_CUR
FLOAT
Current number of CICS tasks that have used a pool
thread. From DB2POTSK.
DB2_POOL_TASK_HWM
FLOAT
Peak number of CICS tasks that have used a pool thread.
From DB2POTSH.
DB2_POOL_TASK_TOT
FLOAT
Total number of completed tasks that have used a pool
thread. From DB2POTOT.
DB2_POOL_RDQ_CUR
FLOAT
Current number of CICS tasks that are waiting for a pool
thread to become available. From DB2POTRE.
DB2_POOL_RDQ_HWM
FLOAT
Peak number of CICS tasks that waited for a pool thread
to become available. From DB2POHRE.
DB2_COMD_AUTHID
CHAR(8)
Static ID that is to be used for DB2 security checking of
command threads. From DB2CMAUT.
DB2_COMD_AUTHTYPE
CHAR(8)
Type of ID that is to be used for DB2 security checking of
command threads. From DB2CMATT.
DB2_COMD_CALLS
FLOAT
Number of DB2 commands that are issued using the
DSNC transaction. From DB2CMDSN.
DB2_COMD_SIGNONS
FLOAT
Number of signons that are performed for command
threads. From DB2CMSIG.
DB2_COMD_THR_TERM
FLOAT
Number of terminate thread requests that are made to DB2
for command threads. From DB2CMTHT.
DB2_COMD_THR_OVERF
FLOAT
Number of times that a DSNC DB2 results in a pool thread
being used because the number of active command threads
exceeds the command threads limit. From DB2CMOVF.
DB2_COMD_THR_LIMIT
FLOAT
Current maximum number of command threads that are
allowed. From DB2CMMTH.
154
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DB2_COMD_THR_CUR
FLOAT
Current number of active command threads. From
DB2CMCTH.
DB2_COMD_THR_HWM
FLOAT
Peak number of active command threads. From
DB2CMHWM.
CICS_S_DB2CONN_D
This table provides daily CICS/DB2 global statistics. For CICS/TS V1.2 and later,
this maps the DFHD2GDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
DB2_CONN_NAME
K
CHAR(8)
Name of the installed DB2CONN. From DB2CONNM.
DB2_SYSID
K
CHAR(4)
Name of the DB2 subsystem to which the CICS-DB2
attachment is connected or will connect. From DB2SYSID.
DB2_RELEASE
K
CHAR(4)
Version and release level of the DB2 subsystem to which
CICS is currently connected. From DB2RLS.
DB2_GMT_CONN_TIME
TIMESTAMP
GMT when CICS connected to DB2 (STCK). From
DB2GCONN.
DB2_LOC_CONN_TIME
TIMESTAMP
Local time when CICS connected to DB2. From
DB2LCONN.
DB2_GMT_DISC_TIME
TIMESTAMP
GMT when CICS disconnected from DB2 (STCK). From
DB2GDISC.
DB2_LOC_DISC_TIME
TIMESTAMP
Local time when CICS disconnected from DB2. From
DB2LDISC.
DB2_PART_SIGNON
FLOAT
Number of partial signons. From DB2POPSI.
DB2_TCB_LIMIT
FLOAT
Maximum number of subtask TCBs that can be attached
to service DB2 requests. From DB2MXTCB.
DB2_TCB_CURRENT
FLOAT
Current number of subtask TCBs that are attached to
service DB2 requests. From DB2CRTCB.
DB2_TCB_HWM
FLOAT
Peak number of subtask TCBs that are attached to service
DB2 requests. From DB2HWMTC.
DB2_TCB_FREE
FLOAT
Current number of subtask TCBs without a DB2 thread.
From DB2FREET.
DB2_TCB_READYQ_CUR
FLOAT
Number of CICS tasks that are queued waiting for a DB2
subtask TCB to become available. From DB2QUTCB.
Chapter 6. Data tables, lookup tables, and control tables
155
CICS statistics component data tables
Column name
Data type
Description
DB2_TCB_READYQ_HWM
FLOAT
Peak number of CICS tasks that are queued waiting for a
DB2 subtask TCB to become available. From
DB2RQUHW.
DB2_POOL_PLAN_NAME
CHAR(8)
Name of the plan being used for the pool. If a dynamic
plan exit is being used for the pool, this field will be null.
From DB2POPNM.
DB2_POOL_PLEX_NAME
CHAR(8)
Name of the dynamic plan exit to be used for the pool. If
a static plan is being used for the pool, this field contains
nulls. From DB2POPEX.
DB2_POOL_AUTHID
CHAR(8)
Static ID that is to be used for DB2 security checking of
pool threads. If an Authtype is being used for pool
threads, this field contains nulls. From DB2POAUI.
DB2_POOL_AUTHTYPE
CHAR(8)
Type of ID that is to be used for DB2 security checking of
pool threads. If an Authtype is being used for pool
threads, this field contains nulls. From DB2POAUT.
DB2_POOL_ACCNTREC
CHAR(4)
Maximum frequency of DB2 accounting records that are
to be used for transactions using pool threads. From
DB2POACC.
DB2_POOL_THRWAIT
CHAR(4)
Specifies whether transactions should wait for a pool
thread or should be abended if the number of active pool
threads exceeds the pool thread limit. From DB2POTHW.
DB2_POOL_PRIORITY
CHAR(8)
Priority of the pool thread subtasks relative to the CICS
main task. From DB2POPRI.
DB2_POOL_CALLS
FLOAT
Number of SQL calls that are made using pool threads.
From DB2POCAL.
DB2_POOL_SIGNONS
FLOAT
Number of DB2 signons that are performed for pool
threads. From DB2POSIG.
DB2_POOL_COMMITS
FLOAT
Number of 2-phase commits that are performed for
UOWs using pool threads. From DB2POCOM.
DB2_POOL_ABORTS
FLOAT
Number of UOWs (using pool threads) that were rolled
back. From DB2POABO.
DB2_POOL_SINGLE_PH
FLOAT
Number of UOWs (using pool threads) that used
single-phase commit, either because they were R/O
UOWs or because DB2 was the only recoverable resource
updated in the UOWs. From DB2POSPH.
DB2_POOL_THR_REUSE
FLOAT
Number of times that CICS transactions, using the pool,
reused an existing DB2 thread. From DB2POTHR.
DB2_POOL_THR_TERM
FLOAT
Number of terminate thread requests made to DB2 for
pool threads. From DB2POTHT.
DB2_POOL_THR_WAITS
FLOAT
Number of times that all available threads in the pool
were busy and a transaction had to wait for a thread to
become available. From DB2POTHW.
DB2_POOL_THR_LIMIT
FLOAT
Current maximum number of pool threads that are
allowed. From DB2POTHM.
DB2_POOL_THR_CUR
FLOAT
Current number of active pool threads. From DB2POTHC.
DB2_POOL_THR_HWM
FLOAT
Peak number of active pool threads. From DB2POTHH.
DB2_POOL_TASK_CUR
FLOAT
Current number of CICS tasks that have used a pool
thread. From DB2POTSK.
DB2_POOL_TASK_HWM
FLOAT
Peak number of CICS tasks that have used a pool thread.
From DB2POTSH.
156
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DB2_POOL_TASK_TOT
FLOAT
Total number of completed tasks that have used a pool
thread. From DB2POTOT.
DB2_POOL_RDQ_CUR
FLOAT
Current number of CICS tasks that are waiting for a pool
thread to become available. From DB2POTRE.
DB2_POOL_RDQ_HWM
FLOAT
Peak number of CICS tasks that waited for a pool thread
to become available. From DB2POHRE.
DB2_COMD_AUTHID
CHAR(8)
Static ID that is to be used for DB2 security checking of
command threads. From DB2CMAUT.
DB2_COMD_AUTHTYPE
CHAR(8)
Type of ID that is to be used for DB2 security checking of
command threads. From DB2CMATT.
DB2_COMD_CALLS
FLOAT
Number of DB2 commands that are issued using the
DSNC transaction. From DB2CMDSN.
DB2_COMD_SIGNONS
FLOAT
Number of signons that are performed for command
threads. From DB2CMSIG.
DB2_COMD_THR_TERM
FLOAT
Number of terminate thread requests that are made to
DB2 for command threads. From DB2CMTHT.
DB2_COMD_THR_OVERF
FLOAT
Number of times that a DSNC DB2 results in a pool
thread being used because the number of active command
threads exceeds the command threads limit. From
DB2CMOVF.
DB2_COMD_THR_LIMIT
FLOAT
Current maximum number of command threads that are
allowed. From DB2CMMTH.
DB2_COMD_THR_CUR
FLOAT
Current number of active command threads. From
DB2CMCTH.
DB2_COMD_THR_HWM
FLOAT
Peak number of active command threads. From
DB2CMHWM.
CICS_S_DB2ENTRY_T
This table provides detailed CICS/DB2 resource statistics. The resource is a
DB2ENTRY. For CICS/TS V1.2 and later, this maps the DFHD2RDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DB2_ENTRY_NAME
K
CHAR(8)
Name of the installed DB2ENTRY. From DB2ENTNM.
CHAR(8)
Name of the plan being used for this DB2ENTRY. If a dynamic
plan exit is being used for the DB2ENTRY, this field is null.
From DB2PLNNM.
DB2_PLAN_NAME
Chapter 6. Data tables, lookup tables, and control tables
157
CICS statistics component data tables
Column name
Data type
Description
DB2_PLANEXIT_NAME
CHAR(8)
Name of the dynamic plan exit to be used for this DB2ENTRY. If
a static plan is being used for the DB2ENTRY, this field is null.
From DB2PLXNM.
DB2_AUTHID
CHAR(8)
Static ID that is to be used for DB2 security checking of this
DB2ENTRY. If an Authtype is being used for the DB2ENTRY,
this field is null. From DB2GSTAU.
DB2_AUTHTYPE
CHAR(8)
Type of ID that is to be used for DB2 security checking of this
DB2ENTRY. If an Authtype is being used for the DB2ENTRY,
this field is null. From DB2AUTTY.
DB2_ACCOUNTREC
CHAR(4)
Frequency of DB2 accounting records that are to be produced for
transactions using this DB2ENTRY. From DB2ACCSE.
DB2_PART_SIGNON
FLOAT
Number of partial signons. From DB2POPSI.
DB2_PRIORITY
CHAR(8)
Priority of the DB2ENTRY thread subtasks relative to the CICS
main task. From DB2TRHPR.
DB2_CALLS
FLOAT
Number of SQL calls that are made using this DB2ENTRY. From
DB2CALLS.
DB2_SIGNONS
FLOAT
Number of DB2 signons that are performed for this DB2ENTRY.
From DB2SIGNO.
DB2_COMMITS
FLOAT
Number of 2-phase commits that are performed for UOWs using
this DB2ENTRY. From DB2COMMT.
DB2_ABORTS
FLOAT
Number of UOWs (using this DB2ENTRY) that were rolled back.
From DB2ABORT.
DB2_SINGLE_PHASE
FLOAT
Number of UOWs (using the DB2ENTRY) that used single-phase
commit, either because they were R/O UOWs or because DB2
was the only recoverable resource updated in the UOWs. From
DB2SINPH.
DB2_THREAD_REUSE
FLOAT
Number of times that CICS transactions, using the DB2ENTRY,
were able to use an existing created DB2 thread. From
DB2THRRE.
DB2_THREAD_TERM
FLOAT
Number of terminate thread requests made to DB2 for threads of
this DB2ENTRY. From DB2THRTE.
DB2_THREAD_WAIT_OV
FLOAT
Number of times that all available threads in the DB2ENTRY
were busy and a transaction had to wait for a thread to become
available or overflow to the pool and use a pool thread instead.
From DB2THWOV.
DB2_THREAD_LIMIT
FLOAT
Current maximum number of threads that are allowed for the
DB2ENTRY. From DB2THLIM.
DB2_THREAD_CUR
FLOAT
Current number of active threads for this DB2ENTRY. From
DB2THCUR.
DB2_THREAD_HWM
FLOAT
Peak number of active threads for this DB2ENTRY. From
DB2THHWM.
DB2_THREADWAIT
CHAR(4)
Specifies whether transactions should wait for a thread abend or
overflow to the pool if the number of active threads for this
DB2ENTRY exceeds its thread limit. From DB2TRWSE.
DB2_PTHREAD_LIMIT
FLOAT
Current maximum number of protected threads that are allowed
for the DB2ENTRY. From DB2PTHMX.
DB2_PTHREAD_CUR
FLOAT
Current number of protected threads for this DB2ENTRY. From
DB2PTHCU.
DB2_PTHREAD_HWM
FLOAT
Peak number of protected threads for this DB2ENTRY. From
DB2PTHHW.
158
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DB2_TASK_CUR
FLOAT
Current number of CICS tasks that are using this DB2ENTRY.
From DB2PTASKC.
DB2_TASK_HWM
FLOAT
Peak number of CICS tasks that have used this DB2ENTRY.
From DB2PTASKH.
DB2_TASK_TOT
FLOAT
Total number of completed tasks that have used this DB2ENTRY.
From DB2PTASKT.
DB2_READYQ_CUR
FLOAT
Current number of CICS tasks that are waiting for a thread to
become available on this DB2ENTRY. From DB2PASKR.
DB2_READYQ_HWM
FLOAT
Peak number of CICS tasks that waited for a thread to become
available on this DB2ENTRY. From DB2EHWMT.
CICS_S_DB2ENTRY_D
This table provides daily CICS/DB2 resource statistics. The resource is a
DB2ENTRY. For CICS/TS V1.2 and later, this maps the DFHD2RDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DB2_ENTRY_NAME
K
CHAR(8)
Name of the installed DB2ENTRY. From DB2ENTNM.
DB2_PLAN_NAME
CHAR(8)
Name of the plan being used for this DB2ENTRY. If a dynamic
plan exit is being used for the DB2ENTRY, this field is null.
From DB2PLNNM.
DB2_PLANEXIT_NAME
CHAR(8)
Name of the dynamic plan exit to be used for this DB2ENTRY.
If a static plan is being used for the DB2ENTRY, this field is
null. From DB2PLXNM.
DB2_AUTHID
CHAR(8)
Static ID that is to be used for DB2 security checking of this
DB2ENTRY. If an Authtype is being used for the DB2ENTRY,
this field is null. From DB2GSTAU.
DB2_AUTHTYPE
CHAR(8)
Type of ID that is to be used for DB2 security checking of this
DB2ENTRY. If an Authtype is being used for the DB2ENTRY,
this field is null. From DB2AUTTY.
DB2_ACCOUNTREC
CHAR(4)
Frequency of DB2 accounting records that are to be produced
for transactions using this DB2ENTRY. From DB2ACCSE.
DB2_THREADWAIT
CHAR(4)
Specifies whether transactions should wait for a thread abend
or overflow to the pool if the number of active threads for this
DB2ENTRY exceeds its thread limit. From DB2TRWSE.
DB2_PRIORITY
CHAR(8)
Priority of the DB2ENTRY thread subtasks relative to the CICS
main task. From DB2TRHPR.
DB2_CALLS
FLOAT
Number of SQL calls that are made using this DB2ENTRY.
From DB2CALLS.
Chapter 6. Data tables, lookup tables, and control tables
159
CICS statistics component data tables
Column name
Data type
Description
DB2_SIGNONS
FLOAT
Number of DB2 signons that are performed for this
DB2ENTRY. From DB2SIGNO.
DB2_COMMITS
FLOAT
Number of 2-phase commits that are performed for UOWs
using this DB2ENTRY. From DB2COMMT.
DB2_ABORTS
FLOAT
Number of UOWs (using this DB2ENTRY) that were totaled
back. From DB2ABORT.
DB2_SINGLE_PHASE
FLOAT
Number of UOWs (using the DB2ENTRY) that used
single-phase commit, either because they were R/O UOWs or
because DB2 was the only recoverable resource updated in the
UOWs. From DB2SINPH.
DB2_THREAD_REUSE
FLOAT
Number of times that CICS transactions, using the DB2ENTRY,
were able to use an existing DB2 thread. From DB2THRRE.
DB2_THREAD_TERM
FLOAT
Number of terminate thread requests made to DB2 for threads
of this DB2ENTRY. From DB2THRTE.
DB2_THREAD_WAIT_OV
FLOAT
Number of times that all available threads in the DB2ENTRY
were busy and a transaction had to wait for a thread to become
available or overflow to the pool and use a pool thread instead.
From DB2THWOV.
DB2_THREAD_LIMIT
FLOAT
Current maximum number of threads that are allowed for the
DB2ENTRY. From DB2THLIM.
DB2_THREAD_CUR
FLOAT
Current number of active threads for this DB2ENTRY. From
DB2THCUR.
DB2_THREAD_HWM
FLOAT
Peak number of active threads for this DB2ENTRY. From
DB2THHWM.
DB2_PART_SIGNON
FLOAT
Number of partial signons. From DB2POPSI.
DB2_PTHREAD_LIMIT
FLOAT
Current maximum number of protected threads that are
allowed for the DB2ENTRY. From DB2PTHMX.
DB2_PTHREAD_CUR
FLOAT
Current number of protected threads for this DB2ENTRY. From
DB2PTHCU.
DB2_PTHREAD_HWM
FLOAT
Peak number of protected threads for this DB2ENTRY. From
DB2PTHHW.
DB2_TASK_CUR
FLOAT
Current number of CICS tasks that are using this DB2ENTRY.
From DB2PTASKC.
DB2_TASK_HWM
FLOAT
Peak number of CICS tasks that have used this DB2ENTRY.
From DB2PTASKH.
DB2_TASK_TOT
FLOAT
Total number of completed tasks that have used this
DB2ENTRY. From DB2PTASKT.
DB2_READYQ_CUR
FLOAT
Current number of CICS tasks that are waiting for a thread to
become available on this DB2ENTRY. From DB2PASKR.
DB2_READYQ_HWM
FLOAT
Peak number of CICS tasks that waited for a thread to become
available on this DB2ENTRY. From DB2EHWMT.
CICS_S_DBCTL_T
This table provides detailed CICS DBCTL statistics. For CICS/ESA and CICS/TS,
this maps the DFHDBUDS record.
The default retention period for this table is 7 days.
160
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DBCTL_ID
K
CHAR(4)
Name of the DBCTL session. From STATDBID.
SESSION_NUMBER
K
INTEGER
Number of the CICS DBCTL session. It is incremented every
time a user connects and disconnects. From STATSENO.
CONNECT_TIME
TIMESTAMP
Time (GMT) when CICS connected to DBCTL. From
STACTIME.
CONNECT_TIME_L
TIMESTAMP
Local time when CICS connected to DBCTL. CICS/ESA V4
and later. From STALCTIM.
DBCTL_RSE_NAME
CHAR(8)
Name of the DBCTL recoverable service element (RSE).
From STARSEN.
DISCONNECT_TIME
TIMESTAMP
Time (GMT) when CICS disconnected from DBCTL. From
STADTIME.
DISCONNECT_TIME_L
TIMESTAMP
Local time when CICS disconnected from DBCTL.
CICS/ESA V4 and later. From STALDTIM.
PSB_SCHEDULE_COUNT
INTEGER
Number of times the DBCTL session successfully scheduled
a PSB. From STAPSBSU.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete.
From SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited),
EOD (End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record. Example:
0330. From SMFSTRVN.
THREADS_HIT_MAX
INTEGER
Number of times the CICS-DBCTL session used the
maximum number of threads. From STANOMATHD.
THREADS_HIT_MIN
INTEGER
Number of times the CICS-DBCTL session used the
minimum number of threads. From STANOMITHD.
THREADS_MAX
INTEGER
Maximum threads specified in the DRA startup parameter
table. From STAMATHD.
THREADS_MAX_TIME
FLOAT
Elapsed time that the DBCTL session used the maximum
number of threads. From STAELMAX.
THREADS_MIN
INTEGER
Minimum threads specified in the DRA startup parameter
table. From STAMITHD.
THREADS_PEAK
INTEGER
Highest number of threads used. From STAHIWAT.
Chapter 6. Data tables, lookup tables, and control tables
161
CICS statistics component data tables
CICS_S_DBCTL_D
This table provides daily statistics on the DBCTL session in the CICS system. It
contains summarized data from the CICS_S_DBCTL_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DBCTL_ID
K
CHAR(4)
Name of the DBCTL session. From STATDBID.
SESSION_NUMBER
K
INTEGER
Number of the CICS DBCTL session. It is incremented every
time a user connects and disconnects. From STATSENO.
PSB_SCHEDULE_COUNT
INTEGER
Number of times the DBCTL session successfully scheduled a
PSB. From STAPSBSU.
THREADS_HIT_MAX
INTEGER
Number of times the CICS-DBCTL session used the maximum
number of threads. From STANOMATHD.
THREADS_HIT_MIN
INTEGER
Number of times the CICS-DBCTL session used the minimum
number of threads. From STANOMITHD.
THREADS_MAX
INTEGER
Maximum threads specified in the DRA startup parameter
table. From STAMATHD.
THREADS_MIN
INTEGER
Minimum threads specified in the DRA startup parameter
table. From STAMITHD.
THREADS_PEAK
INTEGER
Highest number of threads used. From STAHIWAT.
CICS_S_DISPATCH_T
This table provides detailed data from the dispatcher domain statistics records. The
data is from CICS statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
162
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CHAR(8)
This is the name of the CICS dispatcher TCB mode. It can be
either QR, RO, CO, SZ, RP, FO, SL, SO, S8, D2, JM, L8, L9, J8,
J9, X8, or X9 depending on the TCB. It contains MISSING for
CICS 3.2.1, and GLOBAL for summary data. From
DSGTCBNM.
AMAXTASK_COUNT
INTEGER
Current number of user tasks eligible for dispatching. From
DSGAMXTC. This is valid for CICS TS Version 2.1 and later.
AMAXTASK_LIMIT
INTEGER
AMXT value. From DSGAMXTL. This is valid for CICS TS
Version 2.1 and later.
AMAXTASK_PEAK
INTEGER
Peak value of the current number of user tasks eligible for
dispatching. From DSGAMXTP. This is valid for CICS TS
Version 2.1 and later.
CPU_SEC
FLOAT
Accumulated processor time used by this TCB when
executing the default dispatcher task, in seconds. From
DSGTCT.
DISPATCHER_START
TIMESTAMP
Time (GMT) when the dispatcher started. It is the
approximate time when CICS started. From DSGSTART.
DISPATCHER_START_L
TIMESTAMP
Local time when the dispatcher started. It is the approximate
time when CICS started. For CICS V4 and later. From
DSGLSTRT.
ELAPS_JSTEP_SEC
REAL
Total CPU time for all TCBs in this address space,
accumulated during the interval. From DSGJEST.
ICVR_MSEC
INTEGER
This is the current ICVR time. From DSGICVRT.
ICVT_MSEC
INTEGER
ICV time, in milliseconds. From DSGICVT.
ICVTSD_MSEC
INTEGER
ICVTSD time, in milliseconds. From DSGICVSD.
LAST_RESET_TIME
TIMESTAMP
Last time all resettable values in this table were reset to zero.
From DSGLRT. This is valid for CICS TS Version 2.1 and later.
MAX_WAITS
REAL
MAXOPENTCBs value specified in the SIT, or as an override,
or changed dynamically. From DSGMAXOP. This is valid for
CICS TS Version 2.1 and later.
MAXTASK_LIMIT
INTEGER
MXT value. From DSGTL. This is valid for CICS TS Version
2.1 and later.
MAXTASK_REACHED
INTEGER
Number of times the MXT value has been reached. From
DSGTAMXT. This is valid for CICS TS Version 2.1 and later.
MVS_DISPATCH_SEC
FLOAT
Time that this TCB was dispatched, in seconds. From
DSGTDT.
MVS_TCB_COUNT
INTEGER
Number of MVS TCBs under which the CICS dispatcher runs.
From DSGASIZE.
MVS_WAITS
FLOAT
Number of MVS waits on this TCB. From DSGSYSW.
MVS_WAIT_SEC
FLOAT
Time that this TCB was in an MVS wait, in seconds. From
DSGTWT.
PEAK_NO_TCB_USED
REAL
Peak number of TCB used. From DSGTCBUP.
PEAK_TCB_ATTACHS
REAL
Peak value of the number of MVS TCBs attached in this CICS
dispatcher TCB mode. From DSGTCBPA.
PROCESSOR_USE_PCT
INTEGER
Percentage use of the processor for this TCB since the start of
CICS. From DSGPERCT. This is valid for CICS TS Version 2.1
and later.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
TCB_MODE
K
Chapter 6. Data tables, lookup tables, and control tables
163
CICS statistics component data tables
Column name
Data type
Description
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record. Example:
0330. From SMFSTRVN.
SRB_CPU_SEC
REAL
Total CPU time for all service request blocks (SRB) executed
in this address space, accumulated during the interval. From
DSGSRBT.
TASKS
INTEGER
Current number of tasks in the system. From DSGCNT.
TASKS_PEAK
INTEGER
Peak value of the number of tasks in the system. From
DSGPNT.
TCB_ALL_TO_TASK
REAL
TCB allocates to task. From DSGTCBAL.
TCB_ATTACHS
REAL
Current number of MVS TCBs attached in this CICS
dispatcher TCB mode. From DSGTCBCA.
TCB_CPU_SEC
FLOAT
Accumulated processor time for this TCB since CICS startup,
in seconds. From DSGACT.
TCB_DET_EXCESS
REAL
Number of detached TCB in excess. From DSGTCBDE.
TCB_DETACHES
REAL
Current number of MVS TCBs detached in this CICS
dispatcher TCB mode. From
DSGTCBDS+DSGTCBDO+DSGTCBST.
TCB_MISMATCH
REAL
Number of TCB mismatches. From DSGNTCBM.
TCB_STEALS
REAL
Current number of MVS TCBs that have been stolen from
other TCBs. From DSGTCBST.
TCB_USED_CUR
REAL
TCB used current. From DSGTCBUC.
CICS_S_DISPATCH_D
This table provides daily data from the dispatcher domain statistics records. The
data is from CICS statistics records (SMF 110, subtype 2). It contains consolidated
data from the CICS_S_DISPATCH_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TCB_MODE
K
CHAR(8)
This is the name of the CICS dispatcher TCB mode. It can be
either QR, RO, CO, SZ, RP, FO, SL, SO, S8, D2, JM, L8, L9, J8,
J9, X8, or X9 depending on the TCB. It contains MISSING for
CICS 3.2.1.
INTEGER
AMXT value. From DSGAMXTL. This is valid for CICS TS
Version 2.1 and later. This is valid for CICS TS Version 2.1 and
later.
AMAXTASK_LIMIT
164
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
AMAXTASK_PEAK
INTEGER
Peak value of the current number of user tasks eligible for
dispatching. From DSGAMXTP. This is valid for CICS TS
Version 2.1 and later.
CPU_SEC
FLOAT
Accumulated processor time used by this TCB when executing
the default dispatcher task, in seconds. From DSGTCT.
DISPATCHER_START
TIMESTAMP
Time (GMT) when the dispatcher started. It is the approximate
time when CICS started. From DSGSTART.
DISPATCHER_START_L
TIMESTAMP
Local time when the dispatcher started. It is the approximate
time when CICS started. For CICS V4 and later. From
DSGLSTRT.
ELAPS_JSTEP_SEC
REAL
Total CPU time for all TCBs in this address space, accumulated
during the interval. From DSGJEST.
ICVR_MSEC
INTEGER
This is the current ICVR time. From DSGICVRT.
LAST_RESET_TIME
TIMESTAMP
Last time all resettable values in this table were reset to zero.
From DSGLRT. This is valid for CICS TS Version 2.1 and later.
MAX_WAITS
REAL
MAXOPENTCBs value specified in the SIT, or as an override,
or changed dynamically. From DSGMAXOP. This is valid for
CICS TS Version 2.1 and later.
MAXTASK_LIMIT
INTEGER
MXT value. From DSGTL. This is valid for CICS TS Version 2.1
and later.
MAXTASK_REACHED
INTEGER
Number of times the MXT value has been reached. From
DSGTAMXT. This is valid for CICS TS Version 2.1 and later.
MVS_DISPATCH_SEC
FLOAT
Time that this TCB was dispatched, in seconds. From DSGTDT.
MVS_WAITS
FLOAT
Number of MVS waits on this TCB. From DSGSYSW.
MVS_WAIT_SEC
FLOAT
Time that this TCB was in an MVS wait, in seconds. From
DSGTWT.
PEAK_NO_TCB_USED
REAL
Peak number of TCB used. From DSGTCBUP.
PEAK_TCB_ATTACHS
REAL
Peak value of the number of MVS TCBs attached in this CICS
dispatcher TCB mode. From DSGTCBPA.
SRB_CPU_SEC
REAL
Total CPU time for all service request blocks (SRB) executed in
this address space, accumulated during the interval. From
DSGSRBT.
PROCESSOR_USE_PCT
INTEGER
Maximum percentage use of the processor for this TCB since
the start of CICS. From DSGPERCT. This is valid for CICS TS
Version 2.1 and later.
TASKS_PEAK
INTEGER
Peak value of the number of tasks in the system. From
DSGPNT.
TCB_ALL_TO_TASK
REAL
TCB allocates to task. From DSGTCBAL.
TCB_ATTACHS
REAL
Current number of MVS TCBs attached in this CICS dispatcher
TCB mode. From DSGTCBCA.
TCB_CPU_SEC
FLOAT
Accumulated processor time for this TCB since CICS startup,
in seconds. From DSGACT.
TCB_DET_EXCESS
REAL
Number of exceeding TCB detached. From DSGTCBDE.
TCB_DETACHES
REAL
Current number of MVS TCBs detached in this CICS
dispatcher TCB mode. From
DSGTCBDS+DSGTCBDO+DSGTCBST.
TCB_MISMATCH
REAL
Number of TCB mismatches. From DSGNTCBM.
Chapter 6. Data tables, lookup tables, and control tables
165
CICS statistics component data tables
Column name
Data type
Description
TCB_STEALS
REAL
Current number of MVS TCBs that have been stolen from
other TCBs. From DSGTCBST.
TCB_USED_CUR
REAL
TCB used current. From DSGTCBUC.
CICS_S_DLI_T
This table provides detailed data for each DL/I database. The data is from CICS
statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DBD_NAME
K
CHAR(8)
Database name. From A18FNAM if Resource Statistics
(STID=70), GLOBAL if Global Statistics (STID=71).
DBRC_REGISTRATION
CHAR(4)
DBRC registration indicator. From A18IODR. Value is YES if the
database is registered, NO if not registered, and UNK if no PSB
has yet been scheduled.
DELETE_REQ
INTEGER
Number of delete requests. From A18EDLT.
ERRORS_GLOBAL
INTEGER
Number of EEQEs across all subsystems that use this database.
Valid if DBRC_REGISTRATION = YES. From A18IOTG.
ERRORS_LOCAL
INTEGER
Number of extended error queue elements (EEQEs) created for
this database. From A18IOTL.
ERRORS_LOCAL_READ
INTEGER
Number of read EEQEs created for this database. From
A18IORL.
GET_HOLD_NEXT_PAR
INTEGER
Number of get hold next in parent requests against the physical
database. From A18EGHNP.
GET_HOLD_NEXT_REQ
INTEGER
Number of get hold next requests processed against the
physical database. From A18EGHN.
GET_HOLD_UNIQUE_RQ
INTEGER
Number of get hold unique requests processed against the
physical database. From A18EGHU.
GET_NEXT_PARENT_RQ
INTEGER
Number of get next in parent requests processed against the
physical database. From A18EGNP.
GET_NEXT_REQ
INTEGER
Number of get next requests processed against the physical
database. From A18EGN.
GET_UNIQUE_REQ
INTEGER
Number of get unique requests processed against the physical
database. From A18EGU.
IMS_VERSION_FLAG
CHAR(4)
IMS version flag. From A18IMSVR.
INSERT_REQ
INTEGER
Number of insert requests. From A18EISR.
166
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
POOL_DMB_PEAK
INTEGER
Peak number of bytes used from the DMB pool. From
A18DMBMU.
POOL_DMB_SIZE_BYTE
INTEGER
Maximum number of bytes in the DMB pool. From
A18DMBMS.
POOL_DMB_WAITS
INTEGER
Number of times a DMB pool request exceeded the number of
bytes available in the pool. From A18DMBEX.
POOL_ENQ_PEAK
INTEGER
Peak number of bytes used from the ENQ pool during the
entire CICS session. From A18ENQMU.
POOL_ENQ_SIZE_BYTE
INTEGER
Maximum number of bytes in the ENQ pool. From
A18ENQMS.
POOL_PSB_PEAK
INTEGER
Peak number of bytes used from the PSB pool. From
A18PSBMU.
POOL_PSB_SIZE_BYTE
INTEGER
Maximum number of bytes in the PSB pool. From A18PSBMS.
POOL_PSB_WAITS
INTEGER
Number of times a PSB pool request exceeded the number of
bytes available in the pool. From A18PSBEX.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REPLACE_REQ
INTEGER
Number of replace requests. From A18EREP.
REQUESTS
INTEGER
Number of calls on the database. From A18LTOT.
THREADS
INTEGER
Maximum number of threads, specified in the DLTHRED SIT
parameter. From A18THRDS.
THREADS_IN_USE
INTEGER
Number of DL/I threads currently in use. From A18THRDA.
THREADS_USED_PEAK
INTEGER
Peak number of DL/I threads used during the entire CICS
session. From A18THRDM.
THREADS_WAITS
INTEGER
Number of times a DL/I thread was waiting during the entire
CICS session. From A18THRDW.
CICS_S_DLI_D
This table provides daily data for each DL/I database. It contains consolidated
data from the CICS_S_DLI_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
Chapter 6. Data tables, lookup tables, and control tables
167
CICS statistics component data tables
Column name
Data type
Description
CHAR(8)
Database name. From A18FNAM if Resource Statistics
(STID=70), GLOBAL if Global Statistics (STID=71).
DELETE_REQ
INTEGER
Number of delete requests. From A18EDLT.
ERRORS_GLOBAL
INTEGER
Number of EEQEs across all subsystems that use this database.
Valid if DBRC_REGISTRATION = YES. From A18IOTG.
ERRORS_LOCAL
INTEGER
Number of extended error queue elements (EEQEs) created for
this database. From A18IOTL.
ERRORS_LOCAL_READ
INTEGER
Number of read EEQEs created for this database. From
A18IORL.
GET_HOLD_NEXT_PAR
INTEGER
Number of get hold next in parent requests against the
physical database. From A18EGHNP.
GET_HOLD_NEXT_REQ
INTEGER
Number of get hold next requests processed against the
physical database. From A18EGHN.
GET_HOLD_UNIQUE_RQ
INTEGER
Number of get hold unique requests processed against the
physical database. From A18EGHU.
GET_NEXT_PARENT_RQ
INTEGER
Number of get next in parent requests processed against the
physical database. From A18EGNP.
GET_NEXT_REQ
INTEGER
Number of get next requests processed against the physical
database. From A18EGN.
GET_UNIQUE_REQ
INTEGER
Number of get unique requests processed against the physical
database. From A18EGU.
INSERT_REQ
INTEGER
Number of insert requests. From A18EISR.
POOL_DMB_PEAK
INTEGER
Peak number of bytes used from the DMB pool. From
A18DMBMU.
POOL_DMB_SIZE_BYTE
INTEGER
Maximum number of bytes in the DMB pool. From
A18DMBMS.
POOL_DMB_WAITS
INTEGER
Number of times a DMB pool request exceeded the number of
bytes available in the pool. From A18DMBEX.
POOL_ENQ_PEAK
INTEGER
Peak number of bytes used from the ENQ pool during the
entire CICS session. From A18ENQMU.
POOL_ENQ_SIZE_BYTE
INTEGER
Maximum number of bytes in the ENQ pool. From
A18ENQMS.
POOL_PSB_PEAK
INTEGER
Peak number of bytes used from the PSB pool. From
A18PSBMU.
POOL_PSB_SIZE_BYTE
INTEGER
Maximum number of bytes in the PSB pool. From A18PSBMS.
POOL_PSB_WAITS
INTEGER
Number of times a PSB pool request exceeded the number of
bytes available in the pool. From A18PSBEX.
RECORDS
INTEGER
Number of records with a valid value for the number of
threads in use.
REPLACE_REQ
INTEGER
Number of replace requests. From A18EREP.
REQUESTS
INTEGER
Number of calls on the database. From A18LTOT.
THREADS
INTEGER
Maximum number of threads, specified in the DLTHRED SIT
parameter. From A18THRDS.
THREADS_IN_USE
INTEGER
Total number of DL/I threads in use. This is a work field.
Divide by RECORDS to get the average number of current
threads in use. From A18THRDA.
DBD_NAME
168
K
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
THREADS_USED_PEAK
INTEGER
Peak number of DL/I threads used during the entire CICS
session. From A18THRDM.
THREADS_WAITS
INTEGER
Number of times a DL/I thread was waiting during the entire
CICS session. From A18THRDW.
CICS_S_DSPOOL_T
This table provides detailed data from the dispatcher TCB pool statistic section.
The data is from CICS statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF.
idd:break>From SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TCB_POOL_NUM
K
INTEGER
TCB Pool Number. From DSGTPOON.
CUR_MISM_WAIT
REAL
Current Mismatch Waits. From DSGCUMIW.
CUR_NUM_TASK
REAL
Current num of task wait for a TCB. From DSGCURWA.
CUR_TCB_ATTACH
REAL
Current TCBs attached. From DSGCURAT.
CUR_TCB_IN_USE
REAL
Current TCBs in use. From DSGCURUS.
CUR_WAIT_TIME
CHAR(8)
Current waiting time. From DSGCUWAT.
DISPATCHER_START
TIMESTAMP
Time (GMT) when the dispatcher started. It is the approximate
time when CICS started. From DSGSTART.
DISPATCHER_START_L
TIMESTAMP
Local time when the dispatcher started. It is the approximate
time when CICS started. For CICS V4 and later. From
DSGLSTRT.
ELAPS_JSTEP_SEC
REAL
Total CPU time for all TCBs in this address space,
accumulated during the interval. From DSGJEST.
ICVT_MSEC
INTEGER
ICV time, in milliseconds. From DSGICVT.
MAX_TCB_POOL_LIM
REAL
Max TCB Pool Limiter. From DSGMAXPT.
MISM_WAIT_TIME
CHAR(8)
Mismatch Wait Time. From DSGPOMIT.
MVS_REQS_TOT
FLOAT
The total number of MVS storage requests. From
DSGTOTMW.
MVS_REQS_TIME_TOT
FLOAT
The total time spent in MVS storage waits. From DSGTOTMT.
NO_MAX_TCB_LIM
REAL
Number of times at Max TCB pool limit. From DSGTPOOL.
NO_TCB_MISMATCH
REAL
Number of TCB Mismatch Waits. From DSGPOMIW.
NUM_WAIT_TCB_LIM
REAL
Total number of waits Max TCB pool limit. From DSGTOTLI.
PEAK_MISM_WAIT
REAL
The peak mismatch wait. From DSGPEMIW.
Chapter 6. Data tables, lookup tables, and control tables
169
CICS statistics component data tables
Column name
Data type
Description
PEAK_NUM_TASK
REAL
Peak number of task wait for a TCB. From DSGPEAWA.
PEAK_TCB_ATTAC
REAL
Peak TCBs attached. From DSGPEAAT.
PEAK_TCB_IN_USE
REAL
Peak TCBs in use. From DSGPEAUS.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record. Example:
0330. From SMFSTRVN.
SRB_CPU_SEC
REAL
Total CPU time for all service request blocks (SRB) executed in
this address space, accumulated during the interval. From
DSGSRBT.
WAIT_MAX_TCB_LIM
CHAR(8)
Total Wait time at Max TCB pool limit. From DSGTOWAL.
CICS_S_DSPOOL_D
This table provides daily user DRLFPROF data from the dispatcher TCB pool
statistic section. The data is from CICS statistics records (SMF 110, subtype 2).
The default retention period for this table is 30 days.
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TCB_POOL_NUM
K
INTEGER
TCB Pool Number. From DSGTPOON.
CUR_MISM_WAIT
REAL
Current Mismatch Waits. From DSGCUMIW.
CUR_MISM_WAIT_T
CHAR(8)
Current Mismatch Wait Time. From DSGCUMIT.
CUR_NUM_TASK
REAL
Current number of task wait for a TCB. From DSGCURWA.
CUR_TCB_ATTACH
REAL
Current TCBs attached. From DSGCURAT.
CUR_TCB_IN_USE
REAL
Current TCBs in use. From DSGCURUS.
CUR_WAIT_TIME
CHAR(8)
Current waiting time. From DSGCUWAT.
DISPATCHER_START
TIMESTAMP
Time (GMT) when the dispatcher started. It is the approximate
time when CICS started. From DSGSTART.
DISPATCHER_START_L
TIMESTAMP
Local time when the dispatcher started. It is the approximate
time when CICS started. For CICS V4 and later. From
DSGLSTRT.
ELAPS_JSTEP_SEC
REAL
Total CPU time for all TCBs in this address space,
accumulated during the interval. From DSGJEST.
ICVR_MSEC
INTEGER
The current ICVR time. From DSGICVRT.
170
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
ICVT_MSEC
INTEGER
ICV time, in milliseconds. From DSGICVT.
MAX_TCB_POOL_LIM
REAL
Max TCB Pool Limiter. From DSGMAXPT.
MISM_WAIT_TIME
CHAR(8)
Mismatch Wait Time. From DSGPOMIT.
MVS_REQS_TOT
REAL
The total number of MVS storage requests. From
DSGTOTMW.
MVS_REQS_TIME_TOT
REAL
The total time spent in MVS storage waits. From DSGTOTMT.
MVS_TCB_P_COUNT
INTEGER
The current number of TCB pools. From DSGTCPOS.
NO_MAX_TCB_LIM
REAL
Number of times at Max TCB pool limit. From DSGTPOOL.
NO_TCB_MISMATCH
REAL
Number of TCB Mismatch Waits. From DSGPOMIW.
NUM_WAIT_TCB_LIM
REAL
Total number of waits Max TCB pool limit. From DSGTOTLI.
PEAK_MISM_WAIT
REAL
This is the peak mismatch wait. From DSGPEMIW.
PEAK_NUM_TASK
REAL
Peak number of task waits for a TCB. From DSGPEAWA.
PEAK_TCB_ATTAC
REAL
Peak TCBs attached. From DSGPEAAT.
PEAK_TCB_IN_USE
REAL
Peak TCBs in use. From DSGPEAUS.
SRB_CPU_SEC
REAL
Total CPU time for all service request blocks (SRB) executed in
this address space, accumulated during the interval. From
DSGSRBT.
WAIT_MAX_TCB_LIM
CHAR(8)
Total Wait time at Max TCB pool limit. From DSGTOWAL.
CICS_S_DUMP_T
This table provides detailed CICS dump statistics. It maps the system and
transaction dump statistics at the specific (not global) level. For CICS/ESA and
CICS/TS, this maps the DFHSDGDS, DFHSDRDS, DFHTDGDS, and DFHTDRDS
records.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SYSTEM_OR_TRANSACT
K
CHAR(8)
System or transaction dump. It contains SYSTEM if STID=85
and TRANSACT if STID=88.
DUMP_CODE
K
CHAR(8)
Dump code. From SDRCODE if STID=85 and from
TDRCODE if STID=88.
INTEGER
Number of dumps. From TDRTTKN (for transaction dumps)
or from SDRSTKN (for system dumps).
DUMPS
Chapter 6. Data tables, lookup tables, and control tables
171
CICS statistics component data tables
Column name
Data type
Description
DUMPS_DUE2T
INTEGER
Number of system dumps forced by transaction dumps. From
TDRSTKN. This is always zero for system dumps.
DUMPS_DUE2T_SUPPR
INTEGER
Number of suppressed system dumps that were forced by
transaction dumps. From TDRSSUPR. This is always zero for
system dumps.
DUMPS_SUPPR
INTEGER
Number of dumps suppressed. From TDRTSUPR (for
transaction dumps) or SDRSSUPR (for system dumps).
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
CICS_S_DUMP_D
This table provides daily CICS dump statistics. It maps the system and transaction
dump statistics at the specific (not global) level. It contains summarized data from
the CICS_S_DUMP_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Derived from fields SMFSTSID, SMFSTDTE and SMFSTTME
using the PERIOD function
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. VTAM application ID used when
requesting a session with this CICS system. From
SMFSTPRN.
SYSTEM_OR_TRANSACT
K
CHAR(8)
System or transaction dump. It contains ″SYSTEM″ if
STID=85 and ″TRANSACT″ if STID=88.
DUMP_CODE
K
CHAR(8)
Dump code. From SDRCODE if STID=85 and from
TDRCODE if STID=88.
DUMPS
INTEGER
Number of dumps. From TDRTTKN (for transaction dumps)
or from SDRSTKN (for system dumps).
DUMPS_DUE2T
INTEGER
Number of system dumps forced by transaction dumps. From
TDRSTKN. This is always zero for system dumps.
DUMPS_DUE2T_SUPPR
INTEGER
Number of suppressed system dumps that were forced by
transaction dumps. From TDRSSUPR. This is always zero for
system dumps.
DUMPS_SUPPR
INTEGER
Number of dumps suppressed. From TDRTSUPR (for
transaction dumps) or SDRSSUPR (for system dumps).
CICS_S_ENQUE_MGR_T
This table provides detailed CICS Enqueue Manager statistics. For CICS/TS V1.1
and later, this maps the DFHNQGDS record.
172
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
ENQ_POOL_ID
K
CHAR(8)
Enqueue pool ID. From NQGNPOOL for CICS/TS V1.1.
ENQ_ISSUED
FLOAT
Total number of enqueue requests issued. From NQGTNQSI
for CICS/TS V1.1.
ENQ_RETN_TOT
FLOAT
Total number of enqueue requests that were retained due to
the owning UOW being shunted. From NQGTNQSR for
CICS/TS V1.1.
ENQ_RETN_TOT_TIME
FLOAT
Total retention time for the enqueue requests that were
retained due to the owning UOW being shunted. From
NQGTNQRT for CICS/TS V1.1.
ENQ_RETN_CUR
FLOAT
Current number of enqueue requests that are retained. From
NQGCNQSR for CICS/TS V1.1.
ENQ_RETN_CUR_TIME
FLOAT
Current enqueue retention time. From NQGCNQRT for
CICS/TS V1.1.
ENQ_SYS_WAITED
FLOAT
Total number of sysplex enqueue requests that had waited
due to enqueues being held. From NQGGNQSW.
ENQ_SYS_WAITED_TM
FLOAT
Total waiting time for the sysplex enqueue requests that
waited (NQGGNQSW). From NQGGNQST.
ENQ_SYS_WAITING
FLOAT
Current number of sysplex enqueues that are waiting. From
NQGSNQSW.
ENQ_SYS_WAITING_TM
FLOAT
Total waiting time for the sysplex enqueues that are currently
waiting (NQGSNQSW). From NQGSNQWT.
ENQ_WAIT_REQ
FLOAT
Current number of enqueue requests that are waiting. From
NQGCNQSW for CICS/TS V1.1.
ENQ_WAIT_REQ_TIME
FLOAT
Total waiting time for the enqueue requests that are currently
waiting due to the enqueue being held by another transaction.
From NQGCNQWT for CICS/TS V1.1.
ENQ_WAITED
FLOAT
Total number of enqueue requests that have waited due to the
enqueues being held. This value is a subset of the total
number of enqueue requests (NQGTNQSI). From
NQGTNQSW for CICS/TS V1.1.
ENQ_WAITED_TIME
FLOAT
Total waiting time for the enqueue requests that waited. From
NQGTNQWT.
TOT_REJECT_ENQBUSY
FLOAT
Total number of enqueue requests that were immediately
rejected due to the enqueue being busy (ENQBUSY response).
This value is a subset of the total number of enqueue requests
(NQGTNQSI). From NQGTIRJB for CICS/TS V1.1.
Chapter 6. Data tables, lookup tables, and control tables
173
CICS statistics component data tables
Column name
Data type
Description
TOT_REJECT_ENQRETN
FLOAT
Total number of enqueue requests that were immediately
rejected due to the enqueue being in a retained state. This
value is a subset of the total number of enqueue requests
(NQGTNQSI). From NQGTIRJR for CICS/TS V1.1.
TOT_WAITREJ_RETAIN
FLOAT
Total number of waiting enqueue requests that were rejected
due to the required enqueue moving into a retained state. This
value is a subset of the number of enqueue requests that
waited (NQGTNQSW). From NQGTWRJR for CICS/TS V1.1.
TOT_WAITPURGE_OPER
FLOAT
Total number of waiting enqueue requests that were rejected
due to the operator purging the waiting transaction. This
value is a subset of the number of enqueue requests that
waited (NQGTNQSW). From NQGTWPOP for CICS/TS V1.1.
TOT_WAITPURGE_TOUT
FLOAT
Total number of waiting enqueue requests that were rejected
due to the timeout value (DTIMEOUT) being exceeded. This
value is a subset of the number of enqueue requests that
waited (NQGTNQSW). From NQGTWPTO for CICS/TS V1.1.
CICS_S_ENQUE_MGR_D
This table provides daily CICS Enqueue Manager statistics. For CICS/TS V1.1 and
later, this maps the DFHNQGDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
ENQ_POOL_ID
K
CHAR(8)
Enqueue pool ID. From NQGNPOOL for CICS/TS V1.1.
ENQ_ISSUED
FLOAT
Total number of enqueue requests issued. From NQGTNQSI
for CICS/TS V1.1.
ENQ_RETN_TOT
FLOAT
Total number of enqueue requests that were retained due to
the owning UOW being shunted. From NQGTNQSR for
CICS/TS V1.1.
ENQ_RETN_TOT_TIME
FLOAT
Total retention time for the enqueue requests that were
retained due to the owning UOW being shunted. From
NQGTNQRT for CICS/TS V1.1.
ENQ_RETN_CUR
FLOAT
Current number of enqueue requests that are retained. From
NQGCNQSR for CICS/TS V1.1.
ENQ_RETN_CUR_TIME
FLOAT
Current enqueue retention time. From NQGCNQRT for
CICS/TS V1.1.
ENQ_SYS_WAITED
FLOAT
Total number of sysplex enqueue requests that had waited
due to enqueues being held. From NQGGNQSW.
ENQ_SYS_WAITED_TM
FLOAT
Total waiting time for the sysplex enqueue requests that
waited (NQGGNQSW). From NQGGNQST.
174
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
ENQ_SYS_WAITING
FLOAT
Current number of sysplex enqueues that are waiting. From
NQGSNQSW.
ENQ_SYS_WAITING_TM
FLOAT
Total waiting time for the sysplex enqueues that are currently
waiting (NQGSNQSW). From NQGSNQWT.
ENQ_WAIT_REQ
FLOAT
Current number of enqueue requests that are waiting. From
NQGCNQSW for CICS/TS V1.1.
ENQ_WAIT_REQ_TIME
FLOAT
Total waiting time for the enqueue requests that are currently
waiting due to the enqueue being held by another transaction.
From NQGCNQWT for CICS/TS V1.1.
ENQ_WAITED
FLOAT
Total number of enqueue requests that have waited due to the
enqueues being held. This value is a subset of the total
number of enqueue requests (NQGTNQSI). From
NQGTNQSW for CICS/TS V1.1.
ENQ_WAITED_TIME
FLOAT
Total waiting time for the enqueue requests that waited. From
NQGTNQWT.
TOT_REJECT_ENQBUSY
FLOAT
Total number of enqueue requests that were immediately
rejected due to the enqueue being busy (ENQBUSY response).
This value is a subset of the total number of enqueue requests
(NQGTNQSI). From NQGTIRJB for CICS/TS V1.1.
TOT_REJECT_ENQRETN
FLOAT
Total number of enqueue requests that were immediately
rejected due to the enqueue being in a retained state. This
value is a subset of the total number of enqueue requests
(NQGTNQSI). From NQGTIRJR for CICS/TS V1.1.
TOT_WAITREJ_RETAIN
FLOAT
Total number of waiting enqueue requests that were rejected
due to the required enqueue moving into a retained state. This
value is a subset of the number of enqueue requests that
waited (NQGTNQSW). From NQGTWRJR for CICS/TS V1.1.
TOT_WAITPURGE_OPER
FLOAT
Total number of waiting enqueue requests that were rejected
due to the operator purging the waiting transaction. This
value is a subset of the number of enqueue requests that
waited (NQGTNQSW). From NQGTWPOP for CICS/TS V1.1.
TOT_WAITPURGE_TOUT
FLOAT
Total number of waiting enqueue requests that were rejected
due to the timeout value (DTIMEOUT) being exceeded. This
value is a subset of the number of enqueue requests that
waited (NQGTNQSW). From NQGTWPTO for CICS/TS V1.1.
CICS_S_ENTBEANS_T,_D
This tables provides detailed data about resources used for each bean. The data is
from CICS statistics records (SMF 110, subtype 2).
The default retention periods for these tables are:
7 days for CICS_S_ENTBEANS_T
30 days for CICS_S_ENTBEANS_D
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
Chapter 6. Data tables, lookup tables, and control tables
175
CICS statistics component data tables
Column name
Data type
Description
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFSTPRN.
EJB_CORBASERVER_NM
K
CHAR(4)
Name of the CorbaServer in which the bean is installed.
From EJBCORBASVNM.
EJB_BEAN_NM
K
VARCHAR(222)
Name of the bean. From EJBBEANNAME.
EJB_ACT_COUNT
FLOAT
Number of times a bean of this type has been activated.
From EJBACTINUM.
EJB_CREATES_COUNT
FLOAT
Number of times a bean of this type has been created. From
EJBCREATES.
EJB_DJAR_NM
CHAR(32)
Name of the DJar from which this bean originated. From
EJBDJARNAME.
EJB_METCALLS_COUNT
FLOAT
Number of times a remote method call has been invoked
against a bean of this type. From EJBMETHCAL.
EJB_PASS_COUNT
FLOAT
Number of times a bean of this type has been passivated.
From EJBPASSNUM.
EJB_REMOVES_COUNT
FLOAT
Number of times a bean of this type has been removed.
From EJBREMOVES.
CICS_S_FEPI_T
This table provides detailed statistics for the CICS Front End Programming
Interface (FEPI). It contains data about the use of each FEPI pool, a target in any
pool, and each connection. The data is from CICS statistics records (SMF 110,
subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
POOL_NAME
K
CHAR(8)
FEPI pool name. From A22POOL, A23POOL or A24POOL.
TARGET_NAME
K
CHAR(8)
FEPI target pool name. From A23TARG or A24TARG.
NODE_NAME
K
CHAR(8)
FEPI node. From A23NODE.
VTAM_APPL_ID
K
CHAR(8)
This is the VTAM applid for the target. From A24APPL.
176
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
ALLOC_COUNT
INTEGER
Number of conversations that have been allocated from this
pool, or the number of conversations specifically allocated to
this target in this pool. From A22ALLOC or A24ALLOC.
ALLOC_PEAK
INTEGER
Peak number of concurrent conversations allocated from this
pool. From A22PKALL.
ALLOC_TIMEOUT_CNT
INTEGER
Number of conversation allocates that timed out in this pool, or
the number of conversation allocates to this target in this pool
that timed out. From A22TIOUT or A24TIOUT.
ALLOC_WAIT_COUNT
INTEGER
Current number of conversations waiting to be allocated in this
pool, or the number of current conversations waiting to be
allocated to this target in this pool. From A22WAIT or
A24WAIT.
ALLOC_WAIT_PEAK
INTEGER
Peak number of conversations that had to wait to be allocated
in this pool or the peak number of conversations that had to
wait to be allocated to this target in this pool. From A22PKWT
or A24PKWT.
ALLOC_WAIT_TOTAL
INTEGER
Number of conversations that had to wait to be allocated in
this pool, or the number of conversations that had to wait to be
allocated to this target in this pool. From A22TOTWT or
A24TOTWT.
CHARS_RECEIVED_CNT
INTEGER
Number of characters of data received on this connection. From
A23CHIN.
CHARS_SENT_CNT
INTEGER
Number of characters of data sent on this connection. From
A23CHOUT.
CONN_ACQUIRE_CNT
INTEGER
Number of times the connection was acquired. From A23ACQ.
CONN_CONV_USE_CNT
INTEGER
Number of conversations that have used this connection. From
A23CNV.
CONNECTION_COUNT
INTEGER
Number of connections in the pool. From A22CONCT.
CONNECTION_PEAK
INTEGER
Peak number of connections in the pool. This column is needed
because targets and nodes may be deleted between intervals.
From A22CONPK.
ERROR_COUNT
INTEGER
Number of VTAM error conditions raised for this connection.
From A23ERROR.
NODE_COUNT
INTEGER
Current number of nodes in the pool or number of nodes
connected to this target. From A22NDCT or A24NDCT.
RECEIVE_TO_CNT
INTEGER
Number of times a FEPI RECEIVE timed-out on this
connection. From A23RTOUT.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS version and release that wrote this record; for example,
0410. From SMFSTRVN.
TARGET_COUNT
INTEGER
Current number of targets in the pool. From A22TRGCT.
UNSOL_INPUT_CNT
INTEGER
Number of times unsolicited input was received on this
connection. From A23USI.
Chapter 6. Data tables, lookup tables, and control tables
177
CICS statistics component data tables
CICS_S_FEPI_D
This table provides daily statistics for the CICS Front End Programming Interface
(FEPI). It contains data about the use of each FEPI pool, a target in any pool, and
each connection. The data is from CICS statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
POOL_NAME
K
CHAR(8)
FEPI pool name. From A22POOL, A23POOL or A24POOL.
TARGET_NAME
K
CHAR(8)
FEPI target pool name. From A23TARG or A24TARG.
NODE_NAME
K
CHAR(8)
FEPI node. From A23NODE.
VTAM_APPL_ID
K
CHAR(8)
VTAM applid for the target. From A24APPL.
ALLOC_COUNT
INTEGER
Number of conversations that have been allocated from this
pool, or the number of conversations specifically allocated to
this target in this pool. From A22ALLOC or A24ALLOC.
ALLOC_PEAK
INTEGER
Peak number of concurrent conversations allocated from this
pool. From A22PKALL.
ALLOC_TIMEOUT_CNT
INTEGER
Number of conversation allocates that timed out in this pool,
or the number of conversation allocates to this target in this
pool that timed out. From A22TIOUT or A24TIOUT.
ALLOC_WAIT_PEAK
INTEGER
Peak number of conversations that had to wait to be allocated
in this pool, or the peak number of conversations that had to
wait to be allocated to this target in this pool. From A22PKWT
or A24PKWT.
ALLOC_WAIT_TOTAL
INTEGER
Number of conversations that had to wait to be allocated in
this pool, or the number of conversations that had to wait to
be allocated to this target in this pool. From A22TOTWT or
A24TOTWT.
CHARS_RECEIVED_CNT
INTEGER
Number of characters of data received on this connection.
From A23CHIN.
CHARS_SENT_CNT
INTEGER
Number of characters of data sent on this connection. From
A23CHOUT.
CONN_ACQUIRE_CNT
INTEGER
Number of times the connection was acquired. From A23ACQ.
CONN_CONV_USE_CNT
INTEGER
Number of conversations that have used this connection. From
A23CNV.
CONNECTION_PEAK
INTEGER
This is the peak number of connections in the pool. This
column is needed because targets and nodes may be deleted
between intervals. From A22CONPK.
ERROR_COUNT
INTEGER
Number of VTAM error conditions raised for this connection.
From A23ERROR.
RECEIVE_TO_CNT
INTEGER
Number of times a FEPI RECEIVE timed-out on this
connection. From A23RTOUT.
178
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
UNSOL_INPUT_CNT
INTEGER
Number of times unsolicited input was received on this
connection. From A23USI.
CICS_S_FILE_T
This table provides detailed file statistics. The data is from CICS statistics records
(SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
FLOAT
Is the No. Exclusive Control conflicts. From A17FCXCC.
CHAR(8)
Name of the file. From A17FNAM.
ADD_REQUESTS
INTEGER
Number of PUT requests issued. From A17DSWRA.
BASE_DATASET_NAME
CHAR(44)
Base data set name for VSAM paths. For CICS V4 and later.
From A17BDSNM.
BROWSE_REQUESTS
INTEGER
Number of GETNEXT and GETPREV requests issued. From
A17DSBR.
BRWS_UPD_REQUESTS
FLOAT
Number of browse READNEXT and READPREV requests
issued against this file. Note that this field is only applicable
to RLS accessed files. For CICS/TS V1.1 and later. From
A17DSBRU.
CICS_SYSTEM_ID_REM
CHAR(4)
When operating in an ISC or MRO environment, and the file
is held by a remote system, this column specifies the system
where the file is resident. For CICS V4 and later. From
A17RSYS.
CFDT_POOL_NAME
CHAR(8)
Coupling facility data table (CFDT) pool name. From
A17DTCFP.
DATA_BUFF_CNT
INTEGER
Number of buffers to be used for data. For CICS V4 and later.
From A17DSDNB.
DATASET_NAME
CHAR(44)
44-character data set name, or blank if no data set is allocated.
From A17DSNAM.
DATASET_TYPE
CHAR(1)
This is the data set type. B=BDAM, E=VSAM ESDS, K=VSAM
KSDS, R=VSAM RRDS and P=VSAM PATH. For CICS V4 and
later. From A17DSTYP.
DELETE_REQ_LOCAL
INTEGER
Number of DELETE requests against this local file. From
A17DSDEL.
DELETE_REQ_REMOTE
INTEGER
Number of DELETE requests for a VSAM file in a remote
system. From A17RMDEL.
EXCL_CNTL_CONF
FILE_NAME
K
Chapter 6. Data tables, lookup tables, and control tables
179
CICS statistics component data tables
Column name
Data type
Description
FILE_CLOSED_TIME
TIME
Local time when the file was closed. From A17CLOST.
FILE_CLOSE_GMT
TIME
GMT time, in hh:mm:ss format, when this file was closed. Set
to 00:00:00 if not closed. For CICS V4 and later. From
A17GCLST.
FILE_CLOSE_TIME
TIME
Local time, in hh:mm:ss format, when this file was closed. Set
to 00:00:00 if not closed. For CICS V4 and later. From
A17LCLST.
FILE_NAME_REMOTE
CHAR(8)
Name by which this file is known in the system or region in
which it is resident. For CICS V4 and later. From A17RNAME.
FILE_OPENED_TIME
TIME
Local time when the file was opened. From A17OPENT.
FILE_OPEN_GMT
TIME
GMT time, in hh:mm:ss format, when this file was opened. Set
to 00:00:00 if not opened. For CICS V4 and later. From
A17GOPNT.
FILE_OPEN_TIME
TIME
Local time, in hh:mm:ss format, when this file was opened.
Set to 00:00:00 if not opened. For CICS V4 and later. From
A17LOPNT.
GET_REQUESTS
INTEGER
Number of GET requests issued. From A17DSRD.
GET_UPDATE_REQ
INTEGER
Number of GET UPDATE requests issued. From A17DSGU.
INDX_BUFF_CNT
INTEGER
Number of buffers to be used for index. For CICS V4 and
later. From A17DSINB.
LOAD_RESPONSES
FLOAT
Number of times that a LOADING response was issued. From
A17DTLDS.
LOCK_WAITS
FLOAT
Number of times that it was necessary to WAIT for an already
locked name. From A17DTCON.
POOL_NUMBER
INTEGER
Identity of the local shared resource pool. This value is that
specified by the LSRPOOLID operand of the resource
definition online DEFINE FILE command. ’N’ means that it is
not defined in an LSR pool. For CICS V4 and later. From
A17POOL.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REMOTE_OR_LOCAL
CHAR(1)
Set to R if this is a remote file. From A17FLOC.
RLS_FILE_INDICATOR
CHAR(1)
Indicator of whether the file is RLS or not. The value can be R
(RLS accessed file) or a blank (non RLS file). For CICS/TS
V1.1 and later. From A17DSRLS.
RLS_REQ_TIMEOUTS
FLOAT
Number of RLS requests to this file that were not serviced in
the specified time limit and as a result were terminated. For
CICS/TS V1.1 and later. From A17RLSWT.
STORAGE_ALLOC
INTEGER
Total storage allocated for the data table, in kilobytes. From
A17DTALT.
STORAGE_ALLOC_DATA
INTEGER
Storage allocated for the record data. This is valid only if the
shared data tables feature is used. From A17DTALD.
STORAGE_ALLOC_ENT
INTEGER
Storage allocated for record entry blocks. This is valid only if
the shared data tables feature is used. From A17DTALE.
180
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
STORAGE_ALLOC_INDX
INTEGER
Storage allocated for the index. This is valid only if the shared
data tables feature is used. From A17DTALI.
STORAGE_IN_USE
INTEGER
Total storage in use for the data table. This is valid only if the
shared data tables feature is used. From A17DTUST.
STORAGE_IN_USE_DTA
INTEGER
Storage in use for the record data. This is valid only if the
shared data tables feature is used. From A17DTUSD.
STORAGE_IN_USE_ENT
INTEGER
Storage in use for record entry blocks. This is valid only if the
shared data tables feature is used. From A17DTUSE.
STORAGE_IN_USE_IDX
INTEGER
Storage in use for the index. This is valid only if the shared
data tables feature is used. From A17DTUSI.
STRINGS
INTEGER
Maximum permissible number of concurrent updates. For
CICS V4 and later. From A17STRNO.
STRINGS_ACTIVE_CNT
INTEGER
Current number of updates against the file. For CICS V4 and
later. From A17DSASC.
STRING_WAITS
INTEGER
Number of string waits. For CICS V4 and later. From
A17DSASW.
TAB_DELETES
INTEGER
Number of attempts to delete records from the table using
DELETE requests. From A17DTDLS.
TAB_FIELDS_PRESENT
CHAR(1)
R-remote file with table read and source read data. S-there is
data from an associated table. T-this is a data table. X-there is
an associated CICS-maintained data table. From A17DT.
TAB_READ_REQUESTS
INTEGER
Number of attempts to retrieve records from the table. From
A17DTRDS.
TAB_READ_RETRIES
INTEGER
Read retries because a file-only region changed the table
during the read. This is valid only if the shared data tables
feature is used. From A17DTRRS.
TAB_REC_NOT_FOUND
INTEGER
Number of times READ requests were directed to the source
data set because the record was not found in the table. From
A17DTRNF.
TAB_RECORDS
INTEGER
Number of records in the data table. This is valid only if the
shared data tables feature is used. From A17DTSIZ.
TAB_RECORDS_PEAK
INTEGER
Peak number of records in the table. From A17DTSHI.
TAB_REJECTS_EXIT
INTEGER
Number of records rejected by the global user exit. From
A17DTARJ.
TAB_REJECTS_FULL
INTEGER
Number of records that CICS attempted to add, but was
unable to because the table already contained the specified
maximum. From A17DTATF.
TAB_REWRITES
INTEGER
Number of attempts to update records in the table using
REWRITE requests. From A17DTRWS.
TAB_STATUS
CHAR(1)
Unsolicited data only. C-a CICS-maintained table is closed. P-a
file closed but table still open. S-a source data set for a user
table is being closed. U-a user-maintained table is closed.
From A17DTTYP.
TAB_WRITE_REQUESTS
INTEGER
Number of attempts to add records to the table using WRITE
requests. From A17DTADS.
TAB_WRITES_BY_READ
INTEGER
Number of writes caused by loading or READ requests while
loading. From A17DTAVR.
UPDATE_REQUESTS
INTEGER
Number of PUT UPDATE requests issued. From A17DSWRU.
Chapter 6. Data tables, lookup tables, and control tables
181
CICS statistics component data tables
Column name
Data type
Description
VSAM_EXCP_REQ_DATA
INTEGER
Number of data I/O operations on this VSAM file. From
A17DSXCP.
VSAM_EXCP_REQ_INDX
INTEGER
Number of index I/O operations on this VSAM file. From
A17DSIXP.
WAIT_ON_STRING
INTEGER
Number of requests queued because all the strings are in use.
From A17DSTSW.
WAIT_ON_STRNG_PEAK
INTEGER
Peak number of requests that were waiting for a string. From
A17DSHSW.
CICS_S_FILE_D
This table provides daily CICS file statistics. It contains consolidated data from the
CICS_S_FILE_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
FILE_NAME
K
CHAR(8)
Name of the file. From A17FNAM.
ADD_REQUESTS
INTEGER
Number of PUT requests issued. From A17DSWRA.
BROWSE_REQUESTS
INTEGER
Number of GETNEXT and GETPREV requests issued. From
A17DSBR.
BRWS_UPD_REQUESTS
FLOAT
Number of browse READNEXT and READPREV requests
issued against this file. Note that this field is only applicable to
RLS accessed files. For CICS/TS V1.1 and later. From
A17DSBRU.
CFDT_POOL_NAME
CHAR(8)
CFDT pool name. From A17DTCFP.
DATA_BUFF_CNT
INTEGER
Number of buffers to be used for data. For CICS V4 and later.
From A17DSDNB.
DELETE_REQ_LOCAL
INTEGER
Number of DELETE requests against this local file. From
A17DSDEL.
DELETE_REQ_REMOTE
INTEGER
Number of DELETE requests for a VSAM file in a remote
system. From A17RMDEL.
EXCL_CNTL_CONF
FLOAT
Is the No. Exclusive Control conflicts. From A17FCXCC.
GET_REQUESTS
INTEGER
Number of GET requests issued. From A17DSRD.
GET_UPDATE_REQ
INTEGER
Number of GET UPDATE requests issued. From A17DSGU.
INDX_BUFF_CNT
INTEGER
Number of buffers to be used for index. For CICS V4 and later.
From A17DSINB.
LOAD_RESPONSES
FLOAT
Number of times that a LOADING response was issued. From
A17DTLDS.
182
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
LOCK_WAITS
FLOAT
Number of times that it was necessary to WAIT for an already
locked name. From A17DTCON.
RLS_FILE_INDICATOR
CHAR(1)
Indicator of whether the file is RLS or not. The value can be R
(RLS accessed file) or a blank (non RLS file). For CICS/TS V1.1
and later. From A17DSRLS.
RLS_REQ_TIMEOUTS
FLOAT
Number of RLS requests to this file that were not serviced in
the specified time limit and as a result were terminated. For
CICS/TS V1.1 and later. From A17RLSWT.
STORAGE_ALLOC
INTEGER
Total storage allocated for the data table, in kilobytes. From
A17DTALT.
STORAGE_ALLOC_DATA
INTEGER
Storage allocated for the record data. This is valid only if the
shared data tables feature is used. From A17DTALD.
STORAGE_ALLOC_ENT
INTEGER
Storage allocated for record entry blocks. This is valid only if
the shared data tables feature is used. From A17DTALE.
STORAGE_ALLOC_INDX
INTEGER
Storage allocated for the index. This is valid only if the shared
data tables feature is used. From A17DTALI.
STORAGE_IN_USE
INTEGER
Total storage in use for the data table. This is valid only if the
shared data tables feature is used. From A17DTUST.
STORAGE_IN_USE_DTA
INTEGER
Storage in use for the record data. This is valid only if the
shared data tables feature is used. From A17DTUSD.
STORAGE_IN_USE_ENT
INTEGER
Storage in use for record entry blocks. This is valid only if the
shared data tables feature is used. From A17DTUSE.
STORAGE_IN_USE_IDX
INTEGER
Storage in use for the index. This is valid only if the shared
data tables feature is used. From A17DTUSI.
STRINGS
INTEGER
Maximum permissible number of concurrent updates. For CICS
V4 and later. From A17STRNO.
TAB_DELETES
INTEGER
Number of attempts to delete records from the table using
DELETE requests. From A17DTDLS.
TAB_READ_REQUESTS
INTEGER
Number of attempts to retrieve records from the table. From
A17DTRDS.
TAB_READ_RETRIES
INTEGER
Read retries because a file-only region changed the table during
the read. This is valid only if the shared data tables feature is
used. From A17DTRRS.
TAB_REC_NOT_FOUND
INTEGER
Number of times READ requests were directed to the source
data set because the record was not found in the table. From
A17DTRNF.
TAB_RECORDS
INTEGER
Number of records in the data table. This is valid only if the
shared data tables feature is used. From A17DTSIZ.
TAB_RECORDS_PEAK
INTEGER
Peak number of records in the table. From A17DTSHI.
TAB_REJECTS_EXIT
INTEGER
Number of records rejected by the global user exit. From
A17DTARJ.
TAB_REJECTS_FULL
INTEGER
Number of records that CICS attempted to add, but was unable
to because the table already contained the specified maximum.
From A17DTATF.
TAB_REWRITES
INTEGER
Number of attempts to update records in the table using
REWRITE requests. From A17DTRWS.
TAB_WRITE_REQUESTS
INTEGER
Number of attempts to add records to the table using WRITE
requests. From A17DTADS.
Chapter 6. Data tables, lookup tables, and control tables
183
CICS statistics component data tables
Column name
Data type
Description
TAB_WRITES_BY_READ
INTEGER
Number of writes caused by loading or READ requests whilst
loading. From A17DTAVR.
UPDATE_REQUESTS
INTEGER
Number of PUT UPDATE requests issued. From A17DSWRU.
VSAM_EXCP_REQ_DATA
INTEGER
Number of data I/O operations on this VSAM file. From
A17DSXCP.
VSAM_EXCP_REQ_INDX
INTEGER
Number of index I/O operations on this VSAM file. From
A17DSIXP.
WAIT_ON_STRING
INTEGER
Number of requests queued because all the strings are in use.
From A17DSTSW.
WAIT_ON_STRNG_PEAK
INTEGER
Peak number of requests that were waiting for a string. From
A17DSHSW.
CICS_S_GLB_TCPIP_T
This table provides detailed global statistics on TCP/IP. It contains data from CICS
statistics records (SMF 110, subtype 2 stid 107). For CICS/TS V3.1 and later, it takes
information from the DFHSOGDS CICS dsect.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME. (For _T table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SSLCACHE_SETTING
CHAR(8)
Indicates the setting for the SSLCACHE system initialization
parameter, which specifies whether SSL is to use the local or
sysplex caching of session ids. Possible values are 'CICS’ or
'SYSPLEX’. From SOGSSLCA.
MAXSOCKETS
FLOAT
The maximum number of IP sockets that can be managed by
the CICS sockets domain. From SOGMAXSO.
MAXSOCKETS_REACHED
FLOAT
The number of times the maximum number of IP sockets limit
(MAXSOCKETS) was reached. From SOGTMAXS.
IN_SOCK_CUR
FLOAT
The current number of inbound sockets. From SOGCINSO.
IN_SOCK_PEAK
FLOAT
The peak number of non-persistent outbound sockets. From
SOGPOUSO.
OUT_SOCK_CUR
FLOAT
The current number of non-persistent outbound sockets. From
SOGCOUSO.
OUT_SOCK_PEAK
FLOAT
The peak number of non-persistent outbound sockets. From
SOGPOUSO.
OUT_PSOCK_CUR
FLOAT
The current number of persistent outbound sockets. From
SOGCPOUS.
184
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
OUT_PSOCK_PEAK
FLOAT
The peak number of persistent outbound sockets. From
SOGPPOUS.
IN_SOCK_CREATED
FLOAT
The total number of inbound sockets created. From SOGISCR.
OUT_SOCK_CREATED
FLOAT
The total number of outbound sockets created. From
SOGOSCR.
OUT_SOCK_CLOSED
FLOAT
The total number of outbound sockets closed. From SOGOSCL.
DLY_AT_MAXSOCKETS
FLOAT
The number of create socket requests that were delayed
because the system had reached the MAXSOCKETS limit. From
SOGDMAXS.
MAXSOCK_DLY_TIME
TIME
The total time that create socket requests were delayed because
the system had reached the MAXSOCKETS limit. From
SOGQTIMEMAXS.
TOUT_MAXSOCKETS
FLOAT
The number of create socket requests that were timed out
whilst delayed because the system had reached the
MAXSOCKETS limit. From SOGTOMAXS.
TOUT_MAXSOCK_CUR
FLOAT
The current number of create socket requests delayed because
the system is at the MAXSOCKETS limit. From SOGCDELAY.
TOUT_MAXSOCK_PEAK
FLOAT
The peak number of create socket requests delayed because the
system had reached the MAXSOCKETS limit. From
SOGPDELAY.
MAXSOCK_CURDLY_TIM
TIME
The total delay time for the create socket requests that are
currently delayed because the system is at the MAXSOCKETS
limit. From SOGCQTIMEMAXS.
CICS_S_GLB_TCPIP_D
This table provides daily global statistics on TCP/IP. It contains data from CICS
statistics records (SMF 110, subtype 2 stid 107). For CICS/TS V3.1 and later, it takes
information from the DFHSOGDS CICS dsect.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME. (For _T table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SSLCACHE_SETTING
CHAR(8)
Indicates the setting for the SSLCACHE system initialization
parameter, which specifies whether SSL is to use the local or
sysplex caching of session ids. Possible values are 'CICS’ or
'SYSPLEX’. From SOGSSLCA.
MAXSOCKETS
FLOAT
The maximum number of IP sockets that can be managed by
the CICS sockets domain. From SOGMAXSO.
Chapter 6. Data tables, lookup tables, and control tables
185
CICS statistics component data tables
Column name
Data type
Description
MAXSOCKETS_REACHED
FLOAT
The number of times the maximum number of IP sockets limit
(MAXSOCKETS) was reached. From SOGTMAXS.
IN_SOCK_CUR
FLOAT
The current number of inbound sockets. From SOGCINSO.
IN_SOCK_PEAK
FLOAT
The peak number of non-persistent outbound sockets. From
SOGPOUSO.
OUT_SOCK_CUR
FLOAT
The current number of non-persistent outbound sockets. From
SOGCOUSO.
OUT_SOCK_PEAK
FLOAT
The peak number of non-persistent outbound sockets. From
SOGPOUSO.
OUT_PSOCK_CUR
FLOAT
The current number of persistent outbound sockets. From
SOGCPOUS.
OUT_PSOCK_PEAK
FLOAT
The peak number of persistent outbound sockets. From
SOGPPOUS.
IN_SOCK_CREATED
FLOAT
The total number of inbound sockets created. From SOGISCR.
OUT_SOCK_CREATED
FLOAT
The total number of outbound sockets created. From
SOGOSCR.
OUT_SOCK_CLOSED
FLOAT
The total number of outbound sockets closed. From SOGOSCL.
DLY_AT_MAXSOCKETS
FLOAT
The number of create socket requests that were delayed
because the system had reached the MAXSOCKETS limit. From
SOGDMAXS.
MAXSOCK_DLY_TIME
TIME
The total time that create socket requests were delayed because
the system had reached the MAXSOCKETS limit. From
SOGQTIMEMAXS.
TOUT_MAXSOCKETS
FLOAT
The number of create socket requests that were timed out
whilst delayed because the system had reached the
MAXSOCKETS limit. From SOGTOMAXS.
TOUT_MAXSOCK_CUR
FLOAT
The current number of create socket requests delayed because
the system is at the MAXSOCKETS limit. From SOGCDELAY.
TOUT_MAXSOCK_PEAK
FLOAT
The peak number of create socket requests delayed because the
system had reached the MAXSOCKETS limit. From
SOGPDELAY.
MAXSOCK_CURDLY_TIM
TIME
The total delay time for the create socket requests that are
currently delayed because the system is at the MAXSOCKETS
limit. From SOGCQTIMEMAXS.
CICS_S_GLBURIMAP_T
This table provides detailed global statistics on URIMAP. It contains data from
CICS statistics records (SMF 110, subtype 2 stid 101). For CICS/TS V3.1 and later, it
takes information from the DFHWBGDS CICS dsect.).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
186
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME. (For _T table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
URIMAP_REF_COUNT
FLOAT
The number of times a search for matching URIMAP definition
was made. From WBGUREFCNT.
URIMAP_DISABLED
FLOAT
The Number of times a URIMAP definition with a matching
host and path was found, but the URIMAP definition was
disabled. From WBGUMATDISAB.
HOST_PATH_NOMATCH
FLOAT
The number of times a search for a matching URIMAP
definition was made, but no URIMAP definition with a
matching host and path was found. From WBGUNOMATCH.
HOST_PATH_MATCH
FLOAT
The number of times a search for a matching URIMAP
definition was made, and a URIMAP definition with a
matching host and path was found. From WBGUMATCH.
URIMAP_REDIRECTED
FLOAT
The number of times a URIMAP definition with a matching
host and path was found and the request was redirected. From
WBGUMATREDIR.
ANALYZER_USED
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and the analyzer program associated
with the TCPIPSERVICE definition was called. From
WBGUANCALL.
STAT_CONT_DELIVER
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and static content (document
template or HFS file) was delivered as a response. From
WBGUSTATCONT.
DYN_CONT_DELIVER
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and dynamic content (produced by
an application program) was delivered as a response. From
WBGUDYNCONT.
PIPELINE_REQS
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and the request was handled by a
Web service. From WBGUPIPEREQ.
SCHEME_HTTP_REQS
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, and the scheme was HTTP. From
WBGUSCHEMHTTP.
SCHEME_HTTPS_REQS
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, and the scheme was HTTPS (HTTP with
SSL). From WBGUSCHEMHTTPS.
SCHEME_WMQ_REQS
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, and the scheme was WMQ. From
WBGUSCHEMWMQ.
VHOST_DISABLED
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, but the virtual host was disabled. From
WBGUHOSTDISCNT.
Chapter 6. Data tables, lookup tables, and control tables
187
CICS statistics component data tables
CICS_S_GLBURIMAP_D
This table provides daily global statistics on URIMAP. It contains data from CICS
statistics records (SMF 110, subtype 2 stid 101). For CICS/TS V3.1 and later, it takes
information from the DFHWBGDS CICS dsect.).
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME. (For _T table only.)
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
URIMAP_REF_COUNT
FLOAT
The number of times a search for matching URIMAP definition
was made. From WBGUREFCNT.
URIMAP_DISABLED
FLOAT
The Number of times a URIMAP definition with a matching
host and path was found, but the URIMAP definition was
disabled. From WBGUMATDISAB.
HOST_PATH_NOMATCH
FLOAT
The number of times a search for a matching URIMAP
definition was made, but no URIMAP definition with a
matching host and path was found. From WBGUNOMATCH.
HOST_PATH_MATCH
FLOAT
The number of times a search for a matching URIMAP
definition was made, and a URIMAP definition with a
matching host and path was found. From WBGUMATCH.
URIMAP_REDIRECTED
FLOAT
The number of times a URIMAP definition with a matching
host and path was found and the request was redirected. From
WBGUMATREDIR.
ANALYZER_USED
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and the analyzer program associated
with the TCPIPSERVICE definition was called. From
WBGUANCALL.
STAT_CONT_DELIVER
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and static content (document
template or HFS file) was delivered as a response. From
WBGUSTATCONT.
DYN_CONT_DELIVER
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and dynamic content (produced by
an application program) was delivered as a response. From
WBGUDYNCONT.
PIPELINE_REQS
FLOAT
The number of times a URIMAP definition with a matching
host and path was found, and the request was handled by a
Web service. From WBGUPIPEREQ.
SCHEME_HTTP_REQS
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, and the scheme was HTTP. From
WBGUSCHEMHTTP.
188
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
SCHEME_HTTPS_REQS
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, and the scheme was HTTPS (HTTP with
SSL). From WBGUSCHEMHTTPS.
SCHEME_WMQ_REQS
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, and the scheme was WMQ. From
WBGUSCHEMWMQ.
VHOST_DISABLED
FLOAT
Number of times a URIMAP definition with a matching host
and path was found, but the virtual host was disabled. From
WBGUHOSTDISCNT.
CICS_S_GLOBAL_T
This table provides detailed statistics data on a global level from six statistics areas:
v VTAM
v Temporary storage
v Interregion communication (IRC) batch
v Loader
v Dynamic transaction backout (DTB)
v Task control
The table contains data from CICS/ESA and CICS/TS (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
STATISTICS_AREA
K
CHAR(12)
One of six strings derived from the CICS statistics record
read: VTAM, TEMP_STORAGE, LOADER, DTB,
TASK_CONTROL, or IRC_BATCH.
ACCUMULATED_TASKS
INTEGER
Number of tasks that this CICS job has run. From
A01KCTTA.
DFHRPL_REOPENED
INTEGER
Number of times the loader received an end-of-extent
condition. From LDGDREBS.
DTB_OVERFLOWS
INTEGER
Number of times the dynamic transaction backout overflow
mechanism was used. From A05DBSA.
DTB_RECORDS_LOGGED
INTEGER
Number of dynamic transaction backout records logged.
From A05DBLA.
JOBS_PEAK
INTEGER
Peak number of batch jobs sharing the database. From
A19EMCTH.
JOBS_SHARING_DB
INTEGER
Accumulated count of batch jobs that have shared the
database. From A19ETOTH.
Chapter 6. Data tables, lookup tables, and control tables
189
CICS statistics component data tables
Column name
Data type
Description
LIBRARY_LOAD_REQ
INTEGER
Number of times the loader has issued an MVS LOAD
request. From LDGLLR.
LOAD_SEC
FLOAT
Time taken for all the library loads, in seconds. From
LDGLLT.
LOAD_SEC_AVG
FLOAT
Average time to load a program, in seconds. Calculated as
LDGLLT/LDGLLR.
LU_LOGGED_ON_CNT
INTEGER
Current number of LUs in session. These types of LUs are
included: LU6.1 primaries and secondaries in session
(bound), LU6.2 primaries and secondaries in session (bound)
and VTAM terminals. For CICS V4 and later. From
A03LUNUM.
LU_LOGGED_ON_PEAK
INTEGER
Current highest number of LUs in session. These types of
LUs are included: LU6.1 primaries and secondaries in session
(bound), LU6.2 primaries and secondaries in session (bound)
and VTAM terminals. For CICS V4 and later. From
A03LUHWM.
NOT_USED_AVG_SEC
FLOAT
Average length of time a program is eligible for removal, in
seconds. Calculated as LDGDPSCT/LDGDPSCR.
NOT_USED_CDSA_KB
INTEGER
Current amount of CDSA storage which is occupied by
not-in-use programs. From LDGCNIU.
NOT_USED_DSA_KB
INTEGER
Current amount of DSA storage which is occupied by
not-in-use programs. CICS 3.2.1 only. From LDGESNIU.
NOT_USED_ECDSA_KB
INTEGER
Current amount of ECDSA storage which is occupied by
not-in-use programs. From LDGECNIU.
NOT_USED_EDSA_KB
INTEGER
Current amount of EDSA storage which is occupied by
not-in-use programs. CICS 3.2.1 only. From LDGDSNIU.
NOT_USED_ERDSA_KB
INTEGER
Current amount of ERDSA storage which is occupied by
not-in-use programs. From LDGERNIU.
NOT_USED_EUDSA_KB
INTEGER
Current amount of EUDSA storage which is occupied by
not-in-use programs. From LDGEUNIU.
NOT_USED_PROGRAMS
INTEGER
Number of programs in the not-in-use queue. From
LDGPNIU.
NOT_USED_RECLAIMS
INTEGER
Number of reclaims that CICS has made from the not-in-use
queue. From LDGRNIU.
NOT_USED_SEC
FLOAT
Time that all programs spend in the not-in-use queue, in
seconds. From LDGDPSCT.
NOT_USED_UDSA_KB
INTEGER
Current amount of UDSA storage which is occupied by
not-in-use programs. From LDGUNIU.
PROGRAMS_REMOVED
INTEGER
Number of program instances removed from storage. From
LDGDPSCR.
PROGRAM_USES
INTEGER
Number of uses of all programs by the CICS system. From
LDGPUSES.
PS_COUNT
INTEGER
Number of VTAM sessions that persisted. For CICS V4 and
later. From A03PSNC.
PS_ERROR_CNT
INTEGER
Number of persisting sessions that were already unbound
when CICS tried to restore them. For CICS V4 and later.
From A03PSEC.
PS_INQUIRE_COUNT
INTEGER
Number of times CICS issued INQUIRE OPTCD=PERSESS.
For CICS V4 and later. From A03PSIC.
190
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
PS_RESTORED_CNT
INTEGER
Number of persisting sessions that were successfully
restored. For CICS V4 and later. From A03PSOC.
PS_TERMINATED_CNT
INTEGER
Number of persisting sessions that were terminated. For
CICS V4 and later. From A03PSUC.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited),
EOD (End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REQ_PEAK_WAIT
INTEGER
Peak number of tasks waiting for the loader. From
LDGWLRHW.
REQ_TIMES_AT_PEAK
INTEGER
Number of times the peak number of waiting tasks was
reached. From LDGHWMT.
REQ_WAITED
INTEGER
Number of loader domain requests that were forced to
suspend. From LDGWTDLR.
REQ_WAITING
INTEGER
Number of loader domain requests currently forced to
suspend. From LDGWLR.
RPL_PEAK_USED
INTEGER
Peak number of VTAM RPLs posted. From A03RPLX.
RPL_TIMES_AT_PEAK
INTEGER
Number of times the peak number of posted VTAM RPLs
was reached. From A03RPLXT.
TRAN_CUR_ACTIVE
INTEGER
Current active user transactions. For CICS V4 and later. From
XMGCAT.
TRAN_CUR_QUEUED
INTEGER
Current queued user transactions. For CICS V4 and later.
From XMGCQT.
TRAN_CURRENT_Q_SEC
FLOAT
Total time, in seconds, spent by transactions currently
queued for MXT. From XMGCQTME.
TRAN_MXT
INTEGER
Current MAXTASK value. For CICS V4 and later. From
XMGMXT.
TRAN_PEAK_ACTIVE
INTEGER
Peak active user transactions. For CICS V4 and later. From
XMGPAT.
TRAN_PEAK_QUEUED
INTEGER
Peak queued user transactions. For CICS V4 and later. From
XMGPQT.
TRAN_TIMES_AT_MXT
INTEGER
Times at MAXTASK. For CICS V4 and later. From
XMGTAMXT.
TRAN_TOTAL_ACTIVE
INTEGER
Total active user transactions. For CICS V4 and later. From
XMGTAT.
TRAN_TOTAL_DELAYED
INTEGER
Total delayed user transactions. This does not include those
transactions currently queueing. For CICS V4 and later. From
XMGTDT.
TRAN_TOTAL_Q_SEC
FLOAT
Total time, in seconds, spent waiting by transactions that had
to queue for MXT but not including transactions currently
queued. For CICS V4 and later. From XMGTQTME.
TRAN_TOTAL_TASKS
FLOAT
Total number of transactions at the time of the last reset. For
CICS V4 and later. From XMGTNUM.
TS_AUX_CISIZE
INTEGER
Control interval size for the auxiliary temporary storage data
set, in bytes. From A12CSZ.
Chapter 6. Data tables, lookup tables, and control tables
191
CICS statistics component data tables
Column name
Data type
Description
TS_AUX_GETS
INTEGER
Number of records that application programs have obtained
from auxiliary temporary storage. From A12NAG.
TS_AUX_LONGEST
INTEGER
Size of the longest record written, in bytes. From A12LAR.
TS_AUX_NOSPACE_CNT
INTEGER
Number of transaction suspensions because of a NOSPACE
condition on the auxiliary temporary storage data set. From
A12STA8F.
TS_AUX_PUTS
INTEGER
Number of records that application programs have written to
auxiliary temporary storage. From A12STA7F.
TS_BFR_COMPRESSES
INTEGER
Number of times temporary storage buffers were
compressed. From A12STA9F.
TS_BFR_CUR_WAITING
INTEGER
Current number of requests queued because no buffers are
available. From A12BUWT.
TS_BFR_PEAK_WAITS
INTEGER
Peak number of requests queued because no buffers were
available. From A12BUWTH.
TS_BFR_READS
INTEGER
Number of times a CI has to be read from disk. From
A12TRDN.
TS_BFRS_SPECIFIED
INTEGER
Number of temporary storage buffers. From A12NBCA.
TS_BFR_WAITS
INTEGER
Number of times a request was queued because all buffers
were allocated to other tasks. From A12BWTN.
TS_BFR_WRITES_FRC
INTEGER
Number of writes to the temporary storage data set because
of recovery. From A12TWTNR.
TS_BFR_WRITES_TOT
INTEGER
Number of writes to the temporary storage data set. From
A12TWTN.
TS_CI_AVAILABLE
INTEGER
Number of control intervals in the auxiliary temporary
storage data set. From A12NCI.
TS_CI_AVAIL_BYTES
INTEGER
Number of bytes available for use in the auxiliary temporary
storage control interval. From A12NAVB.
TS_CI_IN_USE_CNT
INTEGER
Current number of control intervals in use. From A12NCIA.
TS_CI_PEAK_USED
INTEGER
Peak number of control intervals in use. From A12NCIAH.
TS_CI_SEG_BYTES
INTEGER
Number of bytes per segment. From A12BPSEG.
TS_CI_SEGMENTS
INTEGER
Number of segments available in the auxiliary temporary
storage control interval. From A12SPCI.
TS_CISIZE_EXCEEDED
INTEGER
Number of writes of records whose length was greater than
the control interval. From A12STABF.
TS_FORMAT_WRITES
INTEGER
Number of times a new CI was successfully written at the
end of the data set. From A12TWTNF.
TS_IO_ERRORS
INTEGER
Number of IO errors which occurred on the temporary
storage data set. From A12STAAF.
TS_LONGEST_Q
INTEGER
Peak number of items in any one queue. From A12QINH.
TS_MAIN_CURR_BYTES
INTEGER
Current value, in bytes, of virtual storage used for temporary
storage. From A12STA6A.
TS_MAIN_GETS
INTEGER
Number of records that the application programs obtained
from main temporary storage. From A12NMG.
TS_MAIN_PEAK_BYTES
INTEGER
Peak value, in bytes, of virtual storage used for temporary
storage. From A12STA6F.
TS_MAIN_PUTS
INTEGER
Number of records that the application programs wrote to
main temporary storage. From A12STA5F.
192
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TS_MGSET_VALUE
INTEGER
Number of records held in a single temporary storage group
identifier, TSGID. FROM TSMGSET SIT parameter and
A12GIDNE.
TS_PEAK_Q_NAMES
INTEGER
Peak number of temporary storage queue names in use.
From A12QNUMH.
TS_Q_EXTENSIONS
INTEGER
Number of times it was necessary to create a TSGID
extension. From A12STA4F.
TS_Q_NAMES
INTEGER
Current number of temporary storage queue names in use.
From A12QNUM.
TS_QUEUES_CREATED
INTEGER
Number of times CICS created individual storage queues.
From A12STA3F.
TS_SHR_POOL_CONN
INTEGER
Number of shared TS pools currently connected in the TST.
From TSGSHPCN.
TS_SHR_POOL_DEF
INTEGER
Number of shared TS pools defined in the TST. From
TSGSHPDF.
TS_SHR_READ_REQS
INTEGER
Number of read requests to all shared TS pools. From
TSGSHRDS.
TS_SHR_WRITE_REQS
INTEGER
Number of write requests to all shared TS pools. From
TSGSHWTS.
TS_STRING_CUR_WAIT
INTEGER
Current number of IO requests that are queued because all
strings are in use. From A12VUWT.
TS_STRING_WAITS
INTEGER
Number of IO requests that were queued because no strings
were available. From A12VWTN.
TS_STRNG_PEAK_USED
INTEGER
Peak number of concurrent IO operations to the temporary
storage data set. From A12NVCAH.
TS_STRNG_PEAK_WAIT
INTEGER
Peak number of IO requests that were queued because all
strings were in use. From A12VUWTH.
TS_STRNG_SPECIFIED
INTEGER
Number of temporary storage strings. From A12NVCA.
VTAM_ACB_DYN_OPENS
INTEGER
Number of times the VTAM ACB was opened by the
operator.
VTAM_SOS_COUNT
INTEGER
Number of times VTAM was short on storage. From
A03VTSOS.
WAIT_TIME
FLOAT
Time spent waiting for the loader, in seconds. From
LDGTTW.
CICS_S_GLOBAL_D
This table provides daily CICS statistics data on a global level from six statistics
areas:
v VTAM
v Temporary storage
v Interregion communication (IRC) batch
v Loader
v Dynamic transaction backout (DTB)
v Task control
The table contains consolidated data from the CICS_S_GLOBAL_T table.
The default retention period for this table is 30 days.
Chapter 6. Data tables, lookup tables, and control tables
193
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
STATISTICS_AREA
K
CHAR(12)
One of six strings derived from the CICS statistics record read:
VTAM, TEMP_STORAGE, LOADER, DTB, TASK_CONTROL,
or IRC_BATCH.
ACCUMULATED_TASKS
INTEGER
Number of tasks that this CICS job has run. From A01KCTTA.
DFHRPL_REOPENED
INTEGER
Number of times the loader received an end-of-extent
condition. From LDGDREBS.
DTB_OVERFLOWS
INTEGER
Number of times the dynamic transaction backout overflow
mechanism was used. From A05DBSA.
DTB_RECORDS_LOGGED
INTEGER
Number of dynamic transaction backout records logged. From
A05DBLA.
JOBS_PEAK
INTEGER
Peak number of batch jobs sharing the database. From
A19EMCTH.
JOBS_SHARING_DB
INTEGER
Accumulated count of batch jobs that have shared the
database. From A19ETOTH.
LIBRARY_LOAD_REQ
INTEGER
Number of times the loader has issued an MVS LOAD
request. From LDGLLR.
LOAD_SEC
FLOAT
Time taken for all the library loads, in seconds. From LDGLLT.
LOAD_SEC_AVG
FLOAT
Average time to load a program, in seconds. Calculated as
LDGLLT/LDGLLR.
LU_LOGGED_ON_PEAK
INTEGER
Current highest number of LUs in session. These types of LUs
are included: LU6.1 primaries and secondaries in session
(bound), LU6.2 primaries and secondaries in session (bound)
and VTAM terminals. For CICS V4 and later. From
A03LUHWM.
NOT_USED_AVG_SEC
FLOAT
Average length of time a program is eligible for removal, in
seconds. Calculated as LDGDPSCT/LDGDPSCR.
NOT_USED_CDSA_KB
INTEGER
Current amount of CDSA storage which is occupied by
not-in-use programs. From LDGCNIU.
NOT_USED_DSA_KB
INTEGER
Current amount of DSA storage which is occupied by
not-in-use programs. CICS 3.2.1 only. From LDGESNIU.
NOT_USED_ECDSA_KB
INTEGER
Current amount of ECDSA storage which is occupied by
not-in-use programs. From LDGECNIU.
NOT_USED_EDSA_KB
INTEGER
Current amount of EDSA storage which is occupied by
not-in-use programs. CICS 3.2.1 only. From LDGDSNIU.
NOT_USED_ERDSA_KB
INTEGER
Current amount of ERDSA storage which is occupied by
not-in-use programs. From LDGERNIU.
NOT_USED_EUDSA_KB
INTEGER
Current amount of EUDSA storage which is occupied by
not-in-use programs. From LDGEUNIU.
NOT_USED_PROGRAMS
INTEGER
Number of programs in the not-in-use queue. From
LDGPNIU.
194
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
NOT_USED_RECLAIMS
INTEGER
Number of reclaims that CICS has made from the not-in-use
queue. From LDGRNIU.
NOT_USED_SEC
FLOAT
Time that all programs spend in the not-in-use queue, in
seconds. From LDGDPSCT.
NOT_USED_UDSA_KB
INTEGER
Current amount of UDSA storage which is occupied by
not-in-use programs. From LDGUNIU.
PROGRAMS_REMOVED
INTEGER
Number of program instances removed from storage. From
LDGDPSCR.
PROGRAM_USES
INTEGER
Number of uses of all programs by the CICS system. From
LDGPUSES.
PS_COUNT
INTEGER
Number of VTAM sessions that persisted. For CICS V4 and
later. From A03PSNC.
PS_ERROR_CNT
INTEGER
Number of persisting sessions that were already unbound
when CICS tried to restore them. For CICS V4 and later. From
A03PSEC.
PS_INQUIRE_COUNT
INTEGER
Number of times CICS issued INQUIRE OPTCD=PERSESS.
For CICS V4 and later. From A03PSIC.
PS_RESTORED_CNT
INTEGER
Number of persisting sessions that were successfully restored.
For CICS V4 and later. From A03PSOC.
PS_TERMINATED_CNT
INTEGER
Number of persisting sessions that were terminated. For CICS
V4 and later. From A03PSUC.
REQ_PEAK_WAIT
INTEGER
Peak number of tasks waiting for the loader. From
LDGWLRHW.
REQ_WAITED
INTEGER
Number of loader domain requests that were forced to
suspend. From LDGWTDLR.
REQ_WAITING
INTEGER
Number of loader domain requests currently forced to
suspend. From LDGWLR.
RPL_PEAK_USED
INTEGER
Peak number of VTAM RPLs posted. From A03RPLX.
TRAN_MXT
INTEGER
Current MAXTASK value. For CICS V4 and later. From
XMGMXT.
TRAN_PEAK_ACTIVE
INTEGER
Peak active user transactions. For CICS V4 and later. From
XMGPAT.
TRAN_PEAK_QUEUED
INTEGER
Peak queued user transactions. For CICS V4 and later. From
XMGPQT.
TRAN_TIMES_AT_MXT
INTEGER
Times at MAXTASK. For CICS V4 and later. From
XMGTAMXT.
TRAN_TOTAL_ACTIVE
INTEGER
Total active user transactions. For CICS V4 and later. From
XMGTAT.
TRAN_TOTAL_DELAYED
INTEGER
Total delayed user transactions. This does not include those
transactions currently queueing. For CICS V4 and later. From
XMGTDT.
TRAN_TOTAL_Q_SEC
FLOAT
Total time, in seconds, spent waiting by transactions that had
to queue for MXT but not including transactions currently
queued. For CICS V4 and later. From XMGTQTME.
TRAN_TOTAL_TASKS
FLOAT
Total number of transactions at the time of the last reset. For
CICS V4 and later. From XMGTNUM.
TS_AUX_CISIZE
INTEGER
Control interval size for the auxiliary temporary storage data
set, in bytes. From A12CSZ.
Chapter 6. Data tables, lookup tables, and control tables
195
CICS statistics component data tables
Column name
Data type
Description
TS_AUX_GETS
INTEGER
Number of records that application programs have obtained
from auxiliary temporary storage. From A12NAG.
TS_AUX_LONGEST
INTEGER
Size of the longest record written, in bytes. From A12LAR.
TS_AUX_NOSPACE_CNT
INTEGER
Number of transaction suspensions because of a NOSPACE
condition on the auxiliary temporary storage data set. From
A12STA8F.
TS_AUX_PUTS
INTEGER
Number of records that application programs have written to
auxiliary temporary storage. From A12STA7F.
TS_BFR_COMPRESSES
INTEGER
Number of times temporary storage buffers were compressed.
From A12STA9F.
TS_BFR_CUR_WAITING
INTEGER
Current number of requests queued because no buffers are
available. From A12BUWT.
TS_BFR_PEAK_WAITS
INTEGER
Peak number of requests queued because no buffers were
available. From A12BUWTH.
TS_BFR_READS
INTEGER
Number of times a CI has to be read from disk. From
A12TRDN.
TS_BFRS_SPECIFIED
INTEGER
Number of temporary storage buffers. From A12NBCA.
TS_BFR_WAITS
INTEGER
Number of times a request was queued because all buffers
were allocated to other tasks. From A12BWTN.
TS_BFR_WRITES_FRC
INTEGER
Number of writes to the temporary storage data set because of
recovery. From A12TWTNR.
TS_BFR_WRITES_TOT
INTEGER
Number of writes to the temporary storage data set. From
A12TWTN.
TS_CI_AVAILABLE
INTEGER
Number of control intervals in the auxiliary temporary storage
data set. From A12NCI.
TS_CI_AVAIL_BYTES
INTEGER
Number of bytes available for use in the auxiliary temporary
storage control interval. From A12NAVB.
TS_CI_IN_USE_CNT
INTEGER
Current number of control intervals in use. From A12NCIA.
TS_CI_PEAK_USED
INTEGER
Peak number of control intervals in use. From A12NCIAH.
TS_CI_SEG_BYTES
INTEGER
Number of bytes per segment. From A12BPSEG.
TS_CI_SEGMENTS
INTEGER
Number of segments available in the auxiliary temporary
storage control interval. From A12SPCI.
TS_CISIZE_EXCEEDED
INTEGER
Number of writes of records whose length was greater than
the control interval. From A12STABF.
TS_FORMAT_WRITES
INTEGER
Number of times a new CI was successfully written at the end
of the data set. From A12TWTNF.
TS_IO_ERRORS
INTEGER
Number of IO errors which occurred on the temporary storage
data set. From A12STAAF.
TS_LONGEST_Q
INTEGER
Peak number of items in any one queue. From A12QINH.
TS_MAIN_CURR_BYTES
INTEGER
Current value, in bytes, of virtual storage used for temporary
storage. From A12STA6A.
TS_MAIN_GETS
INTEGER
Number of records that the application programs obtained
from main temporary storage. From A12NMG.
TS_MAIN_PEAK_BYTES
INTEGER
Peak value, in bytes, of virtual storage used for temporary
storage. From A12STA6F.
TS_MAIN_PUTS
INTEGER
Number of records that the application programs wrote to
main temporary storage. From A12STA5F.
196
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TS_MGSET_VALUE
INTEGER
Number of records held in a single temporary storage group
identifier, TSGID. FROM TSMGSET SIT parameter and
A12GIDNE.
TS_PEAK_Q_NAMES
INTEGER
Peak number of temporary storage queue names in use. From
A12QNUMH.
TS_Q_EXTENSIONS
INTEGER
Number of times it was necessary to create a TSGID
extension. From A12STA4F.
TS_Q_NAMES
INTEGER
Current number of temporary storage queue names in use.
From A12QNUM.
TS_QUEUES_CREATED
INTEGER
Number of times CICS created individual storage queues.
From A12STA3F.
TS_SHR_POOL_CONN
INTEGER
Number of shared TS pools currently connected in the TST.
From TSGSHPCN.
TS_SHR_POOL_DEF
INTEGER
Number of shared TS pools defined in the TST. From
TSGSHPDF.
TS_SHR_READ_REQS
INTEGER
Number of read requests to all shared TS pools. From
TSGSHRDS.
TS_SHR_WRITE_REQS
INTEGER
Number of write requests to all shared TS pools. From
TSGSHWTS.
TS_STRING_CUR_WAIT
INTEGER
Current number of IO requests that are queued because all
strings are in use. From A12VUWT.
TS_STRING_WAITS
INTEGER
Number of IO requests that were queued because no strings
were available. From A12VWTN.
TS_STRNG_PEAK_USED
INTEGER
Peak number of concurrent IO operations to the temporary
storage data set. From A12NVCAH.
TS_STRNG_PEAK_WAIT
INTEGER
Peak number of IO requests that were queued because all
strings were in use. From A12VUWTH.
TS_STRNG_SPECIFIED
INTEGER
Number of temporary storage strings. From A12NVCA.
VTAM_ACB_DYN_OPENS
INTEGER
Number of times the VTAM ACB was opened by the operator.
VTAM_SOS_COUNT
INTEGER
Number of times VTAM was short on storage. From
A03VTSOS.
WAIT_TIME
FLOAT
Time spent waiting for the loader, in seconds. From LDGTTW.
CICS_S_INTERCOM_T
This table provides detailed data with both system and mode entries and global
statistics for:
v Interregion communication (IRC)
v Intersystem communication (ISC)
v Multiregion operation (MRO)
The table contains data from CICS/ESA and CICS/TS (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
DATE
K
Data type
Description
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
Chapter 6. Data tables, lookup tables, and control tables
197
CICS statistics component data tables
Column name
Data type
Description
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
CONNECTION_NAME
K
CHAR(6)
Connection name. From A14CNTN. Contains GLOBAL if
STID=54.
APPC_SYSTEM_NAME
K
CHAR(6)
Name of the APPC connection. From A20SYSN. Contains
GLOBAL if STID=54.
MODE_NAME
K
CHAR(8)
Mode group name. From A20MODE. Contains GLOBAL if
STID=54.
CHAR(1)
Communication access method used for this connection.
The values are:
v X(01)=A14VTAM
v X(02)=A14IRC
v X(03)=A14XM
v X(04)=A14XCF
ACCESS_METHOD
For CICS/TS V1.1 and later. This is from A14ACCM.
AIDS_IN_CHAIN
INTEGER
Number of requests queued for a specific session. From
A14EALL.
ALLOCATE_REQ_PEAK
INTEGER
Peak allocate requests queued for this system. From
A14ESTAM.
ALLOCATES
INTEGER
Number of times a program issued an ALLOCATE
command, not including commands failing basic validation
(SYSIDERR). From A14ESTAS.
ALLOCATES_PEAK
INTEGER
Peak allocate requests queued for this LU 6.2 mode group.
From A20ESTAM.
ALLOCATES_QUEUED
INTEGER
Number of times a program issued an ALLOCATE
command (without NOQUEUE) and there were no bound
contention winners available. From A14ESTAQ.
ALLOC_FAILED_LINK
INTEGER
Number of times a program issued an ALLOCATE
command and got a link error, normally resulting in
SESSIONERR. From A14ESTAF.
ALLOC_FAILED_OTHER
INTEGER
Number of times an ALLOCATE failed with SESSBUSY or
SYSBUSY (normally when the connection is heavily used).
From A14ESTAO.
ALLOC_F1_SPEC_REQ
INTEGER
Number of times a program issued an ALLOCATE
command and got a link error, normally resulting in
SESSIONERR, for this APPC mode group. From
A20ESTAF.
ALLOC_F2_SPEC_REQ
INTEGER
Number of times an ALLOCATE failed with SESSBUSY or
SYSBUSY (normally when the connection is heavily used)
for this APPC mode group. From A20ESTAO.
ALLOC_GEN_20
INTEGER
Number of times a generic allocate request was satisfied by
this mode group. From A20ESTAG.
198
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
ALLOC_PURGE_CNT
INTEGER
Total number of allocates purged due to the queue
processing time exceeding the MAXQTIME_SEC value. For
CICS V4 and later. From A14EMQPC.
ALLOC_Q_PURGE_CNT
INTEGER
Total number of times an allocate queue has been purged
due to the MAXQTIME value (A14EMXQT). A queue is
purged when the total time it would take to process a
queue exceeds the MAXQTIME value. For CICS V4 and
later. From A14EQPCT.
ALLOC_Q_SPEC_REQ
INTEGER
Number of times a program issued a specific ALLOCATE
command (without NOQUEUE) and there were no bound
contention winners available for this mode group. From
A20ESTAQ.
ALLOC_REJECT_CNT
INTEGER
Total number of allocates rejected due to the QUEUELIMIT
value (A14EALIM) being reached. For CICS V4 and later.
From A14EALRJ.
ALLOC_SPEC_REQ
INTEGER
Number of times a program issued a specific ALLOCATE
command for this mode group, excluding commands
failing basic validation (SYSIDERR). From A20ESTAS.
ALLOC_SPEC_20
INTEGER
Number of times a specific allocate request for this mode
group was satisfied. From A20ESTAP.
ATI_LOSER_REQ
INTEGER
Number of times a contention loser APPC session was
used. From A20ES1.
ATI_REQ_LOSERS
INTEGER
Number of times a receive session was used (LU 6.1).
From A14ES1.
ATI_REQ_WINNERS
INTEGER
Number of times a send session was used (LU 6.1). From
A14ES2.
ATI_WINNER_REQ
INTEGER
Number of times a contention winner APPC session was
used. From A20ES2.
AUTINST_CONN_GTIME
TIMESTAMP
Time at which this connection was autoinstalled, in GMT.
The time is expressed as hours:minutes:seconds.decimals.
For CICS/TS V1.1 and later. This is from A14GACT.
AUTINST_CONN_LTIME
TIMESTAMP
Time at which this connection was autoinstalled, in
LOCAL time. The time is expressed as
hours:minutes:seconds.decimals. For CICS/TS V1.1 and
later. This is from A14AICT.
BIDS_IN_PROGRESS
INTEGER
Number of bids in progress. From A14EBID. CICS must
send a BID to use a bound contention loser session.
BIDS_PEAK
INTEGER
Peak number of bids that were in progress at any one time.
From A14EBHWM.
BIDS_PEAK_20
INTEGER
Peak number of bids that were in progress at any one time
for this APPC mode group. From A20EBHWM.
BIDS_SENT
INTEGER
Number of times CICS sent a BID to use a contention loser
session. From A14ESBID.
BIDS_SENT_20
INTEGER
Number of times CICS sent a BID to use a contention loser
session. From A20ESBID.
BIDS_20
INTEGER
Number of bids in progress. From A20EBID. CICS must
send a BID to use a bound contention loser session.
Chapter 6. Data tables, lookup tables, and control tables
199
CICS statistics component data tables
Column name
Data type
Description
COMMUNIC_PROTOCOL
CHAR(1)
Communication protocol used for this connection. The
values are:
v X(01)=A14APPC
v X(02)=A14LU61
v X(03)=A14EXCI
For CICS/TS V1.1 and later. This is from A14EFLGS.
CONNECT_NETNAME
CHAR(8)
Name by which the remote system is known in the
network that is, its applid. For CICS/TS V1.1 and later.
This is from A14ESID.
CONTENTION_LOSER
INTEGER
Number of contention loser sessions (primaries for LU6.1)
that are currently in use. For CICS/TS V1.1 and later. This
is the sum of A14E1RY.
CONTENT_WIN_PEAK
INTEGER
Peak number of contention winner sessions for this APPC
mode group. From A20E2HWM.
CONTSESS_MAX_DEF
FLOAT
Maximum number of sessions that the definition of the
session group permits to be contention winners. For
CICS/TS V1.1 and later. This is the max from A20EMCON.
CONT_SESSION_LOSER
FLOAT
Current number of contention loser sessions. For CICS/TS
V1.1 and later. This is the max from A20E1RY.
CONT_SESSION_WIN
FLOAT
Current number of contention winner sessions. For
CICS/TS V1.1 and later. This is the max from A20E2RY.
CURR_LOSER_CONTENT
FLOAT
Number of contention loser sessions that are currently in
use. For CICS/TS V1.1 and later. This is the max from
A20ECONL.
CURR_SESSION_NUM
FLOAT
Current number of sessions in the group. For CICS/TS
V1.1 and later. This is the sum of A20EMAXS.
CURR_WINN_CONTENT
FLOAT
Number of contention winner sessions that are currently in
use. For CICS/TS V1.1 and later. This is the max from
A20ECONW.
DELETE_CONN_GTIME
TIMESTAMP
Time at which this connection was deleted, in GMT. The
time is expressed as hours:minutes:seconds.decimals. For
CICS/TS V1.1 and later. This is from A14GADT.
DELETE_CONN_LTIME
TIMESTAMP
Time at which this connection was deleted, in LOCAL
time. The time is expressed as
hours:minutes:seconds.decimals. For CICS/TS V1.1 and
later. This is from A14AIDT.
ENTRIES_REUSED
INTEGER
Number of times user IDs were reused without referencing
an external security manager. From
A21_SNT_TOTAL_REUSES.
ENTRIES_TIMED_OUT
INTEGER
Number of user IDs signed on to this remote system that
were timed out. From A21_SNT_TOTAL_TIMEOUT.
FUNC_SHIPSCHN_PC
FLOAT
The number of program control link requests, with
channels, for function shipping. From A14PFRC.
FUNC_SHIPSCHN_TS
FLOAT
The number of terminal-sharing channel requests for
function shipping. From A14TSC.
FUNC_SHIPSCHN_IC
FLOAT
The number of interval control START requests, with
channels, for function shipping. From A14IFRC.
FUNCTION_SHIPS_DLI
INTEGER
DL/I function shipping requests. From A14ESTDL.
FUNCTION_SHIPS_FC
INTEGER
File control function shipping requests. From A14ESTFC.
200
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
FUNCTION_SHIPS_IC
INTEGER
Interval control function shipping requests. From
A14ESTIC.
FUNCTION_SHIPS_TD
INTEGER
Transient data function shipping requests. From
A14ESTTD.
FUNCTION_SHIPS_TS
INTEGER
Temporary storage function shipping requests. From
A14ESTTS.
GENERIC_AIDS
INTEGER
Number of requests waiting to use a non-specific session.
From A14ESALL.
LOSERS_PEAK
INTEGER
Peak number of contention losers sessions. From
A14E1HWM.
MAXQTIME_SEC
INTEGER
Maximum time allowed, in seconds, to process an allocate
queue on this connection. If the allocate queue takes
longer, the queue is purged. This only takes effect if the
QUEUELIMIT value has been reached. For CICS V4 and
later. From A14EMXQT.
PEAK_CONT_LOSER
INTEGER
Number of contention winner sessions (primaries for
LU6.1) that are currently in use. For CICS/TS V1.1 and
later. This is the sum of A14E2RY.
PERSISTENT_VER_TIM
INTEGER
How long entries are allowed to remain unused in the
persistent verification list for this system, in minutes. This
is PVDELAY. From A21_SIT_LUIT_TIME.
PGM_CONTROL
FLOAT
Number of program control link requests for function
shipping. For CICS/TS V1.3 and later. This is the sum of
A14PCFR.
QUEUELIMIT
INTEGER
QUEUELIMIT parameter specified on the CONNECTION
definition. If this value is reached, allocates are rejected.
For CICS V4 and later. From A14EALIM.
RECORD_GLOBAL_FLAG
INTEGER
Set to 1 if a ICS/IRC GLOBAL record is processed.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete.
From SMFSTICD.
RECORD_MODE_FLAG
INTEGER
Set to 1 if a ICS/IRC MODE record is processed.
RECORD_SYSTEM_FLAG
INTEGER
Set to 1 if a ICS/IRC SYSTEM record is processed.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited),
EOD (End of day), REQ (Requested), or INT (Interval).
From SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for
example, 0330. From SMFSTRVN.
REC_SESS_COUNT
INTEGER
Number of RECEIVE sessions for this connection. This
field applies to MRO and LU6.1 connections only. For
CICS/TS V1.1 and later. This is the sum of A14EPRMN.
REUSE_TIME_AVG
INTEGER
Average time between each reuse of user IDs signed on to
this remote system, in seconds. From
A21_SNT_AV_REUSE_TIME.
SEND_SESS_COUNT
INTEGER
Number of SEND sessions for this connection. This field
applies to MRO and LU6.1 connections only. For CICS/TS
V1.1 and later. This is the sum of A14ESECN.
SESSION_NUM_MAX
INTEGER
Maximum number of sessions that the definition of the
session group permits. For CICS/TS V1.1 and later. This is
the max from A20ELMAX.
Chapter 6. Data tables, lookup tables, and control tables
201
CICS statistics component data tables
Column name
Data type
Description
SIGNON_REFRESH_TIM
INTEGER
How long user IDs are allowed to remain signed on in this
remote system (ISRDELAY), in minutes. From
A21_SIT_SNT_TIME.
SIGNON_REUSE
INTEGER
Number of times user IDs in the persistent verification list
were used without referencing an external security
manager. From A21_LUIT_TOTAL_REUSES.
SIGNON_REUSE_AVG
INTEGER
Average time between the reuse of entries in the persistent
verification list of this remote system, in seconds. From
A21_LUIT_AV_REUSE_TIME.
SIGNON_TIMEOUT
INTEGER
Number of entries in the persistent verification list of this
remote system that were timed out. From
A21_LUIT_TOTAL_TIMEOUT.
TRANS_ROUTINGS
INTEGER
Transaction routing commands (where a transaction is
defined as remote or is dynamically routed). Not valid for
LU 6.1. This is incremented on both systems. From
A14ESTTC.
WINNERS_PEAK
INTEGER
Peak number of contention winner sessions. From
A14E2HWM.
XZIQUE_ALLOC_PURGS
INTEGER
Total number of allocates purged due to XZIQUE
requesting that queues should be purged (see
XZIQUE_PURGE_CNT) for this connection. For CICS V4
and later. From A14EZQPC.
XZIQUE_PURGE_CNT
INTEGER
Total number of allocate queue purges that have occurred
at XZIQUE request for this connection. For CICS V4 and
later. From A14EZQPU.
XZIQUE_REJECT_CNT
INTEGER
Total number of allocates rejected by the XZIQUE exit. For
CICS V4 and later. From A14EZQRJ.
PGM_CONTROL
FLOAT
Number of Program control, functions shipping requests.
For CICS/TS V1.3 and later. This is the sum of A14PCFR.
CICS_S_INTERCOM_D
This table provides daily data with both system and mode entries and global
statistics for:
v Interregion communication (IRC)
v Intersystem communication (ISC)
v Multiregion operation (MRO)
The table contains consolidated data from the CICS_S_INTERCOM_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
202
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
CONNECTION_NAME
K
CHAR(6)
Connection name. From A14CNTN. Contains GLOBAL if
STID=54.
APPC_SYSTEM_NAME
K
CHAR(6)
Name of the APPC connection. From A20SYSN. Contains
GLOBAL if STID=54.
MODE_NAME
K
CHAR(8)
Mode group name. From A20MODE. Contains GLOBAL if
STID=54.
CHAR(1)
Communication access method used for this connection.
The values are:
v X(01)=A14VTAM
v X(02)=A14IRC
v X(03)=A14XM
v X(04)=A14XCF
ACCESS_METHOD
For CICS/TS V1.1 and later. This is from A14ACCM.
AIDS_IN_CHAIN
INTEGER
Number of requests queued for a specific session. From
A14EALL.
ALLOCATE_REQ_PEAK
INTEGER
Peak allocate requests queued for this system. From
A14ESTAM.
ALLOCATES
INTEGER
Number of times a program issued an ALLOCATE
command, not including commands failing basic validation
(SYSIDERR). From A14ESTAS.
ALLOCATES_PEAK
INTEGER
Peak allocate requests queued for this LU 6.2 mode group.
From A20ESTAM.
ALLOCATES_QUEUED
INTEGER
Number of times a program issued an ALLOCATE
command (without NOQUEUE) and there were no bound
contention winners available. From A14ESTAQ.
ALLOC_FAILED_LINK
INTEGER
Number of times a program issued an ALLOCATE
command and got a link error, normally resulting in
SESSIONERR. From A14ESTAF.
ALLOC_FAILED_OTHER
INTEGER
Number of times an ALLOCATE failed with SESSBUSY or
SYSBUSY (normally when the connection is heavily used).
From A14ESTAO.
ALLOC_F1_SPEC_REQ
INTEGER
Number of times a program issued an ALLOCATE
command and got a link error, normally resulting in
SESSIONERR, for this APPC mode group. From A20ESTAF.
ALLOC_F2_SPEC_REQ
INTEGER
Number of times an ALLOCATE failed with SESSBUSY or
SYSBUSY (normally when the connection is heavily used)
for this APPC mode group. From A20ESTAO.
ALLOC_GEN_20
INTEGER
Number of times a generic allocate request was satisfied by
this mode group. From A20ESTAG.
ALLOC_PURGE_CNT
INTEGER
Total number of allocates purged due to the queue
processing time exceeding the MAXQTIME_SEC value. For
CICS V4 and later. From A14EMQPC.
ALLOC_Q_PURGE_CNT
INTEGER
Total number of times an allocate queue has been purged
due to the MAXQTIME value (A14EMXQT). A queue is
purged when the total time it would take to process a
queue exceeds the MAXQTIME value. For CICS V4 and
later. From A14EQPCT.
Chapter 6. Data tables, lookup tables, and control tables
203
CICS statistics component data tables
Column name
Data type
Description
ALLOC_Q_SPEC_REQ
INTEGER
Number of times a program issued a specific ALLOCATE
command (without NOQUEUE) and there were no bound
contention winners available for this mode group. From
A20ESTAQ.
ALLOC_REJECT_CNT
INTEGER
Total number of allocates rejected due to the QUEUELIMIT
value (A14EALIM) being reached. For CICS V4 and later.
From A14EALRJ.
ALLOC_SPEC_REQ
INTEGER
Number of times a program issued a specific ALLOCATE
command for this mode group, excluding commands
failing basic validation (SYSIDERR). From A20ESTAS.
ALLOC_SPEC_20
INTEGER
Number of times a specific allocate request for this mode
group was satisfied. From A20ESTAP.
ATI_LOSER_REQ
INTEGER
Number of times a contention loser APPC session was
used. From A20ES1.
ATI_REQ_LOSERS
INTEGER
Number of times a receive session was used (LU 6.1). From
A14ES1.
ATI_REQ_WINNERS
INTEGER
Number of times a send session was used (LU 6.1). From
A14ES2.
ATI_WINNER_REQ
INTEGER
Number of times a contention winner APPC session was
used. From A20ES2.
AUTINST_CONN_GTIME
TIMESTAMP
Time at which this connection was autoinstalled, in GMT.
The time is expressed as hours:minutes:seconds.decimals.
For CICS/TS V1.1 and later. This is from A14GACT.
AUTINST_CONN_LTIME
TIMESTAMP
Time at which this connection was autoinstalled, in LOCAL
time. The time is expressed as
hours:minutes:seconds.decimals. For CICS/TS V1.1 and
later. This is from A14AICT.
BIDS_IN_PROGRESS
INTEGER
Number of bids in progress. From A14EBID. CICS must
send a BID to use a bound contention loser session.
BIDS_PEAK
INTEGER
Peak number of bids that were in progress at any one time.
From A14EBHWM.
BIDS_PEAK_20
INTEGER
Peak number of bids that were in progress at any one time
for this APPC mode group. From A20EBHWM.
BIDS_SENT
INTEGER
Number of times CICS sent a BID to use a contention loser
session. From A14ESBID.
BIDS_SENT_20
INTEGER
Number of times CICS sent a BID to use a contention loser
session. From A20ESBID.
BIDS_20
INTEGER
Number of bids in progress. From A20EBID. CICS must
send a BID to use a bound contention loser session.
COMMUNIC_PROTOCOL
CHAR(1)
Communication protocol used for this connection. The
values are:
v X(01)=A14APPC
v X(02)=A14LU61
v X(03)=A14EXCI
For CICS/TS V1.1 and later. This is from A14EFLGS.
CONNECT_NETNAME
204
CHAR(8)
Name by which the remote system is known in the
network that is, its applid. For CICS/TS V1.1 and later.
This is from A14ESID.
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CONTENTION_LOSER
INTEGER
Number of contention loser sessions (primaries for LU6.1)
that are currently in use. For CICS/TS V1.1 and later. This
is the sum of A14E1RY.
CONTENT_WIN_PEAK
INTEGER
Peak number of contention winner sessions for this APPC
mode group. From A20E2HWM.
CONTSESS_MAX_DEF
FLOAT
Maximum number of sessions that the definition of the
session group permits to be contention winners. For
CICS/TS V1.1 and later. This is the max from A20EMCON.
CONT_SESSION_LOSER
FLOAT
Current number of contention loser sessions. For CICS/TS
V1.1 and later. This is the max from A20E1RY.
CONT_SESSION_WIN
FLOAT
Current number of contention winner sessions. For
CICS/TS V1.1 and later. This is the max from A20E2RY.
CURR_LOSER_CONTENT
FLOAT
Number of contention loser sessions that are currently in
use. For CICS/TS V1.1 and later. This is the max from
A20ECONL.
CURR_SESSION_NUM
FLOAT
Current number of sessions in the group. For CICS/TS V1.1
and later. This is the sum of A20EMAXS.
CURR_WINN_CONTENT
FLOAT
Number of contention winner sessions that are currently in
use. For CICS/TS V1.1 and later. This is the max from
A20ECONW.
DELETE_CONN_GTIME
TIMESTAMP
Time at which this connection was deleted, in GMT. The
time is expressed as hours:minutes:seconds.decimals. For
CICS/TS V1.1 and later. This is from A14GADT.
DELETE_CONN_LTIME
TIMESTAMP
Time at which this connection was deleted, in LOCAL time.
The time is expressed as hours:minutes:seconds.decimals.
For CICS/TS V1.1 and later. This is from A14AIDT.
ENTRIES_REUSED
INTEGER
Number of times user IDs were reused without referencing
an external security manager. From
A21_SNT_TOTAL_REUSES.
ENTRIES_TIMED_OUT
INTEGER
Number of user IDs signed on to this remote system that
were timed out. From A21_SNT_TOTAL_TIMEOUT.
FUNC_SHIPSCHN_PC
FLOAT
The number of program control link requests, with
channels, for function shipping. From A14PFRC.
FUNC_SHIPSCHN_TS
FLOAT
The number of terminal-sharing channel requests for
function shipping. From A14TSC.
FUNC_SHIPSCHN_IC
FLOAT
The number of interval control START requests, with
channels, for function shipping. From A14IFRC.
FUNCTION_SHIPS_DLI
INTEGER
DL/I function shipping requests. From A14ESTDL.
FUNCTION_SHIPS_FC
INTEGER
File control function shipping requests. From A14ESTFC.
FUNCTION_SHIPS_IC
INTEGER
Interval control function shipping requests. From
A14ESTIC.
FUNCTION_SHIPS_TD
INTEGER
Transient data function shipping requests. From A14ESTTD.
FUNCTION_SHIPS_TS
INTEGER
Temporary storage function shipping requests. From
A14ESTTS.
GENERIC_AIDS
INTEGER
Number of requests waiting to use a non-specific session.
From A14ESALL.
LOSERS_PEAK
INTEGER
Peak number of contention losers sessions. From
A14E1HWM.
Chapter 6. Data tables, lookup tables, and control tables
205
CICS statistics component data tables
Column name
Data type
Description
PEAK_CONT_LOSER
INTEGER
Number of contention winner sessions (primaries for
LU6.1) that are currently in use. For CICS/TS V1.1 and
later. This is the sum of A14E2RY.
PGM_CONTROL
FLOAT
Number of program control link requests for function
shipping. For CICS/TS V1.3 and later. This is the sum of
A14PCFR.
RECORD_GLOBAL_CNT
INTEGER
Incremented if a ICS/IRC GLOBAL record is processed.
This is the sum of RECORD_GLOBAL_FLAG.
RECORD_MODE_CNT
INTEGER
Incremented if a ICS/IRC MODE record is processed. This
is the sum of RECORD_MODE_FLAG.
RECORD_SYSTEM_CNT
INTEGER
Incremented if a ICS/IRC SYSTEM record is processed.
This is the sum of RECORD_SYSTEM_FLAG.
REC_SESS_COUNT
INTEGER
Number of RECEIVE sessions for this connection. This field
applies to MRO and LU6.1 connections only. For CICS/TS
V1.1 and later. This is the sum of A14EPRMN.
REUSE_TIME_SEC
INTEGER
Total time between each reuse of user IDs signed on to this
remote system, in seconds. Divide by
RECORD_GLOBAL_CNT to get the average. From
A21_SNT_AV_REUSE_TIME.
SEND_SESS_COUNT
INTEGER
Number of SEND sessions for this connection. This field
applies to MRO and LU6.1 connections only. For CICS/TS
V1.1 and later. This is the sum of A14ESECN.
SESSION_NUM_MAX
INTEGER
Maximum number of sessions that the definition of the
session group permits. For CICS/TS V1.1 and later. This is
the max from A20ELMAX.
SIGNON_REUSE
INTEGER
Number of times user IDs in the persistent verification list
were used without referencing an external security
manager. From A21_LUIT_TOTAL_REUSES.
SIGNON_REUSE_SEC
INTEGER
Total time between the reuse of entries in the persistent
verification list of this remote system, in seconds. Divide by
RECORD_GLOBAL_CNT to get the average. From
A21_LUIT_AV_REUSE_TIME.
SIGNON_TIMEOUT
INTEGER
Number of entries in the persistent verification list of this
remote system that were timed out. From
A21_LUIT_TOTAL_TIMEOUT.
TRANS_ROUTINGS
INTEGER
Transaction routing commands (where a transaction is
defined as remote or is dynamically routed). Not valid for
LU 6.1. This is incremented on both systems. From
A14ESTTC.
WINNERS_PEAK
INTEGER
Peak number of contention winner sessions. From
A14E2HWM.
XZIQUE_ALLOC_PURGS
INTEGER
Total number of allocates purged due to XZIQUE
requesting that queues should be purged (see
XZIQUE_PURGE_CNT) for this connection. For CICS V4
and later. From A14EZQPC.
XZIQUE_PURGE_CNT
INTEGER
Total number of allocate queue purges that have occurred
at XZIQUE request for this connection. For CICS V4 and
later. From A14EZQPU.
XZIQUE_REJECT_CNT
INTEGER
Total number of allocates rejected by the XZIQUE exit. For
CICS V4 and later. From A14EZQRJ.
206
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
CICS_S_JOURNAL_T
This table provides detailed CICS journal statistics. For CICS/ESA and CICS/TS,
this maps the DFHA13DS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
JOURNAL_ID
K
INTEGER
Identifier of the journal as specified in the JCT JFILEID
operand. From A13JFID.
ARCHIVES_SUBMITTED
INTEGER
Number of archives submitted. From A13ASUB.
ARCHIVE_WAITS
INTEGER
Number of waits for archive completion. From A13WAC.
BLOCKS_WRITTEN
INTEGER
Number of physical I/Os written to the journal. From A13PBC.
BUFFER_FULL_COUNT
INTEGER
Number of times the receiving buffer was filled before the
alternate buffer was written. From A13BFC.
DATASETS_OPENED
INTEGER
Number of data sets opened (automatic archiving only). From
A13JDO.
JOURNAL_TYPE
CHAR(5)
This CICS V4 field shows which volume the journal has been
written to (DISK1 or DISK2) or whether the journal was written
to an SMF data set. From A13TYPE.
LAST_VOLSER_WRITE
CHAR(6)
Volume identifier of the most recently written volume (labeled
tapes only). From A13LVW.
OUTPUT_BLKSIZE_AVG
INTEGER
Approximate average of the output block size, in bytes. From
A13ABS.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORDS_WRITTEN
INTEGER
Number of records written to the journal. From A13LRC.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
SCRATCH_TAPES_LEFT
INTEGER
Number of scratch tapes left. From A13STL.
TAPES_OPENED
INTEGER
Number of tapes opened for use. From A13VOOC.
CICS_S_JOURNAL_T2
This table provides detailed CICS journal statistics. For CICS TS 1.1 and later, this
maps the DFHLGRDS record.
Chapter 6. Data tables, lookup tables, and control tables
207
CICS statistics component data tables
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
JOURNAL_NAME
K
INTEGER
Identifier of the journal as specified in the JCT JFILEID operand.
From LGRJNLNAME.
RECORDS_WRITTEN
FLOAT
Total number of times that a journal record was written to the
journal. From LGRWRITES.
BYTES_WRITTEN
FLOAT(53)
Total number of bytes written to the journal. From LGRBYTES.
Note: A double-precision floating-point number is a
System/370™ long (64 bits) floating-point number. The range of
magnitude is approximately 5.4E-79 to 7.2E+75. FLOAT(integer):
for a floating-point number. If the integer is between 1 and 21
inclusive, the format is single-precision floating point. If the
integer is between 22 and 53 inclusive, the format is
double-precision floating point.
BUFFER_FLUSHES
FLOAT
Total number of times that a journal block was written to the
logstream or in the SMF. From LGRBUFLUSH.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
JOURNAL_TYPE
INTEGER
Type of the journal. Can be MVS, SMF, or Dummy. From
LGRJTYPE.
LOGSTREAM_NAME
CHAR(26)
Logstream name. From LGRSTREAM.
CICS_S_JOURNAL_D
This table provides daily statistics on journals in the CICS system. It contains
summarized data from the CICS_S_JOURNAL_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
208
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
JOURNAL_ID
K
INTEGER
Identifier of the journal as specified in the JCT JFILEID operand.
From A13JFID.
ARCHIVES_SUBMITTED
INTEGER
Number of archives submitted. From A13ASUB.
ARCHIVE_WAITS
INTEGER
Number of waits for archive completion. From A13WAC.
BLOCKS_WRITTEN
INTEGER
Number of physical I/Os written to the journal. From A13PBC.
BUFFER_FULL_COUNT
INTEGER
Number of times the receiving buffer was filled before the
alternate buffer was written. From A13BFC.
DATASETS_OPENED
INTEGER
Number of data sets opened (automatic archiving only). From
A13JDO.
LAST_VOLSER_WRITE
CHAR(6)
Volume identifier of the most recently written volume (labeled
tapes only). From A13LVW.
RECORDS_WRITTEN
INTEGER
Number of records written to the journal. From A13LRC.
SCRATCH_TAPES_LEFT
INTEGER
Number of scratch tapes left. From A13STL.
TAPES_OPENED
INTEGER
Number of tapes opened for use. From A13VOOC.
CICS_S_JOURNAL_D2
This table provides daily CICS journal statistics. For CICS TS 1.1 and later, this
maps the DFHLGRDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
JOURNAL_NAME
K
INTEGER
Identifier of the journal as specified in the JCT JFILEID operand.
From LGRJNLNAME.
RECORDS_WRITTEN
FLOAT
Total number of times that a journal record was written to the
journal. From LGRWRITES.
BYTES_WRITTEN
FLOAT(53)
Total number of bytes written to the journal. From LGRWRITES.
Note: A double-precision floating-point number is a System/370
long (64 bits) floating-point number. The range of magnitude is
approximately 5.4E-79 to 7.2E+75. FLOAT(integer): for a
floating-point number. If the integer is between 1 and 21
inclusive, the format is single-precision floating point. If the
integer is between 22 and 53 inclusive, the format is
double-precision floating point.
Chapter 6. Data tables, lookup tables, and control tables
209
CICS statistics component data tables
Column name
Data type
Description
BUFFER_FLUSHES
FLOAT
Total number of times that a journal block was written to the
logstream or in the SMF. From LGRBUFLUSH.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
JOURNAL_TYPE
INTEGER
Type of the journal. Can be MVS, SMF, or Dummy. From
LGRJTYPE.
LOGSTREAM_NAME
CHAR(26)
Logstream name. From LGRSTREAM.
CICS_S_JVM_PROF_T,_D
This tables provide profile statistics data grouped by JVM profile and execution
key. They gather information from the statistics record provided by the CICS
statistics records (SMF 110, subtype 2).
The default retention periods for these tables are:
7 days for CICS_S_JVM_PROF_T
30 days for CICS_S_JVM_PROF_D
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFSTPRN.
PROF_NAME
K
CHAR(8)
Name of this JVM profile. From SJR_PROFILE_NAME.
STORAGE_KEY
K
CHAR(4)
The execution key to which these statistics apply. Possible
values are: User (the default), CICS. From SJRSTORKEY.
CURR_PROF_USE
FLOAT
Number of JVMs with this execution key and profile that
are currently in the JVM pool. From SJRCURRCOU.
GARB_COLL_REQ
FLOAT
The number of times GC was requested.
JVM_HEAP_HWM
FLOAT
The highest amount of nonsystem heap storage that was
used by a JVM with this execution key and profile. From
SJRHEAHWM.
JVMS_DESTR_SOS
FLOAT
Number of times that JVMs with this execution key and
profile were destroyed due to a short-on-storage
condition. From SJRDESSOS.
210
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
JVMS_UNRESETTABLE
FLOAT
Number of new JVMs with this execution key and profile
that could not be reset, and therefore could not be reused
by another request. From SJRUNRESCOU.
LE_HEAP_HWM
FLOAT
The highest amount of Language Environment® heap
storage that was used by a JVM with this execution key
and profile. From SJRLEHWM.
MISMATCH_STEALER
FLOAT
Number of times that an application’s request for a JVM
with this execution key and profile resulted in a
mismatch or a steal. From SJRMISSTEA.
MISMATCH_VICTIM
FLOAT
Number of times that a free JVM with this profile was
taken, destroyed and re-initialized. From SJRMISVIC.
NEW_JVMS_CREATED
FLOAT
Number of new JVMs that were created with this
execution key and profile. From SJRNEWCOU.
PEAK_PROF_USE
FLOAT
Peak number of JVMs with this execution key and profile
that the JVM pool has contained. From SJRPEAKCOU.
PROF_CLASS_CACHE
CHAR(1)
Shows whether JVMs with this JVM profile use the
shared class cache. Possible values are Y (Yes), N (No).
From SJRPROFCLCH.
PROF_MODES
INTEGER
Shows the number of execution keys in which JVMs with
this JVM profile can be created. From JVMPROFMODE.
PROF_PATH_NAME
VARCHAR(254)
The complete HFS path name for this JVM profile. From
SJRPROFPANM.
PROF_REQUESTS
FLOAT
Number of requests that applications have made to run a
Java program in a JVM with this execution key and
profile. From SJRREQCOUN.
PROF_XMX_VALUE
CHAR(8)
The value of the Xmx parameter set in this JVM profile.
The Xmx parameter specifies tha maximum total size of
the middleware and transient heaps in the JVM. From
SJRXMXVA.
CICS_S_JVM_PROG_T,_D
This tables provide statistics data about programs running in a JVM. The data is
from CICS statistics records (SMF 110, subtype 2).
The default retention periods for these tables are:
7 days for CICS_S_JVM_PROG_T
30 days for CICS_S_JVM_PROG_D
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. It
applies only to the _T table. From SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
Chapter 6. Data tables, lookup tables, and control tables
211
CICS statistics component data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFSTPRN.
JVMPROGRAM_NAME
K
CHAR(8)
Name of the Java program. From PGRPROGNM.
JVMPROG_EXEC_KEY
CHAR(4)
The execution key that the program requires. Possible
values are: USER (the default), CICS. From PGREXEKEY.
JVMPROG_JVMCLASS
VARCHAR(254)
The main class in the program. From PGRJVMCLA.
JVMPROG_USECOUNT
FLOAT
The number of times the program has been used. From
PGRUSECOU.
PGR_JVMPROG_PROF
CHAR(8)
The JVM profile that the program requires. From
PGRPROGPF.
CICS_S_JVMPOOL_T,_D
This tables provide detailed data about how many requests were for worker JVMs
that use the shared class cache. The data is from CICS statistics records (SMF 110,
subtype 2).
The default retention periods for these tables are:
7 days for CICS_S_JVMPOOL_T
30 days for CICS_S_JVMPOOL_D
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. It applies
only to the _T table. From SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID that is
used when requesting a session with this CICS system. From
SMFSTPRN.
CURR_CACHE_JVMS
FLOAT
Number of JVMs currently in the JVM pool that use the shared
class cache. From SJGCURRWJVM.
JVM_PEAK
FLOAT
Peak number of JVMs. From SJGPEAKJVM.
JVM_REQS_CACHE
FLOAT
Total number of Java programs that requested a JVM that used
the shared class cache. From SJGJVMRECAS.
JVM_REQS_INIT
FLOAT
Number of JVM program requests where the JVM was
initialized. From SJGJVMREQIN.
JVM_REQS_MISMATCH
FLOAT
Number of JVM program requests whose JVM profile specified
resettable but for which there was no JVM already initialized
with the same JVM profile. From SJGJVMREQMI.
JVM_REQS_REUSE
FLOAT
Number of requests to run a program in a continuous JVM.
From SJGJVMREQRE.
JVM_REQS_TERMINAT
FLOAT
Number of JVMs that have been terminated. From
SJGJVMREQTE.
JVM_REQS_TOT
FLOAT
Total number of JVM program requests. From SJGTOTPRREQ.
212
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
JVMS_CURRENT
FLOAT
Current number of JVMs. From SJGCURRJVM.
PEAK_CACHE_JVMS
FLOAT
Peak number of JVMs in the JVM pool that used the shared
class cache. From SJGPEAHWJVM.
SJG_JVM_REQS_RESET
FLOAT
The number of requests to run a program in resettable JVM.
From SJGJVMREQRS. This is no longer used from CICS TS 3.2.
CICS_S_LOGSTREAM_T
This table provides detailed CICS logstream statistics. For CICS/TS V1.1 and later,
this maps the DFHLGSDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
LOGSTREAM_NAME
K
CHAR(26)
Logstream name. From LGSTRNAM.
LOGSTREAM_WRT_REQ
FLOAT
Number of logstream write requests. From LGRWRITES.
BYTES_WRITTEN
FLOAT(53)
Number of bytes written. From LGRBYTES.
FORCE_WAITERS_CURR
FLOAT
Current number of force waiters. From LGSCUFWTRS.
FORCE_WAITERS_PEAK
FLOAT
Peak number of force waiters. From LGSPKFWTRS.
FORCE_WAITERS_TOT
FLOAT
Total number of force waits. From LGSTFCWAIT.
WAITS_BUFFER_FULL
FLOAT
Number of waits due to buffer full. From LGSBUFWAIT.
LOGS_BROWSE_START
FLOAT
Number of log browse starts. From LGSBRWSTRT.
LOGS_DELETES_REQ
FLOAT
Number of log deletes. From LGSDELETES.
LOGS_RETRT_ERRS
FLOAT
Number of errors that can be retried. From LGSRETRERR.
LOGS_BUF_APPEND
FLOAT
Number of buffer appends. From LGSBUFAPP.
LOGS_SYSTEM_LOG
CHAR(1) FOR
BIT DATA
System log flag. From LGSSYSLG.
LOGS_DASD_ONLY
CHAR(1) FOR
idd:break>BIT
DATA
DASD only flag. From LGSDONLY.
LOGS_CF_STRUCTNAME
CHAR(16)
Name of the CF structure. From LGSSTRUC.
LOGS_MAX_BLOCK
FLOAT
Maximum block length. From LGSMAXBL.
LOGS_RET_PERIOD
FLOAT
Data retention period. From LGSRETPD.
Chapter 6. Data tables, lookup tables, and control tables
213
CICS statistics component data tables
Column name
Data type
Description
LOGS_AUTO_DELETE
CHAR(1) FOR
idd:break>BIT
DATA
Data auto deletes flag. From LGSAUTOD.
CICS_S_LOGSTREAM_D
This table provides daily CICS logstream statistics. For CICS/TS V1.1 and later,
this maps the DFHLGSDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
LOGSTREAM_NAME
K
CHAR(26)
Logstream name. From LGSTRNAM.
LOGSTREAM_WRT_REQ
FLOAT
Number of logstream write requests. From LGRWRITES.
BYTES_WRITTEN
FLOAT(53)
Number of bytes written. From LGRBYTES.
FORCE_WAITERS_CURR
FLOAT
Current number of force waiters. From LGSCUFWTRS.
FORCE_WAITERS_PEAK
FLOAT
Peak number of force waiters. From LGSPKFWTRS.
FORCE_WAITERS_TOT
FLOAT
Total number of force waits. From LGSTFCWAIT.
WAITS_BUFFER_FULL
FLOAT
Number of waits due to buffer full. From LGSBUFWAIT.
LOGS_BROWSE_START
FLOAT
Number of log browse starts. From LGSBRWSTRT.
LOGS_DELETES_REQ
FLOAT
Number of log deletes. From LGSDELETES.
LOGS_RETRT_ERRS
FLOAT
Number of errors that can be retried. From LGSRETRERR.
LOGS_BUF_APPEND
FLOAT
Number of buffer appends. From LGSBUFAPP.
LOGS_SYSTEM_LOG
CHAR(1) FOR
BIT DATA
System log flag. From LGSSYSLG.
LOGS_DASD_ONLY
CHAR(1) FOR
idd:break>BIT
DATA
DASD only flag. From LGSDONLY.
LOGS_CF_STRUCTNAME
CHAR(16)
Name of the CF structure. From LGSSTRUC.
LOGS_MAX_BLOCK
FLOAT
Maximum block length. From LGSMAXBL.
LOGS_RET_PERIOD
FLOAT
Data retention period. From LGSRETPD.
LOGS_AUTO_DELETE
CHAR(1) FOR
idd:break>BIT
DATA
Data auto deletes flag. From LGSAUTOD.
214
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
CICS_S_LSR_POOL_T
This table provides detailed data about the local shared resources (LSR) pool
buffers and strings. The counters are never reset; except for the three string
statistics, the counters contain totals accumulated since CICS started.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
POOL_NUMBER
K
INTEGER
LSR pool identifier, from 1 to 8. From A08SRPID.
BUFFER_SIZE
K
CHAR(6)
LSR buffer size, in bytes. From A08BKBSZ.
BUFFERS
INTEGER
Number of buffers of each size available to CICS. From
A08BKBFN.
DATA_BUFF_CNT
INTEGER
Number of buffers used by the pool. (Data buffers, if there are
separate data and index pools, else total for data and index.)
From A08TOBFN_DATA.
DATA_BUFF_LLA
INTEGER
Number of successful lookasides, where data was found,
avoiding an IO. (Data buffers, if there are separate data and
index pools, else total for data and index.) From
A08TOBFF_DATA.
DATA_BUFF_READ
INTEGER
Number of read I/Os to the buffers. (Data buffers, if there are
separate data and index pools, else total for data and index.)
From A08TOFRD_DATA.
DATA_BUFF_WRITE_N
INTEGER
Number of non-user-initiated write I/Os. (Data buffers, if
there are separate data and index pools, else total for data and
index.) From A08TONUW_DATA.
DATA_BUFF_WRITE_U
INTEGER
Number of user-initiated write I/Os. (Data buffers, if there are
separate data and index pools, else total for data and index.)
From A08TOUIW_DATA.
DATAH_BUFF_CNT
INTEGER
Number of hiperspace buffers. (Data buffers, if there are
separate data and index pools, else total for data and index.)
From A08TOHBN_DATA.
DATAH_BUFF_CREAD
INTEGER
Number of successful CREADs from hiperspace to data
buffers. (Data buffers, if there are separate data and index
pools, else total for data and index). From A08TOCRS_DATA.
DATAH_BUFF_CREADF
INTEGER
Number of CREADs that failed. The data was read from
DASD, because MVS had withdrawn the space. (Data buffers,
if separate data and index pools, else total for data and index.)
From A08TOCRF_DATA.
DATAH_BUFF_CWRITE
INTEGER
Number of successful CWRITEs from data buffers to
hiperspace. (Data buffers, if there are separate data and index
pools, else total for data and index.) From A08TOWRS_DATA.
Chapter 6. Data tables, lookup tables, and control tables
215
CICS statistics component data tables
Column name
Data type
Description
DATAH_BUFF_CWRITEF
INTEGER
Number of CWRITEs that failed. There was not enough
hiperspace, and VSAM wrote to DASD instead. (Data buffers,
if there are separate data and index pools, else total of data
and index.) From A08TOCWF_DATA.
FLAGS
CHAR(2)
Set to X″80″ if there are separate data and index pools, else
X″00″. From A08FLAGS.
HIPER_INDEX_BUFFER
INTEGER
Number of hiperspace index buffers.
HIPERSPACE_READ
INTEGER
Number of successful CREAD requests. From A08BKCRS.
HIPERSPACE_WRITE
INTEGER
Number of successful CWRITE requests. From A08BKWRS.
HIPER_INDEX:_BUFFER
INTEGER
Space of index buffer
HS_FAILED_READ
INTEGER
Number of failed CREAD requests. MVS withdrew the space
and VSAM had to read from DASD. From A08BKCRF.
HS_FAILED_WRITE
INTEGER
Number of failed CWRITE requests, because of a lack of
hiperspace. VSAM had to write to DASD. From A08BKCWF.
INDEX_BUFFER_SIZE
INTEGER
Size of index buffer for pool statistics.
INDEX_FAIL_CREADS
INTEGER
Number of index buffer reads that failed.
INDEX_FAIL_CWRITE
INTEGER
Number of index buffer writes that failed.
INDEX_SUXS_CREADS
INTEGER
Number of index buffer reads that were successful.
INDEX_SUXS_CWRITE
INTEGER
Number of index buffer writes that were successful.
INDX_BUFF_CNT
INTEGER
Number of index buffers. From A08TOBFN_INDX.
INDX_BUFF_LLA
INTEGER
Number of successful lookasides to index buffers, avoiding IO.
From A08TOBFF_INDX.
INDX_BUFF_READ
INTEGER
Number of read I/Os to the index buffers. From
A08TOFRD_INDX.
INDX_BUFF_WRITE_N
INTEGER
Number of non-user-initiated write I/Os from the index
buffers. From A08TONIW_INDX.
INDX_BUFF_WRITE_U
INTEGER
Number of user-initiated write I/Os from the index buffers.
From A08TOUIW_INDX.
INDXH_BUFF_CNT
INTEGER
Number of hiperspace index buffers. From A08TOHBN_INDX.
INDXH_BUFF_CREAD
INTEGER
Number of successful CREADs from hiperspace to index
buffers. From A08TOCRS_INDX.
INDXH_BUFF_CREADF
INTEGER
Number of failed CREADs. MVS had withdrawn the space,
and VSAM read from DASD. From A08TOCRF_INDX.
INDXH_BUFF_CWRITE
INTEGER
Number of successful CWRITEs from index buffers to
hiperspace. From A08TOWRS_INDX.
INDXH_BUFF_CWRITEF
INTEGER
Number of failed CWRITEs. There was not enough
hiperspace, and VSAM wrote to DASD. From
A08TOCWF_INDX.
INDEX_BUFFER_SIZE
INTEGER
Index buffer size for statistics of pool
INDEX_FAIL_CREADS
INTEGER
Index failed reads
INDEX_FAIL_CWRITE
INTEGER
Index failed writes
INDEX_SUXS_CREADS
INTEGER
Index successful reads
INDEX_SUXS_CWRITE
INTEGER
Index successful writes
IX_BUFFER_READS
INTEGER
Index buffer reads
IX_SUXS_LOOK_ASID
INTEGER
Index success asides
216
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
IX_BUFFER_READS
INTEGER
Number of index buffer reads.
IX_SUXS_LOOK_ASID
INTEGER
Number of successful lookasides to index buffers.
LOOKASIDES
INTEGER
Number of read requests that VSAM could satisfy without
I/O. From A08BKBFF.
MAX_KEY_LENGTH
INTEGER
Maximum key length of any VSAM data using the pool, in
bytes. From A08BKKYL.
NONUSR_IX_BUF_WRI
INTEGER
Non-user index buffer writes
NUM_INDEX_BUFFER
INTEGER
Number of index buffer
NONUSR_IX_BUF_WRI
INTEGER
Number of index buffer writes initiated by a non-user.
NUMBER_OF_IO_OPS
INTEGER
Number of I/O operations to the buffers, caused by failure to
find the CI in a buffer on a READ request. From A08BKFRD.
NUM_INDEX_BUFFER
INTEGER
Number of index buffers.
NUM_OF_HIPERSPACE
INTEGER
Number of hiperspace buffers specified for pool. From
A08BKHBN.
NUM_OF_NONUSR_WRIT
INTEGER
Number of write I/Os caused by a shortage of buffers for
read operations. From A08BKNUW.
NUM_OF_USR_WRITES
INTEGER
Number of user-initiated I/O write operations. From
A08BKUIW.
POOL_CREATE_TIME
TIME
Local time when the LSR pool was created. From A08LBKCD
A08BKCTD.
POOL_DELETED_TIME
TIME
Local time when the LSR pool was deleted. From A08LBKDD
A08BKDTD.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
STRING_PEAK_USED
INTEGER
Peak number of active strings. CICS does reset this to the
current number of active strings. From A08BKHAS.
STRING_PEAK_WAIT
INTEGER
Peak number of requests that waited for a string. CICS does
reset this to the current number of waiting requests. From
A08BKHSW.
STRINGS
INTEGER
Number of strings. From A08BKSTN.
STRING_WAITS
INTEGER
Number of requests that waited for a string. CICS does reset
this to zero. From A08BKTSW.
USR_IX_BUFFER_WRI
INTEGER
User index buffer writes
USR_IX_BUFFER_WRI
INTEGER
Number of index buffer writes initiated by a user.
CICS_S_LSR_POOL_D
This table provides daily data about the local shared resources (LSR) pool buffers
and strings. The counters are never reset; except for the three string statistics, the
counters contain the highest values from the CICS_S_LSR_POOL_T table. It
contains consolidated data from the CICS_S_LSR_POOL_T table.
The default retention period for this table is 30 days.
Chapter 6. Data tables, lookup tables, and control tables
217
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
POOL_NUMBER
K
INTEGER
LSR pool identifier, from 1 to 8. From A08SRPID.
BUFFER_SIZE
K
CHAR(6)
LSR buffer size, in bytes. From A08BKBSZ.
BUFFERS
INTEGER
Number of buffers of each size available to CICS. From
A08BKBFN.
DATA_BUFF_CNT
INTEGER
Number of buffers used by the pool. (Data buffers, if there are
separate data and index pools, else total for data and index).
From A08TOBFN_DATA.
DATA_BUFF_LLA
INTEGER
Number of successful lookasides, where data was found,
avoiding an IO. (Data buffers, if there are separate data and
index pools, else total for data and index). From
A08TOBFF_DATA.
DATA_BUFF_READ
INTEGER
Number of read I/Os to the buffers. (Data buffers, if there are
separate data and index pools, else total for data and index).
From A08TOFRD_DATA.
DATA_BUFF_WRITE_N
INTEGER
Number of non-user-initiated write I/Os. (Data buffers, if there
are separate data and index pools, else total for data and
index). From A08TONUW_DATA.
DATA_BUFF_WRITE_U
INTEGER
Number of user-initiated write I/Os. (Data buffers, if there are
separate data and index pools, else total for data and index).
From A08TOUIW_DATA.
DATAH_BUFF_CNT
INTEGER
Number of hiperspace buffers. (Data buffers, if there are
separate data and index pools, else total for data and index).
From A08TOHBN_DATA.
DATAH_BUFF_CREAD
INTEGER
Number of successful CREADs from hiperspace to data
buffers. (Data buffers, if there are separate data and index
pools, else total for data and index). From A08TOCRS_DATA.
DATAH_BUFF_CREADF
INTEGER
Number of CREADs that failed. The data was read from
DASD, because MVS had withdrawn the space. (Data buffers,
if separate data and index pools, else total for data and index).
From A08TOCRF_DATA.
DATAH_BUFF_CWRITE
INTEGER
Number of successful CWRITEs from data buffers to
hiperspace. (Data buffers, if there are separate data and index
pools, else total for data and index). From A08TOWRS_DATA.
DATAH_BUFF_CWRITEF
INTEGER
Number of CWRITEs that failed. There was not enough
hiperspace, and VSAM wrote to DASD instead. (Data buffers,
if there are separate data and index pools, else total of data
and index). From A08TOCWF_DATA.
HIPERSPACE_READ
INTEGER
Number of successful CREAD requests. From A08BKCRS.
HIPERSPACE_WRITE
INTEGER
Number of successful CWRITE requests. From A08BKWRS.
HS_FAILED_READ
INTEGER
Number of failed CREAD requests. MVS withdrew the space
and VSAM had to read from DASD. From A08BKCRF.
218
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
HS_FAILED_WRITE
INTEGER
Number of failed CWRITE requests, because of a lack of
hiperspace. VSAM had to write to DASD. From A08BKCWF.
INDX_BUFF_CNT
INTEGER
Number of index buffers. From A08TOBFN_INDX.
INDX_BUFF_LLA
INTEGER
Number of successful lookasides to index buffers, avoiding IO.
From A08TOBFF_INDX.
INDX_BUFF_READ
INTEGER
Number of read I/Os to the index buffers. From
A08TOFRD_INDX.
INDX_BUFF_WRITE_N
INTEGER
Number of non-user-initiated write I/Os from the index
buffers. From A08TONIW_INDX.
INDX_BUFF_WRITE_U
INTEGER
Number of user-initiated write I/Os from the index buffers.
From A08TOUIW_INDX.
INDXH_BUFF_CNT
INTEGER
Number of hiperspace index buffers. From A08TOHBN_INDX.
INDXH_BUFF_CREAD
INTEGER
Number of successful CREADs from hiperspace to index
buffers. From A08TOCRS_INDX.
INDXH_BUFF_CREADF
INTEGER
Number of failed CREADs. MVS had withdrawn the space,
and VSAM read from DASD. From A08TOCRF_INDX.
INDXH_BUFF_CWRITE
INTEGER
Number of successful CWRITEs from index buffers to
hiperspace. From A08TOWRS_INDX.
INDXH_BUFF_CWRITEF
INTEGER
Number of failed CWRITEs. There was not enough hiperspace,
and VSAM wrote to DASD. From A08TOCWF_INDX.
LOOKASIDES
INTEGER
Number of read requests that VSAM could satisfy without
I/O. From A08BKBFF.
MAX_KEY_LENGTH
INTEGER
Maximum key length of any VSAM data using the pool, in
bytes. From A08BKKYL.
NUMBER_OF_IO_OPS
INTEGER
Number of I/O operations to the buffers, caused by failure to
find the CI in a buffer on a READ request. From A08BKFRD.
NUM_OF_HIPERSPACE
INTEGER
Number of hiperspace buffers specified for pool. From
A08BKHBN.
NUM_OF_NONUSR_WRIT
INTEGER
Number of write I/Os caused by a shortage of buffers for read
operations. From A08BKNUW.
NUM_OF_USR_WRITES
INTEGER
Number of user-initiated I/O write operations. From
A08BKUIW.
STRING_PEAK_USED
INTEGER
Peak number of active strings. CICS does reset this to the
current number of active strings. From A08BKHAS.
STRING_PEAK_WAIT
INTEGER
Peak number of requests that waited for a string. CICS does
reset this to the current number of waiting requests. From
A08BKHSW.
STRINGS
INTEGER
Number of strings. From A08BKSTN.
STRING_WAITS
INTEGER
Number of requests that waited for a string. CICS does reset
this to zero. From A08BKTSW.
CICS_S_LSRP_FILE_T
This table provides summary LSR pool data for each file. It contains data from
CICS statistics records.
The default retention period for this table is 7 days.
Chapter 6. Data tables, lookup tables, and control tables
219
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
POOL_NUMBER
K
INTEGER
LSR pool number, in the range 1 to 8. From A09SRPID.
FILE_NAME
K
CHAR(8)
CICS file name. From A09DSID.
BUFFER_WAITS
INTEGER
Number of requests that had to wait because all buffers of the
right size in the pool were in use. From A09TBW.
BUFFER_WAITS_PEAK
INTEGER
Peak number of requests that had to wait because all buffers of
the right size in the pool were in use. From A09HBW.
DATA_BUFFER_SIZE
INTEGER
Buffer size used for data records. This is the last non-zero value
used for the data buffers. From A09DBN.
INDEX_BUFFER_SIZE
INTEGER
Buffer size used for index records. This is the last non-zero value
used for the index buffers. From A09IBN.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
CICS_S_LSRP_FILE_D
This table provides daily LSR pool data for each file. It contains consolidated data
from the CICS_S_LSRP_FILE_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
POOL_NUMBER
K
INTEGER
LSR pool number, in the range 1 to 8. From A09SRPID.
FILE_NAME
K
CHAR(8)
CICS file name. From A09DSID.
220
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
BUFFER_WAITS
INTEGER
Number of requests that had to wait because all buffers of the
right size in the pool were in use. From A09TBW.
BUFFER_WAITS_PEAK
INTEGER
Peak number of requests that had to wait because all buffers of
the right size in the pool were in use. From A09HBW.
DATA_BUFFER_SIZE
INTEGER
Buffer size used for data records. This is the last non-zero value
used for the data buffers. From A09DBN.
INDEX_BUFFER_SIZE
INTEGER
Buffer size used for index records. This is the last non-zero value
used for the index buffers. From A09IBN.
CICS_SMD_SUBP_D
This table provides daily Storage Domain subpool statistics from CICS TS 3.2 (SMF
110, subtype 2). This maps the CICS DFHSMDDS macro.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
SMD_SUBP_NAME
K
CHAR(8)
Subpool name. From SMDSPN.
SMD_DSA_NAME
CHAR(8)
DSA name. From SMDDSANAME.
SMD_TYPE
CHAR(1)
Element type (fixed/var). From SMDETYPE.
SMD_FIXED_LEN
INTEGER
Length (if fixed length). From SMDFLEN.
SMD_ELEM_CHAIN
CHAR(1)
Element chaining (yes/no?). From SMDELCHN.
SMD_BOUNDARY
INTEGER
Boundary. From SMDBNDRY.
SMD_LOCATION
CHAR(10)
Above/below/AboveBar. From SMDLOCN.
SMD_ACCESS
CHAR(10)
CICS/User/ReadOnly. From SMDACCESS.
SMD_DSA_INDEX
CHAR(5)
CDSA/SDSA/RDSA/
ECDSA/ESDSA/
ERDSA/GCDSA.
From SMDDSAINDEX.
SMD_INIT_FREE
INTEGER
Initial free value. From SMDIFREE.
SMD_GETMAIN_REQ
INTEGER
Number of Getmain reqs. From SMDGMREQ.
SMD_FREEMAIN_REQ
INTEGER
Number of Freemain reqs. From SMDFMREQ.
SMD_SUM_ELM_LEN
INTEGER
Sum of all element lengths. From SMDCES.
SMD_CURR_PGE_STOR
INTEGER
Current page storage. From SMDCPS.
SMD_CURR_ELM
INTEGER
Current number of elements. From SMDCELEM.
SMD_PAGE_HWM
INTEGER
High Water Mark Page Storage. From SMDHWMPS.
Chapter 6. Data tables, lookup tables, and control tables
221
CICS statistics component data tables
CICS_SMD_SUBP_H
This table provides hourly Storage Domain subpool statistics from CICS TS 3.2
(SMF 110, subtype 2). This maps the CICS DFHSMDDS macro.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
SMD_SUBP_NAME
K
CHAR(8)
Subpool name. From SMDSPN.
SMD_DSA_NAME
CHAR(8)
DSA name. From SMDDSANAME.
SMD_TYPE
CHAR(1)
Element type (fixed/var). From SMDETYPE.
SMD_FIXED_LEN
INTEGER
Length (if fixed length). From SMDFLEN.
SMD_ELEM_CHAIN
CHAR(1)
Element chaining (yes/no?). From SMDELCHN.
SMD_BOUNDARY
INTEGER
Boundary. From SMDBNDRY.
SMD_LOCATION
CHAR(10)
Above/below/AboveBar. From SMDLOCN.
SMD_ACCESS
CHAR(10)
CICS/User/ReadOnly. From SMDACCESS.
SMD_DSA_INDEX
CHAR(5)
CDSA/SDSA/RDSA/
ECDSA/ESDSA/
ERDSA/GCDSA.
From SMDDSAINDEX.
SMD_INIT_FREE
INTEGER
Initial free value. From SMDIFREE.
SMD_GETMAIN_REQ
INTEGER
Number of Getmain reqs. From SMDGMREQ.
SMD_FREEMAIN_REQ
INTEGER
Number of Freemain reqs. From SMDFMREQ.
SMD_SUM_ELM_LEN
INTEGER
Sum of all element lengths. From SMDCES.
SMD_CURR_PGE_STOR
INTEGER
Current page storage. From SMDCPS.
SMD_CURR_ELM
INTEGER
Current number of elements. From SMDCELEM.
SMD_PAGE_HWM
INTEGER
High Water Mark Page Storage. From SMDHWMPS.
CICS_S_MONITOR_T
This table provides detailed data on the monitoring domain. It contains data from
CICS statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
DATE
222
K
Data type
Description
DATE
Date when the statistics record was written to SMF. From
START.
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DATA_COMPR_STAT
CHAR(10)
Data Compression Option.
EXCEPT_RECORDS
INTEGER
Number of exception records written to SMF. From MNGER.
EXCEPT_REC_SUPPR
INTEGER
Number of exception records suppressed by the global user exit
XMNOUT. From MNGERS.
FILE_RES_LIMIT
FLOAT
File Resource Limit.
MAXAVG_COMP_REC
INTEGER
Max Avg Compressed record length.
MAXAVG_UNCOMP_REC
INTEGER
Max Avg Uncompressed record length.
MINAVG_COMP_REC
INTEGER
Min Avg Compressed recordlength.
MINAVG_UNCOMP_REC
INTEGER
Min Avg Uncompressed record length.
PERFORM_RECORDS
INTEGER
Number of performance records scheduled for output to SMF
(both written and pending write). From MNGPR.
PERFORM_REC_SUPPR
INTEGER
Number of performance records suppressed by the global user
exit XMNOUT. From MNGPRS.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
RES_RECS_COUNT
FLOAT
No. Resource records.
RES_RECS_EXIT_CT
FLOAT
No. Resource records supp.by exit.
SMF_ERRORS
INTEGER
Number of SMF write fails, for example when SMF is inactive.
From MNGSMFE.
SMF_RECORDS
INTEGER
Number of SMF records written to the SMF data set. From
MNGSMFR.
SMF_RECS_COMPRESS
FLOAT
No. SMF records compressed
SMF_RECS_NOT_COMP
FLOAT
No. SMF records not compressed.
SYSEVENT_ERRORS
INTEGER
Number of failed SYSEVENT writes. From MNGSYSEE.
SYSEVENT_RECORDS
INTEGER
Number of SYSEVENT notification records written to the MVS
SRM (for later processing by RMF). From MNGSYSER.
TSQ_RES_LIMIT
FLOAT
Tsqueue Resource Limit.
WLM_ADDR_SERVER
CHAR(10)
WLM Address Space Serverstatus.
WLM_CPU_CRIT
CHAR(15)
WLM CPU Critical.
WLM_GOAL_IMPORT
INTEGER
WLM goal importance.
WLM_GOAL_TYPE
CHAR(15)
WLM Goal type.
Chapter 6. Data tables, lookup tables, and control tables
223
CICS statistics component data tables
Column name
Data type
Description
WLM_GOAL_VALUE
INTEGER
WLM goal value.
WLM_MODE
CHAR(15)
Workload Management Mode.
WLM_OWN_WLOADNM
CHAR(8)
WLM Owning Workload Name.
WLM_RES_GRPNM
CHAR(8)
WLM Resource Group name – if any.
WLM_REP_CLSNM
CHAR(8)
WLM Report Class name – if any.
WLM_SERV_CLASS
CHAR(8)
WLM Service Class name – if any.
WLM_STORE_CRIT
CHAR(15)
WLM Storage Critical.
CICS_S_MONITOR_D
This table provides daily data on the monitoring domain. It contains consolidated
data from the CICS_S_MONITOR_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
EXCEPT_RECORDS
INTEGER
Number of exception records written to SMF. From MNGER.
EXCEPT_REC_SUPPR
INTEGER
Number of exception records suppressed by the global user exit
XMNOUT. From MNGERS.
FILE_RES_LIMIT
FLOAT
File Resource Limit.
PERFORM_RECORDS
INTEGER
Number of performance records scheduled for output to SMF
(both written and pending write). From MNGPR.
PERFORM_REC_SUPPR
INTEGER
Number of performance records suppressed by the global user
exit XMNOUT. From MNGPRS.
SMF_ERRORS
INTEGER
Number of SMF write fails, for example when SMF is inactive.
From MNGSMFE.
SMF_RECORDS
INTEGER
Number of SMF records written to the SMF data set. From
MNGSMFR.
SMF_RECS_COMPRESS
FLOAT
No. SMF records compressed
RES_RECS_COUNT
FLOAT
No. Resource records.
RES_RECS_EXIT_CT
FLOAT
No. Resource records supp. by exit.
SMF_RECS_NOT_COMP
FLOAT
No. SMF records not compressed.
SYSEVENT_ERRORS
INTEGER
Number of failed SYSEVENT writes. From MNGSYSEE.
SYSEVENT_RECORDS
INTEGER
Number of SYSEVENT notification records written to the MVS
SRM (for later processing by RMF). From MNGSYSER.
TSQ_RES_LIMIT
FLOAT
Tsqueue Resource Limit.
224
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
CICS_S_NC_LSTRUC_T
This table provides detailed Named Counter server list structure usage and access
statistics. For CICS/TS V1.3 and later, this maps the DFHNCS4K record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
NC_LSTRUCT_NAME
k
CHAR(16)
Complete name of the list structure. From S4NAME.
NC_CONNECT_NAME
K
CHAR(16)
Name for the connection to structure. From S4CNNAME.
NC_ALLOC_SIZE_MAX
FLOAT
Maximum size to which this structure could be altered.
From S4SIZEMX.
NC_ALLOCATED_SIZE
FLOAT
Allocated size for the list structure. From S4SIZE.
NC_ASYNC_RESP
FLOAT
Number of requests for which completion was
asynchronous. From S4ASYCT.
NC_BROWSE_REQS
FLOAT
Number of inquire KGE requests. From S4KGECT.
NC_CREATE_REQS
FLOAT
Number of create requests. From S4CRECT.
NC_DELETE_REQS
FLOAT
Number of delete requests. From S4DELCT.
NC_GET_INCR_REQS
FLOAT
Number of get and increment requests. From S4GETCT.
NC_INQUIRE_REQS
FLOAT
Number of inquire KEQ requests. From S4KEQCT.
NC_IO_ERR
FLOAT
Number of times that some other error code was returned
by IXLLIST. From S4SRP6CT.
NC_LISTCHK_FAIL
FLOAT
Number of times that a list authority comparison failed,
usually meaning that the table is in the process of being
deleted. From S4SRP4CT.
NC_LISTSTR_FULL
FLOAT
Number of times that the list structure became full. From
S4SRP5CT.
NC_NORMAL_RESP
FLOAT
Number of normal responses. From S4SRP1CT.
NC_NOTFOUND_RESP
FLOAT
Number of times that the specified entry (table or item)
was not found. From S4SRP2CT.
NC_SET_REQS
FLOAT
Number of set requests. From S4SETCT.
NC_SMR_STR_UNAVAIL
FLOAT
Structure temporarily unavailable, during system-managed
rebuild. From S4RSP7CT
NC_USED_ENTR_MAX
FLOAT
Maximum number of entries currently in use. From
S4ENTRHI.
NC_USED_ENTR_MIN
FLOAT
Minimum number of entries currently in use. From
S4ENTRLO.
Chapter 6. Data tables, lookup tables, and control tables
225
CICS statistics component data tables
Column name
Data type
Description
NC_VERSCHK_FAIL
FLOAT
Number of times that a version check failed for an entry
being updated, indicating that another task had updated it
first. From S4SRP3CT.
CICS_S_NC_LSTRUC_D
This table provides daily Named Counter server list structure usage and access
statistics. For CICS/TS V1.3 and later, this maps the DFHNCS4K record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
NC_LSTRUCT_NAME
K
CHAR(16)
Complete name of the list structure. From S4NAME.
NC_CONNECT_NAME
k
CHAR(16)
Name for the connection to structure. From S4CNNAME.
NC_ALLOC_SIZE_MAX
FLOAT
Maximum size to which this structure could be altered.
From S4SIZEMX.
NC_ALLOCATED_SIZE
FLOAT
Allocated size for the list structure. From S4SIZE.
NC_ASYNC_RESP
FLOAT
Number of requests for which completion was
asynchronous. From S4ASYCT.
NC_BROWSE_REQS
FLOAT
Number of inquire KGE requests. From S4KGECT.
NC_CREATE_REQS
FLOAT
Number of create requests. From S4CRECT.
NC_DELETE_REQS
FLOAT
Number of delete requests. From S4DELCT.
NC_GET_INCR_REQS
FLOAT
Number of get and Increment requests. From S4GETCT.
NC_INQUIRE_REQS
FLOAT
Number of inquire KEQ requests. From S4KEQCT.
NC_IO_ERR
FLOAT
Number of times that some other error code was returned
by IXLLIST. From S4SRP6CT.
NC_LISTCHK_FAIL
FLOAT
Number of times that a list authority comparison failed,
usually meaning that the table is in the process of being
deleted. From S4SRP4CT.
NC_LISTSTR_FULL
FLOAT
Number of times that the list structure became full. From
S4SRP5CT.
NC_NORMAL_RESP
FLOAT
Number of normal responses. From S4SRP1CT.
NC_NOTFOUND_RESP
FLOAT
Number of times that the specified entry (table or item)
was not found. From S4SRP2CT.
NC_SET_REQS
FLOAT
Number of set requests. From S4SETCT.
NC_SMR_STR_UNAVAIL
FLOAT
Structure temporarily unavailable, during system-managed
rebuild. From S4RSP7CT
226
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
NC_USED_ENTR_MAX
FLOAT
Maximum number of entries currently in use. From
S4ENTRHI.
NC_USED_ENTR_MIN
FLOAT
Minimum number of entries currently in use. From
S4ENTRLO.
NC_VERSCHK_FAIL
FLOAT
Number of times that a version check failed for an entry
being updated, indicating that another task had updated it
first. From S4SRP3CT.
CICS_S_NCS_STOR_T
This table provides detailed Named Counter server storage statistics. For CICS/TS
V1.3 and later, this maps the DFHNCS5K record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
NC_STORPOOL
K
CHAR(8)
Name of the storage pool AXMPGANY or AXMPGLOW.
From S5ANYNAM or S5LOWNAM.
NC_ADDRESS
FLOAT
Address of the storage pool area. From S5ANYPTR or
S5LOWPTR.
NC_COMPRESS
FLOAT
Number of compress (defragmentation) attempts. From
S5ANYRQC or S5LOWRQC.
NC_FREE_REQS
FLOAT
Number of storage free requests. From S5ANYRQS or
S5LOWRQS.
NC_FREEPAGE_LOW
FLOAT
Lowest number of free pages (since reset). From S5ANYLO
or S5LOWLO.
NC_GET
FLOAT
Number of storage get requests. From S5ANYRQG or
S5LOWRQG.
NC_GET_FAILED
FLOAT
Number of get requests that failed to obtain storage. From
S5ANYRQF or S5LOWRQF.
NC_PAGES_FREE
FLOAT
Number of free pages in the storage pool. From S5ANYFR or
S5LOWFR.
NC_PAGES_TOT
FLOAT
Total number of pages in the storage pool. From S5ANYMX
or S5LOWMX.
NC_PAGES_USED
FLOAT
Number of used pages in the storage pool. From S5ANYUS
or S5LOWUS.
NC_SIZE
FLOAT
Size of the storage pool. From S5ANYSIZ or S5LOWSIZ.
Chapter 6. Data tables, lookup tables, and control tables
227
CICS statistics component data tables
CICS_S_PIPELINE_T
This table provides details of various attribute settings of each PIPELINE
definition. A total use count for all PIPELINE definitions is also available. It
contains data from CICS statistics records (SMF 110, subtype 2 stid 105). For
CICS/TS V3.1 and later, it takes information from the DFHPIRDS CICS dsect.).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
PIPELINE_NAME
K
CHAR(8)
The name of the PIPELINE resource definition. From
PIRPIPNM.
CONFIG_FILE
VARCHAR(254)
The name of the HFS file that provides information about the
message handlers and their configuration. From PIRCONF.
SHELF_DIRECTORY
VARCHAR(254)
The fully qualified name of the shelf directory for the
PIPELINE definition. From PIRSHDIR.
WSDIR_PICKUP_DIR
VARCHAR(254)
The fully qualified name of the Web service binding directory
(also known as the pickup directory). From PIRWSDIR.
PIPELINE_USE_COUNT
FLOAT
The number of times this PIPELINE resource definition was
used to install a Web service or to process a Web service
request. From PIRUSECNT.
CICS_S_PROGRAM_T
This table provides detailed program statistics. It contains data from CICS statistics
records (loader domain resource statistics). It maps the DFHLDRDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
228
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CHAR(8)
Name of program. From LDRPNAME.
AUTOINST_ATTEMPTS
INTEGER
Number of times that a program autoinstall was attempted. For
CICS V4 and later. From PGGATT.
AUTOINST_FAIL_CNT
INTEGER
Number of times that a program autoinstall failed due to
reasons other than rejects. Examples: the URM program did not
provide valid attributes, or the model name specified by the
URM was not defined. For CICS V4 and later. From PGGFAIL.
AUTOINST_REJECTS
INTEGER
Number of times that a program autoinstall request was
rejected by the program autoinstall URM program. For CICS
V4 and later. From PGGREJ.
DFHRPL_REOPENED
INTEGER
Number of times the loader received an end-of-extent condition
during a LOAD, successfully closed and re-opened the
DFHRPL library, and retried the LOAD. For CICS V4 and later.
From LDGDREBS.
FETCH_AVG_SEC
FLOAT
Average time taken to perform a fetch, in seconds. Calculated
as LDRFT/(LDRFC*62500).
FETCHES
INTEGER
Number of times the loader domain has issued an MVS LOAD
request. From LDRFC.
FETCH_SEC
FLOAT
Time taken to perform all fetches, in seconds. Calculated as
LDRFT/62500.
LIB_DSNAME
CHAR(44)
Program library dsname. From LDRLBDNM.
LIB_NAME
CHAR(8)
Program library name. From LDRLBNM.
LIBRARY_LOAD_REQ
INTEGER
Number of times the loader has issued an MVS LOAD request
to load programs from the DFHRPL library concatenation into
CICS managed storage. Modules in the LPA are not included.
For CICS V4 and later. From LDGLLR.
LIB_SRCH_ORD_UP_T
FLOAT
Library search order update time. From LDGLSORT.
LIB_SRCH_ORD_UP
INTEGER
Library search order updates. From LDGLBSOU.
LOAD_REQUESTS
INTEGER
Number of times CICS tasks within the system have issued
load requests to the loader domain. From LDRTU.
LOAD_SEC
FLOAT
Time, in seconds, taken for the number of library loads
indicated by LIBRARY_LOAD_REQ. For CICS V4 and later.
From LDGLLT.
LOAD_SEC_AVG
FLOAT
Average time, in seconds,to load a program. For CICS V4 and
later. Calculated as LDGLLT/LDGLLR.
LOADW_SRCH_ORD_UP
INTEGER
Load waits due to search order update. From LDGLWSOU.
LOCATION
CHAR(7)
Location of the program in storage, if loaded. From LDRLOCN.
NEW_COPIES
INTEGER
Number of times a NEWCOPY has been requested. From
LDRTN.
NOT_USED_AVG_SEC
FLOAT
Average time, in seconds, that a program is eligible for removal
from storage by the DPSC mechanism. For CICS V4 and later.
Calculated as LDGDPSCT/LDGDPSCR.
NOT_USED_PROGRAMS
INTEGER
Number of programs on the Not-In-Use (NIU) queue. For CICS
V4 and later. From LDGPROGNIU.
NOT_USED_RECLAIMS
INTEGER
Number of reclaims made from the Not-In-Use (NIU) queue.
Reclaims occur when a request is issued for programs currently
in the Not-In-Use queue. For CICS V4 and later. From
LDGRECNIU.
PROGRAM_NAME
K
Chapter 6. Data tables, lookup tables, and control tables
229
CICS statistics component data tables
Column name
Data type
Description
NOT_USED_SEC
FLOAT
Time, in seconds, that all programs spent in the Not-In-Use
(NIU) queue. For CICS V4 and later. From LDGDPSCT.
NOT_USED_STOR_KB
INTEGER
Current amount of storage, in kilobytes, that is occupied by
Not-In-Use (NIU) programs. For CICS V4 and later. From
LDGSTGNIU.
PROGRAM_SIZE
INTEGER
Size of the program, in bytes. From LDRPSIZE.
PROGRAMS_REMOVED
INTEGER
Number of program instances removed from storage by the
Dynamic Program Storage Compression (DPSC) mechanism.
For CICS V4 and later. From LDGDPSCR.
PROGRAM_USES
INTEGER
Number of uses of any program by the CICS system. For CICS
V4 and later. From LDGPUSES.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REQ_PEAK_WAIT
INTEGER
Peak number of suspended tasks. For CICS V4 and later. From
LDGWLRHW.
REQ_TIMES_AT_PEAK
INTEGER
Number of times the peak indicated by REQ_PEAK_WAIT was
reached. For CICS V4 and later. From LDGHWMT.
REQ_WAITED
INTEGER
Number of loader domain requests forced to suspend due to
operations like NEWCOPY requests, LPA search, or physical
load in progress. This does not include currently waiting tasks.
For CICS V4 and later. From LDGWTDLR.
REQ_WAITING
INTEGER
Number of loader domain requests currently forced to suspend
due to other operations like: NEWCOPY requests, LPA search
or physical load in progress. For CICS V4 and later. From
LDGWLR.
RPL_OFFSET
INTEGER
Offset into the DFHRPL DD concatenation. The first data set is
offset 0. From LDRRPLO.
TIMES_REMOVED
INTEGER
Number of times an instance of this program has been
removed. From LDRRPC.
WAIT_TIME
FLOAT
Time, in seconds, that the suspended requests counted by
REQ_WAITED spent waiting. For CICS V4 and later. From
LDGTTW.
CICS_S_PROGRAM_D
This table provides daily statistics on programs in the CICS system. It contains
summarized data from the CICS_S_PROGRAM_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
230
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
PROGRAM_NAME
K
CHAR(8)
Name of program. From LDRPNAME.
AUTOINST_ATTEMPTS
INTEGER
Number of times that a program autoinstall was attempted. For
CICS V4 and later. From PGGATT.
AUTOINST_FAIL_CNT
INTEGER
Number of times that a program autoinstall failed due to
reasons other than rejects. Examples: the URM program did not
provide valid attributes, or the model name specified by the
URM was not defined. For CICS V4 and later. From PGGFAIL.
AUTOINST_REJECTS
INTEGER
Number of times that a program autoinstall request was rejected
by the program autoinstall URM program. For CICS V4 and
later. From PGGREJ.
DFHRPL_REOPENED
INTEGER
Number of times the loader received an end-of-extent condition
during a LOAD, successfully closed and re-opened the DFHRPL
library, and retried the LOAD. For CICS V4 and later. From
LDGDREBS.
FETCH_AVG_SEC
FLOAT
Average time taken to perform a fetch, in seconds. Calculated as
LDRFT/(LDRFC*62500).
FETCHES
INTEGER
Number of times the loader domain has issued an MVS LOAD
request. From LDRFC.
FETCH_SEC
FLOAT
Time taken to perform all fetches, in seconds. Calculated as
LDRFT/62500.
LIBRARY_LOAD_REQ
INTEGER
Number of times the loader has issued an MVS LOAD request
to load programs from the DFHRPL library concatenation into
CICS managed storage. Modules in the LPA are not included.
For CICS V4 and later. From LDGLLR.
LIB_SRCH_ORD_UP_T
FLOAT
Library search order update time. From LDGLSORT.
LIB_SRCH_ORD_UP
INTEGER
Library search order updates. From LDGLBSOU.
LOAD_REQUESTS
INTEGER
Number of times CICS tasks within the system have issued load
requests to the loader domain. From LDRTU.
LOAD_SEC
FLOAT
Time, in seconds, taken for the number of library loads indicated
by LIBRARY_LOAD_REQ. For CICS V4 and later. From
LDGLLT.
LOADW_SRCH_ORD_UP
INTEGER
Load waits due to search order update. From LDGLWSOU.
NEW_COPIES
INTEGER
Number of times a NEWCOPY has been requested. From
LDRTN.
NOT_USED_RECLAIMS
INTEGER
Number of reclaims made from the Not-In-Use (NIU) queue.
Reclaims occur when a request is issued for programs currently
in the Not-In-Use queue. For CICS V4 and later. From
LDGRECNIU.
NOT_USED_SEC
FLOAT
Time, in seconds, that all programs spent in the Not-In-Use
(NIU) queue. For CICS V4 and later. From LDGDPSCT.
PROGRAM_SIZE
INTEGER
Size of the program, in bytes. From LDRPSIZE.
PROGRAMS_REMOVED
INTEGER
Number of program instances removed from storage by the
Dynamic Program Storage Compression (DPSC) mechanism. For
CICS V4 and later. From LDGDPSCR.
Chapter 6. Data tables, lookup tables, and control tables
231
CICS statistics component data tables
Column name
Data type
Description
REQ_PEAK_WAIT
INTEGER
Peak number of suspended tasks. For CICS V4 and later. From
LDGWLRHW.
REQ_TIMES_AT_PEAK
INTEGER
Number of times the peak indicated by REQ_PEAK_WAIT was
reached. For CICS V4 and later. From LDGHWMT.
REQ_WAITED
INTEGER
Number of loader domain requests forced to suspend due to
operations like NEWCOPY requests, LPA search, or physical
load in progress. This does not include currently waiting tasks.
For CICS V4 and later. From LDGWTDLR.
TIMES_REMOVED
INTEGER
Number of times an instance of this program has been removed.
From LDRRPC.
WAIT_TIME
FLOAT
Time, in seconds, that the suspended requests counted by
REQ_WAITED spent waiting. For CICS V4 and later. From
LDGTTW.
CICS_S_RECOV_MGR_T
This table provides detailed CICS Recovery Manager statistics. For CICS/TS V1.1
and later, this maps the DFHRMGDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SYNC_FORWARD_NUM
FLOAT
Number of syncpoints that were issued. From RMGSYFWD.
SYNC_BACKWARD_NUM
FLOAT
Number of syncpoint rollbacks that were issued. From
RMGSYBWD.
RESYNC_NUM
FLOAT
Number of resyncs that were issued. From RMGRESYN.
TOT_USH_INDFAIL
FLOAT
Total number of UOWs that were shunted for indoubt failure.
From RMGTSHIN.
TOT_USH_INDFAIL_TM
FLOAT
Total time that UOWs were shunted for indoubt failure. From
RMGTSHTI.
CUR_USH_INDFAIL
FLOAT
Current number of UOWs that were shunted for indoubt
failure. From RMGTSHIN.
CUR_USH_INDFAIL_TM
FLOAT
Total time that the current UOWs were shunted for indoubt
failure. From RMGTSHTI.
TOT_USH_COM_FAIL
FLOAT
Total number of UOWs that were shunted for
commit/backout failure. From RMGTSHRO.
TOT_USH_COM_FAI_TM
FLOAT
Total time that UOWs were shunted for commit/backout
failure. From RMGTSHTR.
232
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CUR_USH_COM_FAIL
FLOAT
Current number of UOWs that were shunted for
commit/backout failure. From RMGTSHRO.
CUR_USH_COM_FAI_TM
FLOAT
Total time that the current UOWs were shunted for
commit/backout failure. From RMGTSHTR.
IN_ACT_FOR_TRANDEF
FLOAT
Number of forced indoubt action resolutions that were due to
the transaction definition specifying that it cannot support
indoubt waiting. From RMGIAFTR.
IN_ACT_FOR_TIMEOUT
FLOAT
Number of forced indoubt action resolutions due to the
indoubt waiting. From RMGIAFTL.
IN_ACT_FOR_NOWAIT
FLOAT
Number of forced indoubt action resolutions due to a
recoverable resource or resource manager coordinator being
unable to support indoubt waiting. From RMGIAFNW.
IN_ACT_FOR_OPERAT
FLOAT
Number of forced indoubt action resolutions due to the
operator canceling the wait for indoubt resolution. From
RMGIAFOP.
IN_ACT_FOR_OTHEREV
FLOAT
Number of forced indoubt action resolutions due to all other
reasons other than those previously spelt out. From
RMGIAFOT.
IN_ACT_FOR_TDQUEUE
FLOAT
Number of forced indoubt action resolutions due to a
recoverable resource or resource manager coordinator being
unable to support indoubt waiting. From RMGNWTD.
IN_ACT_FOR_LU61CON
FLOAT
Number of UOW forces that occurred because the UOW uses
an LU6.1 intersystem link, which cannot support indoubt
waiting. From RMGNW61.
IN_ACT_FOR_MROCON
FLOAT
Number of UOW forces that occurred because the UOW uses
an MRO intersystem link to a downlevel CICS region, which
cannot support indoubt waiting. From RMGNMRO.
IN_ACT_FOR_RMIEXIT
FLOAT
Number of UOW forces that occurred because the UOW uses
an RMI that declared an interst in syncpoint but could not
support indoubt waiting. From RMGNRMI.
IN_ACT_FOR_OTHEREX
FLOAT
Number of forced indoubt action resolutions due to a
recoverable resource or resource manager coordinator being
unable to support indoubt waiting. From RMGWOTH.
IN_ACT_MISMATCHES
FLOAT
Number of forced indoubt action resolutions that a
participating resource manager coordinator solved in a
different manner from CICS. From RMGIAMIS.
CICS_S_RECOV_MGR_D
This table provides daily CICS Recovery Manager statistics. For CICS/TS V1.1 and
later, this maps the DFHRMGDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
Chapter 6. Data tables, lookup tables, and control tables
233
CICS statistics component data tables
Column name
Data type
Description
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SYNC_FORWARD_NUM
FLOAT
Number of syncpoints that were issued. From RMGSYFWD.
SYNC_BACKWARD_NUM
FLOAT
Number of syncpoint rollbacks that were issued. From
RMGSYBWD.
RESYNC_NUM
FLOAT
Number of resyncs that were issued. From RMGRESYN.
TOT_USH_INDFAIL
FLOAT
Total number of UOWs that were shunted for indoubt failure.
From RMGTSHIN.
TOT_USH_INDFAIL_TM
FLOAT
Total time that UOWs were shunted for indoubt failure. From
RMGTSHTI.
CUR_USH_INDFAIL
FLOAT
Current number of UOWs that were shunted for indoubt
failure. From RMGTSHIN.
CUR_USH_INDFAIL_TM
FLOAT
Total time that the current UOWs were shunted for indoubt
failure. From RMGTSHTI.
TOT_USH_COM_FAIL
FLOAT
Total number of UOWs that were shunted for commit/backout
failure. From RMGTSHRO.
TOT_USH_COM_FAI_TM
FLOAT
Total time that UOWs were shunted for commit/backout
failure. From RMGTSHTR.
CUR_USH_COM_FAIL
FLOAT
Current number of UOWs that were shunted for
commit/backout failure. From RMGTSHRO.
CUR_USH_COM_FAI_TM
FLOAT
Total time that the current UOWs were shunted for
commit/backout failure. From RMGTSHTR.
IN_ACT_FOR_TRANDEF
FLOAT
Number of forced indoubt action resolutions that were due to
the transaction definition specifying that it cannot support
indoubt waiting. From RMGIAFTR.
IN_ACT_FOR_TIMEOUT
FLOAT
Number of forced indoubt action resolutions due to the
indoubt waiting. From RMGIAFTL.
IN_ACT_FOR_NOWAIT
FLOAT
Number of forced indoubt action resolutions due to a
recoverable resource or resource manager coordinator being
unable to support indoubt waiting. From RMGIAFNW.
IN_ACT_FOR_OPERAT
FLOAT
Number of forced indoubt action resolutions due to the
operator canceling the wait for indoubt resolution. From
RMGIAFOP.
IN_ACT_FOR_OTHEREV
FLOAT
Number of forced indoubt action resolutions due to all other
reasons other than those previously spelt out. From
RMGIAFOT.
IN_ACT_FOR_TDQUEUE
FLOAT
Number of forced indoubt action resolutions due to a
recoverable resource or resource manager coordinator being
unable to support indoubt waiting. From RMGNWTD.
IN_ACT_FOR_LU61CON
FLOAT
Number of UOW forces that occurred because the UOW uses
an LU6.1 intersystem link, which cannot support indoubt
waiting. From RMGNW61.
IN_ACT_FOR_MROCON
FLOAT
Number of UOW forces that occurred because the UOW uses
an MRO intersystem link to a downlevel CICS region, which
cannot support indoubt waiting. From RMGNMRO.
IN_ACT_FOR_RMIEXIT
FLOAT
Number of UOW forces that occurred because the UOW uses
an RMI that declared an interst in syncpoint but could not
support indoubt waiting. From RMGNRMI.
CICS_SYSTEM_ID
234
K
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
IN_ACT_FOR_OTHEREX
FLOAT
Number of forced indoubt action resolutions due to a
recoverable resource or resource manager coordinator being
unable to support indoubt waiting. From RMGWOTH.
IN_ACT_MISMATCHES
FLOAT
Number of forced indoubt action resolutions that a
participating resource manager coordinator solved in a
different manner from CICS. From RMGIAMIS.
CICS_S_STOR_DOM_T
This table provides detailed domain storage statistics. It maps the DFHSMDDS
record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SUBPOOL_NAME
K
CHAR(8)
Name of the domain subpool. From SMDSPN.
CURRENT_ELEMENTS
INTEGER
Number of storage elements in the subpool. From SMDCELEM.
DSA_IDENTIFIER
CHAR(2)
A unique identifier for the DSA. From SMDDSAINDEX.
DSA_NAME
CHAR(5)
Name of the DSA that the domain subpool is allocated from.
From SMDDSANAME.
ELEMENT_BOUNDRY
INTEGER
Boundary on which each element is aligned. From SMDBNDRY.
ELEMENT_CHAINING
CHAR(2)
Indicates whether SM maintains an element chain for the
subpool with the addresses and length of each element. From
SMDELCHN.
ELEMENTS_LENGTH
INTEGER
Sum of lengths of all the elements in the subpool, in bytes. From
SMDCES.
ELEMENT_TYPE
INTEGER
Indicates whether the elements in the subpool are fixed or
variable length. From SMDETYPE.
FREEMAINS
INTEGER
Number of FREEMAIN requests. From SMDFMREQ.
GETMAINS
INTEGER
Number of GETMAIN requests. From SMDGMREQ.
INITIAL_FREE_BYTE
INTEGER
Initial free area for the subpool, in bytes. From SMDIFREE.
PAGE_STORAGE_BYTE
INTEGER
Space taken by all pages allocated to the subpool, in bytes. From
SMDCPS.
PAGE_STORAGE_PEAK
INTEGER
Peak page storage allocated to support storage requirements.
From SMDHWMPS.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
Chapter 6. Data tables, lookup tables, and control tables
235
CICS statistics component data tables
Column name
Data type
Description
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
STORAGE_LOCATION
CHAR(10)
Storage location of this domain subpool. From SMDLOCN.
SUBPOOL_ACCESS
CHAR(4)
Type of access of the subpool. From SMDACCESS.
CICS_S_STOR_DOM_D
This table provides daily statistics on domain storage in the CICS system. It
contains summarized data from the CICS_S_STOR_DOM_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
SUBPOOL_NAME
K
CHAR(8)
Name of domain subpool. From SMDSPN.
DSA_IDENTIFIER
CHAR(2)
A unique identifier for the DSA. From SMDDSAINDEX.
DSA_NAME
CHAR(5)
Name of the DSA that the domain subpool is allocated from.
From SMDDSANAME.
FREEMAINS
INTEGER
Number of FREEMAIN requests. From SMDFMREQ.
GETMAINS
INTEGER
Number of GETMAIN requests. From SMDGMREQ.
PAGE_STORAGE_PEAK
INTEGER
Peak page storage allocated to support storage requirements.
From SMDHWMPS.
CICS_S_STOR_DSA_T
This table provides detailed CICS/ESA and CICS/TS storage statistics. It maps the
DFHSMSDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
236
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
PAGEPOOL_NAME
K
CHAR(5)
CDSA, UDSA, ECDSA, EUDSA or ERDSA. For CICS 3.3 or
later, from SMSDSANAME. For CICS 3.2, DSA or EDSA, based
on SMSLOCN.
ACCESS_TYPE
CHAR(2)
Type of access of the page subpool. From SMSACCESS.
ADD_SUBPOOL_REQ
INTEGER
Number of ADD SUBPOOL requests. From SMSASR.
CICS_SOS_COUNT
INTEGER
Number of times CICS went short on storage in this pagepool.
From SMSSOS.
CURR_AS_ACTIVE
FLOAT
Current Address Space addressable. From SMSASACTIVE.
CURR_GDSA_ACTIVE
FLOAT
Current GDSA active. From SMSGDSAACTIVE.
CUSHION_BYTES
INTEGER
Size of the cushion, in bytes. From SMSCSIZE.
CUSHION_RELEASES
INTEGER
Number of times the number of free pages went below the
cushion. From SMSCREL.
CUSH_LIMIT
FLOAT
Cushion limit.From SMSATBCUSHLIMIT
CUSH_RELEASE
FLOAT
Allocates in cushion (releases). From SMSATBCUSHRELS.
DELETE_SUBPOOL_REQ
INTEGER
Number of DELETE SUBPOOL requests. From SMSDSR.
DSA_BYTES
INTEGER
Size of the CDSA, UDSA, ECDSA, EUDSA, or ERDSA, in bytes.
From SMSDSASZ.
DSA_BYTES_PEAK
INTEGER
Peak size of the CDSA, UDSA, SDSA, RDSA, ECDSA, EUDSA,
ESDSA, or ERDSA, expressed in bytes, since the last time that
statistics were recorded. For CICS V4 and later. From
SMSHWMDSASZ.
DSA_CURRENT_TOT
INTEGER
Total amount of storage currently allocated to the DSAs below
the line. This value may be smaller or larger than DSA_LIMIT.
For CICS V4 or later. From SMSDSATOTAL.
DSA_INDEX_CODE
CHAR(2)
Code representing the CDSA or DSA (01), UDSA (02), ECDSA
or EDSA (03), EUDSA (04), or ERDSA (05); the pagepool that
this subpool is allocated from. From SMSDSAINDEX, for CICS
3.3 or later, or derived from SMSLOCN for CICS 3.2.
DSA_LIMIT
INTEGER
Current DSA limit, in bytes. For CICS V4 and later. From
SMSDSALIMIT.
DSA_TOTAL_PEAK
INTEGER
Total amount of storage allocated to the DSAs below the line.
This value may be smaller or larger than DSA_LIMIT. For CICS
V4 or later. From SMSHWMDSATOTAL.
EDSA_CURRENT_TOT
INTEGER
Total amount of storage currently allocated to the DSAs above
the line. This value may be smaller or larger than EDSA_LIMIT.
For CICS V4 or later. From SMSDSATOTAL.
EDSA_LIMIT
INTEGER
Current EDSA limit, in bytes. For CICS V4 and later. From
SMSEDSALIMIT.
EDSA_TOTAL_PEAK
INTEGER
Total amount of storage allocated to the DSAs above the line.
This value may be smaller or larger than ESDA_LIMIT. For
CICS V4 or later. From SMSHWMESDATOTAL.
EXTENTS_ADDED
INTEGER
Number of extents added to a dynamic storage area since the
last time statistics were recorded. For CICS V4 and later. From
SMSEXTSA.
Chapter 6. Data tables, lookup tables, and control tables
237
CICS statistics component data tables
Column name
Data type
Description
EXTENTS_COUNT
INTEGER
Number of extents currently allocated to a specified dynamic
storage area. For CICS V4 and later. From SMSEXTS.
EXTENTS_RELEASED
INTEGER
Number of extents that have been released from a dynamic
storage area since the last time statistics were recorded. For
CICS V4 and later. From SMSEXTSR.
FREEMAINS
INTEGER
Number of FREEMAIN requests. From SMSFMREQ.
FREE_STOR_BYTES
INTEGER
Amount of free storage in this pagepool, in bytes. From
SMSFSTG.
FREE_STOR_LOW
INTEGER
Smallest amount of free storage, in bytes, since the last time
that statistics were recorded. For CICS V4 and later. From
SMSLWMFSTG.
FREE_STOR_PCT
FLOAT
Percentage of free storage. Calculated as (SMSFSTG/
SMSDSASZ)*100.
FREE_STOR_PEAK
INTEGER
Largest amount of free storage, in bytes, since the last time that
statistics were recorded. For CICS V4 and later. From
SMSHWMFSTG.
GETMAINS
INTEGER
Number of GETMAIN requests. From SMSGMREQ.
GETMAIN_SUSPENDS
INTEGER
Number of GETMAIN requests currently suspended for
storage. From SMSCSS.
GETMAIN_SUSP_NO
INTEGER
Number of failed GETMAIN requests with SUSPEND(NO).
From SMSCRISS.
GETMAIN_SUSP_PEAK
INTEGER
Peak number of GETMAIN requests suspended. From
SMSHWMSS.
GETMAIN_SUSP_YES
INTEGER
Number of failed GETMAIN requests with SUSPEND(YES).
From SMSUCSS.
GETSTORE_SIZE
FLOAT
GETSTOR request size. From SMSGETSTORSIZE.
HWM_AS_ACTIVE
FLOAT
HWM Address Space addressable. From SMSHWMASACTIVE.
HWM_GDSA_ACTIVE
FLOAT
HWM GDSA active. From SMSHWMGDSAACTIVE.
LARGEST_FREE_AREA
INTEGER
Length of the largest contiguous free area, in bytes. From
SMSLFA.
MEMLIMIT_SIZE
FLOAT
MEMLIMIT Size. From SMSMEMLIMIT
MEMLIMIT_SOURCE
CHAR(8)
MEMLIMIT Source. MEMLIMIT is set by SMFPRMxx, JCL, JCL
Region, or by IEFUSIExit. From SMSMEMLIMITSRC
MVS_A16_REQS_TOT
REAL
The total number of MVS storage requests that have waited for
MVS storage above 16 MB. From SMSMVSSTGREQWAITS.
MVS_A16_TIME_TOT
REAL
The total time that MVS storage requests have spent waiting
for MVS storage above 16 MB, in seconds. From
SMSTIMEWAITMVS.
PAGE_POOL_COUNT
INTEGER
Number of pagepools in the CICS region. For CICS V4 and
later. From SMSNPAGP.
PAGE_STORAGE_PEAK
INTEGER
Peak page storage allocated, in bytes. From SMSHWMPS.
PURGED_REQUESTS
INTEGER
Number of requests that were purged while suspended. From
SMSPWWS.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
238
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record. Example:
0330. From SMFSTRVN.
REENT_PGMS_PROTECT
CHAR(3)
This column indicates if read-only programs reside in key-0
protected storage (YES) or not (NO). For CICS V4 and later.
From SMSRENTPGM.
SOS_SEC
INTEGER
Time that CICS spent in SOS in this pagepool, in seconds. From
SMSTSOS.
STORAGE_LOCATION
CHAR(2)
Above (02) or below (01) the 16 MB line. From SMSLOCN.
STORAGE_VIOLATIONS
INTEGER
Number of storage violations recorded. From SMSSV.
STOR_PROTECT_ACT
CHAR(3)
Indicates if CICS storage protection is active (YES) or inactive
(NO). For CICS V4 and later. From SMSSTGPROT.
SUBPOOLS
INTEGER
Current number of subpools. From SMSCSUBP.
SUBSP_COMMON_CUR
INTEGER
Number of tasks currently allocated to the common subspace.
For CICS V4 and later. From SMSCSSCUR.
SUBSP_COMMON_PEAK
INTEGER
Peak number of tasks concurrently allocated to the common
subspace. For CICS V4 and later. From SMSCSSHWM.
SUBSP_COMMON_TOT
INTEGER
Total number of tasks allocated to the common subspace. For
CICS V4 and later. From SMSCSSCUM.
SUBSP_UNIQUE_CUR
INTEGER
Current number of unique subspace users. Number of tasks
currently allocated a unique subspace. For CICS V4 or later.
From SMSUSSCUR.
SUBSP_UNIQUE_PEAK
INTEGER
Peak number of tasks concurrently allocated a unique subspace.
For CICS V4 and later. From SMSUSSHWM.
SUBSP_UNIQUE_TOT
INTEGER
Total number of tasks that have been allocated a unique
subspace. For CICS V4 and later. From SMSUSSCUM.
TRAN_ISOLAT_ACT
CHAR(3)
This column indicates if transaction isolation is active (YES) or
not (NO). For CICS V4 and later. From SMSTRANISO.
CICS_S_STOR_DSA_D
This table provides daily statistics on storage in the CICS system. It contains
summarized data from the CICS_S_STOR_DSA_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
PAGEPOOL_NAME
K
CHAR(5)
CDSA, UDSA, ECDSA, EUDSA, or ERDSA. For CICS 3.3 or
later, from SMSDSANAME. For CICS 3.2, DSA or EDSA, based
on SMSLOCN.
INTEGER
Number of ADD SUBPOOL requests. From SMSASR.
ADD_SUBPOOL_REQ
Chapter 6. Data tables, lookup tables, and control tables
239
CICS statistics component data tables
Column name
Data type
Description
CICS_SOS_COUNT
INTEGER
Number of times CICS went short on storage in this pagepool.
From SMSSOS.
CURR_AS_ACTIVE
FLOAT
Current Address Space addressable. From SMSASACTIVE
CURR_GDSA_ACTIVE
FLOAT
Current GDSA active. From SMSGDSAACTIVE
CUSHION_BYTES
INTEGER
Size of the cushion, in bytes. From SMSCSIZE.
CUSHION_RELEASES
INTEGER
Number of times the number of free pages went below the
cushion. From SMSCREL.
CUSH_LIMIT
FLOAT
Cushion limit. From SMSATBCUSHLIMIT
CUSH_RELEASE
FLOAT
Allocates in cushion (releases). From SMSATBCUSHRELS
DELETE_SUBPOOL_REQ
INTEGER
Number of DELETE SUBPOOL requests. From SMSDSR.
DSA_BYTES
INTEGER
Size of the CDSA, UDSA, ECDSA, EUDSA or ERDSA, in bytes.
From SMSDSASZ.
DSA_BYTES_PEAK
INTEGER
Peak size of the CDSA, UDSA, SDSA, RDSA, ECDSA, EUDSA,
ESDSA, or ERDSA, expressed in bytes, since the last time that
statistics were recorded. For CICS V4 and later. From
SMSHWMDSASZ.
DSA_TOTAL_PEAK
INTEGER
Total amount of storage allocated to the DSAs below the line.
This value may be smaller or larger than DSA_LIMIT. For CICS
V4 or later. From SMSHWMDSATOTAL.
EDSA_TOTAL_PEAK
INTEGER
Total amount of storage allocated to the DSAs above the line.
This value may be smaller or larger than ESDA_LIMIT. For
CICS V4 or later. From SMSHWMESDATOTAL.
EXTENTS_ADDED
INTEGER
Number of extents added to a dynamic storage area since the
last time statistics were recorded. For CICS V4 and later. From
SMSEXTSA.
EXTENTS_RELEASED
INTEGER
Number of extents that have been released from a dynamic
storage area since the last time statistics were recorded. For
CICS V4 and later. From SMSEXTSR.
FREEMAINS
INTEGER
Number of FREEMAIN requests. From SMSFMREQ.
FREE_STOR_BYTES
INTEGER
Amount of free storage in this pagepool, in bytes. From
SMSFSTG.
FREE_STOR_LOW
INTEGER
Smallest amount of free storage, in bytes, since the last time
that statistics were recorded. For CICS V4 and later. From
SMSLWMFSTG.
FREE_STOR_PCT
FLOAT
Percentage of free storage. Calculated as (SMSFSTG/
SMSDSASZ)*100.
FREE_STOR_PEAK
INTEGER
Largest amount of free storage, in bytes, since the last time that
statistics were recorded. For CICS V4 and later. From
SMSHWMFSTG.
GETMAINS
INTEGER
Number of GETMAIN requests. From SMSGMREQ.
GETMAIN_SUSP_NO
INTEGER
Number of failed GETMAIN requests with SUSPEND(NO).
From SMSCRISS.
GETMAIN_SUSP_PEAK
INTEGER
Peak number of GETMAIN requests suspended. From
SMSHWMSS.
GETMAIN_SUSP_YES
INTEGER
Number of failed GETMAIN requests with SUSPEND(YES).
From SMSUCSS.
GETSTORE_SIZE
FLOAT
GETSTOR request size. From SMSGETSTORSIZE
HWM_AS_ACTIVE
FLOAT
HWM Address Space addressable. From SMSHWMASACTIVE
240
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
HWM_GDSA_ACTIVE
FLOAT
HWM GDSA active. From SMSHWMGDSAACTIVE
LARGEST_FREE_AREA
INTEGER
Length of the largest contiguous free area, in bytes. From
SMSLFA.
MEMLIMIT_SIZE
FLOAT
MEMLIMIT Size. From SMSMEMLIMIT
MEMLIMIT_SOURCE
CHAR(8)
MEMLIMIT Source. MEMLIMIT is set by SMFPRMxx, JCL, JCL
Region, or by IEFUSIExit. From SMSMEMLIMITSRC
MVS_A16_REQS_TOT
REAL
The total number of MVS storage requests that have waited for
MVS storage above 16 MB, in seconds. From
SMSMVSSTGREQWAITS.
MVS_A16_TIME_TOT
REAL
The total time that MVS storage requests have spent waiting
for MVS storage above 16 MB. From SMSTIMEWAITMVS.
PURGED_REQUESTS
INTEGER
Number of requests that were purged while suspended. From
SMSPWWS.
SOS_SEC
INTEGER
Time that CICS spent in SOS in this pagepool, in seconds. From
SMSTSOS.
STORAGE_VIOLATIONS
INTEGER
Number of storage violations recorded. From SMSSV.
SUBPOOLS
INTEGER
Current number of subpools. From SMSCSUBP.
SUBSP_COMMON_PEAK
INTEGER
Peak number of tasks concurrently allocated to the common
subspace. For CICS V4 and later. From SMSCSSHWM.
SUBSP_COMMON_TOT
INTEGER
Total number of tasks allocated to the common subspace. For
CICS V4 and later. From SMSCSSCUM.
SUBSP_UNIQUE_PEAK
INTEGER
Peak number of tasks concurrently allocated a unique subspace.
For CICS V4 and later. From SMSUSSHWM.
SUBSP_UNIQUE_TOT
INTEGER
Total number of tasks that have been allocated a unique
subspace. For CICS V4 and later. From SMSUSSCUM.
CICS_S_STOR_TASK_T
This table provides detailed CICS/ESA and CICS/TS task subpool statistics. It
maps the DFHSMTDS record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DSA_NAME
K
CHAR(5)
CDSA, UDSA, ECDSA, or EUDSA. For CICS 3.3, from
SMTDSANAME. For CICS 3.2, DSA or EDSA, based on
SMTLOCN.
Chapter 6. Data tables, lookup tables, and control tables
241
CICS statistics component data tables
Column name
Data type
Description
DSA_IDENTIFIER
CHAR(2)
Code representing the CDSA or DSA (01), UDSA (02), ECDSA
or EDSA (03), or EUDSA (04); the pagepool that this subpool is
allocated from. From SMTDSAINDEX, for CICS 3.3, or derived
from SMTLOCN for CICS 3.2.
ELEMENTS
INTEGER
Number of elements in all the task subpools in this DSA. From
SMTCNE.
ELEMENTS_BYTES
INTEGER
Sum of storage occupied by all elements, in bytes. From
SMTCES.
FREEMAINS
INTEGER
Number of task subpool FREEMAIN requests. From
SMTFMREQ.
GETMAINS
INTEGER
Number of task subpool GETMAIN requests. From
SMTGMREQ.
PAGEPOOL_LOCATION
CHAR(2)
Above (02) or below (01) the 16MB line. From SMTLOCN.
PAGE_STORAGE_BYTES
INTEGER
Sum of storage in all pages allocated to the task subpools in
this DSA, in bytes. From SMTCPS.
PAGE_STORAGE_PEAK
INTEGER
Peak page storage allocated to the task subpools in this DSA, in
bytes. From SMTHWMPS.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record.
Example: 0330. From SMFSTRVN.
SUBPOOL_ACCESS
CHAR(2)
Type of access of the subpool. From SMTACCESS.
CICS_S_STOR_TASK_D
This table provides daily statistics on task storage in the CICS system. It contains
summarized data from the CICS_S_STOR_TASK_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
START.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DSA_NAME
K
CHAR(5)
CDSA, UDSA, ECDSA, or EUDSA. For CICS 3.3, from
SMTDSANAME. For CICS 3.2, DSA or EDSA, based on
SMTLOCN.
ELEMENTS
INTEGER
Number of elements in all the task subpools in this DSA. From
SMTCNE.
ELEMENTS_BYTES
INTEGER
Sum of storage occupied by all elements, in bytes. From
SMTCES.
242
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
FREEMAINS
INTEGER
Number of task subpool FREEMAIN requests. From
SMTFMREQ.
GETMAINS
INTEGER
Number of task subpool GETMAIN requests. From
SMTGMREQ.
PAGE_STORAGE_BYTES
INTEGER
Sum of storage in all pages allocated to the task subpools in
this DSA, in bytes. From SMTCPS.
PAGE_STORAGE_PEAK
INTEGER
Peak page storage allocated to the task subpools in this DSA,
in bytes. From SMTHWMPS.
CICS_S_TCLASS_T
This table provides detailed statistics on transaction classes. It contains data from
CICS statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TCLASS
K
INTEGER
Transaction class. From A15KTCLS.
TRAN_CLASS_NAME
K
CHAR(8)
8-character name of the transaction class. For CICS V4 and
later. From XMCTCL.
ACCEPT_AFTER_Q_CNT
INTEGER
Number of transactions that became active in this transaction
class but were queued first. For CICS V4 and later. From
XMCAAQ.
ACCEPT_IMMED_CNT
INTEGER
Number of transactions that did not have to queue to become
active in this transaction class. They are accepted immediately.
For CICS V4 and later. From XMCAI.
ACTIVE_CURRENT_CNT
INTEGER
Number of transactions currently active in this transaction
class. For CICS V4 and later. From XMCCAT.
ATTACH_REQUESTS
INTEGER
Total number of attach requests made for transactions in this
transaction class. For CICS V4 and later. From XMCTAT.
PURGE_IMMED_CNT
INTEGER
Number of transactions that were purged immediately
because the queue reached the purge threshold for this
transaction class. For CICS V4 and later. From XMCPI.
PURGE_TH_REACH_CNT
INTEGER
Number of separate times that the purge threshold of the
transaction class has been reached (times at purge threshold).
For CICS V4 and later. From XMCTAPT.
PURGE_THRESHOLD
INTEGER
Limit at which transactions are purged instead of being added
to the queue of transactions that are waiting for membership
of the transaction class. For CICS V4 and later. From XMCTH.
Chapter 6. Data tables, lookup tables, and control tables
243
CICS statistics component data tables
Column name
Data type
Description
PURGE_WHILE_Q_CNT
INTEGER
Number of transactions purged while queueing. This includes
those transactions purged explicitly through CEMT, or
implicitly through the purge threshold of the transaction class
being lowered. For CICS V4 and later. From XMCPWQ.
QUEUED_CURRENT_CNT
INTEGER
Number of transactions that are currently queueing in this
transaction class. For CICS V4 and later. From XMCCQT.
QUEUED_CURR_TIME
TIME
Maximum time, in hh:mm:ss format, spent waiting by those
transactions in the class that were waiting at the end of a
collection interval. For CICS V4 and later. From XMCCQTME.
QUEUED_PREV_CNT
INTEGER
Number of transactions that had to queue but are no longer
queued. This includes those that were purged and those that
were finally accepted. For CICS V4 and later. From XMCTQ.
QUEUED_PREV_TIME
TIME
Maximum time, in hh:mm:ss format, spent queueing by those
transactions in the class that finished queueing in a collection
interval. For CICS V4 and later. From XMCTQTME.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
TASKS
INTEGER
Number of tasks in this class in the system (executing and
waiting). From A15MXTC.
TASKS_PEAK
INTEGER
Peak tasks in the system (executing and waiting). From
A15MXTR.
TCLASS_LIMIT
INTEGER
Highest number of tasks in this class allowed to execute
concurrently (CMXT). From A15MXT.
TIMES_AT_LIMIT
INTEGER
Number of times the class limit (CMXT) was reached. From
A15MXTM.
TRAN_INSTALL_CNT
INTEGER
Number of installed transaction definitions that are defined to
belong to this class. For CICS V4 and later. From XMCITD.
TRAN_QUEUED_PEAK
INTEGER
Highest number of transactions queued waiting for
admittance to the class. For CICS V4 and later. From
XMCPQT.
CICS_S_TCLASS_D
This table provides daily statistics on CICS transaction classes. It contains
consolidated data from the CICS_S_TCLASS_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
244
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TCLASS
K
INTEGER
Transaction class. From A15KTCLS.
TRAN_CLASS_NAME
K
CHAR(8)
8-character name of the transaction class. For CICS V4 and
later. From XMCTCL.
ACCEPT_AFTER_Q_CNT
INTEGER
Number of transactions that became active in this transaction
class but were queued first. For CICS V4 and later. From
XMCAAQ.
ACCEPT_IMMED_CNT
INTEGER
Number of transactions that did not have to queue to become
active in this transaction class. They are accepted immediately.
For CICS V4 and later. From XMCAI.
ATTACH_REQUESTS
INTEGER
Total number of attach requests made for transactions in this
transaction class. For CICS V4 and later. From XMCTAT.
PURGE_IMMED_CNT
INTEGER
Number of transactions that were purged immediately because
the queue reached the purge threshold for this transaction
class. For CICS V4 and later. From XMCPI.
PURGE_TH_REACH_CNT
INTEGER
Number of separate times that the purge threshold of the
transaction class has been reached (times at purge threshold).
For CICS V4 and later. From XMCTAPT.
PURGE_WHILE_Q_CNT
INTEGER
Number of transactions purged while queueing. This includes
those transactions purged explicitly through CEMT, or
implicitly through the purge threshold of the transaction class
being lowered. For CICS V4 and later. From XMCPWQ.
QUEUED_CURR_TIME
TIME
Maximum time, in hh:mm:ss format, spent waiting by those
transactions in the class that were waiting at the end of a
collection interval. For CICS V4 and later. From XMCCQTME.
QUEUED_PREV_CNT
INTEGER
Number of transactions that had to queue but are no longer
queued. This includes those that were purged and those that
were finally accepted. For CICS V4 and later. From XMCTQ.
QUEUED_PREV_TIME
TIME
Maximum time, in hh:mm:ss format, spent queueing by those
transactions in the class that finished queueing in a collection
interval. For CICS V4 and later. From XMCTQTME.
TASKS
INTEGER
Number of tasks in this class in the system (executing and
waiting). From A15MXTC.
TASKS_PEAK
INTEGER
Peak tasks in the system (executing and waiting). From
A15MXTR.
TIMES_AT_LIMIT
INTEGER
Number of times the class limit (CMXT) was reached. From
A15MXTM.
TRAN_INSTALL_CNT
INTEGER
Number of installed transaction definitions that are defined to
belong to this class. For CICS V4 and later. From XMCITD.
TRAN_QUEUED_PEAK
INTEGER
Highest number of transactions queued waiting for admittance
to the class. For CICS V4 and later. From XMCPQT.
CICS_S_TCPIP_T
This table provides detailed TCP/IP services statistics. For CICS/TS V1.3 and later,
this maps the DFHSORDS record.
The default retention period for this table is 7 days.
Chapter 6. Data tables, lookup tables, and control tables
245
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTDTE.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
AUTHENTICATE
CHAR(12)
The authentication and identification scheme, for internet
security, specified for this TCP/IP service. Possible values are:
None, Basic, Certificate, Autoregister, Automatic, Kerberos,
Asserted. From TCPAUTH.
PRIVACY
CHAR(12)
The level of SSL encryption support, for internet security, that
applies to this TCP/IP service. Possible values are:
NotSupported, Supported, Required. From TCPPRIV.
ATTACH_SECURITY
CHAR(6)
The level of attach-time security, for internet security, required
for this TCP/IP service. Possible values are: Local and Verify.
From TCPATTCH.
TSQUEUE_PREFIX
CHAR(6)
The name of the temporary storage queue prefix used to store
inbound data and Web documents created by applications. This
field is related to internet security. From TCPTSQPR.
MAXDATA
FLOAT
The maximum length of data that may be received on this
TCP/IP service. This field is related to internet security. From
TCPMAXDL.
CHAR(8)
Name of the TCP/IP service. From TCPSERNM.
TCPIP_BACKLOG
FLOAT
Port backlog for this TCP/IP service. From TCPBACK.
TCPIP_BYTES_RECV
FLOAT(53)
Number of bytes received for this TCP/IP service. From
TCPBYTER.
TCPIP_BYTES_SENT
FLOAT(53)
Number of bytes sent for this TCP/IP service. From TCPBYTES.
TCPIP_CONNECT_CUR
FLOAT
Current number of connections for the TCP/IP service. From
TCPCURCN.
TCPIP_CONNECT_PEAK
FLOAT
Peak number of connections for the TCP/IP service. From
TCPPKCON.
TCPIP_DNS_GROUP
CHAR(18)
DNS group identifier used for this TCP/IP service. From
TCPIP_DNS_GROUP
TCPIP_DNS_GROUP
CHAR(18)
DNS group identifier used for this TCP/IP service. From
TCPIP_DNS_GROUP (??).
TCPIP_GMTCLO_DATE
DATE
Date (GMT) when this TCP/IP service was closed. From
TCPCLGMT.
TCPIP_GMTCLO_TIME
TIME
Time (GMT) when this TCP/IP service was closed. From
TCPCLGMT.
TCPIP_GMTOPEN_DATE
DATE
Date (GMT) when this TCP/IP service was opened. From
TCPOPGMT.
TCPIP_GMTOPEN_TIME
TIME
Time (GMT) when this TCP/IP service was opened. From
TCPOPGMT.
TCPIP_SERVICE_NAME
246
K
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TCPIP_IPADDR
CHAR(15)
IP address defined for the TCP/IP stack used for this TCP/IP
service. From TCPIPADDR.
TCPIP_LOCCLO_DATE
DATE
LOCAL date when this TCP/IP service was closed. From
TCPCLLOC.
TCPIP_LOCCLO_TIME
TIME
LOCAL time when this TCP/IP service was closed. From
TCPCLLOC.
TCPIP_LOCOPEN_DATE
DATE
LOCAL date when this TCP/IP service was opened. From
TCPOPLOC.
TCPIP_LOCOPEN_TIME
TIME
LOCAL time when this TCP/IP service was opened. From
TCPOPLOC.
TCPIP_PORT_NUMBER
INTEGER
Port number being used for this TCP/IP service. From
TCPPORTN.
TCPIP_PROTOCOL
CHAR(8)
Protocol identifier
TCPIP_PROTOCOL
CHAR(8)
Protocol identifier.
TCPIP_RECV_NUM
FLOAT
Number of send requests issued for this TCP/IP service. From
TCPSEND.
TCPIP_SEND_NUM
FLOAT
Number of receive requests issued for this TCP/IP service. From
TCPRECVS.
TCPIP_SSL_SUPPORT
INTEGER
Level of SSL support defined for this TCP/IP service. From
TCPSSL.
TCPIP_TRANS_ATTACH
FLOAT
Number of attached transactions. From TCPATCTR.
CICS_S_TCPIP_D
This table provides daily TCP/IP services statistics. For CICS/TS V1.3 and later,
this maps the DFHSORDS record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
AUTHENTICATE
CHAR(12)
The authentication and identification scheme, for internet
security, specified for this TCP/IP service. Possible values are:
None, Basic, Certificate, Autoregister, Automatic, Kerberos,
Asserted. From TCPAUTH.
PRIVACY
CHAR(12)
The level of SSL encryption support, for internet security, that
applies to this TCP/IP service. Possible values are:
NotSupported, Supported, Required. From TCPPRIV.
ATTACH_SECURITY
CHAR(6)
The level of attach-time security, for internet security, required
for this TCP/IP service. Possible values are: Local and Verify.
From TCPATTCH.
Chapter 6. Data tables, lookup tables, and control tables
247
CICS statistics component data tables
Column name
Data type
Description
TSQUEUE_PREFIX
CHAR(6)
The name of the temporary storage queue prefix used to store
inbound data and Web documents created by applications. This
field is related to internet security. From TCPTSQPR.
MAXDATA
FLOAT
The maximum length of data that may be received on this
TCP/IP service. This field is related to internet security. From
TCPMAXDL.
CHAR(8)
Name of the TCP/IP service. From TCPSERNM.
TCPIP_BACKLOG
FLOAT
Port backlog for this TCP/IP service. From TCPBACK.
TCPIP_BYTES_RECV
FLOAT(53)
Number of bytes received for this TCP/IP service. From
TCPBYTER.
TCPIP_BYTES_SENT
FLOAT(53)
Number of bytes sent for this TCP/IP service. From TCPBYTES.
TCPIP_CONNECT_PEAK
FLOAT
Peak number of connections for the TCP/IP service. From
TCPPKCON.
TCPIP_CONNECTIONS
FLOAT
Current number of connections for the TCP/IP service. From
TCPCURCN.
TCPIP_DNS_GROUP
CHAR(18)
DNS group identifier used for this TCP/IP service. From
TCPIP_DNS_GROUP
TCPIP_DNS_GROUP
CHAR(18)
DNS group identifier used for this TCP/IP service. From
TCPIP_DNS_GROUP (??).
TCPIP_IPADDR
CHAR(15)
IP address defined for the TCP/IP stack used for this TCP/IP
service. From TCPIPADDR.
TCPIP_PORT_NUMBER
INTEGER
Port number being used for this TCP/IP service. From
TCPPORTN.
TCPIP_PROTOCOL
CHAR(8)
Protocol identifier
TCPIP_PROTOCOL
CHAR(8)
Protocol identifier.
TCPIP_RECV_NUM
FLOAT
Number of send requests issued for this TCP/IP service. From
TCPSEND.
TCPIP_SEND_NUM
FLOAT
Number of receive requests issued for this TCP/IP service.
From TCPRECVS.
TCPIP_SSL_SUPPORT
INTEGER
Level of SSL support defined for this TCP/IP service. From
TCPSSL.
TCPIP_TRANS_ATTACH
FLOAT
Number of attached transactions. From TCPATCTR.
TCPIP_SERVICE_NAME
K
CICS_S_TERMINAL_T
This table provides detailed data for each terminal. It contains data from CICS
statistics records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
248
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TERMINAL_ID
K
CHAR(4)
Terminal identifier. From A06TETI or AUSTETI.
ACCESS_METHOD
CHAR(2)
Terminal access method as defined in the TCT. From
A06EAMIB.
INPUT_MSGS
INTEGER
Number of messages sent to CICS from the terminal. From
A06TENI or AUSTENI.
LINE_ID
CHAR(4)
Line number for TCAM and BSAM lines. From A06TETI.
LOGOFF_GMT_TIME
TIMESTAMP
GMT time, in timestamp format, when this terminal was
logged off. For CICS V4 and later. From AUSGOFTM. From
A06GOFTM for CICS/TS V1.1 and later.
LOGOFF_LOCAL_TIME
TIMESTAMP
Local time, in timestamp format, when this terminal was
logged off. For CICS V4 and later. From AUSOFFTM. From
A06OFFTM for CICS/TS V1.1. and later.
LOGON_GMT_TIME
TIMESTAMP
GMT time, in timestamp format, when this terminal was
autoinstalled. For CICS V4 and later. From AUSGONTM.
From A06GONTM for CICS/TS V1.1 and later.
LOGON_LOCAL_TIME
TIMESTAMP
Local time, in timestamp format, when this terminal was
autoinstalled. For CICS V4 and later. From AUSONTM. From
A06ONTM for CICS/TS V1.1 and later.
LU_NAME
CHAR(8)
LU name of this terminal. For CICS V4 and later. From
AUSLUNAM.
OUTPUT_MSGS
INTEGER
Number of messages sent to the terminal from CICS. From
A06TENO or AUSTENO.
OWN_CONNECT_NAME
CHAR(8)
Owning connection name of this terminal or session. For
CICS/TS V1.1 and later. From A06SYSID.
PIPELINE_MSG
INTEGER
Total throwaway count (3600 terminals). From A06TCNT.
PIPELINE_MSG_GROUP
INTEGER
Number of consecutive throwaways (3600 terminals). From
A06SCNT.
PIPELINE_MSG_MAX
INTEGER
Maximum throwaway count (3600 terminals). From
A06MCNT.
POLLS
INTEGER
Number of polls that have been sent to the terminal. For
TCAM and BSAM terminals only. From A06LENP.
PRIORITY
CHAR(1)
Terminal priority for this terminal. For CICS V4 and later.
From AUSPRTY.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited),
EOD (End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
STORAGE_VIOLATIONS
INTEGER
Number of storage violations that occurred on this terminal.
From A06CSVC.
TERMINAL_TYPE
CHAR(2)
Terminal type as defined in the TCT. From A06TETT.
Chapter 6. Data tables, lookup tables, and control tables
249
CICS statistics component data tables
Column name
Data type
Description
TRANSACT_ERROR
INTEGER
Number of transactions not started because they were
undefined or disabled, or the operator had insufficient
security. From A06TEOE or AUSTEOE.
TRANSACTIONS
INTEGER
Number of transactions. A conversational transaction can be
many input and output messages, but is only one
transaction. From A06TEOT or AUSTEOT.
XMISSION_ERROR
INTEGER
Number of errors recorded for this terminal. From A06TETE
or AUSTETE.
CICS_S_TERMINAL_D
This table provides daily data for each terminal. The data is taken from the
CICS_S_TERMINAL_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TERMINAL_ID
K
CHAR(4)
Terminal identifier. From A06TETI or AUSTETI.
ACCESS_METHOD
CHAR(2)
Terminal access method as defined in the TCT. From
A06EAMIB.
INPUT_MSGS
INTEGER
Number of messages sent to CICS from the terminal. From
A06TENI or AUSTENI.
LU_NAME
CHAR(8)
LU name or this terminal. For CICS V4 and later. From
AUSLUNAM.
OUTPUT_MSGS
INTEGER
Number of messages sent to the terminal from CICS. From
A06TENO or AUSTENO.
PIPELINE_MSG
INTEGER
Total throwaway count (3600 terminals). From A06TCNT.
PIPELINE_MSG_GROUP
INTEGER
Number of consecutive throwaways (3600 terminals). From
A06SCNT.
PIPELINE_MSG_MAX
INTEGER
Maximum throwaway count (3600 terminals). From A06MCNT.
POLLS
INTEGER
Number of polls that have been sent to the terminal. For TCAM
and BSAM terminals only. From A06LENP.
STORAGE_VIOLATIONS
INTEGER
Number of storage violations that occurred on this terminal.
From A06CSVC.
TERMINAL_TYPE
CHAR(2)
Terminal type as defined in the TCT. From A06TETT.
TRANSACT_ERROR
INTEGER
Number of transactions not started because they were
undefined or disabled, or the operator had insufficient security.
From A06TEOE or AUSTEOE.
250
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TRANSACTIONS
INTEGER
Number of transactions. A conversational transaction can be
many input and output messages, but is only one transaction.
From A06TEOT or AUSTEOT.
XMISSION_ERROR
INTEGER
Number of errors recorded for this terminal. From A06TETE or
AUSTETE.
CICS_S_TRAN_T
This table provides detailed transaction data. It contains data from CICS statistics
records (SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
ACTION_FORCED_TRA
INTEGER
Forced action by trandef for the task
ACTION_FORCED_TIM
INTEGER
Forced action by timeout for the task
ACTION_FORCED_NOW
INTEGER
Forced action by nowait for the task
ACTION_FORCED_OPE
INTEGER
Forced action by the operator for the task
ACTION_FORCED_OTH
INTEGER
Forced action by other for the task
ACTION_MISMATCHES
INTEGER
Action mismatches for the task
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From A02TI.
PROGRAM_NAME
K
CHAR(8)
Program name. From A02IPIA.
ACTION_FORCED_NOW
INTEGER
Forced action by nowait for the task.
ACTION_FORCED_OPE
INTEGER
Forced action by operator for the task.
ACTION_FORCED_OTH
INTEGER
Forced action by other for the task.
ACTION_FORCED_TIM
INTEGER
Forced action by timeout for the task.
ACTION_FORCED_TRA
INTEGER
Forced action by transaction definition for the task.
ACTION_MISMATCHES
INTEGER
Action mismatches for the task.
DYNAMIC_INDICATOR
CHAR(1)
Indicates whether the transaction has been defined as
DYNAMIC=YES (Y) or DYNAMIC=NO (N). For CICS V4 and
later. From XMRDYN.
DYNAMIC_ROUTING_L
INTEGER
Number of times the dynamic routing exit chose to run this
transaction locally. From XMRDLC or A02TADL.
DYNAMIC_ROUTING_R
INTEGER
Number of times the dynamic routing exit chose to run this
transaction remotely. From XMRDRC or A02TADR.
INDOUBT_TIMEOUT_VA
INTEGER
Timeout value of the task performed
Chapter 6. Data tables, lookup tables, and control tables
251
CICS statistics component data tables
Column name
Data type
Description
INDOUBT_WAIT_OPTIO
CHAR(1)
Optional waiting time of the executed time
INDOUBT_ACTION
CHAR(1)
Type of action of the task performed
INDOUBTS_WAITS
INTEGER
Time waited
INDOUBT_ACTION
CHAR(1)
Type of action for the executed task.
INDOUBT_TIMEOUT_VA
INTEGER
Timeout value for the executed task.
INDOUBT_WAIT_OPTIO
CHAR(1)
Optional wait for the executed task.
INDOUBT_WAITS
CHAR(1)
The time waited.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited), EOD
(End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REMOTE_START_COUNT
INTEGER
Number of attempts to start this transaction on a remote
system. This can be more than the number of successful starts.
For CICS V4 and later. From XMRRSC.
RESTARTS
INTEGER
Number of times this transaction was automatically restarted
after an abend. From XMRRC or A02ATRCT.
STORAGE_VIOLATIONS
INTEGER
Number of storage violations for this transaction. From
XMRSVC or A02SCSVC.
SYSTEM_ID_R
CHAR(4)
Name of the remote system where the transaction resides. For
CICS V4 and later. From XMRRSYS.
TRAN_CLASS_NAME
CHAR(8)
Name of the transaction class in which the transaction is
defined. For CICS V4 and later. From XMRTCL.
TRANSACTION_ID_R
CHAR(8)
Name of the transaction on the remote system. For CICS V4
and later. From XMRRNAM.
TRANSACTION_PRIO
SMALLINT
Priority of the transaction, from 0-255. For CICS V4 and later.
From XMRPRTY.
TRANSACTIONS
INTEGER
Number of times the transaction has been used. From XMRAC
or A02TTA.
CICS_S_TRAN_D, _M
These tables provide summarized transaction data from the CICS_S_TRAN_T table.
The default retention periods are 30 days for CICS_S_TRAN_D, and 565 days for
CICS_S_TRAN_M.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
252
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From A02TI.
PROGRAM_NAME
K
CHAR(8)
Program name. From A02IPIA.
DYNAMIC_ROUTING_L
INTEGER
Number of times the dynamic routing exit chose to run this
transaction locally. From A02TADL.
DYNAMIC_ROUTING_R
INTEGER
Number of times the dynamic routing exit chose to run this
transaction remotely. From A02TADR.
REMOTE_START_COUNT
INTEGER
Number of attempts to start this transaction on a remote
system. This can be more than the number of successful starts.
For CICS V4 and later. From XMRRSC.
RESTARTS
INTEGER
Number of times this transaction was automatically restarted
after an abend. From A02ATRCT.
STORAGE_VIOLATIONS
INTEGER
Number of storage violations for this transaction. From
A02SCSVC.
TRANSACTIONS
INTEGER
Number of times the transaction has been used. From A02TTA.
CICS_S_TRANSIENT_T
This table provides detailed statistics for global and individual transient-data (TD)
queues from TD statistics records. It contains data from CICS statistics records
(SMF 110, subtype 2).
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters
in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
CONTROL_INTERVAL
INTEGER
Number of control intervals in the intrapartition data set
DFHINTRA. From TQGANCIS.
CONTROL_INTERV_INUSE
INTEGER
Current number of control intervals in the intrapartition data
set DFHINTRA. From TQGACTCI.
CHAR(6)
Destination identifier. This is set to GLOBAL for global
statistics. From A10DEST.
EXTRA_OUTPUTS
INTEGER
Number of outputs (write-only queue) or inputs (read-only
queue). This is the sum of A10EO.
INDIRECT_Q_NAME
CHAR(4)
Indirect destination queue name (for a TYPE=INDIRECT
queue), as specified via the TYPE=INDIRECT, DESTID
operand of the DFHDCT macro. For CICS V4 and later. From
A10IDQN.
DEST_ID
K
Chapter 6. Data tables, lookup tables, and control tables
253
CICS statistics component data tables
Column name
Data type
Description
INDIRECT_REQUESTS
INTEGER
Number of reads from and writes to this indirect destination.
This is the sum of A10IR.
INTRA_OUTPUTS
INTEGER
Number of outputs to a local intrapartition queue. This is the
sum of A10IO.
Q_DESTINATION_TYPE
CHAR(2)
Destination type: extrapartition (01), intrapartition (02),
indirect (03), or remote (04). From A10TYPE.
RECORD_INCOMPLETE
CHAR(3)
Contains YES if the CICS statistics record is incomplete. From
SMFSTICD.
RECORD_TYPE
CHAR(3)
Type of CICS statistics record. Can be USS (Unsolicited),
EOD (End of day), REQ (Requested), or INT (Interval). From
SMFSTRQT.
RECORD_VERSION
CHAR(4)
CICS Version and Release that wrote this record; for example,
0330. From SMFSTRVN.
REMOTE_Q_NAME
CHAR(4)
Remote queue name (for a TYPE=REMOTE queue), as
specified via the TYPE=REMOTE, RMTNAME operand of
the DFHDCT macro. For CICS V4 and later. From A10RQID.
REMOTE_REQUESTS
INTEGER
Number of read and write requests to this remote
destination. This is the sum of A10RR.
REMOTE_SYS_NAME
CHAR(4)
Remote system name (for a TYPE=REMOTE queue), as
specified via the TYPE=REMOTE, SYSIDNT operand of the
DFHDCT macro. For CICS V4 and later. From A10RSID.
STRING_ACCESS_PEAK
INTEGER
Peak number of concurrent intrapartition I/Os. From
A11SMXAL.
STRINGS
INTEGER
Number of strings. This is the maximum number of
concurrent I/O operations. From A11SNSTA.
STRINGS_ACCESSED
INTEGER
Number of I/Os to and from the intrapartition data set. This
is the sum of A11STNAL.
STRINGS_CONC_WAIT
INTEGER
Current number of strings concurrently accessed in the
system. From TQGACNWT.
STRING_WAIT_PEAK
INTEGER
Peak number of tasks waiting for a intrapartition string. This
is the maximum of A11SMXWT.
STRING_WAITS
INTEGER
Number of times tasks had to wait for a intrapartition string.
This is the sum of A11STNWT.
TD_BFR_ACCESSES
INTEGER
Number of times a buffer was accessed for writing or
reading an intrapartition record. This is the sum of
A11ATNAL.
TD_BFR_ACC_CONC
INTEGER
Current value of the number of concurrent intrapartition
buffer accesses. From TQGACNAL.
TD_BFR_ACC_PEAK
INTEGER
Peak number of concurrent intrapartition buffer accesses.
This is the sum of A11AMXAL.
TD_BFR_INTPAR_WAIT
INTEGER
Current number of requests queued because no buffers were
available. From TQGACNWT.
TD_BFR_VALID_DATA
INTEGER
Current number of intrapartition buffers that contain valid
data. From TQGACNIU.
TD_BFRS_PEAK_USED
INTEGER
Peak number of buffers containing unread data. This is the
maximum of A11AMXIU.
TD_BFRS_SPECIFIED
INTEGER
Number of buffers specified in the SIT. CICS uses at most
one buffer per queue. From A11ANBFA.
254
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TD_BFR_WAIT_PEAK
INTEGER
Peak number of intrapartition requests queued because all
buffers were in use, or the required CI was in a locked
buffer. This is the maximum of A11AMXWT.
TD_BFR_WAITS
INTEGER
Number of times intrapartition requests were queued
because all buffers were in use, or the required CI was in a
locked buffer. This is the sum of A11ATNWT.
TD_INTRA_CI_ACTIVE
INTEGER
Number of formatted control intervals. This is the maximum
of A11ANCIS.
TD_INTRA_CI_PEAK
INTEGER
Peak number of control intervals logically used (not
necessarily written to disk). This is the maximum of
A11AMXCI.
TD_INTRA_CISIZE
INTEGER
Control interval (CI) size, in bytes. From A11ACISZ. The
maximum usable space is the CI size minus 32 bytes.
TD_INTRA_IO_ERRORS
INTEGER
Number of errors on this data set. VSAM should have
reported the details of each error in the message log. This is
the sum of A11ACTIO.
TD_INTRA_NOSPACE
INTEGER
Number of times there was no space on the intrapartition
data set. This is the sum of A11ANOSP.
TD_INTRA_READS
INTEGER
Number of times a CI had to be read from DASD. Increasing
the buffer allocation can decrease this. This is the sum of
A11ACTGT.
TD_INTRA_WRITES
INTEGER
Number of writes to the intrapartition data set, both for
recovery and because of a lack of buffer space. This is the
sum of A11ACTPT.
TD_INTRA_WRITES_FO
INTEGER
Number of times a new CI was written. It does not include
the formatting of the first extent. This is the sum of
A11ACTFT.
CICS_S_TRANSIENT_D
This table provides daily statistics for global and individual transient-data (TD)
queues from TD statistics records. The data is consolidated from the
CICS_S_TRANSIENT_T table.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics records were written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
DEST_ID
K
CHAR(6)
Destination identifier. Is set to GLOBAL for global statistics.
From A10DEST.
INTEGER
Current number of control intervals in the intrapartition data
set DFHINTRA. From TQGACTCI.
CONTR_INTERV_INUSE
Chapter 6. Data tables, lookup tables, and control tables
255
CICS statistics component data tables
Column name
Data type
Description
CONTROL_INTERVAL
INTEGER
Number of control intervals in the intrapartition data set
DFHINTRA. From TQGANCIS.
EXTRA_OUTPUTS
INTEGER
Number of outputs (write-only queue) or inputs (read-only
queue). This is the sum of A10EO.
INDIRECT_REQUESTS
INTEGER
Number of reads from and writes to this indirect destination.
This is the sum of A10IR.
INTRA_OUTPUTS
INTEGER
Number of outputs to a local intrapartition queue. This is the
sum of A10IO.
REMOTE_REQUESTS
INTEGER
Number of read and write requests to this remote destination.
This is the sum of A10RR.
STRING_ACCESS_PEAK
INTEGER
Peak number of concurrent intrapartition I/Os. From
A11SMXAL.
STRINGS
INTEGER
Number of strings. This is the maximum number of concurrent
I/O operations. From A11SNSTA.
STRINGS_ACCESSED
INTEGER
Number of I/Os to and from the intrapartition data set. This is
the sum of A11STNAL.
STRINGS_CONC_ACC
INTEGER
Current number of strings concurrently accessed in the system.
From TQGSCNAL.
STRINGS_CONC_WAIT
INTEGER
Current number of concurrent string waits in the system. From
TQGSCNWT.
STRING_WAIT_PEAK
INTEGER
Peak number of tasks waiting for a intrapartition string. This is
the maximum of A11SMXWT.
STRING_WAITS
INTEGER
Number of times tasks had to wait for a intrapartition string.
This is the sum of A11STNWT.
TD_BFR_ACC_CONC
INTEGER
Current value of the number of concurrent intrapartition buffer
accesses. From TQGACNAL.
TD_BFR_ACCESSES
INTEGER
Number of times a buffer was accessed for writing or reading
an intrapartition record. This is the sum of A11ATNAL.
TD_BFR_ACC_PEAK
INTEGER
Peak number of concurrent intrapartition buffer accesses.
TD_BFR_INTPAR_WAIT
INTEGER
Current number of requests queued because no buffers were
available. From TQGACNWT. This is the maximum of
A11AMXAL.
TD_BFRS_PEAK_USED
INTEGER
Peak number of buffers containing unread data. This is the
maximum of A11AMXIU.
TD_BFRS_SPECIFIED
INTEGER
Number of buffers specified in the SIT. CICS uses at most one
buffer per queue. From A11ANBFA.
TD_BFR_VALID_DATA
INTEGER
Current number of intrapartition buffers that contain valid data.
From TQGACNIU.
TD_BFR_WAIT_PEAK
INTEGER
Peak number of intrapartition requests queued because all
buffers were in use, or the required CI was in a locked buffer.
This is the maximum of A11AMXWT.
TD_BFR_WAITS
INTEGER
Number of times intrapartition requests were queued because
all buffers were in use, or the required CI was in a locked
buffer. This is the sum of A11ATNWT.
TD_INTRA_CI_ACTIVE
INTEGER
Number of formatted control intervals. This is the maximum of
A11ANCIS.
TD_INTRA_CI_PEAK
INTEGER
Peak number of control intervals logically used (not necessarily
written to disk). This is the maximum of A11AMXCI.
256
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TD_INTRA_CISIZE
INTEGER
Control interval (CI) size, in bytes. From A11ACISZ. The
maximum usable space is the CI size minus 32 bytes.
TD_INTRA_IO_ERRORS
INTEGER
Number of errors on this data set. VSAM should have reported
the details of each error in the message log. This is the sum of
A11ACTIO.
TD_INTRA_NOSPACE
INTEGER
Number of times there was no space on the intrapartition data
set. This is the sum of A11ANOSP.
TD_INTRA_READS
INTEGER
Number of times a CI had to be read from DASD. Increasing
the buffer allocation can decrease this. This is the sum of
A11ACTGT.
TD_INTRA_WRITES
INTEGER
Number of writes to the intrapartition data set, both for
recovery and because of a lack of buffer space. This is the sum
of A11ACTPT.
TD_INTRA_WRITES_FO
INTEGER
Number of times a new CI was written. It does not include the
formatting of the first extent. This is the sum of A11ACTFT.
CICS_S_TS_BPOOL_T
This table provides detailed statistics for the queue index BPOOL that is used to
Read/Write entries and the associated data. For CICS/TS V1.2 and later, this maps
the DFHXQS2D record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in the
PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TS_BUF_TOT
FLOAT
Total number of defined buffers. From S2BFQTY.
TS_BUF_USEMAX
FLOAT
Number of buffers already used. From S2BFENTH.
TS_BUF_USECUR
FLOAT
Number of active buffers owned by tasks. From S2BFACTS.
TS_BUF_REUSE
FLOAT
Number of valid buffers on the LRU chain. From S2BFLRUS.
TS_BUF_EMPTY
FLOAT
Number of empty buffers on the free chain. From S2BFEMPS.
TS_BUF_GETS
FLOAT
Number of GET requests. From S2BFGETS.
TS_BUF_PUTS
FLOAT
Number of PUT requests (put back buffer as valid). From
S2BFPUTS.
TS_BUF_KEEP
FLOAT
Number of KEEP requests (put back buffer as modified). From
S2BFKEPS.
TS_BUF_FREE
FLOAT
Number of FREE requests (put back buffer as empty). From
S2BFFRES.
Chapter 6. Data tables, lookup tables, and control tables
257
CICS statistics component data tables
Column name
Data type
Description
TS_BUF_PURGES
FLOAT
Number of PURGE requests (mark buffer as invalid). From
S2BFPURS.
TS_BUF_GOTHIT
FLOAT
Number of GET requests that found a valid buffer. From
S2BFHITS.
TS_BUF_GOTFREE
FLOAT
Number of GET requests that used a free buffer. From S2BFGFRS.
TS_BUF_GOTNEW
FLOAT
Number of GET requests that used a new buffer. From
S2BFGNWS.
TS_BUF_GOTLRU
FLOAT
Number of GET requests that used the LRU buffer. From
S2BFGLRS.
TS_BUF_NOBUF
FLOAT
Number of GET requests that returned no buffer. From
S2BFGNBS.
TS_BUF_NOTFREED
FLOAT
Number of FREE errors, buffer not owned. From S2BFFNOS.
TS_BUF_NOPURGE
FLOAT
Number of PURGE requests with no matching buffer. From
S2BFPNFS.
TS_BUF_NOTOWNED
FLOAT
Number of PURGE errors, buffer not owned. From S2BFPNOS.
TS_BUF_POOLLOCK
FLOAT
Number of waits on buffer pool lock. From S2BFPWTS.
TS_BUF_BUFLOCK
FLOAT
Number of GET waits on buffer lock. From S2BFLWTS.
CICS_S_TS_BPOOL_D
This table provides daily statistics for the queue index BPOOL that is used to
Read/Write queue index entries and the associated data. For CICS/TS V1.2 and
later, this maps the DFHXQS2D record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in the
PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used when
requesting a session with this CICS system. From SMFSTPRN.
TS_BUF_TOT
FLOAT
Total number of defined buffers. From S2BFQTY.
TS_BUF_USEMAX
FLOAT
Number of buffers already used. From S2BFENTH.
TS_BUF_USECUR
FLOAT
Number of active buffers owned by tasks. From S2BFACTS.
TS_BUF_REUSE
FLOAT
Number of valid buffers on the LRU chain. From S2BFLRUS.
TS_BUF_EMPTY
FLOAT
Number of empty buffers on the free chain. From S2BFEMPS.
TS_BUF_GETS
FLOAT
Number of GET requests. From S2BFGETS.
TS_BUF_PUTS
FLOAT
Number of PUT requests (put back buffer as valid). From
S2BFPUTS.
TS_BUF_KEEP
FLOAT
Number of KEEP requests (put back buffer as modified). From
S2BFKEPS.
TS_BUF_FREE
FLOAT
Number of FREE requests (put back buffer as empty). From
S2BFFRES.
258
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TS_BUF_PURGES
FLOAT
Number of PURGE requests (mark buffer as invalid). From
S2BFPURS.
TS_BUF_GOTHIT
FLOAT
Number of GET requests that found a valid buffer. From
S2BFHITS.
TS_BUF_GOTFREE
FLOAT
Number of GET requests that used a free buffer. From S2BFGFRS.
TS_BUF_GOTNEW
FLOAT
Number of GET requests that used a new buffer. From S2BFGNWS.
TS_BUF_GOTLRU
FLOAT
Number of GET requests that used the LRU buffer. From
S2BFGLRS.
TS_BUF_NOBUF
FLOAT
Number of GET requests that returned no buffer. From S2BFGNBS.
TS_BUF_NOTFREED
FLOAT
Number of FREE errors, buffer not owned. From S2BFFNOS.
TS_BUF_NOPURGE
FLOAT
Number of PURGE requests with no matching buffer. From
S2BFPNFS.
TS_BUF_NOTOWNED
FLOAT
Number of PURGE errors, buffer not owned. From S2BFPNOS.
TS_BUF_POOLLOCK
FLOAT
Number of waits on buffer pool lock. From S2BFPWTS.
TS_BUF_BUFLOCK
FLOAT
Number of GET waits on buffer lock. From S2BFLWTS.
CICS_S_TS_CF_T
This table provides detailed Shared TS queue server CF statistics. For CICS/TS
V1.2 and later, this maps the DFHXQS1D record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TS_CF_STR_PREF
K
CHAR(8)
First part of the structure name. From S1PREF.
TS_CF_POOL_NAME
K
CHAR(8)
Pool name part of the structure name. From S1POOL.
TS_CF_CONN_PREF
K
CHAR(8)
Prefix for connection name. From S1CNPREF.
TS_CF_MVS_SYSN
K
CHAR(8)
Own MVS system name from CVTSNAME. From S1NSYSN.
TS_CF_SIZE
FLOAT
Current allocated size of the list structure. From S1SIZE.
TS_CF_MAX_SIZE
FLOAT
Maximum size to which this structure could be altered. From
S1SIZEMX.
TS_CF_LHEAD_MAX
FLOAT
Maximum number of list headers. From S1HDRS.
TS_CF_CHEAD
FLOAT
Headers used for control lists. From S1HDRSCT.
TS_CF_QDATA_HEAD
FLOAT
Headers available for queue data row. From S1HDRSQD.
TS_CF_ELEM_SIZE
FLOAT
Data element size of the list structure. From S1ELEMLN.
Chapter 6. Data tables, lookup tables, and control tables
259
CICS statistics component data tables
Column name
Data type
Description
TS_CF_DATAEL_SIZE
FLOAT
Data element size, to the power of 2, used for the structure.
From S1ELEMPW.
TS_CF_ENTREL_MAX
FLOAT
Maximum number of elements per entry (for 32 kilobytes) From
S1ELEMPE.
TS_CF_EMTRY_ELSZ
FLOAT
Element size of entry-to-element ratio. From S1ELEMRT.
TS_CF_ENTRSZ_RATIO
FLOAT
Entry size of entry-to-element ratio. From S1ENTRRT.
TS_CF_ENTRUSE_CUR
FLOAT
Number of entries currently in use. From S1ENTRCT.
TS_CF_ENTRUSE_MAX
FLOAT
Maximum number of entries in use (since last reset). From
S1ENTRHI.
TS_CF_ENTRFRE_MIN
FLOAT
Minimum number of free entries (since last reset). From
S1ENTRLO.
TS_CF_ENTRALL_TOT
FLOAT
Total number of data entries in the current allocated structure.
From S1ENTRMX.
TS_CF_ELUSE_CUR
FLOAT
Number of elements currently in use. From S1ELEMCT.
TS_CF_ELUSE_MAX
FLOAT
Maximum number of elements in use. From S1ELEMHI.
TS_CF_ELFREE_MIN
FLOAT
Lowest number of elements currently free (total − used). From
S1ELEMLO.
TS_CF_ELCUR_TOT
FLOAT
Maximum number of elements returned by IXLCONN. From
S1ELEMMX.
TS_CF_USLST_HEAD
FLOAT
Number of elements on used list. From S1USEDCT.
TS_CF_USED_MAX
FLOAT
Highest number of elements on used list. From S1USEDHI.
TS_CF_ENTR_FREE
FLOAT
Number of entries on free list. From S1FREECT.
TS_CF_ENTRFRE_MAX
FLOAT
Highest number of entries on free list. From S1FREEHI.
TS_CF_QUEUE_NUM
FLOAT
Number of current existing queues. From S1INDXCT.
TS_CF_QUEUE_MAX
FLOAT
Highest number of queues at any time (since last reset) From
S1INDXHI.
TS_CF_ENTRIX_QREAD
FLOAT
Read queue index entry. From S1RDQCT.
TS_CF_ENTRIX_QWR
FLOAT
Write queue index entry. From S1WRQCT.
TS_CF_ENTRIX_QDEL
FLOAT
Delete queue index entry. From S1DLQCT.
TS_CF_DATALIST
FLOAT
Number of times that a separate data list was created. From
S1CRLCT.
TS_CF_DELETE_LIST
FLOAT
Delete list (one for each overall delete). From S1DLLCT.
TS_CF_DATA_QREAD
FLOAT
Number of queue index reads. From S1RDLCT.
TS_CF_DATA_QWRITE
FLOAT
Number of queue writes (new or update) including data. From
S1WRLCT.
TS_CF_LISTEN_RREA
FLOAT
Rewrite list entry. From S1RWLCT.
TS_CF_ENTRIX_QINQ
FLOAT
Inquire on queue index entry. From S1INQCT.
TS_CF_LISTEN_ENQY
FLOAT
Inquiry in list entry. From S1INLCT.
TS_CF_ENTRIX_WRITE
FLOAT
Number of index writes to update adjunct area only. This area
contains the read cursor for small queues and the queues and
the queue status, including last used data. From S1WRACT.
TS_CF_ENTRFRE_RRD
FLOAT
Number of index data reads that had to be repeated because the
data was larger than the default data transfer size. From
S1RRQCT.
260
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TS_CF_LISTDATA_RD
FLOAT
Number of list data reads that had to be repeated because the
data was larger than the default data transfer size. From
S1RRLCT.
TS_CF_ASYNC_REQS
FLOAT
Number of asynchronous requests. From S1ASYCT.
TS_CF_NORMAL_RESP
FLOAT
Number of normal responses. From S1RSP1CT.
TS_CF_TIMOUT_REQS
FLOAT
Request timed out by the CF and should be restarted. From
S1RSP2CT.
TS_CF_ENTR_NOTFND
FLOAT
Specified entry (queue or item) was not found. From S1RSP3CT.
TS_CF_FAIL_VRSCHK
FLOAT
A verification check failed for an entry being updated, indicating
that another task had updated it first. From S1RSP4CT.
TS_CF_FAIL_LSTCHK
FLOAT
A list authority comparison failed, usually indicating that a large
queue was deleted. From S1RSP5CT.
TS_CF_FAIL_LSTFUL
FLOAT
Maximum list key reached, indicating that the maximum queue
size or the maximum number of queues has been reached,
depending on list. From S1RSP6CT.
TS_CF_FAIL_STRFUL
FLOAT
The list structure is out of space. From S1RSP7CT.
TS_CF_FAIL_IOERR
FLOAT
An IXLLIST RC occurred other than those previously described.
From S1RSP8CT.
CICS_S_TS_CF_D
This table provides daily Shared TS queue server CF statistics. For CICS/TS V1.2
and later, this maps the DFHXQS1D record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TS_CF_STR_PREF
K
CHAR(8)
First part of the structure name. From S1PREF.
TS_CF_POOL_NAME
K
CHAR(8)
Pool name part of the structure name. From S1POOL.
TS_CF_CONN_PREF
K
CHAR(8)
Prefix for connection name. From S1CNPREF.
TS_CF_MVS_SYSN
K
CHAR(8)
Own MVS system name from CVTSNAME. From S1NSYSN.
TS_CF_SIZE
FLOAT
Current allocated size of the list structure. From S1SIZE.
TS_CF_MAX_SIZE
FLOAT
Maximum size to which this structure could be altered. From
S1SIZEMX.
TS_CF_LHEAD_MAX
FLOAT
Maximum number of list headers. From S1HDRS.
TS_CF_CHEAD
FLOAT
Headers used for control lists. From S1HDRSCT.
TS_CF_QDATA_HEAD
FLOAT
Headers available for queue data row. From S1HDRSQD.
TS_CF_ELEM_SIZE
FLOAT
Data element size of the list structure. From S1ELEMLN.
Chapter 6. Data tables, lookup tables, and control tables
261
CICS statistics component data tables
Column name
Data type
Description
TS_CF_DATAEL_SIZE
FLOAT
Data element size, to the power of 2, used for the structure. From
S1ELEMPW.
TS_CF_ENTREL_MAX
FLOAT
Maximum number of elements per entry (for 32 kilobytes) From
S1ELEMPE.
TS_CF_EMTRY_ELSZ
FLOAT
Element size of entry-to-element ratio. From S1ELEMRT.
TS_CF_ENTRSZ_RATIO
FLOAT
Entry size of entry-to-element ratio. From S1ENTRRT.
TS_CF_ENTRUSE_CUR
FLOAT
Number of entries currently in use. From S1ENTRCT.
TS_CF_ENTRUSE_MAX
FLOAT
Maximum number of entries in use (since last reset). From
S1ENTRHI.
TS_CF_ENTRFRE_MIN
FLOAT
Minimum number of free entries (since last reset). From
S1ENTRLO.
TS_CF_ENTRALL_TOT
FLOAT
Total number of data entries in the current allocated structure.
From S1ENTRMX.
TS_CF_ELUSE_CUR
FLOAT
Number of elements currently in use. From S1ELEMCT.
TS_CF_ELUSE_MAX
FLOAT
Maximum number of elements in use. From S1ELEMHI.
TS_CF_ELFREE_MIN
FLOAT
Lowest number of elements currently free (total − used). From
S1ELEMLO.
TS_CF_ELCUR_TOT
FLOAT
Maximum number of elements returned by IXLCONN. From
S1ELEMMX.
TS_CF_USLST_HEAD
FLOAT
Number of elements on used list. From S1USEDCT.
TS_CF_USED_MAX
FLOAT
Highest number of elements on used list. From S1USEDHI.
TS_CF_ENTR_FREE
FLOAT
Number of entries on free list. From S1FREECT.
TS_CF_ENTRFRE_MAX
FLOAT
Highest number of entries on free list. From S1FREEHI.
TS_CF_QUEUE_NUM
FLOAT
Number of current existing queues. From S1INDXCT.
TS_CF_QUEUE_MAX
FLOAT
Highest number of queues at any time (since last reset) From
S1INDXHI.
TS_CF_ENTRIX_QREAD
FLOAT
Read queue index entry. From S1RDQCT.
TS_CF_ENTRIX_QWR
FLOAT
Write queue index entry. From S1WRQCT.
TS_CF_ENTRIX_QDEL
FLOAT
Delete queue index entry. From S1DLQCT.
TS_CF_DATALIST
FLOAT
Number of times that a separate data list was created. From
S1CRLCT.
TS_CF_DELETE_LIST
FLOAT
Delete list (one for each overall delete). From S1DLLCT.
TS_CF_DATA_QREAD
FLOAT
Number of queue index reads. From S1RDLCT.
TS_CF_DATA_QWRITE
FLOAT
Number of queue writes (new or update) including data. From
S1WRLCT.
TS_CF_LISTEN_RREA
FLOAT
Rewrite list entry. From S1RWLCT.
TS_CF_ENTRIX_QINQ
FLOAT
Inquire on queue index entry. From S1INQCT.
TS_CF_LISTEN_ENQY
FLOAT
Inquiry in list entry. From S1INLCT.
TS_CF_ENTRIX_WRITE
FLOAT
Number of index writes to update adjunct area only. This area
contains the read cursor for small queues and the queues and the
queue status, including last used data. From S1WRACT.
TS_CF_ENTRFRE_RRD
FLOAT
Number of index data reads that had to be repeated because the
data was larger than the default data transfer size. From
S1RRQCT.
262
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TS_CF_LISTDATA_RD
FLOAT
Number of list data reads that had to be repeated because the
data was larger than the default data transfer size. From
S1RRLCT.
TS_CF_ASYNC_REQS
FLOAT
Number of asynchronous requests. From S1ASYCT.
TS_CF_NORMAL_RESP
FLOAT
Number of normal responses. From S1RSP1CT.
TS_CF_TIMOUT_REQS
FLOAT
Request timed out by the CF and should be restarted. From
S1RSP2CT.
TS_CF_ENTR_NOTFND
FLOAT
Specified entry (queue or item) was not found. From S1RSP3CT.
TS_CF_FAIL_VRSCHK
FLOAT
A verification check failed for an entry being updated, indicating
that another task had updated it first. From S1RSP4CT.
TS_CF_FAIL_LSTCHK
FLOAT
A list authority comparison failed, usually indicating that a large
queue was deleted. From S1RSP5CT.
TS_CF_FAIL_LSTFUL
FLOAT
Maximum list key reached, indicating that the maximum queue
size or the maximum number of queues has been reached,
depending on list. From S1RSP6CT.
TS_CF_FAIL_STRFUL
FLOAT
The list structure is out of space. From S1RSP7CT.
TS_CF_FAIL_IOERR
FLOAT
An IXLLIST RC occurred other than those previously described.
From S1RSP8CT.
CICS_S_TS_STOR_T
This table provides detailed storage statistics. For CICS/TS V1.2 and later, this
maps the DFHXQS3D record.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TS_STOR_POOL
K
CHAR(8)
Name of the storage pool. AXMPGANY (for LOC=ANY) or
AXMPGLOW (for LOC=BELOW) From S3ANYNAM or
S3MPFLOW.
TS_STOR_PSIZE_TOT
FLOAT
Size of the storage pool area. Calculated as maximum of
S3ANYSIZ or S3LOWSIZ.
TS_STOR_PADDR
FLOAT
Address of the storage pool area. From S3ANYPTR or
S3LOWPTR.
TS_STOR_PPAGE_TOT
FLOAT
Total pages in the storage pool. Calculated as maximum of
S3ANYMX or S3LOWMX.
TS_STOR_USE_MAX
FLOAT
Number of used pages in the storage pool. Calculated as
maximum of S3ANYUS or S3LOWUS.
Chapter 6. Data tables, lookup tables, and control tables
263
CICS statistics component data tables
Column name
Data type
Description
TS_STOR_FREE_MAX
FLOAT
Maximum number of free pages in the storage pool. Calculated
as maximum of S3ANYFR or S3LOWFR.
TS_STOR_FREE_MIN
FLOAT
Minimum number of free pages in the storage pool (since reset).
Calculated as minimum of S3ANYLO or S3LOWLO.
TS_STOR_GETS
FLOAT
Number of storage GET requests. From S3ANYRQG or
S3LOWRQG.
TS_STOR_REQ_FAILS
FLOAT
Number of GET requests that failed to obtain storage. From
S3ANYRQF or S3LOWRQF.
TS_STOR_FREES
FLOAT
Number of storage FREE requests. From S3ANYRQS or
S3LOWRQS.
TS_STOR_RETRIES
FLOAT
Number of compression (defragmentation) attempts. From
S3ANYRQC or S3LOWRQC.
CICS_S_TS_STOR_D
This table provides daily storage statistics. For CICS/TS V1.2 and later, this maps
the DFHXQS3D record.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN.
TS_STOR_POOL
K
CHAR(8)
Name of the storage pool. AXMPGANY (for LOC=ANY storage
pool) or AXMPGLOW (for LOC=BELOW storage pool). From
S3ANYNAM or S3MPFLOW.
TS_STOR_PSIZE_TOT
FLOAT
Size of the storage pool area. Calculated as maximum of
S3ANYSIZ or S3LOWSIZ.
TS_STOR_PADDR
FLOAT
Address of the storage pool area. From S3ANYPTR or
S3LOWPTR.
TS_STOR_PPAGE_TOT
FLOAT
Total pages in the storage pool. Calculated as maximum of
S3ANYMX or S3LOWMX.
TS_STOR_USE_MAX
FLOAT
Number of used pages in the storage pool. Calculated as
maximum of S3ANYUS or S3LOWUS.
TS_STOR_FREE_MAX
FLOAT
Maximum number of free pages in the storage pool. Calculated
as maximum of S3ANYFR or S3LOWFR.
TS_STOR_FREE_MIN
FLOAT
Minimum number of free pages in the storage pool (since reset).
Calculated as minimum of S3ANYLO or S3LOWLO.
TS_STOR_GETS
FLOAT
Number of storage GET requests. From S3ANYRQG or
S3LOWRQG.
TS_STOR_REQ_FAILS
FLOAT
Number of GET requests that failed to obtain storage. From
S3ANYRQF or S3LOWRQF.
264
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
TS_STOR_FREES
FLOAT
Number of storage FREE requests. From S3ANYRQS or
S3LOWRQS.
TS_STOR_RETRIES
FLOAT
Number of compress (defragmentation) attempts. From
S3ANYRQC or S3LOWRQC.
CICS_S_URIMAP_T
This table provides detailed statistics for individual URIMAP. It contains data from
CICS statistics records (SMF 110, subtype 2 stid 104). For CICS/TS V3.1 and later, it
takes information from the DFHWBRDS CICS dsect.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
URIMAP_NAME
K
CHAR(8)
The name of the URIMAP definition. From
WBRUNAME.
URIMAP_USAGE
CHAR(8)
The intended use of this URIMAP. The possible values
are: SERVER: the URIMAP definition is used to locate the
resources for CICS to produce an HTTP response to the
request identified by HOST and PATH. CLIENT: the
URIMAP definition is used to specify information for
making an HTTP request from CICS an HTTP client.
PIPELINE: the URIMAP definition is used to locate the
resources for CICS to produce an XML response to the
request identified by HOST and PATH. From WBRUUSG.
URIMAP_SCHEME
CHAR(8)
The scheme for the HTTP request. The possible values
are HTTP, HTTPS(HTTP with SSL) and WMQ. From
WBRSCHEME.
ANALYZER
CHAR(1)
Whether (Y) or not (N) the analyzer associated with the
TCPIPSERVICE definition is called to process the request.
From WBRUANUSE.
REDIRECTION_TYPE
CHAR(10)
Whether or not matching requests should be redirected,
on a temporary or permanent basis. From
WBRUREDTYPE.
URIMAP_HOST
VARCHAR(116)
The host name of the URL to which the HTTP request is
to be sent for USAGE (CLIENT). The host name on the
incoming HTTP request that is used to select this
URIMAP definition for any other USAGE. From
WBRUHNAME.
Chapter 6. Data tables, lookup tables, and control tables
265
CICS statistics component data tables
Column name
Data type
Description
URIMAP_PATH
VARCHAR(254)
The path of the target URL to which the HTTP request is
to be sent for USAGE (CLIENT). The path on the
incoming HTTP request that is used to select this
URIMAP definition, for any other USAGE. The PATH
may terminate in an asterisk, meaning that it is generic,
and matches any path whose characters are the same up
to but excluding the asterisk. From WBRUPATH.
TEMPLATE_NAME
VARCHAR(48)
The name of a CICS document template whose contents
are returned as the HTTP response. From WBRUTNAME.
HFS_FILE
VARCHAR(254)
The name of a file in the z/OS UNIX System Services
Hierarchical File System (HFS), whose contents are
returned as the HTTP response. From WBRUHFSFILE.
LOCATION_REDIRECT
VARCHAR(254)
An alternate URL to which the Web client will be
redirected, if redirection is specified. From WBRULOC.
TRANSACTION_ID
CHAR(4)
The name of the alias transaction that processes the
incoming HTTP request. From WBRUTRANID.
TCPSERVICE_NAME
CHAR(8)
The TCPIPSERVICE to which this URIMAP definition
applies. Only requests received on this TCPIPSERVICE
are matched to this URIMAP definition. If no
TCPIPSERVICE is specified, the URIMAP definition
applies to all incoming HTTP requests. From
WBRUTCPSRV.
CONVERTER
CHAR(8)
The name of a converter program that is used to
transform the HTTP request into a form suitable for the
application program specified in PROGRAM. From
WBRUCONVNM.
PROGRAM_NAME
CHAR(8)
The name of the application program that processes the
incoming HTTP request. From WBRUPGMNM.
WEBSERVICE_NAME
VARCHAR(32)
The name of the WEBSERVICE resource definition for the
Web service that handles the incoming HTTP request.
From WBRUWEBSER.
PIPELINE_NAME
CHAR(8)
The name of the PIPELINE resource definition for the
Web service that handles the incoming HTTP request.
From WBRUPIPEL.
URIMAP_REF_CNT
FLOAT
Number of times this URIMAP definition was referenced.
From WBRUREFCNT.
URIMAP_DISABLED
FLOAT
Number of times this host and path were matched, but
the URIMAP definition was disabled. From
WBRUMTCHDIS.
URIMAP_REDIRECTED
FLOAT
Number of times this host and path were matched and
the request was redirected. From WBRUMTCHRED.
CICS_S_WEBSERV_T
This table provides details of various attribute settings of each WEBSERVICE
resource definition. It contains data from CICS statistics records (SMF 110, subtype
2 stid 106). For CICS/TS V3.1 and later, it takes information from the DFHPIWDS
CICS dsect.).
The default retention period for this table is 7 days.
266
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE.
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields
SMFSTSID, SMFSTDTE, and SMFSTTME from the record
as parameters in the PERIOD function.
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFSTSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
used when requesting a session with this CICS system.
From SMFSTPRN.
WEBSERVICE_NAME
K
CHAR(8)
The name of the WEBSERVICE resource definition. From
PIWSERNM.
PROGRAM_INTERFACE
CHAR(8)
For a service provider, indicates whether CICS passes data
to the target application program in a COMMAREA or a
CHANNEL or N/A. From PIWPGINT.
VALIDATION
CHAR(1)
Indicates whether full validation of SOAP messages
against the corresponding schema in the Web service
description is specified. Possible values are N or Y. From
PIWMSGVAL.
PIPELINE_NAME
CHAR(8)
The name of the PIPELINE resource that contains this Web
service resource. From PIWPIPNM.
URIMAP_NAME
CHAR(8)
The name of a dynamically installed URIMAP resource
definition, if there is one that is associated with this Web
service. From PIWURINM.
WSBIND_FILE
VARCHAR(254)
The file name of the Web service binding file associated
with the Web service resource. From PIWWSBFL.
WSDL_FILE
VARCHAR(254)
The file name of the Web service description (WSDL) file
associated with the Web service resource. From
PIWWSDLFL.
WSDL_BIND
VARCHAR(254)
The WSDL binding represented by the Web service. This
binding is one of (potentially) many that appear in the
WSDL file. From PIWWSDLBD.
ENDPOINT_URI
VARCHAR(254)
The URI specifying the location on the network (or
endpoint) of the Web service, as defined in the Web service
description. From PIWENDPURI.
PROGRAM_NAME
CHAR(8)
The name of the target application program. From
PIWPROGNM.
CONTAINER_NAME
VARCHAR(16)
When CICS passes data to the target application program
in a channel, indicates the name of the container that holds
the top level data. From PIWCONTNM.
WEBSERVICE_USECNT
FLOAT
The number of times this Web service was used to process
a Web service request. From PIWWEBUSECNT.
CICS_TCPIP_CONN_D
This table provides daily TCP/IP connection statistics from CICS TS 3.2 (SMF 110,
subtype 2). This maps the CICS DFHISRDS macro.
The default retention period for this table is 30 days.
Chapter 6. Data tables, lookup tables, and control tables
267
CICS statistics component data tables
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
IP_CONN_NAME
K
CHAR(8)
IP Connection name. From ISR_IPCONN_NAME.
IP_APPLID
CHAR(8)
IP Connection applid. From ISR_APPLID.
IP_NETWORK_ID
CHAR(8)
IP Connection network id. From ISR_NETWORK_ID.
IP_HOST_NAME
CHAR(116)
IP Connection Host name. From ISR_HOST_NAME.
IP_PORT_NUMBER
INTEGER
IP Connection port number. From ISR_PORT_NUMBER.
IP_SSL_SUPPORT
CHAR(1)
IPCONN SSL Support – Y or N
IP_USERAUTH
CHAR(15)
IPCONN Userauth. From ISR_USERAUTH.
IP_TCPIP_SERVICE
CHAR(8)
IP Connection Tcpip service. From ISR_TCPIP_SERVICE.
IP_CON_GMT_CREATE
TIMESTAMP
AI Ipconn create time – GMT. From ISR_CON_GMT_CTIME.
IP_CON_LOC_CREATE
TIMESTAMP
AI Ipconn create time-Local. From ISR_CON_CTIME.
IP_CON_GMT_DELETE
TIMESTAMP
AI Ipconn delete time – GMT. From ISR_CON_GMT_DTIME.
IP_CON_LOC_DELETE
TIMESTAMP
AI Ipconn delete time-Local. From ISR_CON_DTIME.
IP_SEND_SESS
INTEGER
Send sessions. From ISR_SEND_SESS.
IP_CUR_SEND_SESS
INTEGER
Current send sessions. From ISR_CUR_SEND_SESS.
IP_PEAK_SEND_SESS
INTEGER
Peak send sessions. From ISR_PEAK_SEND_SESS.
IP_RECV_SESS
INTEGER
Receive sessions. From ISR_RECV_SESS.
IP_CUR_RECV_SESS
INTEGER
Current receive sessions. From ISR_CUR_RECV_SESS.
IP_PEAK_RECV_SESS
INTEGER
Peak receive sessions. From ISR_PEAK_RECV_SESS.
IP_TOT_ALLOC
INTEGER
IP Connection total allocates. From ISR_TOT_ALLOC.
IP_CUR_QD_ALLOC
INTEGER
Current queued allocates. From ISR_CURQ_ALLOC.
IP_PEAK_QD_ALLOC
INTEGER
Peak queued allocates. From ISR_PEAKQ_ALLOC.
IP_ALLOC_FAIL_LNK
INTEGER
Failed allocates – Link. From ISR_ALLOC_FAIL_LNK.
IP_ALLOC_FAIL_OTR
INTEGER
Failed allocates – Other. From ISR_ALLOC_FAIL_OTR.
IP_ALLOCQ_LIMIT
INTEGER
Allocate queuelimit. From ISR_ALLOCQ_LIMIT.
IP_QLIM_ALLOC_REJ
INTEGER
Queuelimit allocate rejects. From ISR_QLIM_ALLOC_REJ.
IP_MAXQ_TIME
INTEGER
Max queue time. From ISR_MAX_QUEUE_TIME.
IP_MAXQ_QPURGE
INTEGER
Maxq time allocate qpurges. From ISR_MAXQ_ALLOC_QP.
IP_MAXQ_PURGED
INTEGER
Maxq time allocates purged. From ISR_MAXQ_ALLOC_PRG.
IP_XISQ_REJECT
INTEGER
Xisque allocate rejects. From ISR_XISQ_ALLOC_REJ.
IP_XISQ_QPURGE
INTEGER
Xisque allocate qpurges. From ISR_XISQ_ALLOC_QP.
IP_XISQ_PURGE
INTEGER
Xisque allocates purged. From ISR_XISQ_ALLOC_PRG.
IP_TRANS_ATTACHED
INTEGER
No. transactions attached. From ISR_TRANS_ATTACHED.
268
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS statistics component data tables
Column name
Data type
Description
IP_FUNSHP_PRG_REQ
INTEGER
Function Shipped Program requests. From
ISR_FS_PG_REQUESTS.
IP_FUNSHP_BYT_SENT
FLOAT
FS Program reqs bytes sent. From ISR_FS_PG_BYT_SENT.
IP_FUNSHP_BYT_RECV
FLOAT
FS Program reqs bytes received. From ISR_FS_PG_BYT_RECV.
CICS_TCPIP_CONN_H
This table provides hourly TCP/IP connection statistics from CICS TS 3.2 (SMF
110, subtype 2). This maps the CICS DFHISRDS macro.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
IP_CONN_NAME
K
CHAR(8)
IP Connection name. From ISR_IPCONN_NAME.
IP_APPLID
CHAR(8)
IP Connection applid. From ISR_APPLID.
IP_NETWORK_ID
CHAR(8)
IP Connection network id. From ISR_NETWORK_ID.
IP_HOST_NAME
CHAR(116)
IP Connection Host name. From ISR_HOST_NAME.
IP_PORT_NUMBER
INTEGER
IP Connection port number. From ISR_PORT_NUMBER.
IP_SSL_SUPPORT
CHAR(1)
IPCONN SSL Support – Y or N
IP_USERAUTH
CHAR(15)
IPCONN Userauth. From ISR_USERAUTH.
IP_TCPIP_SERVICE
CHAR(8)
IP Connection Tcpip service. From ISR_TCPIP_SERVICE.
IP_CON_GMT_CREATE
TIMESTAMP
AI Ipconn create time – GMT. From ISR_CON_GMT_CTIME.
IP_CON_LOC_CREATE
TIMESTAMP
AI Ipconn create time-Local. From ISR_CON_CTIME.
IP_CON_GMT_DELETE
TIMESTAMP
AI Ipconn delete time – GMT. From ISR_CON_GMT_DTIME.
IP_CON_LOC_DELETE
TIMESTAMP
AI Ipconn delete time-Local. From ISR_CON_DTIME.
IP_SEND_SESS
INTEGER
Send sessions. From ISR_SEND_SESS.
IP_CUR_SEND_SESS
INTEGER
Current send sessions. From ISR_CUR_SEND_SESS.
IP_PEAK_SEND_SESS
INTEGER
Peak send sessions. From ISR_PEAK_SEND_SESS.
IP_RECV_SESS
INTEGER
Receive sessions. From ISR_RECV_SESS.
IP_CUR_RECV_SESS
INTEGER
Current receive sessions. From ISR_CUR_RECV_SESS.
IP_PEAK_RECV_SESS
INTEGER
Peak receive sessions. From ISR_PEAK_RECV_SESS.
IP_TOT_ALLOC
INTEGER
IP Connection total allocates. From ISR_TOT_ALLOC.
IP_CUR_QD_ALLOC
INTEGER
Current queued allocates. From ISR_CURQ_ALLOC.
IP_PEAK_QD_ALLOC
INTEGER
Peak queued allocates. From ISR_PEAKQ_ALLOC.
Chapter 6. Data tables, lookup tables, and control tables
269
CICS statistics component data tables
Column name
Data type
Description
IP_ALLOC_FAIL_LNK
INTEGER
Failed allocates – Link. From ISR_ALLOC_FAIL_LNK.
IP_ALLOC_FAIL_OTR
INTEGER
Failed allocates – Other. From ISR_ALLOC_FAIL_OTR.
IP_ALLOCQ_LIMIT
INTEGER
Allocate queuelimit. From ISR_ALLOCQ_LIMIT.
IP_QLIM_ALLOC_REJ
INTEGER
Queuelimit allocate rejects. From ISR_QLIM_ALLOC_REJ.
IP_MAXQ_TIME
INTEGER
Max queue time. From ISR_MAX_QUEUE_TIME.
IP_MAXQ_QPURGE
INTEGER
Maxqtime allocate qpurges. From ISR_MAXQ_ALLOC_QP.
IP_MAXQ_PURGED
INTEGER
Maxqtime allocates purged. From ISR_MAXQ_ALLOC_PRG.
IP_XISQ_REJECT
INTEGER
Xisque allocate rejects. From ISR_XISQ_ALLOC_REJ.
IP_XISQ_QPURGE
INTEGER
Xisque allocate qpurges. From ISR_XISQ_ALLOC_QP.
IP_XISQ_PURGE
INTEGER
Xisque allocates purged. From ISR_XISQ_ALLOC_PRG.
IP_TRANS_ATTACHED
INTEGER
No. transactions attached. From ISR_TRANS_ATTACHED.
IP_FUNSHP_PRG_REQ
INTEGER
Function Shipped Program requests. From
ISR_FS_PG_REQUESTS.
IP_FUNSHP_BYT_SENT
FLOAT
FS Program reqs bytes sent. From ISR_FS_PG_BYT_SENT.
IP_FUNSHP_BYT_RECV
FLOAT
FS Program reqs bytes received. From ISR_FS_PG_BYT_RECV.
Tables in the CICS transaction and unit-of-work analysis component
As described in “Evaluating the CICS transaction and unit-of-work analysis
component” on page 16, if you install the CICS transaction and unit-of-work
analysis component, Tivoli Decision Support for z/OS loads into its system tables
the data table and view tables described in this section.
If you install this component, use a separate collection job for it. In the daily CICS
collection job, exclude the data table provided with this component. Otherwise,
data collection takes too much time to complete and results in a table that is too
large to manage. For more information, see “Optimizing data collection” on page
19.
CICS_T_TRAN_T
This table provides statistics on CICS transactions. It contains information from
CICS performance class monitoring records for CICS/ESA and CICS/TS (SMF 110,
subtype 1) and CICS/MVS (SMF 110, subtype 0).
The default retention period for this table is 2 days.
Column name
Data type
Description
START_TIMESTAMP
K
TIMESTAMP
Date and time (timestamp) when the transaction was
started. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. When XRF is used, the two systems have the
same generic but different specific IDs. From
SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
270
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
ABEND_CODE_CURRENT
CHAR(4)
Current abend code. From ABCODEC (CICS V3) or
ABCODE (CICS V2).
ABEND_CODE_ORIGIN
CHAR(4)
Original (first) abend code. From ABCODEO (CICS V3) or
ABCODE (CICS V2).
BMS_INPUTS
INTEGER
Number of BMS IN requests. This is the number of
RECEIVE MAP requests that incurred a terminal I/O.
From BMSINCT.
BMS_MAP_REQUESTS
INTEGER
Number of BMS MAP requests. This is the number of
RECEIVE MAP requests that did not incur a terminal I/O
and the number of RECEIVE MAP FROM requests. From
BMSMAPCT.
BMS_OUTPUTS
INTEGER
Number of BMS OUT requests. This is the number of
SEND MAP requests. From BMSOUTCT.
BMS_REQUESTS_TOTAL
INTEGER
Total number of BMS requests. From BMSTOTCT.
BRIDGE_TRANS_ID
FLOAT
3270 Bridge transaction identification. From BRDGTRAN.
CFDTWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for CF data table
I/O. From CFDTWAIT.
CFDTWAIT_COUNT
FLOAT
Number of times that the user task waited for CF data
table I/O. From CFDTWAIT.
CHARS_IN_ALT_LU62
FLOAT
Number of characters received from the alternate terminal
facility by the user task for LUTYPE6.2 (APPC) sessions.
This is the sum of TCC62IN2.
CHARS_INPUT_ALT
INTEGER
Number of characters received from the LUTYPE6.1
alternate terminal facility. From TCCHRIN2.
CHARS_INPUT_PRIME
INTEGER
Number of characters received from the principal
terminal facility. From TCCHRIN1.
CHARS_OUT_ALT_LU62
FLOAT
Number of characters sent to the alternate terminal
facility by the user task for LUTYPE6.2 (APPC) sessions.
This is the sum of TCC62OU2.
CHARS_OUTPUT_ALT
INTEGER
Number of characters sent to the LUTYPE6.1 alternate
terminal facility. From TCCHROU2.
CHARS_OUTPUT_PRIME
INTEGER
Number of characters sent to the principal terminal
facility. From TCCHROU1.
CPU_SEC
FLOAT
CPU time, in seconds. From USRCPUT.
DB2_REQS_COUNT
FLOAT
Number of DB2 (EXEC SQL IFI) requests issued by the
user task. From DB2REQCT.
DB2CONWT_CLOCK
FLOAT
Elapsed time that the user task waited for a CICS DB2
subtask to become available. From DB2CONWT.
DB2CONWT_COUNT
FLOAT
Number of times that the user task waited for a CICS
DB2 subtask to become available. From DB2CONWT.
DB2RDYQW_CLOCK
FLOAT
Elapsed time that the user task waited for a DB2 thread
to become available. From DB2RDYQW.
DB2RDYQW_COUNT
FLOAT
Number of times that the user task waited for a DB2
thread to become available. From DB2RDYQW.
DB2WAIT_CLOCK
FLOAT
Elapsed time that the user task waited for DB2 to service
the DB2 EXEC SQL and IFI requests. From DB2WAIT.
DB2WAIT_COUNT
FLOAT
Number of times that the user task waited for DB2 to
service the DB2 EXEC SQL and IFI requests. From
DB2WAIT.
Chapter 6. Data tables, lookup tables, and control tables
271
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
DECRYPT_BYTES
FLOAT
Number of bytes decrypted by the secure sockets layer
for the user task. From SOBYDECT.
DISP_TCB_HWM
FLOAT
The peak number of CICS open TCBs (in TCB modes H8,
J8, J9, L8, or S8) that have been allocated to the user task.
From DSTCBHWM.
DISPATCH_COUNT
INTEGER
Total number of times that the transaction was
dispatched. From USRDISPT.
DISPATCH_DELAY_SEC
FLOAT
Time waiting for the first dispatch, in seconds. This is a
subset of SUSPEND_SEC. This is the sum of DSPDELAY.
DISPATCH_SEC
FLOAT
Elapsed time that the transaction was dispatched, in
seconds. From USRDISPT.
DISPATCH_WAITS
INTEGER
Number of times that the transaction was waiting for
redispatch. This is valid for CICS V3 and later. From
DISPWTT.
DISPATCH_WAIT_SEC
FLOAT
Time that the transaction was waiting for redispatch, in
seconds. This is valid for CICS V3 and later. From
DISPWTT.
DSMMSC_CLOCK
FLOAT
The elapsed time which the user task spent waiting
because no TCB was available, and none could be created
due to MVS storage constraints. From DSMMSC_CLOCK.
DSMMSC_COUNT
FLOAT
The number of times that the user task waited because no
TCB was available, and none could be created due to
MVS storage constraints. From DSMMSC_COUNT.
DSTCBM_CLOCK
FLOAT
The elapsed time which the user task spent in TCB
mismatch waits, that is, waiting because there was no
available TCB matching the request, but there was at least
one non-matching free TCB. From DSTCBM_CLOCK.
DSTCBM_COUNT
FLOAT
The number of times that the user task waited due to
TCB mismatch, because there was no available TCB
matching the request, but there was at least one
non-matching free TCB. From DSTCBM_COUNT.
ENCRYPT_BYTES
FLOAT
Number of bytes encrypted by the secure sockets layer
for the user task. From SOBYENCT.
ENQ_WAITS
FLOAT
Number of CICS Task Control ENQ waits. This is the sum
of ENQDELAY.
ENQ_WAIT_SEC
FLOAT
Time waiting for CICS Task Control ENQ, in seconds.
This is the sum of ENQDELAY.
EXCEPTIONS
INTEGER
Number of exception conditions that have occurred for
this task. Exception conditions are waits for storage, waits
for a string, and waits for a file buffer. This is valid for
CICS V3 and later. From EXWTTIME.
EXCEPTION_WAIT_SEC
FLOAT
Exception wait time, in seconds. This is valid for CICS V3
and later. From EXWTTIME.
FC_ACCESS_METHODS
INTEGER
Number of file control access method calls. Not
incremented if the request is function shipped. From
FCAMCT.
FC_ADD_REQUESTS
INTEGER
Number of file control ADD requests. Incremented even if
the request is function shipped. From FCADDCT.
FC_BROWSE_REQUESTS
INTEGER
Number of file control BROWSE requests. Incremented
even if the request is function shipped. From FCBRWCT.
272
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
FC_DELETE_REQUESTS
INTEGER
Number of file control DELETE requests. Incremented
even if the request is function shipped. From FCDELCT.
FC_GET_REQUESTS
INTEGER
Number of file control GET requests. Incremented even if
the request is function shipped. From FCGETCT.
FC_IO_WAITS
INTEGER
Number of file control I/O waits. From FCIOWTT.
FC_IO_WAIT_SEC
FLOAT
File control I/O wait time, in seconds. From FCIOWTT.
FC_PUT_REQUESTS
INTEGER
Number of file control PUT requests. Incremented even if
the request is function shipped. From FCPUTCT.
FC_REQUESTS_TOTAL
INTEGER
Total number of file control requests. Incremented even if
the request is function shipped. From FCTOTCT.
FE_ALLOC_COUNT
FLOAT
Number of conversations allocated by the user task. This
number is incremented for each FEPI ALLOCATE POOL
or FEPI CONVERSE POOL. This is the sum of
SZALLOCT.
FE_ALLOC_TIMEOUT
FLOAT
Number of times the user task timed out while waiting to
allocate a conversation. This is the sum of SZALLCTO.
FE_CHARS_RECEIVED
FLOAT
Number of characters received through FEPI by the user
task. This is the sum of SZCHRIN.
FE_CHARS_SENT
FLOAT
Number of characters sent through FEPI by the user task.
This is the sum of SZCHROUT.
FE_RECEIVE_REQ
FLOAT
Number of FEPI RECEIVE requests made by the user
task. This number is also incremented for each FEPI
CONVERSE request. This is the sum of SZRCVCT.
FE_RECEIVE_TIMEOUT
FLOAT
Number of times the user task timed out while waiting to
receive data. This is the sum of SZRCVTO.
FE_REQUESTS_TOTAL
FLOAT
Total number of all FEPI API and SPI requests made by
the user task. This is the sum of SZTOTCT.
FE_SEND_REQUESTS
FLOAT
Number of FEPI SEND requests made by the user task.
This number is also incremented for each FEPI
CONVERSE request. This is the sum of SZSENDCT.
FE_START_REQUESTS
FLOAT
Number of FEPI START requests made by the user task.
This is the sum of SZSTRTCT.
FE_WAITS
FLOAT
Number of times that the user task waited for FEPI
services. This is the sum of SZWAIT.
FE_WAIT_SEC
FLOAT
Time that the user task waited for all FEPI services, in
seconds. This is the sum of SZWAIT.
GETMAINS_CDSA
INTEGER
Number of user_storage GETMAIN requests below the
16MB line, in the CDSA. From SCCGETCT.
GETMAINS_ECDSA
INTEGER
Number of user_storage GETMAIN requests above the
16MB line, in the ECDSA. From SCCGETCTE.
GETMAINS_EUDSA
INTEGER
Number of user_storage GETMAIN requests above the
16MB line, in the EUDSA. From SCUGETCTE.
GETMAINS_UDSA
INTEGER
Number of user_storage GETMAIN requests below the
16MB line, in the UDSA. From SCUGETCT.
GNQDELAY_CLOCK
FLOAT
Elapsed time that the user task waited for a CICS task
control global enqueue. From GNQDELAY.
GNQDELAY_COUNT
FLOAT
Number of times that the user task waited for a CICS
task control global enqueue. From GNQDELAY.
Chapter 6. Data tables, lookup tables, and control tables
273
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
GVUPWAIT_CLOCK
FLOAT
Elapsed time that the user task waited as the result of
relinquishing control to another task. From GVUPWAIT.
GVUPWAIT_COUNT
FLOAT
Number of times that the user task waited as the result of
relinquishing control to another task. From GVUPWAIT.
IC_START_REQUESTS
INTEGER
Number of interval control START or INITIATE requests.
From ICPUINCT.
ICDELAY_CLOCK
FLOAT
Elapsed time that the user task waited the result from
EXEC CICS DELAY or RETRIEVE command. From
ICDELAY.
ICDELAY_COUNT
FLOAT
Number of times that the user task waited the result from
EXEC CICS DELAY or RETRIEVE command. From
ICDELAYT.
ICTOT_REQS
FLOAT
Total number of Interval Control Start, Cancel, Delay and
Retrieve requests issued by the user task. From ICTOTCT.
IMS_REQS_COUNT
FLOAT
Number of IMS (DBCTL) requests issued by the user task.
From IMSREQCT.
IMSWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for DBCTL to
service the IMS requests issued by the user task. From
IMSWAIT.
IMSWAIT_COUNT
FLOAT
Number of times that the user task waited for DBCTL to
service the IMS requests issued by the user task. From
IMSWAIT.
J8CPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on each
CICS J8 TCB. From J8CPUT.
J8CPUT_COUNT
FLOAT
Number of times that the user task was dispatched on
each CICS J8 TCB. From J8CPUT.
J9CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS J9
mode TCB. From J9CPUT_CLOCK.
J9CPUT_COUNT
FLOAT
The number of times that the user task was dispatched by
the CICS dispatcher domain on a CICS J9 mode TCB.
From J9CPUT_COUNT.
JAVA_OO_REQS
FLOAT
Total number of CICS OO foundation class requests
(JCICS) issued by the user task. From CFCAPICT.
JC_IO_WAITS
INTEGER
Number of journal control I/O waits. From JCIOWTT.
JC_IO_WAIT_SEC
FLOAT
Journal control I/O wait time, in seconds. From
JCIOWTT.
JC_OUTPUT_REQUESTS
INTEGER
Journal control output (PUT) requests. From JCPUWRCT.
JVMITI_CLOCK
FLOAT
JVM elapsed time, initialize - clock. From
JVMITI_CLOCK.
JVMITI_COUNT
FLOAT
JVM elapsed time, initialize - count. From
JVMITI_COUNT.
JVMRTI_CLOCK
FLOAT
JVM elapsed time, reset - clock. From JVMRTI_CLOCK.
JVMRTI_COUNT
FLOAT
JVM elapsed time, reset - count. From JVMRTI_COUNT.
JVMSUSP_CLOCK
FLOAT
Elapsed time that the task was suspended by the CICS
dispatcher while running in the CICS JVM. From
JVMSUSP.
274
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
JVMSUSP_COUNT
FLOAT
Number of times that the task was suspended by the
CICS dispatcher while running in the CICS JVM. From
JVMSUSP.
JVMTIME_CLOCK
FLOAT
Elapsed time that was spent in the CICS JVM by the user.
From JVMTIME.
JVMTIME_COUNT
FLOAT
Number of times that were spent in the CICS JVM by the
user. From JVMTIME.
KY8DIS_CLOCK
FLOAT
User task key 8 mode dispatch time - clock.
idd:break>From KY8DIS_CLOCK.
KY8DIS_COUNT
FLOAT
User task key 8 mode dispatch time - count.
idd:break>From KY8DIS_COUNT.
KY8CPU_CLOCK
FLOAT
User task key 8 mode CPUtime - clock. idd:break>From
KY8CPU_CLOCK.
KY8CPU_COUNT
FLOAT
User task key 8 mode CPU time - count. idd:break>From
KY8CPU_COUNT.
KY9_COUNT
FLOAT
The number of times the user task was dispatched by the
CICS dispatcher on a CICS key 9 mode TCB. From
KY9_COUNT.
KY9CPU_CLOCK
FLOAT
Processor time during which the user task was dispatched
by the CICS dispatcher on a CICS key 9 mode TCB. From
KY9CPU_CLOCK.
KY9DIS_CLOCK
FLOAT
The total elapsed time during which the user task was
dispatched by the CICS dispatcher on a CICS key 9 mode
TCB. From KY9DIS_CLOCK.
L8CPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on each
CICS L8 TCB. From L8CPUT.
L8CPUT_COUNT
FLOAT
Number of times that the user task was dispatched on
each CICS L8 TCB. From L8CPUT.
L9CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS L9
mode TCB. When a transaction invokes an OPENAPI
application program defined with EXECKEY= USER, it is
allocated and uses a CICS L9 mode TCB. From L9CPUT.
L9CPUT_COUNT
FLOAT
Number of times the user task was dispatched by the
CICS dispatcher domain on a CICS L9 mode TCB. This
field is related to XPlink support. From L9CPUT.
LINK_URM_REQS
FLOAT
Number of program LINK URM requests issued by the
user task. This is the sum of PLCURMCT.
LMDELAY_CLOCK
FLOAT
Elapsed time that the user task waited to acquire a lock
on a resource. From LMDELAY.
LMDELAY_COUNT
FLOAT
Number of times that the user task waited to acquire a
lock on a resource. From LMDELAY.
LOGGER_WRITE_COUNT
FLOAT
Number of CICS logger write requests issued by the user
task. This is the sum of LOGWRTCT.
LU_NAME
CHAR(8)
VTAM logical unit name (if available) of the terminal
associated with this transaction. From LUNAME.
LU61_IO_WAITS
FLOAT
Number of waits for I/O on a LUTYPE6.1 connection or
session. Includes waits for conversations across
LUTYPE6.1 connections, but not waits due to LUTYPE6.1
syncpoint flows. This is the sum of LU61WTT.
Chapter 6. Data tables, lookup tables, and control tables
275
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
LU61_IO_WAIT_SEC
FLOAT
I/O wait time for a LUTYPE6.1 connection or session, in
seconds. Includes wait time for conversations across
LUTYPE6.1 connections, but not waits due to LUTYPE6.1
syncpoint flows. This is the sum of LU61WTT.
LU62_IO_WAITS
FLOAT
Number of waits for I/O on a LUTYPE6.2 (APPC)
connection or session. Includes waits for conversations
across LUTYPE6.2 (APPC) connections, but not waits due
to LUTYPE6.2 (APPC) syncpoint flows. This is the sum of
LU62WTT.
LU62_IO_WAIT_SEC
FLOAT
I/O wait time for a LUTYPE6.2 (APPC) connection or
session, in seconds. Includes wait time for conversations
across LUTYPE6.2 (APPC) connections, but not waits due
to LUTYPE6.2 (APPC) syncpoint flows. This is the sum of
LU62WTT.
MAXHTD_CLOCK
FLOAT
Max hot-pooling TCB delay time - clock. idd:break>From
MAXHTD_CLOCK.
MAXHTD_COUNT
FLOAT
Max hot-pooling TCB delay time - count. idd:break>From
MAXHTD_COUNT.
MAXJTD_CLOCK
FLOAT
Max JVM TCB delay time - clock. idd:break>From
MAXJTD_CLOCK.
MAXJTD_COUNT
FLOAT
Max JVM TCB delay time - count. idd:break>From
MAXJTD_COUNT.
MAXOTDLY_CLOCK
FLOAT
Elapsed time that the user task waited to obtain a CICS
open TCB, because the region had reached the limit set by
MAXOPENTCBS parameter. From MAXOTDLY.
MAXOTDLY_COUNT
FLOAT
Number of times that the user task waited to obtain a
CICS open TCB, because the region had reached the limit
set by MAXOPENTCBS parameter. From MAXOTDLY.
MAXSSLTCBS_COUNT
FLOAT
Number of times the CICS system reached the limit set by
the system initialization parameter MAXSSLTCBS. From
MAXSTDLY.
MAXXPTCBS_COUNT
FLOAT
Number of times the CICS system reached the limit set by
the system initialization parameter MAXXPTCBS. From
MAXXTDLY.
MRO_WAITS
INTEGER
Number of times the task waited for control at this end of
an MRO link. From IRIOWTT.
MRO_WAIT_SEC
FLOAT
Elapsed time, in seconds, that the task waited for control
at this end of an MRO link. From IRIOWTT.
MSCPUT_CLOCK
FLOAT
Total processor time that the user task was dispatched on
each CICS TCB. From MSDISPT.
MSCPUT_COUNT
FLOAT
Number of times that the user task was dispatched on
each CICS TCB. From MSDISPT.
MSDISPT_CLOCK
FLOAT
Total elapsed time that the user task was dispatched on
each CICS TCB. From MSDISPT.
MSDISPT_COUNT
FLOAT
Number of times that the user task was dispatched on
each CICS TCB. From MSDISPT.
MSGS_IN_ALT_LU62
FLOAT
Number of messages received from the alternate terminal
facility by the user task for LUTYPE6.2 (APPC) sessions.
This is the sum of TCM62IN2.
MSGS_INPUT_ALT
INTEGER
Number of messages received from the LUTYPE6.1
alternate terminal facility. From TCMSGIN2.
276
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
MSGS_INPUT_PRIME
INTEGER
Number of messages received from the principal terminal
facility. From TCMSGIN1.
MSGS_OUT_ALT_LU62
FLOAT
Number of messages sent to the alternate terminal facility
by the user task for LUTYPE6.2 (APPC) sessions. This is
the sum of TCM62OU2.
MSGS_OUTPUT_ALT
INTEGER
Number of messages sent to the LUTYPE6.1 alternate
terminal facility. From TCMSGOU2.
MSGS_OUTPUT_PRIME
INTEGER
Number of messages sent to the principal terminal
facility. From TCMSGOU1.
MXT_DELAY_SEC
FLOAT
Time waiting for the first dispatch caused by MXT limits
being reached, in seconds. This is the sum of MXTDELAY.
NET_ID
CHAR(8)
Network ID. Form NETID
NO_CHAR_RCV
FLOAT
Number of characters received. From SOCHRIN.
NO_CHAR_RCV_IN
FLOAT
Number of characters received inbound. From
SOCHRIN1.
NO_CHAR_SEND
FLOAT
Number of characters sent. From SOCHROUT.
NO_CHAR_SND_IN
FLOAT
Number of characters sent inbound. From SOMSROU1.
NO_CRT_NP_SOCK
FLOAT
Number of create non-persistent socket requests.
idd:break>From SOCPSCT.
NO_CRT_P_SOCK
FLOAT
Number of create persistent socket requests.
idd:break>From SOCNPSCT.
NO_EXT_CERTIF
FLOAT
Number of extract TCP/IP and certificate requests.
idd:break>From SOEXTRCT.
NO_INBO_RCV
FLOAT
Number of inbound socket receive requests.
idd:break>From SOMSGIN1.
NO_IN_SOCKET
FLOAT
Number of inbound socket send requests. From
SOMSGOU1.
NO_SOCKET_RCV
FLOAT
Number of socket receive requests. From SORCVCT.
NO_SOCKET_SND
FLOAT
Number of socket send requests. From SOSENDCT.
NON_PERS_SOCK
FLOAT
Persistent socket high-water-mark. From SONPSHWM.
NET_NAME
CHAR(20)
Network name. This name has two parts, separated by a
period. The first part is VTAMs name for the system
services control point (SSCP). The second part is the task
origin: either the terminal LU name or the generic CICS
LU name. From NETNAME.
OPERATOR_ID
CHAR(3)
Operator identification at task creation. From OPR.
OTSIND_CLOCK
FLOAT
OTS indoubt wait time - clock. From OTSIND_CLOCK.
OTSIND_COUNT
FLOAT
OTS indoubt wait time - count. From OTSIND_COUNT.
OTS_TRANS_ID
CHAR(128)
OTS transaction ID. From OTSTID.
PAGEINS
INTEGER
Number of virtual storage page-ins. For CICS V2 only.
From PAGINCT.
PERF_REC_COUNT
FLOAT
Number of performance class records written by the CICS
Monitoring Facility (CMF) for the user task. From
PERRECNT.
PERSISTE_SOCK
FLOAT
Non-persistent socket high-water-mark. From SOPSHWM.
PGM_COMPRESS
INTEGER
Number of program compressions. For CICS V2 only.
From PCCMPRTM.
Chapter 6. Data tables, lookup tables, and control tables
277
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
PGM_COMPRESS_SEC
FLOAT
Time, in seconds, that the task spent in program
compression. For CICS V2 only. From PCCMPRTM.
PGM_DTL_COUNT
FLOAT
Number of distributed program LINK requests issued by
the user task. From PCDPLCT.
PGM_LINK_REQUESTS
INTEGER
Number of program LINK requests. From PCLINKCT.
PGM_LOAD_REQUESTS
INTEGER
Number of program LOAD requests. From PCLOADCT.
PGM_LOADS
INTEGER
Number of program library fetches. From PCLOADTM.
PGM_LOAD_SEC
FLOAT
Time, in seconds, that the task waited for program library
(DFHRPL) fetches. From PCLOADTM.
PGM_XCTL_REQUESTS
INTEGER
Number of program XCTL (transfer control) requests.
From PCXCTLCT.
PORT_NUMBER
FLOAT
Port number being used for this TCP/IP service. From
PORTNUM.
PROGRAM_NAME
CHAR(8)
Name of the first program invoked at attach time. If the
transaction is routed to another system, the name on this
system is DFHCRP. From PGMNAME.
PTPWAI_CLOCK
FLOAT
Partner wait time - clock. From PTPWAI_CLOCK.
PTPWAI_COUNT
FLOAT
Partner wait time - count. From PTPWAI_COUNT.
QRCPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on the
CICS QR TCB. From QRCPUT.
QRCPUT_COUNT
FLOAT
Number of times that the user task was dispatched on the
CICS QR TCB. From QRCPUT.
QRDISPT_CLOCK
FLOAT
Elapsed time that the user task was dispatched on the
CICS QR TCB. From QRDISPT.
QRDISPT_COUNT
FLOAT
Number of times that the user task was dispatched on the
CICS QR TCB. From QRDISPT.
QRMODDLY_CLOCK
FLOAT
Elapsed time that the user task waited for a redispatch on
the CICS QR TCB. From QRMODDLY.
QRMODDLY_COUNT
FLOAT
Number of times that the user task waited for a
redispatch on the CICS QR TCB. From QRMODDLY.
RECOVERY_MGR_UOW
CHAR(8)
Identifier of the logical unit of work (unit of recovery) for
this task. Unit-of-recovery values are used to synchronize
recovery operations among CICS and their resource
managers, such as IMS and DB2. From RMUOWID.
RECORD_TYPE
CHAR(4)
Record type: C for a terminal converse, D for user EMP
DELIVER request, T for a task termination, MT for a
semi-permanent mirror suspend (CICS V3 only), F for a
long-running transaction and S for a syncpoint. From
RTYPE.
REDISPATC_COUNT
FLOAT
Number of times that the user task was re-dispatched
after a CICS Dispatcher change TCB mode request. From
DSCHMDLY.
REDISPATC_WAIT_SEC
FLOAT
The elapsed time, in seconds, the user task waited for
re-dispatch after a CICS Dispatcher change-TCB mode
request was issued by or on behalf of the user task. This
field is related to Internet Security and is a subset of
SUSPEND_SEC. From DSCHMDLY.
RESPONSE_SEC
FLOAT
Transaction response time, in seconds. Calculated as STOP
- START.
278
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
RLSWAIT_CLOCK
FLOAT
Elapsed time during which the user task waited for RLS
file I/O. This is from RLSWAIT.
RLSWAIT_COUNT
FLOAT
Number of times that the user task was waiting for RLS
file I/O. This is the sum of RLSWAIT.
RLUNAME
CHAR(8)
VTAM logical unit name. From RLUNAME.
RMI_COUNT
FLOAT
Number of times that the user task was in the Resource
Manager Interface (RMI). This is the sum of RMITIME.
RMI_SEC
FLOAT
Time spent in the Resource Manager Interface (RMI), in
seconds. This is the sum of RMITIME.
RMI_SUSPENDS
FLOAT
Number of times that the task was suspended while in
the Resource Manager Interface (RMI). This is a subset of
SUSPENDS and RMI_COUNT. This is the sum of
RMISUSP.
RMI_SUSPEND_SEC
FLOAT
Time the task was suspended by the dispatcher while in
the Resource Manager Interface (RMI), in seconds. This is
a subset of SUSPEND_SEC and RMI_SEC. This is the sum
of RMISUSP.
ROCPUT_CLOCK
FLOAT
User task RO mode CPU time - clock. idd:break>From
ROCPUT_CLOCK.
ROCPUT_COUNT
FLOAT
User task RO mode CPU time - count. idd:break>From
ROCPUT_COUNT.
RODISP_CLOCK
FLOAT
User task RO mode dispatch time - clock. idd:break>From
RODISP_CLOCK.
RODISP_COUNT
FLOAT
User task RO mode dispatch time - count.
idd:break>From RODISP_COUNT.
RQPWAI_CLOCK
FLOAT
Request processor wait time - clock. From
RQPWAI_CLOCK.
RQPWAI_COUNT
FLOAT
Request processor wait time - count. From
RQPWAI_COUNT.
RQRWAI_CLOCK
FLOAT
Request receiver wait time - clock. From
RQPWAI_CLOCK.
RQRWAI_COUNT
FLOAT
Request receiver wait time - count. From
RQPWAI_COUNT.
RRMSWAIT_CLOCK
FLOAT
Elapsed time that the user task waited in doubt using
resource recovery services for EXCI. From RRMSWAIT.
RRMSWAIT_COUNT
FLOAT
Number of times that the user task waited in doubt using
resource recovery services for EXCI. From RRMSWAIT.
RUNTRWTT_CLOCK
FLOAT
Elapsed time that the user task waited for completion of a
transaction that executed as the result of a CICS BTS run
process or run activity. From RUNTRWTT.
RUNTRWTT_COUNT
FLOAT
Number of times that the user task waited for completion
of a transaction that executed as the result of a CICS BTS
run process or run activity. From RUNTRWTT.
S8CPUT_CLOCK
FLOAT
Processor time that the user task was dispatched on each
CICS S8 TCB. From S8CPUT.
S8CPUT_COUNT
FLOAT
Number of times that the user task was dispatched on
each CICS S8 TCB. From S8CPUT.
Chapter 6. Data tables, lookup tables, and control tables
279
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
SHR24_BYTE_COUNT
FLOAT
Number of bytes of shared storage GETMAINed by the
user task below the 16MB line, in the CDSA or SDSA.
This is the sum of SC24SGCT.
SHR24_FREEM_COUNT
FLOAT
Number of bytes of shared storage FREEMAINed by the
user task below the 16MB line, in the CDSA or SDSA.
This is the sum of SC24SGCT.
SHR24_GETM_COUNT
FLOAT
Number of storage GETMAIN requests issued by the user
task below the 16MB line, in the CDSA or SDSA. This is
the sum of SC24FSHR.
SHR31_BYTE_COUNT
FLOAT
Number of bytes of shared storage GETMAINed by the
user task above the 16MB line, in the ECDSA or ESDSA.
This is the sum of SC31GSHR.
SHR31_FREEM_COUNT
FLOAT
Number of bytes of shared storage FREEMAINed by the
user task above the 16MB line, in the ECDSA or ESDSA.
This is the sum of SC31FSHR.
SHR31_GETM_COUNT
FLOAT
Number of storage GETMAIN requests issued by the user
task above the 16MB line, in the ECDSA or ESDSA. This
is the sum of SC31SGCT.
SOIOWTT_CLOCK
FLOAT
Elapsed time that the user task waited for SOCKETS I/O.
From SOIOWTT.
SOIOWTT_COUNT
FLOAT
Number of times that the user task waited for SOCKETS
I/O. From SOIOWTT.
SOOIOW_CLOCK
FLOAT
Outbound socket I/O wait time - clock. idd:break>From
SOOIOW_CLOCK.
SOOIOW_COUNT
FLOAT
Outbound socket I/O wait time - count. idd:break>From
SOOIOW_COUNT.
SRVSYWTT_CLOCK
FLOAT
Elapsed time that the user task waited for a CF data table
to process syncpoint requests. From SRVSYWT.
SRVSYWTT_COUNT
FLOAT
Number of times that the user task waited for a CF data
table to process syncpoint requests. From SRVSYWT.
SSLTCB_WAIT_SEC
FLOAT
The elapsed time, in seconds, in which the user task
waited to obtain a CICS SSL TCB (S8 mode), because the
CICS system had reached the limit set by the system
initialization parameter MAXSSLTCBS. This field is
related to Internet Security. From MAXSTDLY.
STOP_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when the transaction finished.
From STOP.
STORAGE_CDSA_MAX
INTEGER
Peak user storage allocated below the 16MB line, in the
CICS dynamic storage area (CDSA), in bytes. From
SC24CHWM.
STORAGE_ECDSA_MAX
INTEGER
Peak user storage allocated above the 16MB line, in the
extended CICS dynamic storage area (ECDSA), in bytes.
From SC31CHWM.
STORAGE_EUDSA_MAX
INTEGER
Peak of user storage allocated above the 16MB line, in the
extended user dynamic storage area (EUDSA), in bytes.
From SCUSRHWME.
STORAGE_OCC_CDSA
FLOAT
Storage occupancy below the 16MB line, in the CDSA, in
kilobyte-seconds. This measures the area under the curve
of storage in use against elapsed time. From SC24COCC.
280
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
STORAGE_OCC_ECDSA
FLOAT
Storage occupancy above the 16MB line, in the ECDSA, in
kilobyte-seconds. This measures the area under the curve
of storage in use against elapsed time. From SC31COCC.
STORAGE_OCC_EUDSA
FLOAT
Storage occupancy above the 16MB line, in the EUDSA, in
kilobyte-seconds. This measures the area under the curve
of storage in use against elapsed time. From SCUSRSTGE.
STORAGE_OCC_UDSA
FLOAT
Storage occupancy below the 16MB line, in the UDSA, in
kilobyte-seconds. This measures the area under the curve
of storage in use against elapsed time. From SCUSRSTG.
STORAGE_PGM_A16M
INTEGER
Peak program storage above the 16MB line, in bytes. This
includes ECDSA, EUDSA and ERDSA. From
PC31AHWM.
STORAGE_PGM_B16M
INTEGER
Peak program storage below the 16MB line, in bytes. This
includes CDSA and UDSA. From PC24BHWM.
STORAGE_PGM_CDSA
INTEGER
Peak program storage below the 16MB line, in the CICS
dynamic storage area (CDSA), in bytes. From
PC24CHWM.
STORAGE_PGM_ECDSA
INTEGER
Peak program storage above the 16MB line, in the
extended CICS dynamic storage area (ECDSA), in bytes.
From PC31CHWM.
STORAGE_PGM_ERDSA
INTEGER
Peak program storage above the 16MB line, in the
extended read-only dynamic storage area (ERDSA), in
bytes. From PC31RHWM.
STORAGE_PGM_ESDSA
FLOAT
Peak program storage above the 16MB line in the
extended shared dynamic storage area (ESDSA). This is a
subset of STORAGE_PGM_A16M. This is the maximum
of PC31SHWM.
STORAGE_PGM_EUDSA
INTEGER
Peak program storage above the 16MB line, in the
extended user dynamic storage area (EUDSA), in bytes.
From PC31UHWM.
STORAGE_PGM_RDSA
FLOAT
Peak program storage below the 16MB line in the
read-only dynamic storage area (RDSA). This is a subset
of STORAGE_PGM_B16M. This is the maximum of
PC24RHWM.
STORAGE_PGM_SDSA
FLOAT
Peak program storage below the 16MB line in the shared
dynamic storage area (SDSA). This is a subset of
STORAGE_PGM_B16M. This is the maximum of
PC24SHWM.
STORAGE_PGM_TOTAL
INTEGER
Peak program storage both above and below the 16MB
line, in bytes. From PCSTGHWM.
STORAGE_PGM_UDSA
INTEGER
Peak program storage below the 16MB line, in the user
dynamic storage area (UDSA), in bytes. From
PC24UHWM.
STORAGE_TIOA
INTEGER
Terminal storage allocated to the terminal associated with
this task, if applicable, in bytes. From TCSTG.
STORAGE_UDSA_MAX
INTEGER
Peak user storage allocated below the 16MB line, in the
user dynamic storage area (UDSA), in bytes. From
SCUSRHWM.
SUSPENDS
INTEGER
Number of times the task was suspended because of
waiting for dispatch or redispatch. From SUSPTIME.
Chapter 6. Data tables, lookup tables, and control tables
281
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
SUSPEND_SEC
FLOAT
Total elapsed time, in seconds, that the task was
suspended by the dispatcher. This includes time waiting
for first dispatch, task suspend time and time waiting for
redispatch after a suspended task has been resumed.
From SUSPTIME.
SYNCDLY_CLOCK
FLOAT
Elapsed time that the user task waited for a SYNC
request to be issued by its parent transaction. From
SYNCDLY.
SYNCDLY_COUNT
FLOAT
Number of times that the user task waited for a SYNC
request to be issued by its parent transaction. From
SYNCDLY.
SYNCPOINT_REQUESTS
INTEGER
Number of SYNCPOINT requests. From SPSYNCCT.
SYNCTIME_CLOCK
FLOAT
Total elapsed time that the user task was dispatched and
was processing Syncpoint requests. This is from
SYNCTIME.
SYNCTIME_COUNT
FLOAT
Number of times that the user task was dispatched and
was processing Syncpoint requests. This is the sum of
SYNCTIME.
TASK_FLAG
CHAR(4)
Task error flags, a string of 31 bits used for signalling
unusual conditions occurring during the transaction.
From TASKFLAG.
TC_ALLOCATE_REQ
INTEGER
Number of TCTTE ALLOCATE requests issued by the
task for APPC, LUTYPE6.1, and IRC sessions. From
TCALLOCT.
TC_IO_WAITS
INTEGER
Number of terminal control I/O waits. This includes
LUTYPE6.1 communication waits for CICS V3 data. (See
LU61_IO_WAITS for CICS V4 and later.) This is the sum
of TCIOWTT.
TC_IO_WAIT_SEC
FLOAT
Terminal control I/O wait time, in seconds. This includes
LUTYPE6.1 communication wait time for CICS V3 data.
(See LU61_IO_WAIT_SEC for CICS V4 and later.) This is
the sum of TCIOWTT.
TCB_ATTACH_COUNT
FLOAT
Number of CICS TCBs attached by the user task. From
TCBATTCT.
TCB_CHANGE_MODES
FLOAT
Number of CICS change-TCB modes issued by the user
task. From CHMODECT.
TCLSNAME_DELAY_SEC
FLOAT
Time waiting for the first dispatch caused by transaction
class limits being reached, in seconds. This is the sum of
TCLDELAY.
TCP_SERVICE
CHAR(8)
Name of the CP/IP service. From TCPSRVCE.
TD_GET_REQUESTS
INTEGER
Number of transient data GET requests. From TDGETCT.
TD_IO_WAITS
INTEGER
Number of transient data I/O waits. This is valid for
CICS V3 and later. From TDIOWTT.
TD_IO_WAIT_SEC
FLOAT
Transient data I/O wait time, in seconds. This is valid
only for CICS V3. From TDIOWTT.
TD_PURGE_REQUESTS
INTEGER
Number of transient data PURGE requests. From
TDPURCT.
TD_PUT_REQUESTS
INTEGER
Number of transient data PUT requests. From TDPUTCT.
TD_REQUESTS_TOTAL
INTEGER
Total number of transient data requests. From TDTOTCT.
TERMINAL_ID
CHAR(4)
Terminal identifier. From TERM.
282
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
TERM_CONNECT_NAME
CHAR(4)
Terminal session connection name. From TERMCNNM.
TERM_INFO
CHAR(4)
Terminal or session information for this tasks principal
facility as identified in the TERM field id 002. This field is
null if the task is not associated with a terminal or
session. From TERMINFO.
TOT_NO_SOCKET
FLOAT
Total number of socket requests. From SOTOTCT.
TRAN_CLASS_NAME
CHAR(8)
Transaction class name at task creation. From
TCLSNAME.
TRANSACTION_CLASS
SMALLINT
Transaction class at task creation. From TCLASS.
TRANSACTION_FLAG
CHAR(8)
Transaction flags. A string of 64 bits used for signalling
the transaction definition and status information. From
TRANGLAG.
TRANSACTION_NO
DECIMAL(5, 0)
This column is replaced by TRANSACTION_NUM.
TRANSACTION_NUM
CHAR(5)
Transaction identification number, normally a decimal
number. However, some CICS system tasks are identified
by: III for system initialization, JBS or Jnn for journal
control (nn = journal number 01-99), and TCP for terminal
control. From TRANNUM.
TRANSACTION_PRIO
SMALLINT
Transaction priority at task creation. From TRANPRI.
TRANSACTION_TYPE
CHAR(4)
Transaction start type. From T.
TRANS_FACILITY_NAM
CHAR(8)
Transaction facility name. From FCTYNAME.
TS_AUX_PUT_REQ
INTEGER
Number of auxiliary temporary storage PUT requests.
From TSPUTACT.
TS_GET_REQUESTS
INTEGER
Number of temporary storage GET requests. From
TSGETCT.
TS_IO_WAITS
INTEGER
Number of temporary storage I/O waits. From TSIOWTT.
TS_IO_WAIT_SEC
FLOAT
Temporary storage I/O wait time, in seconds. From
TSIOWTT.
TS_MAIN_PUT_REQ
INTEGER
Number of main temporary storage PUT requests. From
TSPUTMCT.
TS_REQUESTS_TOTAL
INTEGER
Total number of temporary storage requests. From
TSTOTCT.
TSSHWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for the completion
of an asynchronous shared temporary storage request to a
temporary storage data server. From TSSHWAIT.
TSSHWAIT_COUNT
FLOAT
Number of times that the user task waited for the
completion of an asynchronous shared temporary storage
request to a temporary storage data server. From
TSSHWAIT.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system.
It is a binary value derived from the originating system
clock or a character value (hhmmss), if the originating
system is communicating through a DL/I batch session.
From first 6 bytes of UOWID.
UOW_PERIOD_COUNT
SMALLINT
Unit of work period count. It may change during the life
of a task as a result of syncpoint activity. From the last
two bytes of UOWID.
Chapter 6. Data tables, lookup tables, and control tables
283
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
USER_ID
CHAR(8)
User ID at task creation. This can also be the remote user
ID for a task created as the result of receiving an
ATTACH request across an MRO or APPC link with
attach-time security. From USERID.
WORKLOAD_REPCLASS
CHAR(8)
MVS Workload Manager (WLM) report class for this
transaction. This field is null if the transaction was
WLM-classified in another CICS region. From RPTCLASS.
WORKLOAD_SERVCLASS
CHAR(8)
MVS Workload Manager (WLM) service class for this
transaction. This field is null if the transaction was
WLM-classified in another CICS region. From SRVCLASS.
WTCEWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for one or more
ECBs or the completion of an event. From WTEXWAIT.
WTCEWAIT_COUNT
FLOAT
Number of times that the user task waited for one or
more ECBs or the completion of an event. From
WTEXWAIT.
WTEXWAIT_CLOCK
FLOAT
Elapsed time that the user task waited for one or more
ECBs, passed to CICS by the user task. From WTEXWAIT.
WTEXWAIT_COUNT
FLOAT
Number of times that the user task waited for one or
more ECBs, passed to CICS by the user task. From
WTEXWAIT.
X8CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS X8
mode TCB. When a transaction invokes a C or C++
program that was compiled with the XPLINK option, and
that is defined with EXECKEY= CICS, it is allocated and
uses a CICS X8 mode TCB. From X8CPUT.
X8CPUT_COUNT
FLOAT
Number of times the user task was dispatched by the
CICS dispatcher domain on a CICS X8 mode TCB. This
field is related to XPlink support. From X8CPUT.
X9CPUT_CLOCK
FLOAT
The processor time during which the user task was
dispatched by the CICS dispatcher domain on a CICS X9
mode TCB. When a transaction invokes a C or C++
program that was compiled with the XPLINK option, and
that is defined with EXECKEY= USER, it is allocated and
uses a CICS X9 mode TCB. From X9CPUT.
X9CPUT_COUNT
FLOAT
Number of times the user task was dispatched by the
CICS dispatcher domain on a CICS X9 mode TCB. This
field is related to XPlink support. From X9CPUT.
XPTCBS_WAIT_SEC
FLOAT
The elapsed time, in seconds, in which the user task
waited to obtain a CICS XP TCB (C8 or X9 mode),
because the CICS system had reached the limit set by the
system parameter MAXXPTCBS. From MAXXTDLY.
CICSBTS_T_TRAN_T
This table provides statistics on CICS transactions. It contains information from
CICS performance class monitoring records for CICS/TS (SMF 110, subtype 1)
related to the business transaction service (BTS).
The default retention period for this table is 2 days.
284
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
START_TIMESTAMP
K
TIMESTAMP
Date and time (timestamp) when the transaction was
started. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
ABEND_CODE_CURRENT
CHAR(4)
Current abend code. From ABCODEC (CICS V3) or
ABCODE (CICS V2).
ABEND_CODE_ORIGIN
CHAR(4)
Original (first) abend code. From ABCODEO (CICS V3) or
ABCODE (CICS V2).
LU_NAME
CHAR(8)
VTAM logical unit name (if available) of the terminal
associated with this transaction. From LUNAME.
NET_NAME
CHAR(20)
Network name. This name has two parts, separated by a
period. The first part is VTAMs name for the system
services control point (SSCP). The second part is the task
origin: either the terminal LU name or the generic CICS
LU name. From NETNAME.
OPERATOR_ID
CHAR(3)
Operator identification at task creation. From OPR.
PROGRAM_NAME
CHAR(8)
Name of the first program invoked at attach time. If the
transaction is routed to another system, the name on this
system is DFHCRP. From PGMNAME.
RECORD_TYPE
CHAR(4)
Record type: C for a terminal converse, D for user EMP
DELIVER request, T for a task termination, MT for a
semi-permanent mirror suspend (CICS V3 only), F for a
long-running transaction, and S for a syncpoint. From
RTYPE.
STOP_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when the transaction finished.
From STOP.
TASK_FLAG
CHAR(4)
Task error flags, a string of 31 bits used for signalling
unusual conditions occurring during the transaction.
From TASKFLAG.
TERMINAL_ID
CHAR(4)
Terminal identifier. From TERM.
TRAN_CLASS_NAME
CHAR(8)
Transaction class name at task creation. From
TCLSNAME.
TRANSACTION_NUM
CHAR(5)
Transaction identification number, normally a decimal
number. However, some CICS system tasks are identified
by: III for system initialization, JBS or Jnn for journal
control (nn = journal number 01-99), and TCP for terminal
control. From TRANNUM.
TRANSACTION_PRIO
SMALLINT
Transaction priority at task creation. From TRANPRI.
TRANSACTION_TYPE
CHAR(4)
Transaction start type. From T.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system.
This is a binary value derived from the originating system
clock or, if the originating system is communicating
through a DL/I batch session, a character value
(hhmmss). From first 6 bytes of UOWID.
Chapter 6. Data tables, lookup tables, and control tables
285
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
UOW_PERIOD_COUNT
SMALLINT
Unit of work period count. This may change during the
life of a task as a result of syncpoint activity. From the
last two bytes of UOWID.
USER_ID
CHAR(8)
User ID at task creation. This can also be the remote user
ID for a task created as the result of receiving an
ATTACH request across an MRO or APPC link with
attach-time security. From USERID.
Remaining fields
See “Common fields for the business transaction service
(BTS)” on page 89.
CICSCHN_T_TRAN_T
This table provides statistics on CICS transactions. It contains information from
CICS performance class monitoring records for CICS/TS (SMF 110, subtype 1)
related to the use of channels and containers for data transfer between programs.
The default retention period for this table is 2 days.
Column name
Data type
Description
START_TIMESTAMP
K
TIMESTAMP
Date and time (timestamp) when the transaction was
started. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
ABEND_CODE_CURRENT
CHAR(4)
Current abend code. From ABCODEC.
ABEND_CODE_ORIGIN
CHAR(4)
Original (first) abend ode. From ABCODEO.
LU_NAME
CHAR(8)
VTAM logical unit name (if available) of the terminal
associated with this transaction. From LUNAME.
NET_NAME
CHAR(20)
Network name. This name has two parts, separated by a
period. The first part is VTAMs name for the system
services control point (SSCP). The second part is the task
origin: either the terminal LU name or the generic CICS
LU name. From NETNAME.
OPERATOR_ID
CHAR(3)
Operator identification at task creation. From OPR.
PROGRAM_NAME
CHAR(8)
Name of the first program invoked at attach time. If the
transaction is routed to another system, the name on this
system is DFHCRP. From PGMNAME.
RECORD_TYPE
CHAR(4)
Record type: C for a terminal converse, D for user EMP
DELIVER request, T for a task termination, MT for a
semi-permanent mirror suspend (CICS V3 only), F for a
long-running transaction and S for a syncpoint. From
RTYPE.
STOP_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when the transaction finished.
From STOP.
TASK_FLAG
CHAR(4)
Task error flags, a string of 31 bits used for signalling
unusual conditions occurring during the transaction.
From TASKFLAG.
286
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
TERMINAL_ID
CHAR(4)
Terminal identifier. From TERM.
TRAN_CLASS_NAME
CHAR(8)
Transaction class name at task creation. From
TCLSNAME.
TRANSACTION_NUM
CHAR(5)
Transaction identification number, normally a decimal
number. However, some CICS system tasks are identified
by: III for system initialisation, JBS or Jnn for journal
control (nn = journal number 01-99), and TCP for terminal
control. From TRANNUM.
TRANSACTION_PRIO
SMALLINT
Transaction priority at task creation. From TRANPRI.
TRANSACTION_TYPE
CHAR(4)
Transaction start type. From T.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system.
This is a binary value derived from the originating system
clock or, if the originating system is communicating
through a DL/I batch session, a character value
(hhmmss). From first 6 bytes of UOWID.
UOW_PERIOD_COUNT
SMALLINT
Unit of work period count. It may change during the life
of a task as a result of syncpoint activity. From the last
two bytes of UOWID.
USER_ID
CHAR(8)
User ID at task creation. This can also be the remote user
ID for a task created as the result of receiving an
ATTACH request across an MRO or APPC link with
attach-time security. From USERID.
START_CHAN_LREQS
FLOAT
Total number of local interval control START requests,
with the CHANNEL option, issued by the user task. From
ICSTACCT.
LREQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all
the locally-executed START CHANNEL requests issued
by the user task. This total includes the length of any
headers to the data. From ICSTACDL.
START_CHAN_RREQS
FLOAT
Total number of interval control START CHANNEL
requests, to be executed on remote systems, issued by the
user task. From ICSTRCCT.
RREQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all
the remotely-executed START CHANNEL requests issued
by the user task. This total includes the length of any
headers to the data. From ICSTRCDL.
DPL_REQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all
the distributed program link (DPL) requests, with the
CHANNEL option, issued by the user task. This total
includes the length of any headers to the data. From
PCDLCSDL.
DPLRET_REQS_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all
DPL RETURN CHANNEL commands issued by the user
task. This total includes the length of any headers to the
data. From PCDLCRDL.
LINK_CHAN_REQS
FLOAT
Number of local program LINK requests, with the
CHANNEL option, issued by the user task. From
PCLNKCCT.
XCTL_CHAN_REQS
FLOAT
Number of program XCTL requests issued with the
CHANNEL option by the user task. From PCXCLCCT.
Chapter 6. Data tables, lookup tables, and control tables
287
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
DPL_CHAN_REQS
FLOAT
Number of program distributed program link (DPL)
requests issued with the CHANNEL option by the user
task. From PCDPLCCT.
RET_CHAN_REQS
FLOAT
Number of remote pseudoconversational RETURN
requests, with the CHANNEL option, issued by the user
task. From PCRTNCCT.
RET_CHAN_BYTES
FLOAT
Total length, in bytes, of the data in the containers of all
the remote pseudoconversational RETURN CHANNEL
commands issued by the user task. This total includes the
length of any headers to the data. From PCRTNCDL.
CHAN_CONTAIN_REQS
FLOAT
Number of CICS requests for channel containers issued
by the user task. From PGTOTCCT.
CHAN_BRWCONT_REQS
FLOAT
Number of CICS browse requests for channel containers
issued by the user task. From PGBRWCCT.
CHAN_GETCONT_REQS
FLOAT
Number of GET CONTAINER requests for channel
containers issued by the user task. From PGGETCCT.
CHAN_PUTCONT_REQS
FLOAT
Number of PUT CONTAINER requests for channel
containers issued by the user task. From PGPUTCCT.
CHAN_MOVCONT_REQS
FLOAT
Number of MOVE CONTAINER requests for channel
containers issued by the user task. From PGMOVCCT.
CHAN_GETCONT_BYTES
FLOAT
The total length, in bytes, of the data in the containers of
all the GET CONTAINER CHANNEL commands issued
by the user task. From PGGETCDL.
CHAN_PUTCONT_BYTES
FLOAT
The total length, in bytes, of the data in the containers of
all the PUT CONTAINER CHANNEL commands issued
by the user task. From PGPUTCDL.
CHAN_MOVEPUT_CONT
FLOAT
The number of containers created by MOVE and PUT
CONTAINER requests for channel containers issued by
the user task. From PGCRECCT.
CICSDOC_T_TRAN_T
This table provides statistics on CICS transactions. It contains information from
CICS performance class monitoring records for CICS/TS (SMF 110, subtype 1)
related to the document handler.
The default retention period for this table is 2 days.
Column name
Data type
Description
START_TIMESTAMP
K
TIMESTAMP
Date and time (timestamp) when the transaction was
started. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
CHAR(4)
Current abend code. From ABCODEC (CICS V3) or
ABCODE (CICS V2).
ABEND_CODE_CURRENT
288
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
ABEND_CODE_ORIGIN
CHAR(4)
Original (first) abend code. From ABCODEO (CICS V3) or
ABCODE (CICS V2).
LU_NAME
CHAR(8)
VTAM logical unit name (if available) of the terminal
associated with this transaction. From LUNAME.
NET_NAME
CHAR(20)
Network name. This name has two parts, separated by a
period. The first part is VTAMs name for the system
services control point (SSCP). The second part is the task
origin: either the terminal LU name or the generic CICS
LU name. From NETNAME.
OPERATOR_ID
CHAR(3)
Operator identification at task creation. From OPR.
PROGRAM_NAME
CHAR(8)
Name of the first program invoked at attach time. If the
transaction is routed to another system, the name on this
system is DFHCRP. From PGMNAME.
RECORD_TYPE
CHAR(4)
Record type: C for a terminal converse, D for user EMP
DELIVER request, T for a task termination, MT for a
semi-permanent mirror suspend (CICS V3 only), F for a
long-running transaction and S for a syncpoint. From
RTYPE.
STOP_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when the transaction finished.
From STOP.
TASK_FLAG
CHAR(4)
Task error flags, a string of 31 bits used for signalling
unusual conditions occurring during the transaction.
From TASKFLAG.
TERMINAL_ID
CHAR(4)
Terminal identifier. From TERM.
TRAN_CLASS_NAME
CHAR(8)
Transaction class name at task creation. From
TCLSNAME.
TRANSACTION_NUM
CHAR(5)
Transaction identification number, normally a decimal
number. However, some CICS system tasks are identified
by: III for system initialization, JBS or Jnn for journal
control (nn = journal number 01-99), and TCP for terminal
control. From TRANNUM.
TRANSACTION_PRIO
SMALLINT
Transaction priority at task creation. From TRANPRI.
TRANSACTION_TYPE
CHAR(4)
Transaction start type. From T.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system.
This is a binary value derived from the originating system
clock or, if the originating system is communicating
through a DL/I batch session, a character value
(hhmmss). From first 6 bytes of UOWID.
UOW_PERIOD_COUNT
SMALLINT
Unit of work period count. This may change during the
life of a task as a result of syncpoint activity. From the
last two bytes of UOWID.
USER_ID
CHAR(8)
User ID at task creation. This can also be the remote user
ID for a task created as the result of receiving an
ATTACH request across an MRO or APPC link with
attach-time security. From USERID.
Remaining fields
See “Common fields for the document handler (DOC)” on
page 92.
Chapter 6. Data tables, lookup tables, and control tables
289
CICS transaction and UOW analysis component data tables
CICSWEB_T_TRAN_T
This table provides statistics on CICS transactions. It contains information from
CICS performance class monitoring records for CICS/TS (SMF 110, subtype 1)
related to the Web interface activity.
The default retention period for this table is 2 days.
Column name
Data type
Description
START_TIMESTAMP
K
TIMESTAMP
Date and time (timestamp) when the transaction was
started. From START.
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From
SMFMNSID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID
that is used when requesting a session with this CICS
system. From SMFMNPRN.
TRANSACTION_ID
K
CHAR(4)
Transaction identifier. From TRAN.
ABEND_CODE_CURRENT
CHAR(4)
Current abend code. From ABCODEC (CICS V3) or
ABCODE (CICS V2).
ABEND_CODE_ORIGIN
CHAR(4)
Original (first) abend code. From ABCODEO (CICS V3) or
ABCODE (CICS V2).
BEANTOT_REQ_NUM
FLOAT
The total of beans occurred. From EJBTOTCT.
LU_NAME
CHAR(8)
VTAM logical unit name (if available) of the terminal
associated with this transaction. From LUNAME.
NET_NAME
CHAR(20)
Network name. This name has two parts, separated by a
period. The first part is VTAMs name for the system
services control point (SSCP). The second part is the task
origin: either the terminal LU name or the generic CICS
LU name. From NETNAME.
OPERATOR_ID
CHAR(3)
Operator identification at task creation. From OPR.
PROGRAM_NAME
CHAR(8)
Name of the first program invoked at attach time. If the
transaction is routed to another system, the name on this
system is DFHCRP. From PGMNAME.
RECORD_TYPE
CHAR(4)
Record type: C for a terminal converse, D for user EMP
DELIVER request, T for a task termination, MT for a
semi-permanent mirror suspend (CICS V3 only), F for a
long-running transaction and S for a syncpoint. From
RTYPE.
STOP_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when the transaction finished.
From STOP.
TASK_FLAG
CHAR(4)
Task error flags, a string of 31 bits used for signalling
unusual conditions occurring during the transaction.
From TASKFLAG.
TERMINAL_ID
CHAR(4)
Terminal identifier. From TERM.
TRAN_CLASS_NAME
CHAR(8)
Transaction class name at task creation. From
TCLSNAME.
TRANSACTION_NUM
CHAR(5)
Transaction identification number, normally a decimal
number. However, some CICS system tasks are identified
by: III for system initialization, JBS or Jnn for journal
control (nn = journal number 01-99), and TCP for terminal
control. From TRANNUM.
TRANSACTION_PRIO
SMALLINT
Transaction priority at task creation. From TRANPRI.
290
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
TRANSACTION_TYPE
CHAR(4)
Transaction start type. From T.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system.
This is a binary value derived from the originating system
clock or, if the originating system is communicating
through a DL/I batch session, a character value
(hhmmss). From first 6 bytes of UOWID.
UOW_PERIOD_COUNT
SMALLINT
Unit of work period count. It may change during the life
of a task as a result of syncpoint activity. From the last
two bytes of UOWID.
USER_ID
CHAR(8)
User ID at task creation. This can also be the remote user
ID for a task created as the result of receiving an
ATTACH request across an MRO or APPC link with
attach-time security. From USERID.
Remaining fields
See “Common fields for the Web interface (WEB)” on
page 92.
CICS_T_UOW_TV1
This is a work view used by CICS Transaction and UOW Analysis Reports. It lists
UOW response times by unit of work ID. It is based on the CICS_T_TRAN_T table.
Column name
Data type
Description
NET_NAME
CHAR(20)
This name has two parts, separated by a period. The first
part is VTAMs name for the system services control point
(SSCP). The second part is the task origin: either the
terminal LU name or the generic CICS LU name. From
NET_NAME.
RESPONSE_TIME_SEC
DECIMAL(20, 6)
Response time, in seconds, for this unit of work. This
includes time for long running mirror tasks thus making
this response time unreliable. See RESPONSE_TIME_SEC
for CICS_T_UOW_TV2. Calculated as
MAX(STOP_TIMESTAMP) - MIN(START_TIMESTAMP).
START_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when this unit of work was
started. This (erroneously) includes long running mirror
tasks. See START_TIMESTAMP for CICS_T_UOW_TV2.
From START_TIMESTAMP.
TRAN_COUNT
INTEGER
Number of transactions in this unit of work. Calculated as
number of rows in CICS_T_TRAN_T with identical
UNIT_OF_WORK_ID.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system. It
is a binary value derived from the originating system clock
or a character value (hhmmss), if the originating system is
communicating through a DL/I batch session. From
UNIT_OF_WORK_ID.
CICS_T_UOW_TV2
This is a work view used by CICS Transaction and UOW Analysis Reports. It lists
UOW response times by unit of work ID. Long running mirror tasks are excluded.
It is based on the CICS_T_TRAN_T table.
Chapter 6. Data tables, lookup tables, and control tables
291
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
NET_NAME
CHAR(20)
This name has two parts, separated by a period. The first
part is VTAMs name for the system services control point
(SSCP). The second part is the task origin: either the
terminal LU name or the generic CICS LU name. From
NET_NAME.
RESPONSE_TIME_SEC
DECIMAL(20, 6)
Response time, in seconds, for this unit of work.
Calculated as MAX(STOP_TIMESTAMP) MIN(START_TIMESTAMP). Long running mirror tasks
(DFHMIR based transactions) are excluded.
START_TIMESTAMP
TIMESTAMP
Date and time (timestamp) when this unit of work was
started. Long running mirror tasks are excluded since they
can corrupt the unit of work start time. From
START_TIMESTAMP.
TRAN_COUNT
INTEGER
Number of transactions in this unit of work. Calculated as
number of rows in CICS_T_TRAN_T with identical
UNIT_OF_WORK_ID.
UNIT_OF_WORK_ID
CHAR(12)
Unit of work ID as known within the originating system. It
is a binary value derived from the originating system clock
or a character value (hhmmss), if the originating system is
communicating through a DL/I batch session. From
UNIT_OF_WORK_ID.
CICS_WMQ_CONN_D
This table provides daily Websphere MQ connection statistics from CICS TS 3.2
(SMF 110, subtype 2). This maps the CICS DFHMQGDS macro.
The default retention period for this table is 30 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statistics record was written to SMF. From
SMFSTDTE
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
MQ_QMANAGER_NAME
K
CHAR(4)
Queue manager name. From MQG_Qmgr_name.
MQ_INIT_QUEUE
CHAR(48)
Initiation queue name. From MQG_Init_queue.
MQ_CONN_STAT
CHAR(1)
Connection status. C for Connected. N for Not connected.
MQ_RELEASE
CHAR(4)
Release of MQ vvrr. From MQG_MQ_Release.
MQ_CURR_TASKS
INTEGER
Number of current tasks. From MQG_TTasks.
MQ_FUTILE_ATT
INTEGER
Number of futile attempts. From MQG_TFutileAtt.
MQ_API_CALLS
INTEGER
Total number of calls. From MQG_TApi.
MQ_API_CALLS_OK
INTEGER
Total number of calls compok. From MQG_TApiOk.
MQ_TOT_FLOWS
INTEGER
Total number of flows. From MQG_TCall.
MQ_CALL_SYNC_COMP
INTEGER
Total number of calls compsync. From MQG_TCallSyncComp
292
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
MQ_CALL_REQ_IO
INTEGER
Total number of calls completed synchronously. From
MQG_TCallIO.
MQ_REAL_GETWAIT
INTEGER
Total number of real GETWAIT. From MQG_TWaitMsg.
MQ_CALL_SWITCHED
INTEGER
Total number of calls switched. From MQG_TSubtasked.
MQ_TOTAL_OPEN
INTEGER
Total number of OPEN. From MQG_TOPEN.
MQ_TOTAL_CLOSE
INTEGER
Total number of CLOSE. From MQG_TCLOSE.
MQ_TOTAL_GET
INTEGER
Total number of GET. From MQG_TGET.
MQ_TOTAL_GETWAIT
INTEGER
Total number of GETWAIT. From MQG_TGETWAIT.
MQ_TOTAL_PUT
INTEGER
Total number of PUT. From MQG_TPUT.
MQ_TOTAL_PUT1
INTEGER
Total number of PUT1. From MQG_TPUT1.
MQ_TOTAL_INQ
INTEGER
Total number of INQ. From MQG_TINQ.
MQ_TOTAL_SET
INTEGER
Total number of SET. From MQG_TSET.
MQ_INDOUBT_UOW
INTEGER
Count of indoubt units of work. From MQG_IndoubtUOW.
MQ_UNRES_UOW
INTEGER
Count of unresolved units of work. From
MQG_UnResolvedUOW.
MQ_RES_COMMIT
INTEGER
Count of resolved committed UOWs. From
MQG_ResolveComm.
MQ_RES_BACKOUT
INTEGER
Count of resolved backout UOWs. From MQG_ResolveBack.
MQ_TOT_BACK_UOW
INTEGER
Total number of backout UOWs. From MQG_TBackUOW.
MQ_TOT_COMM_UOW
INTEGER
Total number of committed UOWs. From MQG_TCommUOW.
MQ_TOT_TASKS
INTEGER
Total number of tasks. From MQG_TTaskend.
MQ_1PHASE_COMM
INTEGER
Total number of Single Phase Commits. From MQG_TSPComm.
MQ_2PHASE_COMM
INTEGER
Total number of 2 Phase Commits. From MQG_T2PComm.
CICS_WMQ_CONN_H
This table provides hourly Websphere MQ connection statistics from CICS TS 3.2
(SMF 110, subtype 2). This maps the CICS DFHMQGDS macro.
The default retention period for this table is 7 days.
Column name
Data type
Description
DATE
K
DATE
Date when the statisticsecord was written to SMF.rom
SMFSTDTE
TIME
K
TIME
Time when the statistics record was written to SMF. From
SMFSTTME
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID. From SMFSTSID
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic APPLID. This is the VTAM application ID used
when requesting a session with this CICS system. From
SMFSTPRN
PERIOD_NAME
K
CHAR(8)
Name of the period. This is derived using fields SMFSTSID,
SMFSTDTE, and SMFSTTME from the record as parameters in
the PERIOD function
MQ_QMANAGER_NAME
K
CHAR(4)
Queue manager name. From MQG_Qmgr_name.
MQ_INIT_QUEUE
CHAR(48)
Initiation queue name. From MQG_Init_queue.
MQ_CONN_STAT
CHAR(1)
Connection status. C for Connected. N for Not connected.
Chapter 6. Data tables, lookup tables, and control tables
293
CICS transaction and UOW analysis component data tables
Column name
Data type
Description
MQ_RELEASE
CHAR(4)
Release of MQ vvrr. From MQG_MQ_Release.
MQ_CURR_TASKS
INTEGER
Number of current tasks. From MQG_TTasks.
MQ_FUTILE_ATT
INTEGER
Number of futile attempts. From MQG_TFutileAtt.
MQ_API_CALLS
INTEGER
Total number of calls.From MQG_TApi.
MQ_API_CALLS_OK
INTEGER
Total number of calls compok. From MQG_TApiOk.
MQ_TOT_FLOWS
INTEGER
Total number of flows. From MQG_TCall.
MQ_CALL_SYNC_COMP
INTEGER
Total number of calls compsync. From MQG_TCallSyncComp
MQ_CALL_REQ_IO
INTEGER
Total number of calls need I/O. From MQG_TCallIO.
MQ_REAL_GETWAIT
INTEGER
Total number of real GETWAIT. From MQG_TWaitMsg.
MQ_CALL_SWITCHED
INTEGER
Total number of calls switched. From MQG_TSubtasked.
MQ_TOTAL_OPEN
INTEGER
Total number of OPEN. From MQG_TOPEN.
MQ_TOTAL_CLOSE
INTEGER
Total number of CLOSE. From MQG_TCLOSE.
MQ_TOTAL_GET
INTEGER
Total number of GET. From MQG_TGET.
MQ_TOTAL_GETWAIT
INTEGER
Total number of GETWAIT. From MQG_TGETWAIT.
MQ_TOTAL_PUT
INTEGER
Total number of PUT. From MQG_TPUT.
MQ_TOTAL_PUT1
INTEGER
Total number of PUT1. From MQG_TPUT1.
MQ_TOTAL_INQ
INTEGER
Total number of INQ. From MQG_TINQ.
MQ_TOTAL_SET
INTEGER
Total number of SET. From MQG_TSET.
MQ_INDOUBT_UOW
INTEGER
Count of indoubt units of work. From MQG_IndoubtUOW.
MQ_UNRES_UOW
INTEGER
Count of unresolved units of work. From
MQG_UnResolvedUOW.
MQ_RES_COMMIT
INTEGER
Count of resolved committed UOWs. From
MQG_ResolveComm.
MQ_RES_BACKOUT
INTEGER
Count of resolved backout UOWs. From MQG_ResolveBack.
MQ_TOT_BACK_UOW
INTEGER
Total number of backout UOWs. From MQG_TBackUOW.
MQ_TOT_COMM_UOW
INTEGER
Total number of committed UOWs. From MQG_TCommUOW.
MQ_TOT_TASKS
INTEGER
Total number of tasks. From MQG_TTaskend.
MQ_1PHASE_COMM
INTEGER
Total number of Single Phase Commits. From MQG_TSPComm.
MQ_2PHASE_COMM
INTEGER
Total number of 2 Phase Commits. From MQG_T2PComm.
Lookup tables
This section describes the lookup tables specific to the CICS Performance feature.
For descriptions of common lookup tables used by the CICS Performance feature
and other Tivoli Decision Support for z/OS features, refer to the Administration
Guide and Reference.
Note: To obtain local time, Tivoli Decision Support for z/OS uses the timestamp in
the SMF header.
CICS_AVAIL_RES
This lookup table defines which CICS resources are used for tracking availability. It
also contains the schedule names and availability objectives to use for the different
resources.
294
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Lookup tables
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID that the resource is associated with. It can
contain global search characters.
CICS_SYSTEM_ID
K
CHAR(8)
The CICS subsystem ID that the resource is associated with.
It can contain global search characters.
RESOURCE_SOURCE_NM
K
CHAR(8)
Resource Source Name. It specifies the resource you want
to monitor. It can contain global search characters. When
tracking the CICS subsystem itself, this field must be equal
to the CICS_SYSTEM_ID.
RESOURCE_TYPE
K
CHAR(8)
Resource Type: CICSSYS (CICS system), DB2CONN
(DB2CONN resource).
AVAIL_OBJ_PCT
DECIMAL(4, 1)
Availability objective for the resource, in percent.
RESOURCE_TARGET_NM
CHAR(18)
Resource Target Name. It is the final name that will be
associated with the resource. If nothing is specified
$UNKNOWN is used as default.
RESOURCE_CHKPOINT
INTEGER
Resource checkpoint interval in seconds.
SCHEDULE_NAME
CHAR(8)
Schedule name to use for the resource. If nothing is
specified STANDARD is used as default.
Example of table contents
MVS
SYSTEM
ID
------%
%
%
CICS
SYSTEM
ID
------%
%
%
RESOURCE
SOURCE
NM
--------CICS3T8X
CICS3TTS
DB23T8X
RESOURCE
TYPE
--------CICSSYS
CICSSYS
DB2CONN
RESOURCE
AVAIL
TARGET
RESOURCE SCHEDULE
OBJ
NM
CHKPOINT
NAME
PCT
--------- --------- --------- ------3600
STANDARD
95.0
--3600
STANDARD
95.0
MPP
3600
STANDARD
95.0
The RESOURCE CHKPOINT corresponds to the STATSINTERVAL system
initialization parameter in CICS which defines the interval for CICS statistics. Refer
to CICS System Definition Guide and CICS Customization Guide for further details.
CICS_LOOKUP_APPL
This lookup table converts CICS transaction IDs to application names. It contains
response-time boundaries for applications and transactions. The Tivoli Decision
Support for z/OS administrator maintains this table through the administration
dialog.
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used
when requesting a session with this CICS system.
APPLICATION_NAME
K
CHAR(18)
Application name.
TRANSACTION_ID
K
CHAR(4)
Transaction ID.
APPL_RESP_BND1_SEC
FLOAT
First application response-time boundary, in seconds. The default
is 1 second. This can be used for counting transactions in each
response time range.
APPL_RESP_BND2_SEC
FLOAT
Second application response-time boundary, in seconds. The
default is 2 seconds. This can be used for counting transactions
in each response time range.
Chapter 6. Data tables, lookup tables, and control tables
295
Lookup tables
Column name
Data type
Description
APPL_RESP_BND3_SEC
FLOAT
Third application response-time boundary, in seconds. The
default is 5 seconds. This can be used for counting transactions
in each response time range.
APPL_RESP_BND4_SEC
FLOAT
Fourth application response-time boundary, in seconds. The
default is 10 seconds. This can be used for counting transactions
in each response time range.
TRAN_RESP_BND1_SEC
FLOAT
First transaction response-time boundary, in seconds. The default
is 1 second. This can be used for counting transactions in each
response time range.
TRAN_RESP_BND2_SEC
FLOAT
Second transaction response-time boundary, in seconds. The
default is 2 seconds. This can be used for counting transactions
in each response time range.
TRAN_RESP_BND3_SEC
FLOAT
Third transaction response-time boundary, in seconds. The
default is 5 seconds. This can be used for counting transactions
in each response time range.
TRAN_RESP_BND4_SEC
FLOAT
Fourth transaction response-time boundary, in seconds. The
default is 10 seconds. This can be used for counting transactions
in each response time range.
CICS_LOOKUP_SYSTEM
This lookup table converts the CICS generic application ID to a CICS group
(CICSPlex) name. The Tivoli Decision Support for z/OS administrator maintains
this table through the administration dialog.
Column name
Data type
Description
MVS_SYSTEM_ID
K
CHAR(4)
MVS system ID. This is the SMF system ID.
CICSPLEX_ID
K
CHAR(18)
CICS group name. This is your name for a group of related CICS
regions. For example, you can call all the production terminal-owning
and application-owning regions PRODCICS, even though they have
different VTAM names.
CICS_SYSTEM_ID
K
CHAR(8)
CICS generic ID. This is the VTAM application ID that is used when
requesting a session with this CICS system.
CICS_OMEG_FIELD
This lookup table is used in the File and Database Detailed usage subcomponent.
When this subcomponent collects data to its CICS_O_FL_DTL_* tables, it uses this
lookup table to determine the value of column FILE_DB_ACTION.
Column name
Data type
Description
FILE_DB_TYPE
K
CHAR(10)
File or Database Type.
FILE_DB_SUBTYPE
K
CHAR(6)
File or database subtype.
FILE_DTL_FLD_NO
K
SMALLINT(4) Occurrence of clock and count fields in SMF112 subtype 203 record.
FILE_DB_ACTION
CHAR(3)
File or database action in target table – CICS_O_FL_DTL_H.
When the File and Database Detailed usage subcomponent is installed, the
following rows are inserted into this lookup table:
296
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Lookup tables
FILE_DB_TYPE
FILE_DB_SUBTYPE
FILE_DTL_FLD_NO
FILE_DB_ACTION
VSAM
N/A
1
REA
VSAM
N/A
2
WRI
VSAM
N/A
3
UPD
VSAM
N/A
4
DEL
VSAM
N/A
5
BRO
VSAM
N/A
6
MIS
DLI
PSB
1
SCH
DLI
PSB
2
TER
DLI
PSB
3
GU
DLI
PSB
4
GN
DLI
PSB
5
GNP
DLI
PSB
6
GHU
DLI
PSB
7
GHN
DLI
PSB
8
GHP
DLI
PSB
9
INS
DLI
PSB
10
DEL
DLI
PSB
11
REP
DLI
DBD
1
SCH
DLI
DBD
2
TER
DLI
DBD
3
GU
DLI
DBD
4
GN
DLI
DBD
5
GNP
DLI
DBD
7
GHN
DLI
DBD
8
GHP
DLI
DBD
9
INS
DLI
DBD
10
DEL
DLI
DBD
11
REP
IDMS
RECORD
1
BIN
IDMS
RECORD
2
GFO
IDMS
RECORD
3
AR
IDMS
RECORD
4
KEE
IDMS
RECORD
5
STO
IDMS
RECORD
6
MOD
IDMS
RECORD
7
ERP
IDMS
RECORD
8
ERS
IDMS
RECORD
9
ERA
IDMS
RECORD
10
ERU
IDMS
RECORD
11
CON
IDMS
AREA
1
GFO
IDMS
AREA
2
AR
IDMS
AREA
3
KEE
Chapter 6. Data tables, lookup tables, and control tables
297
Lookup tables
FILE_DB_TYPE
FILE_DB_SUBTYPE
FILE_DTL_FLD_NO
FILE_DB_ACTION
IDMS
AREA
4
REA
IDMS
SET
1
GFO
IDMS
SET
2
AR
IDMS
SET
3
KEE
IDMS
SET
4
IFS
IDMS
NONAME
1
GFO
IDMS
NONAME
2
AR
IDMS
NONAME
3
KEE
ADABAS
N/A
1
ISN
ADABAS
N/A
2
SEA
ADABAS
N/A
3
RRE
ADABAS
N/A
4
RFI
ADABAS
N/A
5
RDE
ADABAS
N/A
6
HOL
ADABAS
N/A
7
ADD
ADABAS
N/A
8
UPD
ADABAS
N/A
9
DEL
ADABAS
N/A
10
REL
SUPRA
N/A
1
ADD
SUPRA
N/A
2
DEL
SUPRA
N/A
3
FIN
SUPRA
N/A
4
REA
SUPRA
N/A
4
WRI
DATACOM
N/A
1
ADD
DATACOM
N/A
2
CNT
DATACOM
N/A
3
DEL
DATACOM
N/A
4
GN
DATACOM
N/A
5
GS
DATACOM
N/A
6
LSP
DATACOM
N/A
7
REA
DATACOM
N/A
8
REL
DATACOM
N/A
9
SEL
DATACOM
N/A
10
SSE
DATACOM
N/A
11
UPD
MQ
N/A
1
OPN
MQ
N/A
2
CLO
MQ
N/A
3
GET
MQ
N/A
4
PUT
MQ
N/A
5
PU1
MQ
N/A
6
INQ
MQ
N/A
7
SET
298
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Lookup tables
FILE_DB_TYPE
FILE_DB_SUBTYPE
FILE_DTL_FLD_NO
FILE_DB_ACTION
MQ
N/A
8
MIS
USEREVT
N/A
1
F1
USEREVT
N/A
2
F2
USEREVT
N/A
3
F3
USEREVT
N/A
4
F4
USEREVT
N/A
5
F5
USEREVT
N/A
6
F6
USEREVT
N/A
7
F7
USEREVT
N/A
8
F8
USEREVT
N/A
9
F9
USEREVT
N/A
10
F10
CICS_TIMEZONES
This lookup table associates a relative number with each MVS_SYSTEM_ID. This
number represents the hour difference (negative or positive) with respect to GMT.
The Tivoli Decision Support for z/OS administrator maintains this table through
the administration dialog.
Column name
MVS_SYSTEM_ID
K
TIMEOFF
Data type
Description
CHAR(4)
MVS system ID. This is the SMF system ID.
INTEGER
Local time offset with respect to GMT.
Control tables
Tivoli Decision Support for z/OS creates and loads control tables during its
installation; these tables control the results returned by the log collector. This
section describes the CICS control tables, CICS_DICTIONARY and CICS_FIELD,
used by the DRL2CICS record procedure in its handling of CICS monitoring
records.
CICS_DICTIONARY
The CICS_DICTIONARY control table provides CICS dictionary records. As
described in Chapter 5, “Data flow and Tivoli Decision Support for z/OS objects,”
on page 55, the record procedure that handles CICS monitoring records
(DRL2CICS) uses and maintains this table. It contains information about the last
CICS dictionary record found for each combination of MVS_SYSTEM_ID,
CICS_SYSTEM_ID, CLASS, and VERSION.
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).
CICS_VER
K
CHAR(4)
CICS Version and Release that created this dictionary (from the field
SMFMNRVN). Ex.0410.
Chapter 6. Data tables, lookup tables, and control tables
299
Control 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), 3 for CICS/ESA Version 3, and so on. Set by
DRL2CICS based on SMFMNSTY (V3 and later) 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
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
As described in Chapter 5, “Data flow and Tivoli Decision Support for z/OS
objects,” on page 55, the CICS_FIELD control table provides CICS dictionary fields.
It updates the dictionary blocks in DRL2CICS with field length and field offset,
which are used to build the output record.
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)
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
Field length that will be used to build the output record.
OUTPUT_OFFSET
INTEGER
Field offset that will be used to build the output record. This offset
should match the SMF_CICS_T, _G, _A, _E2 record definitions.
300
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Chapter 7. Reports
The reporting function produces reports based on the data in the Tivoli Decision
Support for z/OS database. Reports can show data from tables or from views. You
can request reports online or by submitting batch jobs. Typically, you use online
reporting for reports that you use once, and batch reporting for regularly required
reports. This chapter contains examples of reports that accompany the CICS
Performance feature.
Report format and general description
Tivoli Decision Support for z/OS presents reports in tables, graphs, or charts. All
reports have the same basic report layout. This section describes the elements that
are common among Tivoli Decision Support for z/OS feature reports:
v Report ID
v Report group
v Source
v Attributes
v Variables
Report ID
Tivoli Decision Support for z/OS assigns each report a unique identifier. The CICS
Performance feature uses this format for report IDs:
CICSyxx
Where:
y
Can be on of the following:
1-7
The number of a CICS monitoring subcomponent
8
The statistics component
9
The transaction and unit-of-work analysis component
xx
Is a sequential number given to the reports in a component or
subcomponent.
Examples:
CICS404
CICS802
Report group
Tivoli Decision Support for z/OS uses several predefined report groups. Typically,
each component has one group, but some components have several groups. Some
groups are shared by many components (for example, management overview
reports, performance reports, problem reports, and exception reports).
All reports supplied with the CICS Performance feature are in the CICS report
group.
Source
Each report contains information from one or more source tables. The report
descriptions in this chapter list source tables. Refer to these source tables if you are
interested in learning where certain data originates.
© Copyright IBM Corp. 1994, 2009
301
Report format and general description
Attributes
Each report has certain attributes associated with it. Use these attributes as
keywords to search for specific reports in the dialogs.
You can specify any number of attributes for a report, but these attributes are
always present for predefined reports:
v The area to which the report belongs (for example, CICS/ESA)
v The task that the report supports:
Performance
Performance control task
Service
Service-level planning task
Capacity
Capacity planning task
Security
Security control task
Configuration
Configuration management discipline
Operation
Operations management discipline
Change
Change management discipline
Problem
Problem management discipline
You can also specify these attributes, when appropriate:
v Resource types, such as storage or CPU
v Performance issues, such as availability or response
v Presentation forms, such as detail, overview, or trend
v Time resolutions, such as hourly, daily, weekly, monthly, or yearly
Variables
Each report has variables associated with it. You specify the values for these
variables when you generate the report using the reporting dialog.
When you specify a date for a monthly report, specify the first day of the month.
When you specify a date for weekly reports, specify the first day (Monday) of the
week. Otherwise, there is no match in the data table.
For reports that specify a range of weeks, the data is taken from the summary
records for all Mondays in the specified date range. For example, if you specify
‘2000-04-21’ (a Friday) to ‘2000-04-28’, one summary row is selected, the one for the
week beginning ‘2000-04-24’. So the report shows summary data for the week
‘2000-04-24’ to ‘2000-04-30’ inclusive.
If a character variable happens to have only numeric characters, enclose it in single
quote marks, otherwise it will not match the data. For example, if you have an
MVS system ID (SMF ID) of 3090™, specify it as ’3090’ on the Variables window.
Reports in the CICS monitoring component
As described in “Evaluating the CICS monitoring component” on page 13, the
CICS monitoring facility provides the performance data for the CICS monitoring
component. It is the only CICS Performance feature component that contains
subcomponents. This section describes the reports for the CICS monitoring
component and indicates which subcomponents must be installed to create them.
CICS Transaction Performance, Detail
Supplied with the CICS basic subcomponent, this report shows details from CMF
performance records.
302
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
For information on how to use this report, see “Monitoring volumes and
throughput” on page 35.
This information identifies the report:
Report ID
CICS101 (CICS101P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_TRANSACTION_D (CICS_TRANSACTIO_DP for CICS
Partitioning feature)
Attributes
CICS, Perform, Transaction, Daily, Detail
Variables
From date, To date, MVS system ID, CICS system ID
CICS Transaction Performance, Detail
MVS ID ='IPO2' CICS ID ='CFGTV1 '
Date: '2000-03-19' to '2000-03-20'
Tran
Tran
ID
count
------------QUIT
7916
CRTE
1760
AP00
1750
PM94
1369
VCS1
737
PM80
666
CESN
618
SU01
487
...
GC11
1
DM08
1
=========
20359
Avg
Avg
resp
CPU
time
time
(sec)
(sec)
--------- -------0.085
0.017
4.847
0.004
0.184
0.036
0.086
0.012
0.073
0.008
1.053
0.155
8.800
0.001
0.441
0.062
0.341
0.028
0.014
0.002
Prog
load
reqs
(avg)
----0
0
0
0
2
1
0
4
1
0
Program
Prog
FC
storage Getmains Getmains
loads calls Excepbytes
< 16 MB > 16 MB
(avg) (avg) tions
(max)
(avg)
(avg)
----- ----- ------ ------------ -------- -------0
18
0
74344
22
0
0
0
0
210176
1
0
0
8
0
309800
66
0
0
6
0
130096
24
0
0
7
0
81200
14
0
0
62
0
104568
583
0
0
0
0
41608
0
0
0
126
0
177536
38
0
0
0
2
0
0
0
37048
5040
============
309800
10
3
0
0
Tivoli Decision Support for z/OS Report: CICS101
Figure 36. Example of a CICS Transaction Performance, Detail report
The report contains this information:
Tran ID
Transaction ID.
Tran count
The SIT (system initialization table) parameter MNCONV=YES is
important for this field, because setting MNCONV=YES causes CMF to
write a monitoring record for each terminal I/O, not just at the end of the
transaction. So, for a MNCONV=YES system, this is not the number of
transactions, but the number of terminal interactions. From RECORDS.
Avg resp time (sec)
Internal response time, which does not include any network time.
Calculated as RESPONSE_SUM_SEC/RECORDS.
Avg CPU time (sec)
Processor time. Calculated as CPU_SUM_SEC/RECORDS.
Prog load reqs (avg)
Average number of program load requests per transaction. Calculated as
PGM_LOAD_REQUESTS/RECORDS.
Prog loads (avg)
Average number of program library fetches per transaction. Calculated as
PGM_LOADS/RECORDS.
Chapter 7. Reports
303
Reports in the CICS monitoring component
FC calls (avg)
Average number of file control requests per transaction. Calculated as
FC_REQUESTS_TOTAL/RECORDS.
Exceptions
Total number of exceptions. If this is not zero, you can get more
information in the CICS Exceptions report.
Program storage bytes (max)
Peak amount of program storage both above and below the 16MB line, in
bytes. This is the maximum of STORAGE_PGM_TOTAL.
Getmains < 16 MB
Average number of user-storage GETMAIN requests below the 16MB line.
Calculated as (GETMAINS_UDSA + GETMAINS_CDSA)/RECORDS.
Getmains > 16 MB
Average number of user-storage GETMAIN requests above the 16MB line.
Calculated as (GETMAINS_EUDSA + GETMAINS_ECDSA)/RECORDS.
CICS Transaction Channel Performance, Detail
Supplied with CICS basic subcomponent, this report shows details from CMF
performance records related to channel mechanism usage for data exchange
between CICS programs.
This information identifies the report:
Report ID
CICS102 (CICS102P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICSCHN_TRANSACT_D, CICS_TRANSACTION_D
(CICSCHN_TRANSAC_DP, CICS_TRANSACTIO_DP for CICS
Partitioning feature)
Attributes
CICS, Perform, Channel, Containers, Transaction, Daily, Detail
Variables
From date, To date, MVS system ID, CICS system ID, Tran ID
CICS Transaction Channel Performance, Detail
MVS System: 'MVSB' CICS system = 'FGAIZ'
Date: '2005-05-01' to '2005-05-03'
Tran
Tran
ID
count
------------QUIT
507
CRTE
120
=========
627
Local
Avg
Avg
Start
resp
CPU
Channel
time
time reqs
(sec)
(sec) (avg)
--------- -------- ----6.964
0.000 0.000
2.439
0.000 0.000
Remote
Start
Channel
reqs
(avg)
----0.000
0.000
Local
Start
Channel
bytes
(avg)
----0.000
0.000
Remote
Start
Channel
bytes
(avg)
-----0.000
0.000
Tivoli Decision Support for z/OS Report: CICS102
Figure 37. Example of a CICS Transaction Channel Performance, Detail report
The report contains this information:
Tran ID
Transaction ID.
Tran count
Number of transactions. The SIT (system initialization table) parameter
304
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
MNCONV=YES is important for this field, because setting MNCONV=YES
causes CMF to write a monitoring record for each terminal I/O, not just at
the end of the transaction. So, for a MNCONV=YES system, this is not the
number of transactions, but the number of terminal interactions. From
RECORDS.
Avg resp time (sec)
Internal response time, which does not include any network time.
Calculated as RESPONSE_SUM_SEC/RECORDS.
Avg CPU time (sec)
Processor time. Calculated as CPU_SUM_SEC/RECORDS.
Local Start Channel reqs (avg)
Average number of local interval control START requests, with CHANNEL
option. Calculated as START_CHAN_LREQS/RECORDS.
Remote Start Channel reqs (avg)
Average number of interval control START CHANNEL requests, to be
executed on remote systems. Calculated as START_CHAN_RREQS/
RECORDS.
Local Start Channel bytes (avg)
Average length in bytes, of the data in the containers of all the
locally-executed START CHANNEL requests issued by the user task.
Calculated as LREQS_BYTES/RECORDS.
Remote Start Channel bytes (avg)
Average length in bytes, of the data in the containers of all the
remotely-executed START CHANNEL requests issued by the user task.
Calculated as RREQS_BYTES/RECORDS.
CICS Application Channel Performance, Detail
Supplied with CICS basic application analysis subcomponent, this report shows
details on channel mechanism usage for data exchange between CICS programs for
selected applications for one day. Before collecting the data for this report, you
must first group transactions by application ID using the CICS_LOOKUP_APPL
lookup table. The columns give the average value for each transaction, but the
value is really the average for each performance record. RECORDS is the number
of performance records collected, and can be higher than the number of
transactions if MNCONV=YES is specified in the SIT, because a performance
record is then written for each terminal interaction.
This information identifies the report:
Report ID
CICS408 (CICS408P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICSCHN_A_BASIC_H, CICS_A_BASIC_H
(CICSCHN_A_BASIC_HP, CICS_A_BASIC_HP for CICS
Partitioning feature)
Attributes
CICS, Perform, Channel, Containers, Transaction, Daily, Detail
Variables
From date, To date, MVS system ID, CICS system ID, Application
name
Chapter 7. Reports
305
Reports in the CICS monitoring component
CICS Transaction Channel Performance, Detail
MVS System: 'MVSB' CICS system = 'FGAIZ'
Date: '2005-05-01' to '2005-05-03'
Avg
resp
Application Tran
time
name
count
(sec)
----------- -------- -------OTHER
507
6.964
SYSTEM
120
2.439
=========
627
Avg
PGM
PGM
CPU
Link
XCTL
time channel channel
(sec) (avg) (avg)
------- ------- -----0.000
0.000 0.000
0.000
0.000 0.000
Local
PGM
SPL
channel
(avg)
----0.000
0.000
Remote
Start
Channel
reqs
(avg)
----0.000
0.000
Local
Start
Channel
reqs
(avg)
----0.000
0.000
Remote
Start
Channel
bytes
(avg)
-----0.000
0.000
Tivoli Decision Support for z/OS Report: CICS408
Figure 38. Example of a CICS Application Channel Performance, Detail report
The report contains this information:
Application name
Application name.
Tran count
Number of transactions. The SIT (system initialization table) parameter
MNCONV=YES is important for this field, because setting MNCONV=YES
causes CMF to write a monitoring record for each terminal I/O, not just at
the end of the transaction. So, for a MNCONV=YES system, this is not the
number of transactions, but the number of terminal interactions. From
RECORDS.
Avg resp time (sec)
Internal response time, which does not include any network time.
Calculated as RESPONSE_SUM_SEC/RECORDS.
Avg CPU time (sec)
Processor time. Calculated as CPU_SUM_SEC/RECORDS.
PGM link channel (avg)
Average number of local program LINK requests, with CHANNEL option.
Calculated as LINK_CHAN_REQS/RECORDS.
PGM XCTL channel (avg)
Average number of program XCTL requests issued with the CHANNEL
option. Calculated as XCTL_CHAN_REQS/RECORDS.
PGM DPL channel (avg)
Average number of program distributed program link (DPL) requests
issued with the CHANNEL option. Calculated as DPL_CHAN_REQS/
RECORDS.
Local Start Channel bytes (avg)
Average length in bytes, of the data in the containers of all the
locally-executed START CHANNEL requests issued by the user task.
Calculated as LREQS_BYTES/RECORDS.
Remote Start Channel bytes (avg)
Average length in bytes, of the data in the containers of all the
remotely-executed START CHANNEL requests issued by the user task.
Calculated as RREQS_BYTES/RECORDS.
306
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
CICS Application Response Times, Overview
Supplied with the basic application analysis subcomponent, this report shows the
average internal response time for selected applications over a specified time
period. For information on how to use this report, see “Monitoring response time”
on page 29.
This information identifies the report:
Report ID
CICS401 (CICS401P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_A_BASIC_H (CICS_A_BASIC_HP for CICS Partitioning
feature)
Attributes
CICS, Perform, Resp, Application, Overview
Variables
From date, To tstem ID, CICS system ID, Period name, Appl name
list
Figure 39. Example of a CICS Application Response Times, Overview report
The report contains this information:
Application name
Application name, as defined in the CICS_LOOKUP_APPL table.
Resp time objective (seconds)
Response time objective is from APPL_RESP_BND1_SEC in the
CICS_LOOKUP_APPL lookup table.
Average resp time (seconds)
Average internal response time, which does not include any network time.
Calculated as RESPONSE_SUM_SEC/RECORDS. RECORDS is the number
of performance records collected, and can be higher than the number of
transactions if MNCONV=YES is specified in the SIT, because a
performance record is then written for each terminal interaction.
Chapter 7. Reports
307
Reports in the CICS monitoring component
CICS Application Response Times, Trend
Supplied with the basic application analysis subcomponent, this report shows the
trend in internal response times for selected applications at weekly intervals.
Before collecting the data for this report, you must first group transactions by
application ID using the CICS_LOOKUP_APPL lookup table. For information on
how to use this report, see “Monitoring response time” on page 29.
This information identifies the report:
Report ID
CICS402 (CICS402P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_A_BASIC_W (CICS_A_BASIC_WP for CICS Partitioning
feature)
Attributes
CICS, Perform, Resp, Application, Weekly, Trend
Variables
From date, To date, MVS system ID, CICS system ID, Appl name
list
x
x
x
x
+
+
+
+
+
+
x
Figure 40. Example of a CICS Application Response Times, Trend report
The report contains this information:
Week start date
There is a bar for each week in the selected range of dates.
Application name
Application name, as defined in the CICS_LOOKUP_APPL table.
Average seconds
Average internal response time, which does not include any network time.
Calculated as RESPONSE_SUM_SEC/RECORDS. RECORDS is the number
of performance records collected, and can be higher than the number of
transactions if MNCONV=YES is specified in the SIT, because a
performance record is then written for each terminal interaction.
308
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
CICS Application Response Times, Detail
Supplied with the basic application analysis subcomponent, this report shows
detailed CMF data for selected applications for one day. Before collecting the data
for this report, you must first group transactions by application ID using the
CICS_LOOKUP_APPL lookup table.
The columns give the average value for each transaction, but the value is really the
average for each performance record. RECORDS is the number of performance
records collected, and can be higher than the number of transactions if
MNCONV=YES is specified in the SIT, because a performance record is then
written for each terminal interaction.
For information on how to use this report, see “Monitoring response time” on page
29.
This information identifies the report:
Report ID
CICS403 (CICS403P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_A_BASIC_H (CICS_A_BASIC_HP for CICS Partitioning
feature)
Attributes
CICS, Perform, Resp, Application, Daily, Detail
Variables
Date, MVS system ID, CICS system ID
CICS Application Response Times, Detail
MVS system ='MVSB' CICS system ='FGAIZ'
Date: 2000-05-10
Average Average Average
Average Average Average disp re-disp SSL-TCB XP-TCB
Application Tran elapsed
CPU
disp
wait
wait
wait
wait
name
count (sec)
(sec)
(sec)
(sec) (sec) (sec) (sec)
----------------------- -------- ------- ------- ------- ------- ------OTHER
507
6.964
0.000
0.000
0.064
0.000 0.000 0.000
SYSTEM
120
2.439
0.000
0.000
0.058
0.000 0.000 0.000
=========
627
Average
suspend
(sec)
------0.307
0.201
Average
program
load
(sec)
------0.025
0.077
Average
TD IO
wait
(sec)
------0.001
0.000
Average
TS IO
wait
(sec)
------0.023
0.011
Average
TC IO
wait
(sec)
------0.403
0.002
Average
FC IO
wait
(sec)
------0.000
0.000
Average
JC IO
wait
(sec)
------0.678
1.921
Average
MRO
wait
(sec)
------0.069
0.001
Average
except
wait
------6.657
2.237
Tivoli Decision Support for z/OS Report: CICS403
Figure 41. Example of a CICS Application Response Times, Detail report
The report contains this information:
Application name
Transactions are grouped by application name, according to the lookup
table CICS_LOOKUP_APPL.
Tran count
Number of transactions. This is the sum of RECORDS.
Chapter 7. Reports
309
Reports in the CICS monitoring component
Average elapsed (sec)
Average elapsed time per transaction, in seconds. Calculated as
RESPONSE_SUM_SEC/RECORDS.
Average CPU (sec)
Average processor time per transaction, in seconds. Calculated as
CPU_SUM_SEC/RECORDS.
Average disp (sec)
Average dispatch time per transaction, in seconds. Calculated as
DISPATCH_SEC/RECORDS.
Average disp wait (sec)
Average dispatch wait time per transaction, in seconds. Calculated as
DISPATCH_WAIT_SEC/RECORDS.
Average re-disp wait (sec)
Average elapsed time the user task waited for re-dispatch after a CICS
Dispatcher change-TCB mode request was issued by the user task.
Average SSL-TCB wait (sec)
Average elapsed time in which the user task waited to obtain a CICS SSL
TCB (S8 mode) because the CICS system had reached the limit set by the
system initialisation parameter MAXSSLTCBS.
Average XP-TCB wait (sec)
Average elapsed time in which the user task waited to obtain a CICS XP
TCB (C8 or X9 mode), because the CICS system had reached the limit set
by the system parameter MAXXPTCBS.
Average suspend (sec)
Average suspended time per transaction, in seconds. Calculated as
SUSPEND_SEC/RECORDS.
Average program load (sec)
Average program load time per transaction, in seconds. Calculated as
PGM_LOAD_SEC/RECORDS.
Average TD IO wait (sec)
Average I/O wait time for the transient data intrapartition data set per
transaction, in seconds. Calculated as TD_IO_WAIT_SEC/RECORDS.
Average TS IO wait (sec)
Average I/O wait time for the auxiliary temporary storage data set per
transaction, in seconds. Calculated as TS_IO_WAIT_SEC/RECORDS.
Average TC IO wait (sec)
Average terminal I/O wait time per transaction, in seconds. Calculated as
TC_IO_WAIT_SEC/RECORDS.
Average FC IO wait (sec)
Average file I/O wait time per transaction, in seconds. Calculated as
FC_IO_WAIT_SEC/RECORDS.
Average JC IO wait (sec)
Average journal I/O wait time per transaction, in seconds. Calculated as
JC_IO_WAIT_SEC/RECORDS.
Average MRO wait (sec)
Average multiregion operation (MRO) wait time per transaction, in
seconds. Calculated as MRO_WAIT_SEC/RECORDS.
310
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
Average except wait (sec)
Average exception wait time per transaction, in seconds. Calculated as
EXCEPTION_WAIT_SEC/RECORDS.
CICS Application CPU Utilization, Trend
Supplied with the basic application analysis subcomponent, this report shows the
trend in CPU utilization for selected applications for successive weeks. Before
collecting the data for this report, you must first group transactions by application
ID using the CICS_LOOKUP_APPL lookup table.
For information on how to use this report, see “Monitoring processor use” on page
32.
This information identifies the report:
Report ID
CICS404 (CICS404P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_A_BASIC_W (CICS_A_BASIC_WP for CICS Partitioning
feature)
Attributes
CICS, Perform, CPU, Application, Weekly, Trend
Variables
From date, To date, MVS system ID, CICS system ID, Appl name
list
x
x
+
x
x
+
+
x
+
+
x
+
Figure 42. Example of a CICS Application CPU Utilization, Trend report
The report contains this information:
Week start date
There is a bar for each week in the specified date range.
Application name
Application name, as defined in the CICS_LOOKUP_APPL table.
Chapter 7. Reports
311
Reports in the CICS monitoring component
CPU seconds
Average processor time per transaction. Calculated as CPU_SUM_SEC/
RECORDS.
The report gives the average value per transaction, but the value is really
the average per performance record. RECORDS is the number of
performance records collected, and can be higher than the number of
transactions if MNCONV=YES is specified in the SIT, because a
performance record is then written for each terminal interaction.
CICS Application I/O Wait Times, Detail
This report shows I/O wait times for selected applications for one day. Before
collecting the data for this report, you must first group transactions by application
ID using the CICS_LOOKUP_APPL lookup table.
The columns give the average value for each transaction, but the value is really the
average for each performance record collected. RECORDS is the number of
performance records collected and can be higher than the number of transactions if
MNCONV=YES is specified in the SIT, because a performance record is then
written for each terminal interaction.
For information on how to use this report, see “Monitoring response time” on page
29.
This information identifies the report:
Report ID
CICS405 (CICS405P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_A_BASIC_H (CICS_A_BASIC_HP for CICS Partitioning
feature)
Attributes
CICS, Perform, IO, Wait, Application, Daily, Detail
Variables
Date, MVS system ID, CICS system ID
The report contains this information:
Application name
Transactions are grouped by application name, according to the
CICS_LOOKUP_APPL table.
Tran Count
Number of transactions. This is the sum of RECORDS.
Average TC IO wait (sec)
Average elapsed time that the user task waited for input from the terminal
operator, after issuing a RECEIVE request. Calculated as
TC_IO_WAIT_SEC/RECORDS.
Average TS IO wait (sec)
Average elapsed time that the user task waited for input from the terminal
operator, after issuing a RECEIVE request. Calculated as
TC_IO_WAIT_SEC/RECORDS.
Average SHARED TS IO wait (sec)
Average elapsed time the user task waited for the completion of an
asynchronous shared temporary storage request to a temporary storage
data server. Calculated as TSSHWAIT_CLOCK/RECORDS.
312
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
Average TD IO wait (sec)
Average elapsed time that the user waited for VSAM transient data I/O.
Calculated as TD_IO_WAIT_SEC/RECORDS.
Average JC IO wait (sec)
Average elapsed time that the user task waited for VSAM transient data
I/O. Calculated as TD_IO_WAIT_SEC/RECORDS.
Average TD IO wait (sec)
Average elapsed time that the user task waited for journal I/O. Calculated
as JC_IO_WAIT_SEC/RECORDS.
Average FC IO wait (sec)
Average elapsed time that the user waited for file I/O. Calculated as
FC_IO_WAIT_SEC/RECORDS.
Average RLS IO wait (sec)
Average elapsed time that the user task waited for RLS file I/O. Calculated
as RLSWAIT_CLOCK/RECORDS.
Average CFDT IO wait (sec)
Average elapsed time that the user task waited for a data table access
request to the Coupling Facility Data Table server to complete. Calculated
as CFDTWAIT_CLOCK/RECORDS.
Average SOCKET IO wait (sec)
Average elapsed time that the user waited for socket I/O. Calculated as
SOIOWTT_CLOCK/RECORDS.
Average LU61 TC IO wait (sec)
Average elapsed time that the user task waited for I/O on a LUTYPE6.1
connection or session. This value includes the waits incurred for
conversations across LUTYPE6.1 connections, but does not include the
waits incurred due to LUTYPE6.1 syncpoint flows. Calculated as
LU61_IO_WAIT_SEC/RECORDS.
Average LU62 TC IO wait (sec)
Average elapsed time that the user task waited for I/O on a LUTYPE6.2
(APPC) connection or session. This value includes the waits incurred for
conversations across LUTYPE6.2 (APPC) connections, but does not include
the waits incurred due to LUTYPE6.2 (APPC) syncpoint flows. Calculated
as LU62_IO_WAIT_SEC/RECORDS.
Average MRO wait (sec)
Average elapsed time that the user task waited for control at the end of an
MRO link. Calculated as MRO_WAIT_SEC/RECORDS.
Average FEPI IO wait (sec)
Average elapsed time that the user task waited for all FEPI services.
Calculated as FE_WAIT_SEC/RECORDS.
Total IO wait time (sec)
Total average I/O wait time. Calculated as
(TC_IO_WAIT_SEC+TS_IO_WAIT_SEC+
TSSHWAIT_CLOCK+TD_IO_WAIT_SEC+JC_IO_WAIT_SEC+
FC_IO_WAIT_SEC+RLSWAIT_CLOCK+CFDTWAIT_CLOCK+
SOIOWTT_CLOCK+MRO_WAIT_SEC+LU61_IO_WAIT_SEC+
LU62_IO_WAIT_SEC+FE_WAIT_SEC)/RECORDS.
Chapter 7. Reports
313
Reports in the CICS monitoring component
CICS Application Main Response Times, Detail
This report shows main response times for selected applications for one day. Before
collecting the data for this report, you must first group transactions by application
ID using the CICS_LOOKUP_APPL lookup table.
The columns give the average value for each transaction, but the value is really the
average for each performance record collected. RECORDS is the number of
performance records collected and can be higher than the number of transactions if
MNCONV=YES is specified in the SIT, because a performance record is then
written for each terminal interaction.
For information on how to use this report, see “Monitoring response time” on page
29.
This information identifies the report:
Report ID
CICS406 (CICS406P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_A_BASIC_H (CICS_A_BASIC_HP for CICS Partitioning
feature)
Attributes
CICS, Perform, Response, Application, Daily, Detail
Variables
Date, MVS system ID, CICS system ID
CICS Application Main response Times, Detail
MVS System: 'MVSB' CICS system = 'FGAIZ'
Date: '2005-05-01'
Application Tran Average Average Average
Name
count elapsed CPU
DISP
(sec) (sec)
----------- ----- ------- ------- ------OTHER
507 6.964 0.000
0.000
SYSTEM
120 2.439 0.000
0.000
Average
QRMODDLY
elapsed
(sec)
------0.000
0.000
Average
QRDISPT
elapsed
(sec)
------0.000
0.000
Average
QRCPUT
elapsed
(sec)
------0.000
0.000
Average Average
MSDISPT MSCPUT
elapsed proc.
(sec) (sec)
------- ------0.000 0.000
0.000 0.000
Average Average
Program RMI
Load elapsed
(sec) (sec)
-------- -----0.000 0.000
0.000 0.000
Average
JVM
wait
(sec)
------0.000
0.000
Average
syncpoint
elapsed
(sec)
------0.000
0.000
Average Average Average Average
J8CPUT S8CPUT X8CPUT X9CPUT
proc. proc. proc. proc.
(sec) (sec) (sec) (sec)
------ ------- ------- ------0.000 0.000 0.000 0.000
0.000 0.000 0.000 0.000
Tivoli Decision Support for z/OS Report: CICS406
Figure 43. Example of a CICS Application Main Response Times, Detail report
The report contains this information:
Application name
Transactions are grouped by application name, according to the
CICS_LOOKUP_APPL table.
Tran Count
Number of transactions. This is the sum of RECORDS.
Average Elapsed (sec)
Average elapsed time per transaction, in seconds. Calculated as
RESPONSE_SUM_SEC/RECORDS.
Average CPU (sec)
Average processor time per transaction, in seconds. Calculated as
CPU_SUM_SEC/RECORDS.
314
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
Average DISP (sec)
Average time dispatched per transaction, in seconds. Calculated as
DISPATCH_SEC/RECORDS.
Average Program Load (sec)
Average program load time per transaction, in seconds. Calculated as
PGM_LOAD_SEC/RECORDS.
Average RMI Elapsed (sec)
Average amount of elapsed time spent in the Resource Manager Interface
(RMI). Calculated as RMI_SEC/RECORDS.
Average JVM wait (sec)
Average elapsed time that was spent in the CICS JVM by the user task.
Calculated as JVMTIME_CLOCK/RECORDS.
Average syncpoint elapsed (sec)
Average elapsed time that the user task was dispatched and was
processing Syncpoint requests. Calculated as SYNCTIME_CLOCK/
RECORDS.
Average QRMODDLY elapsed (sec)
Average elapsed time that the user task waited for redispatch on the CICS
QR TCB. This is the aggregate of the wait times between each event
completion and user-task redispatch. Calculated as QRMODDLY_CLOCK/
RECORDS.
Average QRDISPT elapsed (sec)
Average elapsed time that the user task was dispatched on the CICS QR
TCB. Calculated as QRDISPT_CLOCK/RECORDS.
Average QRCPUT processor (sec)
Average processor time that the user task was dispatched on the CICS QR
TCB. Calculated as QRCPUT_CLOCK/RECORDS.
Average MSDISPT elapsed (sec)
Average elapsed time that the user task was dispatched on each CICS TCB
(RO, CO, FO, SZ if FEPI is active, and RP if the ONC/RCP or CICS WEB
Interface feature is installed and active). Calculated as
MSDISPT_CLOCK/RECORDS.
Average MSCPUT processor (sec)
Average processor time that the user task was dispatched on each CICS
TCB (RO, CO, FO, SZ if FEPI is active, and RP if the ONC/RCP or CICS
WEB Interface feature is installed and active). Calculated as
MSCPUT_CLOCK/RECORDS.
Average J8CPUT processor (sec)
Average processor time that the user task was dispatched on each CICS J8
TCB installed. Calculated as J8CPUT_CLOCK/RECORDS.
Average S8CPUT processor (sec)
Average processor time that the user task was dispatched on each CICS S8
TCB installed. Calculated as S8CPUT_CLOCK/RECORDS.
Average X8CPUT processor (sec)
Average processor time during which the user task was dispatched by the
CICS dispatcher domain on a CICS X8 mode TCB. When a transaction
invokes a C or C++ program that was compiled with XPLINK option, and
that is defined with EXECKEY=CICS, uses a CICS X8 mode TCB.
Chapter 7. Reports
315
Reports in the CICS monitoring component
Average X9CPUT processor (sec)
Average processor time during which the user task was dispatched by the
CICS dispatcher domain on a CICS X9 mode TCB. When a transaction
invokes a C or C++ program that was compiled with XPLINK option, and
that is defined with EXECKEY=USER, uses a CICS X9 mode TCB.
CICS Application Wait Times, Detail
This report shows wait (suspend) times for selected applications for one day.
Before collecting the data for this report, you must first group transactions by
application ID using the CICS_LOOKUP_APPL lookup table.
The columns give the average value for each transaction, but the value is really the
average for each performance record collected. RECORDS is the number of
performance records collected and can be higher than the number of transactions if
MNCONV=YES is specified in the SIT, because a performance record is then
written for each terminal interaction.
For information on how to use this report, see “Monitoring response time” on page
29.
This information identifies the report:
Report ID
CICS407 (CICS407P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_A_BASIC_H (CICS_A_BASIC_HP for CICS Partitioning
feature)
Attributes
CICS, Perform, Wait, Application, Daily, Detail
Variables
Date, MVS system ID, CICS system ID
The report contains this information:
Application name
Transactions are grouped by application name, according to the
CICS_LOOKUP_APPL table.
Tran Count
Number of transactions. This is the sum of RECORDS.
Total IO wait time (sec)
Total average I/O wait time. Calculated as
(TC_IO_WAIT_SEC+TS_IO_WAIT_SEC+
TSSHWAIT_CLOCK+TD_IO_WAIT_SEC+JC_IO_WAIT_SEC+
FC_IO_WAIT_SEC+RLSWAIT_CLOCK+CFDTWAIT_CLOCK+
SOIOWTT_CLOCK+MRO_WAIT_SEC+LU61_IO_WAIT_SEC+
LU62_IO_WAIT_SEC+FE_WAIT_SEC)/RECORDS.
Total other wait time (sec)
Total average I/O wait time. Calculated as
(TC_IO_WAIT_SEC+TS_IO_WAIT_SEC+
TSSHWAIT_CLOCK+TD_IO_WAIT_SEC+
JC_IO_WAIT_SEC+FC_IO_WAIT_SEC+
RLSWAIT_CLOCK+CFDTWAIT_CLOCK+
SOIOWTT_CLOCK+MRO_WAIT_SEC+
LU61_IO_WAIT_SEC+LU62_IO_WAIT_SEC+
FE_WAIT_SEC+REDISPATC_WAIT_SEC+
SSLTCB_WAIT_SEC+XPTCBS_WAIT_SEC)/RECORDS.
316
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
Suspend time (sec)
Total average suspend time. Calculated as SUSPEND_SEC+/RECORDS.
CICS Application DLI Call Utilization, Trend
This report consolidates data from the DBCTL application analysis subcomponent
and the DL/I application analysis subcomponent. It shows the database call rate,
by application.
Note: Although subcomponent 5 supplies this report, subcomponents 1, 2, 3, and 6
must also be installed to create it.
This information identifies the report:
Report ID
CICSA51 (CICSA51P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_A_DLI_W, CICS_A_DBCTL_W (CICS_A_DLI_WP,
CICS_A_DBCTL_WP for CICS Partitioning feature)
Attributes
CICS, DL/I, Application, Weekly, Trend
Variables
MVS system ID, CICS system ID, Appl name list, From date, To
date
x
x
x
x
x
+
+
+
+
+
+
x
Figure 44. Example of a CICS Application DLI Call Utilization, Trend report
The report contains this information:
Date
There is one bar for each week in the specified date range. The dates are
the first day (Monday) of each week.
Application name
Application name, as defined in the CICS_LOOKUP_APPL table.
Chapter 7. Reports
317
Reports in the CICS monitoring component
Call counts
Number of database calls, the sum of CALL_CNT from the
CICS_A_DLI_W table and DLI_CALL_CNT from the CICS_A_DBCTL_W
table.
CICS/MVS CMF Transaction Statistics
Supplied with the CICS/MVS subcomponent (global + accounting), this report
shows the most frequent transactions, using CMF accounting class data from a
CICS Version 2 system.
The data is from a weekly table, so the total is calculated from the summary
records for all Mondays in the specified date range. For example, if you specify
‘2000-04-21’ (a Friday) to ‘2000-04-28’, one summary row is selected: the one for the
week beginning ‘2000-04-24’. So the report shows the total number of transactions
run in the week ‘2000-04-24’ to ‘2000-04-30’ inclusive.
This information identifies the report:
Report ID
CICS701 (CICS701P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_M_ACCOUNT_W (CICS_M_ACCOUNT_WP for CICS
Partitioning feature)
Attributes
CICS, Transactions, System, Daily, Statistics
Variables
MVS system ID, CICS system ID, From date, To date
CICS/MVS CMF Transaction Statistics
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-06-01'
25 most frequent transactions
Transaction
ID
Transactions
----------- -----------QUIT
7944
AP00
1754
PM94
1373
CRTE
819
VCS1
739
PM80
668
SU01
489
...
...
PM23
118
VA02
105
VA23
102
GC08
100
IN24
93
DD01
85
Tivoli Decision Support for z/OS Report: CICS701
Figure 45. Example of a CICS/MVS CMF Transaction Statistics report
The report contains this information:
Transaction ID
Transaction name.
Transactions
Sum of transactions performed in the selected weeks.
318
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
CICS Transaction Processor Utilization, Daily
Supplied with the CICS/MVS subcomponent (global + accounting), this report
shows the number of CICS transactions per processor second. The report provides
information for CICS running on MVS working both in toleration and goal modes.
This information identifies the report:
Report ID
CICSA07 (CICSA07P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_M_ACCOUNT_D (CICS_M_ACCOUNT_DP for CICS
Partitioning feature), MVS_WORKLOAD_D,
MVS_WORKLOAD2_M
Attributes
CICS, Performance, Transaction, Daily, Detail
Variables
MVS system ID, CICS system ID, From date, To date
Figure 46. Example of a CICS Transaction Processor Utilization, Daily report
The report contains this information:
Date
There is one bar for each day in the specified date range.
Tran count/CPU sec
Number of transactions per processor second. The number of transactions
is from the CICS/MVS CMF accounting records, and the processor time is
the sum of TCB_SECONDS and SRB_SECONDS, from MVS.
CICS Transaction Processor Utilization, Monthly
Supplied with the CICS/MVS subcomponent (global + accounting), this report
shows the number of CICS transactions per processor second. The report provides
information for CICS running on MVS working both in toleration and goal modes.
This information identifies the report:
Chapter 7. Reports
319
Reports in the CICS monitoring component
Report ID
CICSA05 (CICSA05P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_M_ACCOUNT_M (CICS_M_ACCOUNT_MP for CICS
Partitioning feature), MVS_WORKLOAD_M,
MVS_WORKLOAD2_D
Attributes
CICS, Performance, Transaction, Monthly, Detail
Variables
MVS system ID, CICS system ID, From date, To date
Figure 47. Example of a CICS Transaction Processor Utilization, Monthly report
The report contains this information:
Date
There is one bar for each month in the specified date range.
Tran count/CPU sec
Number of transactions per processor second. The number of transactions
is from the CICS/MVS CMF accounting records, and the processor time is
the sum of TCB_SECONDS and SRB_SECONDS, from MVS.
CICS Transactions Resources Details, Daily
This report shows details about the files and TS queues used by each transaction.
This information identifies the report:
320
Report ID
CICST01 (CICST01P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_FILE_TRAN_D, CICS_QUEUE_TRAN_D
Attributes
Monitoring, Transaction, Resources, Daily
Variables
From date, To date, Period name, MVS system ID, CICS system ID
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS monitoring component
CICS Transactions Resources Details, Daily
MVS ID ='IPO2'
CICS ID ='CFGTV1'
Date: '2004-03-02' to '2004-03-08'
Date
---------2004-03-02
2004-03-02
2004-03-02
Tran
ID
---QUIT
CRTE
QUIT
File Tot
Time (Clock)
-----------1.28160E-02
1.39200E-02
1.55130E-02
File I/O Wait
Time (Clock)
------------1.03200E-02
1.14000E-02
1.06600E-02
TSQueue Tot
Time (Clock)
-----------3.74720E-02
3.98720E-02
3.00520E-02
TSQueue I/O Wait
Time (Clock)
--------------0.00000E+00
0.00000E+00
0.00000E+00
Tivoli Decision Support for z/OS Report: CICST01
Figure 48. Example of a CICS Transactions Resources Details, Daily report
The report contains this information:
Date
The date of the measurement. From Date.
Tran ID
The transaction identifier. From TRANSACTION_ID.
File Tot Time (Clock)
The total elapsed time that the user task waited for the completion of all
the requests issued by the user task for this file. From FILE_TOT_CLOCK.
File I/O Wait Time (Clock)
The total I/O wait time on this file. From FILE_IOWAIT_CLOCK.
TSQueue Tot Time (Clock)
The total elapsed time waited for completion of all requests for this
temporary storage queue. From TSQUEUE_TOT_CLOCK.
TSQueue I/O Wait Time (Clock)
The total I/O wait time on this temporary storage queue. From
TSQUEUE_IOWAIT_CLOCK.
CICS Enterprise Java Beans Details, Daily
This report shows details about enterprise java beans data, by CORBA server
name.
This information identifies the report:
Report ID
CICSJ01 (CICSJ01P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_BEAN_REQ_D
Attributes
Monitoring, EJB, CORBA, Daily
Variables
From date, To date, Period name, MVS system ID, CICS system ID
CICS Enterprise Java Beans Details, Daily
MVS ID ='IPO2'
CICS ID ='CFGTV1'
Date: '2004-05-21' to '2004-05-27'
Date
-------2004-05-21
CORBA
server
------CBS1
Bean
activations
----------50.00
Bean
passivations
-----------32.00
Bean creation Bean removal Bean method Total beans
calls
calls
calls
occurred
------------- --------------------------83.00
10.00
60.00
180.00
Tivoli Decision Support for z/OS Report: CICSJ01
Figure 49. Example of a CICS Transactions Resources Details, Daily report
Chapter 7. Reports
321
Reports in the CICS monitoring component
The report contains this information:
Date
The date of the measurement.
CORBA server
The CORBA server name. From CORBASER_NAME.
Bean activations
The number of bean activations. From BEANACT_REQ_NUM.
Bean passivations
The number of bean passivations. From BEANPAS_REQ_NUM.
Bean creation calls
The number of bean creation calls. From BEANCRE_REQ_NUM.
Bean removal calls
The number of bean removal calls. From BEANREM_REQ_NUM.
Bean method calls
The number of bean method calls executed. From BEANMET_REQ_NUM.
Bean method calls
The total beans occurred. From BEANTOT_REQ_NUM.
Reports in the CICS OMEGAMON monitoring component
As described in “Evaluating the CICS OMEGAMON monitoring component” on
page 15, OMEGAMON XE for CICS provides the performance data for the CICS
OMEGAMON monitoring component. The CICS OMEGAMON monitoring
component contains subcomponents. This section describes the reports for the
CICS monitoring component and indicates which subcomponents must be installed
to create them.
CICS OMEGAMON database/file total requests, hourly
This report shows the hourly total request count, per database/file type. The File
and Database Detailed Usage Subcomponent needs to be installed to run this
report.
This information identifies the report:
Report ID
CICSOMEG001
Report Description
OMEGAMON database/file total requests, hourly
322
Report group
CICS_OMEG
Source
CICS_O_FL_DTL_H
Attributes
CICS, OMEGAMON, TOTAL, REQUESTS, HOURLY
Variables
From date, MVS system ID, CICS system ID, Period Name, File DB
Type
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS OMEGAMON monitoring component
OMEGAMON database/file total requests, hourly
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
DATE: '2007-06-07'
FILE/DATABASE TYPE: All
---------------------------------- TYPE ----------------------------------
ADABAS - DATACOM - IDMS -- -- MQ --- - SUPRA - - VSAM --
HOUR
---- ---------20
72576
21
==========
72576
---------44352
---------16128
===========
44352
=========
16128
---------- ----------- ----------3879
30240
34272
2304
=======
========== ==========
6183
30240
34272
Tivoli Decision Support: CICSOMEG001
Figure 50. Example of a CICS OMEGAMON database/file total requests, hourly report
The report contains this information:
Hour
The time of the measurement.
Type
The file or database type.
Total requests
The total number of requests issued against the file or database type.
Calculated as SUM(COUNT).
CICS OMEGAMON database/file total commands, hourly
This report shows the hourly total command count, for the selected database/file
type. The File and Database Detailed Usage Subcomponent needs to be installed to
run this report.
This information identifies the report:
CICSOMEG002
Report ID
Report Description
OMEGAMON database/file total commands, hourly
Report group
CICS_OMEG
Source
CICS_O_FL_DTL_H
Attributes
CICS, OMEGAMON, TOTAL, REQUESTS, HOURLY
Variables
From date, MVS system ID, CICS system ID, Period Name, File DB
Type
OMEGAMON database/file total commands, hourly
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
DATE: '2007-06-07'
FILE/DATABASE TYPE: 'MQ
'
--------------------- COMMAND -------------------------------
-- CLO -- -- GET -- -- INQ -- -- OPN -- -- PUT --
HOUR
---- ----------- ------------------ ---------- ---------20
431
1891
246
431
4423
21
256
650
135
256
642
===== ======
=====
=====
=====
687
2541
381
687
5065
Tivoli Decision Support: CICSOMEG002
Figure 51. Example of a CICS OMEGAMON database/file total commands, hourly report
The report contains this information:
Chapter 7. Reports
323
Reports in the CICS OMEGAMON monitoring component
Hour
The time of the measurement.
Command
The command issued against the file or database type.
Total requests
The total number of requests issued against the file or database type.
Calculated as SUM(COUNT).
CICS OMEGAMON database/file avg request response, daily
This report shows the daily average response time, for the total commands, per
file/database type. The File and Database Detailed Usage Subcomponent needs to
be installed to run this report.
This information identifies the report:
Report ID
CICSOMEG003
Report Description
OMEGAMON database/file avg request response, daily
Report group
CICS_OMEG
Source
CICS_O_FL_DTL_D
Attributes
CICS, OMEGAMON, AVERAGE, REQUEST, RESPONSE, DAILY
Variables
From date, To Date, MVS system ID, CICS system ID, Period
Name, File DB Type
OMEGAMON database/file avg request response, daily
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
FROM '2007-06-07' TO '2007-06-07'
FILE/DATABASE TYPE: All
-------------------------- TYPE -------------------------
ADABAS - DATACOM - IDMS -- -- MQ --- - SUPRA -
DATE
---------- ----------- ----------- ----------- ----------- ----------2007-06-07 3.880E-05 7.986E-03 5.821E-03 5.387E-03 1.680E-02
=========== ========== ========= ========= ========
3.880E-05 7.986E-03 5.821E-03 5.387E-03 1.680E-02
Tivoli Decision Support: CICSOMEG003
Figure 52. Example of a CICS OMEGAMON database/file avg request response, daily report
The report contains this information:
Date
The date of the measurement.
Type
The file or database type.
Average response time
The average response time for all requests issued against the file or
database type. Calculated as SUM(CLOCK)/SUM(COUNT).
CICS OMEGAMON database/file avg command response, daily
This report shows the daily average response time, per command, for the selected
file/database type. The File and Database Detailed Usage Subcomponent needs to
be installed to run this report.
This information identifies the report:
324
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS OMEGAMON monitoring component
CICSOMEG004
Report ID
Report Description
OMEGAMON database/file avg command response, daily
Report group
CICS_OMEG
Source
CICS_O_FL_DTL_D
Attributes
CICS, OMEGAMON, AVERAGE, COMMAND, RESPONSE, DAILY
Variables
From date, To Date, MVS system ID, CICS system ID, Period
Name, File DB Type
OMEGAMON database/file avg command response, daily
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
FROM '2007-06-07' TO '2007-06-07'
FILE/DATABASE TYPE: 'MQ
'
----------------------------- COMMAND ----------------------->
-- CLO -- -- GET -- -- INQ -- -- OPN -- -- PUT --
DATE
---------2007-06-07
----------5.118E-03
========
5.118E-03
----------4.590E-03
========
4.590E-03
----------4.351E-03
==========
4.351E-03
----------8.329E-03
========
8.329E-03
----------5.111E-03
=========
5.111E-03
Tivoli Decision Support: CICSOMEG004
Figure 53. Example of a CICS OMEGAMON database/file avg command response, daily
report
The report contains this information:
Date
The date of the measurement.
Command
The command issued against the file or database type.
Average response time
The average response time for all requests issued against the file or
database type. Calculated as SUM(CLOCK)/SUM(COUNT).
CICS OMEGAMON transaction database/file requests, daily
This report shows the daily total requests, per file/database type, per transaction.
The File and Database Detailed Usage Subcomponent needs to be installed to run
this report.
This information identifies the report:
Report ID
CICSOMEG005
Report Description
OMEGAMON transaction database/file requests, daily
Report group
CICS_OMEG
Source
CICS_O_FL_DTL_D
Attributes
CICS, OMEGAMON, TRANSACTION, REQUESTS, DAILY
Variables
From date, To Date, MVS system ID, CICS system ID, Period
Name, File DB Type
Chapter 7. Reports
325
Reports in the CICS OMEGAMON monitoring component
OMEGAMON transaction database/file requests, daily
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
DATE: '2007-06-07'
FILE/DATABASE TYPE: All
--------------------- TYPE -------------------------
- ADABAS - DATACOM - -- IDMS -- --- MQ ---
TRANSACTION ID
-------------- ------------ ------------ ------------ -----------ADA3
12096
ADA4
60480
AMG1
693
AMG2
684
AMG3
693
AMG4
693
AMG5
684
AMG6
684
AMG7
684
AMG8
684
AMG9
684
DCO1
44352
IDM1
16128
RSV1
RSV2
RSV5
==========
72576
==========
44352
==========
16128
==========
6183
Tivoli Decision Support: CICSOMEG005
Figure 54. Example of a CICS OMEGAMON transaction database/file requests, daily report
The report contains this information:
Transaction ID
The CICS Transaction ID.
Type
The file or database type.
Total requests
The total number of requests the transaction issued against the file or
database type. Calculated as SUM(COUNT).
CICS OMEGAMON transaction database/file commands, daily
This report shows the daily total requests, per file/database type, per transaction.
The File and Database Detailed Usage Subcomponent needs to be installed to run
this report.
This information identifies the report:
Report ID
CICSOMEG006
Report Description
OMEGAMON transaction database/file commands, daily
326
Report group
CICS_OMEG
Source
CICS_O_FL_DTL_D
Attributes
CICS, OMEGAMON, TRANSACTION, COMMANDS, DAILY
Variables
From date, MVS system ID, CICS system ID, Period Name, File DB
Type
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS OMEGAMON monitoring component
OMEGAMON transaction database/file commands, daily
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
DATE: '2007-06-07'
FILE/DATABASE TYPE: 'MQ
'
-------------------------- COMMAND ----------------------
-- CLO -- -- GET -- -- INQ -- -- OPN -- -- PUT --
TRANSACTION ID
-------------- ----------- ----------- ----------- ----------- ----------AMG1
77
77
77
231
77
AMG2
76
76
76
228
76
AMG3
77
77
77
231
77
AMG4
77
77
77
231
77
AMG5
76
76
76
228
76
AMG6
76
76
76
228
76
AMG7
76
76
76
228
76
AMG8
76
76
76
228
76
AMG9
76
76
76
228
76
======== ========
========
======== ========
687
687
687
2061
687
Tivoli Decision Support: CICSOMEG006
Figure 55. Example of a CICS OMEGAMON transaction database/file commands, daily report
The report contains this information:
Transaction ID
The CICS Transaction ID.
Command
The command the transaction issued against the file or database type.
Total requests
The total number of requests the transaction issued against the file or
database type. Calculated as SUM(COUNT).
CICS OMEGAMON transaction DB2 averages, hourly
This report shows the hourly average DB2 information, per transaction. The File
and Database subcomponent (CICS OMEGAMON Monitoring Component) and the
Basic Transaction subcomponent (CICS Monitoring Component) need to be
installed to run this report.
This information identifies the report:
Report ID
CICSOMEG007
Report Description
OMEGAMON transaction DB2 averages, hourly
Report group
CICS_OMEG
Source
CICS_O_FL_H, CICS_TRANSACTION_H
Attributes
CICS, OMEGAMON, TRANSACTION, DB2, AVERAGES, HOURLY
Variables
From date, MVS system ID, CICS system ID, Period Name
Chapter 7. Reports
327
Reports in the CICS OMEGAMON monitoring component
OMEGAMON transaction DB2 averages, hourly
MVS ID: 'SYS ' CICS ID: 'CICSXX64'
DATE: '2007-06-07'
TRANSACTION
HOUR ID
REQUEST COUNT REQUEST RESPONSE TIME
---- ---- ------------- --------------------20
AMG1
1446
5.118E-03
DB2 WAIT COUNT DB2 WAIT TIME
-------------- ------------684
3.136E-06
Tivoli Decision Support: CICSOMEG007
Figure 56. Example of a CICS OMEGAMON transaction DB2 averages, hourly report
The report contains this information:
Hour
The time of the measurement.
Transaction ID
The CICS Transaction ID.
Request count
The average number of DB2 requests for this transaction. Calculated as
AVG(COUNT/TRANSACTION_COUNT).
Request response time
The average response time of the DB2 requests for this transaction.
Calculated as AVG((CLOCK/COUNT)/TRANSACTION_COUNT).
DB2 wait count
The average number of times this transaction waited for DB2 to service the
request. Calculated as AVG(DB2WAIT_COUNT/
TRANSACTION_COUNT).
DB2 wait time
The average DB2 wait time for this transaction. Calculated as
AVG(DB2WAIT_CLOCK/TRANSACTION_COUNT).
Reports in the CICS statistics component
As described in “Evaluating the CICS statistics component” on page 16, the CICS
Performance feature supports statistics only for CICS/ESA and CICS/TS. If you
install the CICS statistics component, Tivoli Decision Support for z/OS provides
the reports described in this section.
CICS Global Loader
This report shows global CICS/ESA and CICS/TS statistics from the loader
domain.
This information identifies the report:
328
Report ID
CICS801 (CICS801P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_S_GLOBAL_D (CICS_S_GLOBAL_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, Global, Loader
Variables
MVS system ID, CICS system ID, From date, To date
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
CICS Global Loader
MVS ID ='IPO2'
CICS ID ='CSFGHT'
Date: '2000-05-12' to '2000-05-13'
Library
Load
Average
Peak
Average
load
time
time to
requests
wait
Programs
requests
(seconds)
removal
waiting
time
removed
----------- ---------- ----------- ----------- ---------- ----------2022
21
123
0
0
138
Tivoli Decision Support for z/OS Report: CICS801
Figure 57. Example of a CICS Global Loader report
The report contains this information:
Library load requests
Application requests to load programs. This is the sum of
LIBRARY_LOAD_REQ.
Load time (seconds)
Time spent loading programs, in seconds. This is the sum of LOAD_SEC.
Average time to removal
Average time, in seconds, that a program is left in storage when not in use
before being removed by dynamic program storage compression. A value
of zero can indicate that no programs were removed by compression. This
is calculated as NOT_USED_SEC/PROGRAMS_REMOVED.
Peak requests waiting
Maximum number of application load requests that are queued because
the requested program is locked. If a task has to wait because the loader
domain is busy (that is, the resource-owning subtask is busy), the wait is
counted in dispatch wait time and this counter is not incremented. This is
the maximum of REQ_PEAK_WAIT.
Average wait time
Average time spent waiting for the loader, in seconds, each time a task had
to wait. This is calculated as WAIT_TIME/REQ_WAITED.
Programs removed
Number of programs removed by compression (removal of unused
programs to save space). This is the sum of PROGRAMS_REMOVED.
CICS Global Temporary Storage
This report shows global CICS/ESA and CICS/TS temporary storage statistics.
This information identifies the report:
Report ID
CICS802 (CICS802P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_GLOBAL_D (CICS_S_GLOBAL_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, Global, Temporary, Storage
Variables
MVS system ID, CICS system ID, From date, To date
Chapter 7. Reports
329
Reports in the CICS statistics component
CICS Global Temporary Storage
MVS ID ='IPO2'
CICS ID ='CFGHY7'
Date: '2000-05-13' to '2000-05-14'
TS
TS
TS
TS
main
peak
TS
TS
main
main
peak
CIs
buffer
string
puts
gets
bytes
used
waits
waits
----------- ---------- ----------- ----------- ---------- ----------123
3333
4304
270
2
0
Tivoli Decision Support for z/OS Report: CICS802
Figure 58. Example of a CICS Global Temporary Storage report
The report contains this information:
TS main puts
Number of PUT requests to main storage.
TS main gets
Number of GET requests from main storage.
TS main peak bytes
Peak main storage used, in bytes.
TS peak CIs used
Peak number of control intervals in which at least one segment is active
(used). They have not necessarily been written to disk. When a queue is
deleted, this figure is updated, although the disk records are not
immediately updated. When a disk record containing deleted segments is
next read from disk, CICS compresses the record by putting all the active
segments together. An empty record (having no active segments) is never
read from disk; CICS merely overwrites it (a PUT with no preceding
Get-for-update).
TS buffer waits
Number of times application programs waited because no buffers were
available for auxiliary temporary storage. The number is set using the TS=
operand of the SIT.
TS string waits
Number of times that I/O to or from the auxiliary temporary storage data
set had to wait for lack of a string. The number of strings is specified using
the TS= operand of the SIT.
CICS Global VTAM
This report shows global CICS/ESA and CICS/TS VTAM statistics.
This information identifies the report:
330
Report ID
CICS803 (CICS803P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_GLOBAL_D (CICS_S_GLOBAL_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, Global, VTAM
Variables
MVS system ID, CICS system ID, From date, To date
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
CICS Global VTAM
MVS ID ='IPO2'
CICS ID ='CFGHT6'
Date: '2000-04-04' to '2000-04-05'
VTAM
RPL
VTAM
ACB
peak
SOS
dynamic
used
count
opens
---------- ----------- ----------1
0
0
Tivoli Decision Support for z/OS Report: CICS803
Figure 59. Example of a CICS Global VTAM report
The report contains this information:
RPL peak used
Peak number of VTAM RPLs found POSTed on one scan.
VTAM SOS count
Number of times that VTAM rejected a CICS request due to a buffer
shortage. The VTAM command D NET,BFRUSE gives information on the
use of VTAM buffer pools. This is a serious error condition.
VTAM ACB dynamic opens
Number of times the CICS operator has opened the CICS VTAM ACB after
initialization (that is, issued a CEMT SET VTAM OPEN command).
CICS Global DTB
This report shows global CICS/ESA and CICS/TS dynamic transaction backout
statistics.
This information identifies the report:
Report ID
CICS804 (CICS804P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_GLOBAL_D (CICS_S_GLOBAL_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, Global, DTB, Backout
Variables
MVS system ID, CICS system ID, From date, To date
CICS Global DTB
MVS ID ='IPO1'
CICS ID ='CFGHT4'
Date: '2000-06-05' to '2000-06-07'
DTB
records
DTB
logged
overflows
----------- ---------3410
0
Tivoli Decision Support for z/OS Report: CICS804
Figure 60. Example of a CICS Global DTB report
The report contains this information:
DTB records logged
Number of records logged for the purpose of dynamic transaction backout.
If the number seems high, check that RECOVERY has not been
Chapter 7. Reports
331
Reports in the CICS statistics component
unnecessarily specified for your files. If you have migrated your PCT,
remember that all your transactions now have DTB=YES specified. So if
you had a PCT where many transactions had DTB=NO, you may get a
large increase in DTB logging.
DTB overflows
Number of records for which there was no space in the dynamic log buffer.
When there is no space, CICS puts the records either to auxiliary
temporary storage (if DTB=AUX is specified in the SIT) or to a main
storage chain. This degrades performance. CICS attempts to tune the buffer
size for each transaction by initially allocating half the maximum and then
monitoring the amount used, so that a more appropriate value is allocated
the next time the transaction is invoked. For this reason, there may be
spills when a transaction is first used, while CICS is finding the optimum
value. If there are spills over long periods, increase the maximum size of
the dynamic log buffer using the SIT DBUFSZ= operand. It is allocated in
extended storage. It is possible that it is always the same transaction that
causes spillage. If so, consider adding SYNCPOINT requests to the
application code.
CICS Global IRC Batch
This report shows global CICS/ESA and CICS/TS statistics for batch jobs sharing a
DL/I database.
This information identifies the report:
Report ID
CICS806 (CICS806P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_GLOBAL_D (CICS_S_GLOBAL_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, Global, IRC, Batch
Variables
MVS system ID, CICS system ID, From date, To date
CICS Global IRC Batch
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
Jobs
Jobs
sharing
peak
database
----------- ---------1
1
Tivoli Decision Support for z/OS: CICS806
Figure 61. Example of a CICS Global IRC Batch report
The report contains this information:
Jobs peak
Peak number of batch DL/I jobs whose database accesses were routed
through the CICS system.
Jobs sharing database
Number of batch jobs whose database accesses were routed through CICS.
332
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
CICS Transaction Usage
This report shows CICS/ESA and CICS/TS transaction statistics. For information
on how to use this report, see “Interpreting combined CICS and DB2 performance
data” on page 36.
This information identifies the report:
Report ID
CICS807 (CICS807P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TRAN_D (CICS_S_TRAN_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, Transactions
Variables
MVS system ID, CICS system ID, From date, To date
CICS Transaction Usage
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
25 most frequent transactions
Transaction
ID
----------CEMT
CEDA
FIST
CXRE
CATA
CATD
CRSQ
CSFU
CSGM
CSNE
CATR
CATS
CBRC
CDBC
CDBD
CDBI
CDBN
CDBO
CECS
CEDB
CEDC
CDBT
CDTS
CEBR
CECI
Dynamic
Dynamic
Program
routing
routing
Storage
name
Transactions
local
remote
Restarts violations
-------- ------------ ----------- ----------- ----------- ----------DFHEMTP
18
0
0
0
0
DFHEDAP
5
0
0
0
0
FISTPROG
2
0
0
0
0
DFHZXRE
1
0
0
0
0
DFHZATA
1
0
0
0
0
DFHZATD
1
0
0
0
0
DFHCRQ
1
0
0
0
0
DFHFCU
1
0
0
0
0
DFHGMM
1
0
0
0
0
DFHZNAC
1
0
0
0
0
DFHZATR
1
0
0
0
0
DFHZATS
0
0
0
0
0
DFHBRCP
0
0
0
0
0
DFHDBME
0
0
0
0
0
DFHDBDI
0
0
0
0
0
DFHDBIQ
0
0
0
0
0
DFHDBCON
0
0
0
0
0
DFHDBCT
0
0
0
0
0
DFHECSP
0
0
0
0
0
DFHEDAP
0
0
0
0
0
DFHEDAP
0
0
0
0
0
DFHDBDSC
0
0
0
0
0
DFHZATS
0
0
0
0
0
DFHEDFBR
0
0
0
0
0
DFHECIP
0
0
0
0
0
Tivoli Decision Support for z/OS Report: CICS807
Figure 62. Example of a CICS Transaction Usage report
The report contains this information:
Transaction ID
Name of the transaction.
Program name
Program to which CICS passes control when the transaction starts.
Transactions
Number of executions of this transaction.
Dynamic routing local
Number of times that this transaction, if it is capable of being routed
(having the DYnamic=YES CEDA parameter), was run locally.
Chapter 7. Reports
333
Reports in the CICS statistics component
Dynamic routing remote
Number of times that this transaction, if it is capable of being routed
(having the DYnamic=YES CEDA parameter), was run remotely.
Restarts
Restarts can occur for transactions that have RESTART=YES specified. This
is affected by any user code in the retry program DFHRTY.
Storage violations
If this is not zero, there is a serious problem, which not only threatens
performance but also the integrity of your data. Force CICS to take a dump
when this occurs by putting SVD=YES in the SIT. Violations are often
detected by comparing the eight-byte storage accounting areas at each end
of a storage accounting area when the storage is being released. If the two
areas are not identical, one has been overwritten. The violation is logged
against the transaction that owns the storage being released, but it is not
certain that this transaction is the cause of the violation.
CICS Program Usage
This report shows CICS/ESA and CICS/TS program statistics. It shows how much
time MVS spends loading programs. You should see that the most frequently used
programs are loaded only once, because CICS chooses the least recently used
programs when it removes programs from the program subpools. If frequently
used programs are being frequently loaded and removed, this suggests that virtual
storage is insufficient for the program subpools.
This information identifies the report:
334
Report ID
CICS808 (CICS808P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_S_PROGRAM_D (CICS_S_PROGRAM_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, Programs
Variables
MVS system ID, CICS system ID, From date, To date
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
CICS Program Usage
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
Most used programs
Avg
Fetch
fetch
time
time
Newcopy
Times
(seconds)
(sec)
count
removed
----------- -------- -------- -------0.03
0.03
0
0
0.08
0.08
0
0
0.03
0.03
0
0
0.01
0.01
0
0
0.05
0.05
0
0
0.01
0.01
0
0
0.13
0.13
0
0
Program
Times
Fetch
name
used
count
-------- -------- -------DFHDMP
2311
1
DFHAMP
2146
1
DFHPUP
1416
1
DFHEITMT
18
1
DFHEMTD
18
1
DFHEMTP
18
1
DFHZCQ
9
1
...
DFHCXCU
0
0
0.00
0.00
0
0
DFHDBAT
0
0
0.00
0.00
0
0
DFHDBCON
0
0
0.00
0.00
0
0
======== ======== =========== ======== ======== ========
6316
251
4.34
0.01
0
0
Tivoli Decision Support for z/OS Report: CICS808
Figure 63. Example of a CICS Program Usage report
The report contains this information:
Program name
Name of the program.
Times used
CICS does not know about branches to a loaded program. This counter is
incremented when the program in LINKed to, XCTLed to, or LOADed,
and when the program is the first program for a transaction. This is the
sum of LOAD_REQUESTS.
Fetch count
Number of times the program is loaded. This is the sum of FETCHES.
Fetch time (seconds)
Total time spent loading this program. This is the sum of FETCH_SEC.
Avg fetch time (sec)
Average time spent loading this program. This is calculated as
FETCH_SEC/FETCHES.
Newcopy count
Number of times a new copy of the program was loaded by operator
request. This is the sum of NEW_COPIES.
Times removed
Number of times CICS removed this program when not in use, to reclaim
space in the subpool.
CICS Dynamic Storage (DSA) Usage
This report shows CICS/ESA and CICS/TS dynamic storage area statistics. For
information on how to use this report, see “Monitoring storage use” on page 34.
This information identifies the report:
Report ID
CICS809 (CICS809P for CICS Partitioning feature)
Report group
CICS Reports
Chapter 7. Reports
335
Reports in the CICS statistics component
Source
CICS_S_STOR_DSA_D (CICS_S_STOR_DSA_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS
Variables
MVS system ID, CICS system ID, From date, To date
CICS Dynamic Storage (DSA) Usage
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
Pagepool
name
-------CDSA
ECDSA
ERDSA
EUDSA
UDSA
Free
Free
Largest
DSA
Cushion
storage storage
free
(bytes)
(bytes)
(bytes) (pct)
area
Getmains Freemains
--------- -------- --------- ------- --------- -------- --------1048576
65536
802816
76
765952
3695
3620
8388608
262144
7667712
91
7667712
8946
7252
3145728
262144
1302528
41
1290240
204
3
8388608
262144
8388608
100
8388608
1
1
4194304
65536
4186112
99
4182016
6
4
Tivoli Decision Support for z/OS Report: CICS809
Figure 64. Example of a CICS Dynamic Storage (DSA) Usage report
The report contains this information:
Pagepool name
Name of the pagepool.
DSA (bytes)
Maximum number of bytes in the subpool. This is the maximum of
DSA_BYTES.
Cushion (bytes)
Size of the storage cushion. This is the maximum of CUSHION_BYTES.
Free storage (bytes)
Smallest amount of free storage, in bytes. This is the minimum of
FREE_STOR_BYTES.
Free storage (pct)
Lowest percentage of free storage. This is the minimum of
FREE_STOR_PCT.
Largest free area
Minimum largest free area in the subpool, in bytes. This is the minimum of
LARGEST_FREE_AREA.
Getmains
Number of GETMAIN requests for this subpool.
Freemains
Number of FREEMAIN requests for this subpool.
CICS File Statistics
This report shows CICS/ESA and CICS/TS file statistics.
This information identifies the report:
336
Report ID
CICS810 (CICS810P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_FILE_D (CICS_S_FILE_DP for CICS Partitioning feature)
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Attributes
Statistics, CICS, File
Variables
MVS system ID, CICS system ID, From date, To date
CICS File Statistics
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
File
name
-------GHTIPO
GTSTFILE
Delete Delete
Get
Browse
Add
Update
req
req
VSAM
requests requests requests requests local
remote
EXCPs
-------- -------- -------- -------- ------ ------- ------18
5486
0
0
0
0
22
0
4
2000
0
0
0
2061
======== ======== ======== ======== ====== ======= =======
18
5490
2000
0
0
0
2083
Tivoli Decision Support for z/OS Report: CICS810
Figure 65. Example of a CICS File Statistics report
The report contains this information:
File name
Name of the file.
Get requests
Number of GET requests that were passed from the application interface to
file control. Invalid requests filtered out by the command interface are not
included. This is generally true for all counts of applications requests to
CICS.
Browse requests
Number of BROWSE requests.
Add requests
Number of ADD requests.
Update requests
Number of UPDATE requests.
Delete req local
Number of DELETE requests for a file on this system.
Delete req remote
Number of function-shipped DELETE requests.
VSAM EXCPs
Number of VSAM EXCPs issued, from VSAM_EXCP_REQ_DATA.
CICS ISC/IRC Function Shipping by Connection
This report shows CICS TS inter-region and intersystem statistics related to
function-shipping with and without channel option.
This information identifies the report:
Report ID
CICS833 (CICS833P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_INTERCOM_D (CICS_S_INTERCOM_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, IRC, ISC, Function, Shipping, Channel
Chapter 7. Reports
337
Reports in the CICS statistics component
Variables
Date, MVS system ID, CICS system ID, Connection name
CICS ISC/IRC Function Shipping by Connection
MVS ID = 'MV2C' CICS ID 'DFHXQ'
Date: '2005-05-01'
Connection
name
---------GHT00001
Function
Shipping
FC
-------0
Function
Shipping
IC
-------0
Function
Shipping
TD
-------0
Function
Shipping
TS
-------0
Function
Shipping
PC
-------0
--------CHANNEL---------
Function Function Function
Shipping Shipping Shipping
IC
TS
PC
-------- -------- -------0
0
0
Tivoli Decision Support for z/OS Report: CICS833
Figure 66. Example of a CICS ISC/IRC Function Shipping by Connection report
The report contains this information:
Connection name
Connection name. From CONNECTION_NAME.
Function Shipping FC
Number of file control requests for function shipping. From
FUNCTION_SHIPS_FC.
Function Shipping IC
Number of interval control requests for function shipping. From
FUNCTION_SHIPS_IC.
Function Shipping TD
Number of transient data requests for function shipping. From
FUNCTION_SHIPS_TD.
Function Shipping TS
Number of temporary storage requests for function shipping. From
FUNCTION_SHIPS_TS.
Function Shipping PC
Number of program control link requests for function shipping. From
PGM_CONTROL.
Channel
Function Shipping IC
Number of interval control requests for function shipping. From
FUNC_SHIPSCHN_IC.
Function Shipping TS
Number of temporary storage channel requests for function
shipping. From FUNC_SHIPSCHN_TS.
Function Shipping PC
Number of program control LINK requests, with channels, for
function shipping. From FUNC_SHIPCHN_PC.
CICS ISC/IRC Global
This report shows global CICS/ESA and CICS/TS interregion and intersystem
statistics. CICS has mechanisms to improve the efficiency of authorizing remote
user access, and this report shows how much this mechanism is being used. The
first three columns help in tuning the ISRDELAY parameter of the SIT, and the last
three columns help in the tuning of the PVDELAY parameter.
338
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
This information identifies the report:
Report ID
CICS811 (CICS811P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_S_INTERCOM_D (CICS_S_INTERCOM_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, IRC, ISC, Global
Variables
MVS system ID, CICS system ID, From date, To date
CICS ISC/IRC Global
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
Reuse
Signon
Entries
time
Signon reuse
Entries timed
avg
Signon
timed
avg
reused
out
(sec) reuse
out
(sec)
------- ------- -------- ------- --------- ------0
0
0.0
0
0
0.0
Tivoli Decision Support for z/OS Report: CICS811
Figure 67. Example of a CICS ISC/IRC Global report
The report contains this information:
Entries reused
Number of times user IDs were reused without referring an external
security manager.
Entries timed out
Number of times that user IDs signed on to this remote system were timed
out.
Reuse time avg (sec)
Average time between each reuse of user IDs signed on to this remote
system, in seconds. This is calculated as REUSE_TIME_SEC/
RECORD_GLOBAL_CNT.
Signon reuse
Number of times user IDs in the persistent verification list were used
without referencing an external security manager.
Signon timed out
Number of entries in the persistent verification list of this remote system
that were timed out.
Signon reuse avg (sec)
Average time between the reuse of entries in the persistent verification list
of this remote system. This is calculated as SIGNON_REUSE_SEC/
RECORD_GLOBAL_CNT.
CICS ISC/IRC Mode Entries
This report shows CICS/ESA and CICS/TS statistics for APPC (LU 6.2)
connections.
Chapter 7. Reports
339
Reports in the CICS statistics component
A program issues an ALLOCATE command to establish an LU6.2 session. When
the program specifies the system and log-mode group, the ALLOCATE is specific;
otherwise, the program can leave it to CICS to find one that is suitable.
When allocating a session, it is more efficient to use a contention winner (or
receive) session, if possible. If a contention loser (or send) session must be used,
CICS sends a BID to the session partner and waits for a positive response to the
BID before letting the application continue. But if a contention winner session
becomes available while CICS waits for the BID response, CICS discontinues its
attempt to use the contention loser session and uses the newly available contention
winner session instead.
CICS ISC/IRC Mode Entries
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
APPC
system
name
-----TR45
Alloc
Mode requests
name
(peak)
-------- -------TYRI0004
0
Alloc
Queued
Failed
Loser
Winner
requests alloc
alloc
ATI
ATI
(total) requests requests requests requests
--------- -------- -------- -------- -------0
0
0
0
0
Tivoli Decision Support for z/OS Report: CICS812
Figure 68. Example of a CICS ISC/IRC Mode Entries report
This information identifies the report:
Report ID
CICS812 (CICS812P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_S_INTERCOM_D (CICS_S_INTERCOM_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, IRC, ISC, Mode
Variables
MVS system ID, CICS system ID, From date, To date
The report contains this information:
APPC system name
Connection name, from APPC_SYSTEM_NAME.
Mode name
Logmode name, from MODE_NAME.
Alloc requests (peak)
Peak allocate requests queued for this mode group, from
ALLOCATES_PEAK.
Alloc requests (total)
Number of times a program issued a specific ALLOCATE command for
this mode group, excluding commands failing basic validation
(SYSIDERR). This is the sum of ALLOC_SPEC_REQ.
Queued alloc requests
Maximum number of times a program issued a specific ALLOCATE
command (without NOQUEUE) and there were no bound contention
winners available for this more group. This is the maximum of
ALLOC_Q_SPEC_REQ.
340
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Failed alloc requests
Number of times a program issued a specific ALLOCATE command for
this mode group, and got an error. This is the sum of
ALLOC_F1_SPEC_REQ and ALLOC_F2_SPEC_REQ.
Loser ATI requests
Number of times a contention-loser APPC session was used. This is the
sum of ATI_LOSER_REQ.
Winner ATI requests
Number of times a contention-winner APPC session was used. This is the
sum of ATI_WINNER_REQ.
CICS ISC/IRC System Entries by Connection
This report shows CICS/ESA and CICS/TS interregion and intersystem statistics. It
differs from “CICS ISC/IRC Mode Entries” on page 339 in that it is for non-LU6.2
sessions, which are identified only by connection name (not by a combination of
connection name and log-mode group). This is multiregion operation (MRO) using
interregion communication (IRC) and LU6.1 intersystem communication (ISC).
This information identifies the report:
Report ID
CICS813 (CICS813P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_INTERCOM_D (CICS_S_INTERCOM_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, IRC, ISC, System
Variables
MVS system ID, CICS system ID, From date, To date
CICS ISC/IRC System Entries by Connection
MVS ID ='IPO2'
CICS ID ='CSRT5'
Date: '2000-05-01' to '2000-05-02'
Connection
name
---------GHT00001
ATI
loser
request
------0
ATI
winner
Bids
Trans
Losers Winners
request
sent Allocates routings
peak
peak
------- ------ --------- -------- ------- ------0
0
0
0
0
0
Tivoli Decision Support for z/OS Report: CICS813
Figure 69. Example of a CICS ISC/IRC System Entries by Connection report
The report contains this information:
Connection name
Connection name, from CONNECTION_NAME.
ATI loser requests
Number of times a receive session was used. This is the sum of
ATI_REQ_LOSERS.
ATI winner requests
Number of times a send session was used. This is the sum of
ATI_REQ_WINNERS.
Chapter 7. Reports
341
Reports in the CICS statistics component
Bids sent
Number of times CICS sent a BID to use a contention loser session. This is
the sum of BIDS_SENT.
Allocates
Number of times a program issued an ALLOCATE command, not
including commands failing basic validation (SYSIDERR). This is the sum
of ALLOCATES.
Trans routings
Number of transaction routing commands (where a transaction is defined
as remote or is dynamically routed). This is not valid for LU 6.1. This
counter is incremented on both systems (sending and receiving). This is the
sum of TRANS_ROUTINGS. Note that START commands are not counted
here, but in FUNCTION_SHIPS_IC, which is not shown on this report.
Trans routings is a count of all other types of transaction routing, for
example, where a transaction is defined as being remote or is dynamically
routed.
Losers peak
Peak number of contention loser sessions, from LOSERS_PEAK.
Winners peak
Peak number of contention winner sessions, from WINNERS_PEAK.
CICS TS Recovery Manager
This report shows CICS TS recovery manager statistics that detail the syncpoint
activity of all the transactions in the system. From this statistics report, you can
assess the impact of shunted UOWs. Shunted UOWs are units of work that have
suffered an indoubt failure and that are waiting for resynchronization with their
recovery coordinator or for the problem with the resources to be resolved. Shunted
UOWs still hold locks and enqueues until they are resolved.
This information identifies the report:
Report ID
CICS814 (CICS814P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_RECOV_MGR_D (CICS_S_RECO_MGR_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, Recovery, Manager
Variables
MVS system ID, CICS system ID, From date, To date
CICS TS Recovery Manager
MVS ID ='VSG1'
CICS ID ='A6POCM01'
Date: '2000-02-08' to '2000-02-08'
Time
shunted
Syncpoints Syncpoints
indoubt
forward backward Resyncs failure
---------- ---------- ------- ------1.020E+04 1.410E+02 0.000 0.000
Time
shunted
commit
back
failure
------0.000
Indoubt
action
forced
trandef
------0.000
Indoubt
action
forced
timeout
------0.000
Indoubt
action
forced
nowait
------0.000
Indoubt
action
forced
operator
-------0.000
Indoubt
action
forced
tdqueues
-------0.000
Tivoli Decision Support for z/OS Report: CICS814
Figure 70. Example of a CICS TS Recovery Manager report
The report contains this information:
342
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Indoubt
action
forced
LU61conn
-------0.000
Indoubt
action
forced
MROconn
------0.000
Indoubt
action
Indoubt
forced
action
RMIexits mismatches
-------- ---------0.000
0.000
Reports in the CICS statistics component
Syncpoints forward
Number of syncpoints that were issued.
Syncpoints backward
Number of syncpoint rollbacks that were issued.
Resyncs
Number of resynchronizations that were issued.
Time shunted indoubt failure
Total time that UOWs were shunted for indoubt failure.
Time shunted commit back failure
Total time that current UOWs were shunted for commit/backout failure.
Indoubt action forced trandef
Number of forced indoubt action resolutions due to the transaction
definition specifying that it cannot support indoubt waiting.
Indoubt action forced timeout
Number of forced indoubt action resolutions due to the indoubt waits
timing.
Indoubt action forced nowait
Number of forced indoubt action resolutions due to a recoverable resource
or resource manager coordinator being unable to support indoubt waiting.
Indoubt action forced operator
Number of forced indoubt action resolutions due to the operator canceling
the wait for indoubt resolution.
Indoubt action forced tdqueues
Number of resolutions due to an attribute WAIT=NO in the definition of
the recoverable transient data queue.
Indoubt action forced LU61conn
Number of forced indoubt action resolutions (for LU61 connections) due to
a recoverable resource or resource manager coordinator being unable to
support indoubt waiting.
Indoubt action forced MROconn
Number of forced indoubt action resolutions (for MRO connections) due to
a recoverable resource or resource manager coordinator being unable to
support indoubt waiting.
Indoubt action forced RMIexits
Number of forced indoubt action resolutions (for RMI exits) due to a
recoverable resource or resource manager coordinator being unable to
support indoubt waiting.
Indoubt action mismatches
Number of forced indoubt action resolutions that a participating resource
manager coordinator solved in a different manner from CICS.
CICS TS Enqueue Manager
This report shows CICS TS statistics on the enqueue activity for each enqueue pool
ID.
This information identifies the report:
Report ID
CICS815 (CICS815P for CICS Partitioning feature)
Report group
CICS reports
Chapter 7. Reports
343
Reports in the CICS statistics component
Source
CICS_S_ENQUE_MGR_D (CICS_S_ENQU_MGR_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, Enqueue, Manager
Variables
MVS system ID, CICS system ID, From date, To date
CICS TS Enqueue Manager
MVS ID ='VSG1'
CICS ID ='A6PO0A11'
Date: '1999-02-08' to '2000-02-08'
Enqueue
Enqueue
Enqueue
poolname
issued
waited
-------- ---------- ---------EXECADDR 0.000
0.000
EXECSTRN 0.000
0.000
FCDSESWR 0.000
0.000
FCDSLDMD 0.000
0.000
FCDSRECD 0.000
0.000
FCDSRNGE 0.000
0.000
FCFLRECD 0.000
0.000
FCFLUMTL 0.000
0.000
JOURNALS 1.000
0.000
KCADDR
3.260E+02 1.200E+01
KCSTRING 4.410E+02 0.000
LOGSTRM 1.000
0.000
TDNQ
0.000
0.000
TSNQ
0.000
0.000
Avg
enqueue
wait time
--------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
1.033
0.000
0.000
0.000
0.000
Tot
enqueue
retained
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Avg
enqueue
retention
time
--------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Curr
enqueue
retained
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Curr avg
enqueue
retention
time
--------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Enqueue
rejected
enqbusy
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Enqueue
rejected
retained
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Waiting
enqueues
rejected
retained
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Waiting
enqueues
purged
operator
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Waiting
enqueues
purged
timeout
-------0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Tivoli Decision Support for z/OS Report: CICS815
Figure 71. Example of a CICS TS Recovery Manager report
The report contains this information:
Enqueue poolname
Enqueue pool name.
Enqueue issued
Number of enqueue requests that were issued.
Enqueue waited
Number of enqueue requests that have waited.
Avg enqueue wait time
Average enqueue wait time. Calculated as Sum(Enq_Waited_Time) ÷
Sum(Enq_Waited).
Tot enqueue retained
Total number of enqueue requests that were retained.
Avg enqueue retention time
Average enqueue retention time. Calculated as Sum(Enq_Retn_Tot_Time) ÷
Sum(Enq_Retn_Tot).
Curr enqueue retained
Current number of enqueue requests that were retained.
Curr avg enqueue retention time
Current average enqueue retention time. Calculated as
Sum(Enq_Retn_Cur_Time) ÷ Sum(Enq_Retn_Cur).
Enqueue rejected enqbusy
Number of enqueue requests that were immediately rejected (ENQBUSY
response).
Enqueue rejected retained
Number of retained enqueue requests that were immediately rejected.
344
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Waiting enqueues rejected retained
Number of retained enqueue requests that are awaiting rejection.
Waiting enqueues purged operator
Number of enqueue requests that are awaiting rejection because of
operator intervention.
Waiting enqueues purged timeout
Number of enqueue requests that are awaiting rejection because of timeout.
CICS TS Logstreams
This report shows CICS TS statistics on the data written to each logstream that can
be used to analyze the activity of a single region. Logstream statistics contain data
about the use of each logstream including the following:
v
v
v
v
The
The
The
The
number
number
number
number
of
of
of
of
write requests to the logstream
bytes written to the logstream
logstream buffer waits
logstream browse and delete requests
This information identifies the report:
Report ID
CICS816 (CICS816P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_LOGSTREAM_D (CICS_S_LOGSTREA_DP)
Attributes
Statistics, CICS, TS, Logstreams
Variables
MVS system ID, CICS system ID, From date, To date
CICS TS Logstreams
MVS ID ='VSG1'
CICS ID ='A6PO0A11'
Date: '1999-02-08' to '2000-02-08'
Logstream
name
----------------------TEAM0.A6PO0A11.DFHLOG
TEAM0.A6PO0A11.DFHSHUNT
TEAM0.DFHJ02
Write
requests
--------1.105E+05
0.000
3.936E+03
Bytes
written
--------3.308E+07
0.000
1.123E+06
Average
bytes
----------2.994E+0200
0.00000
2.854E+0200
Buffer
full
waits
-----0.000
0.000
0.000
Buffer
appends
--------1.116E+05
0.000
7.604E+03
Retry
errors
-----0.000
0.000
0.000
Force
waits
--------3.500E+01
0.000
0.000
Peak
waiters
-------1.103E+0
0.000
0.000
Browse
starts
--------2.610E+02
0.000
0.000
Browse
reads
--------1.600E+02
0.000
0.000
Stream
deletes
--------2.700E+01
0.000
0.000
Tivoli Decision Support for z/OS Report: CICS816
Figure 72. Example of a CICS TS Logstream report
The report contains this information:
Logstream name
Name of the logstream.
Write requests
Number of ISXGWRITE requests issued to this logstream.
Bytes written
Number of bytes written to this logstream.
Average bytes
Average number of bytes written to this logstream for each request.
Calculated as Sum(Bytes_Written) ÷ Sum(Logstream_Wrt_Req).
Chapter 7. Reports
345
Reports in the CICS statistics component
Buffer full waits
Number of times that buffer full has occurred for this logstream.
Buffer appends
Number of times that a journal record was successfully appended to the
current logstream buffer.
Retry errors
When a block of data was being written to the logstream, the number of
times that MVS system logger errors occurred that can be retried.
Force waits
Total number of force waits for this logstream.
Peak waiters
Peak number of force waiters for this logstream.
Browse starts
Number of browse start requests issued for this logstream.
Browse reads
Number of browse read requests issued for this logstream.
Stream deletes
Number of delete (IXGDELET) requests issued for this logstream.
CICS DB2 Connection: TCB Statistics
This report shows CICS TS statistics on TCB activity related to DB2 connection.
This information identifies the report:
Report ID
CICS817 (CICS817P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_DB2CONN_D (CICS_S_DB2CONN_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, DB2, Connection, TCB
Variables
MVS system ID, CICS system ID, From date, To date
CICS DB2 Connection: TCB Statistics
MVS ID ='MV26'
CICS ID ='IYCQCTS6'
Date: '2003-02-08' to '2004-02-08'
DB2
conn
name
-------JRBJRB
Peak
Tot DB2
tasks
DB2
connection
TCB
TCB
on
SYSID
time
limit
peak TCB readyq
----- ----------- ---------- ---------- ---------DC26
2 5.000E+01 0.000
0.000
Tivoli Decision Support for z/OS Report: CICS817
Figure 73. Example of a CICS DB2 Connection: TCB Statistics report
The report contains this information:
DB2 conn name
Name of the installed DB2CONN.
346
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
DB2 SYSID
The DB2 system ID specified in this DB2CONN. If the system ID has
changed, it is the last setting of SYSID.
Tot DB2 connection time
Total amount of time (in hours) that CICS was connected to the DB2
subsystem specified in this DB2CONN. Calculated as
(DB2_GMT_DISC_TIME − DB2_GMT_CONN_TIME), if greater than 0.
Otherwise, calculated as (DB2_LOC_DISC_TIME −
DB2_LOC_CONN_TIME), if greater than 0. If none of the fields are
meaningful, the value will be set to 0.
TCB limit
The TCBLIMIT value that was set in the DB2CONN. If the TCBLIMIT has
changed, it is the last setting of TCBLIMIT.
TCB peak
Peak number of subtask TCBs that are attached to service DB2 requests.
Peak tasks on TCB readyq
Peak number of CICS tasks that are queued waiting for a DB2 subtask TCB
to become available.
CICS DB2 Connection: Buffer Pool Statistics
This report shows CICS TS statistics on Buffer Pool activity related to DB2
connection.
This information identifies the report:
Report ID
CICS818 (CICS818P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_DB2CONN_D (CICS_S_DB2CONN_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, DB2, Connection, Buffer, Pool
Variables
MVS system ID, CICS system ID, From date, To date
CICS DB2 Connection: BUFFER POOL Statistics
MVS ID ='VSG1'
CICS ID ='A6PO0A11'
Date: '2003-02-08' to '2004-02-08'
DB2
conn
name
-------DB2
DB2
pool
DB2 DB2
plan
SYSID Release name
----- ------- -------DB1C 0510
""""""""
Tot
DB2
calls
Tot
Tot
pool
using
Tot
Tot
Tot poolthread
Tot
Tot
pool
plex
pool poolthread poolthread poolthread
single poolthread poolthread
thread
name
thread
signons
commits
aborts
phases
reuse terminates
waits
-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------DSNCUEXT 6.369E+05 8.000
0.000
8.000E+01 1.496E+04 1.200E+01 1.502E+04 1.200E+01
Peak
Peak
pool
Tot
tasks
Pool
thread
Peak
pool
on pool
thread limit
inuse pool tasks
tasks
readyq
------------ ---------- ---------- ---------- ---------8.000
8.000
2.000E+01 1.504E+04 1.200E+01
Tivoli Decision Support for z/OS Report: CICS818
Figure 74. Example of a CICS DB2 Connection: Buffer Pool Statistics report
The report contains this information:
DB2 conn name
Name of the installed DB2CONN.
Chapter 7. Reports
347
Reports in the CICS statistics component
DB2 SYSID
The DB2 system ID specified in this DB2CONN. If the system ID has
changed, it is the last setting of SYSID.
DB2 release
The DB2 version and release for this DB2CONN. (It can be blank if not
present in the table.)
DB2 pool plan name
Name of the plan being used for the pool. If a dynamic plan exit is being
used for the pool, this field is null.
DB2 pool plex name
Name of the dynamic plan exit to be used for the pool. If a static plan is
being used for the pool, this field contains nulls.
Tot calls using pool thread
Total number of SQL calls made using pool threads.
Tot poolthread signons
Total number of DB2 signons performed for pool threads.
Tot poolthread commits
Number of 2-phase commits that are performed for UOWs using pool
threads.
Tot poolthread aborts
Total number of UOWs (using pool threads) that were rolled back.
Tot poolthread single phases
Total number of UOWs (using pool threads) that used single-phase
commit, either because they were R/O UOWs or because DB2 was the
only recoverable resource updated in the UOWs.
Tot poolthread reuse
Total number of times that CICS transactions using the pool were able to
reuse a created DB2 thread. This count includes transactions that overflow
to the pool so as to acquire a thread and reuse an existing thread.
Tot poolthread terminates
Total number of terminate thread requests that were made to DB2 for pool
threads. This count includes pool threads used by transactions that
overflow to the pool.
Tot poolthread waits
Total number of times that all available threads in the pool were busy and
a transaction had to wait for a thread to become available. This count
includes transactions that overflow to the pool to acquire a thread and that
have to wait for a pool thread.
Pool thread limit
Thread limit value for the pool. If the pool thread limit has changed, it is
the last setting of the pool thread limit.
Peak pool thread inuse
Peak number of active pool threads.
Peak pool tasks
Peak number of CICS tasks that have used a pool thread.
Tot pool tasks
Total number of completed tasks that have used a pool thread.
348
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Peak tasks on pool readyq
Peak number of CICS tasks that waited for a pool thread to become
available.
CICS DB2 Connection: Command Statistics
This report shows CICS TS statistics on Command activity related to DB2
connection.
This information identifies the report:
Report ID
CICS819 (CICS819P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_DB2CONN_D (CICS_S_DB2CONN_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, DB2, Connection, Command
Variables
MVS system ID, CICS system ID, From date, To date
CICS DB2 Connection: COMMAND Statistics
MVS ID ='VSG1'
CICS ID ='A6PO0A12'
Date: '2003-02-21' to '2004-02-21'
DB2
conn
name
-------DB2
DB2
DB2
DB2 DB2
comd
SYSID release authid
----- ------- -------DB1C """"
""""""""
DB1C 0510
""""""""
Calls
DB2
using Command
Command
Command
Command
Peak
comd
command thread
threads
threads
thread
command
authtype threads signons terminated overflows
limit
threads
-------- ------- ------- ---------- ---------- ---------- ---------USERID
0.000 0.000 0.000
1.000
0.000
0.000
USERID
0.000 0.000 0.000
1.000
0.000
0.000
Tivoli Decision Support for z/OS Report: CICS819
Figure 75. Example of a CICS DB2 Connection: Command Statistics report
The report contains this information:
DB2 conn name
Name of the installed DB2CONN.
DB2 SYSID
The DB2 system ID specified in this DB2CONN. If the system ID has
changed, it is the last setting of SYSID.
DB2 release
The DB2 version and release for this DB2CONN. (It can be blank if not
present in the table.)
DB2 comd authid
Static ID to be used for DB2 security checking of command threads. If an
Authtype is being used for command threads, this field contains nulls.
DB2 comd authtype
Type of ID to be used for DB2 security checking of command threads. If an
Authid is being used for command threads, this field contains nulls.
Calls using command threads
Total number of DB2 commands that are issued using the DSNC
transaction.
Chapter 7. Reports
349
Reports in the CICS statistics component
Command thread signons
Total number of DB2 signons performed for command threads.
Command threads terminated
Total number of terminate thread requests made to DB2 for command
threads.
Command threads overflows
Number of times that a DSNC DB2 resulted in a pool thread being used
because the number of active command threads exceeded the command
threads limit.
Command thread limit
Maximum number of command threads that are allowed.
Peak command threads
Peak number of active command threads.
CICS DB2 Entries: Resource Info
This report shows CICS TS statistics on Resource information related to DB2
entries.
This information identifies the report:
Report ID
CICS820 (CICS820P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_DB2ENTRY_D (CICS_S_DB2ENTRY_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, DB2, Entries, Resource
Variables
MVS system ID, CICS system ID, From date, To date
The report ( Figure 76 on page 351) contains this information:
DB2 entry name
Name of the installed DB2ENTRY.
DB2 plan name
Name of the plan being used for this DB2ENTRY. If a dynamic plan exit is
being used for the DB2ENTRY, this field is null.
DB2 planexit name
Name of the dynamic plan exit to be used for this DB2ENTRY. If a static
plan is being used for the DB2ENTRY, this field is null.
DB2 authid
Static ID that is to be used for DB2 security checking of this DB2ENTRY.
DB2 authtype
Type of ID that is to be used for DB2 security checking of this DB2ENTRY.
DB2 accountr
Frequency of DB2 accounting records that are to be produced for
transactions using this DB2ENTRY.
DB2 threadwa
Specifies whether transactions should wait for a thread abend or overflow
to the pool if the number of active threads for this DB2ENTRY exceeds its
thread limit.
350
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
DB2 priority
Priority of the DB2ENTRY thread subtasks relative to the CICS main task.
CICS DB2 Entries: Resource Info
MVS ID ='MV26'
CICS ID ='IYCQCTS6'
Date: '2003-03-21' to '2003-12-03'
DB2
entry
name
-------A2000
A2001
A2002
A2003
A2004
A2005
A2006
A2007
A2008
A2009
A2010
A2011
A2012
A2013
A2014
A2015
A2016
A2017
A2018
A2019
A2020
A2021
A2022
A2023
A2024
A2025
A2026
A2027
A2028
A2029
A2030
A2031
A2032
A2033
A2034
A2035
A2036
A2037
A2038
A2039
A2040
A2041
A2042
A2043
A2044
A2045
A2046
A2047
A2048
A2049
A2050
DB2
plan
name
-------RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
RDORCT05
DB2
planexit
name
-------""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
DB2
authid
-------""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
""""""""
DB2
authtype
-------USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
USERID
DB2
accountr
-------NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
NONE
DB2
threadwa
-------POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
POOL
DB2
priority
------HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
HIGH
Tivoli Decision Support for z/OS Report: CICS820
Figure 76. Example of a CICS DB2 Entries: Resource Info report
CICS DB2 Entries: Request Statistics
This report shows CICS TS statistics on Requests related to DB2 entries.
This information identifies the report:
Report ID
CICS821 (CICS821P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_DB2ENTRY_D (CICS_S_DB2ENTRY_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, DB2, Entries, Requests
Variables
MVS system ID, CICS system ID, From date, To date
Chapter 7. Reports
351
Reports in the CICS statistics component
CICS DB2 Entries: Requests Statistics
MVS ID ='MV2C'
CICS ID ='IYK2Z1V2'
Date: '2003-03-21' to '2003-12-03'
DB2
Calls
DB2entry DB2entry DB2entry
thread
entry
using
DB2entry
DB2entry
DB2entry
single
thread
thread
waits
name
DB2entry
signons
commits
aborts
phase
reuse
term overflows
-------- ---------- ---------- ---------- ---------- ---------- --------- ---------- ---------SAMPLE
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
SAMPLE2
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Tivoli Decision Support for z/OS Report: CICS821
Figure 77. Example of a CICS DB2 Entries: Requests Statistics report
The report contains this information:
DB2 entry name
Name of the installed DB2ENTRY.
Calls using DB2entry
Number of DB2 calls that are made using a thread from this DB2ENTRY.
DB2entry signons
Number of DB2 signons that are performed for threads of this DB2ENTRY.
DB2entry commits
Number of 2-phase commits that are performed for UOWs using threads
from this DB2ENTRY.
DB2entry aborts
Number of UOWs (using this DB2ENTRY) that were rolled back.
DB2entry single phase
Number of UOWs (using the DB2ENTRY) that used single-phase commit,
either because they were R/O UOWs or because DB2 was the only
recoverable resource updated in the UOWs.
DB2entry thread reuse
Number of times that CICS transactions, using the DB2ENTRY, were able
to use an existing created DB2 thread.
DB2entry thread term
Number of terminate thread requests made to DB2 for threads of this
DB2ENTRY.
DB2entry thread waits overflows
Number of times that all available threads in the DB2ENTRY were busy
and a transaction had to wait for a thread to become available or overflow
to the pool and use a pool thread instead.
CICS DB2 Entries: Performance Statistics
This report shows CICS TS Performance statistics related to DB2 entries.
This information identifies the report:
352
Report ID
CICS822 (CICS822P for CICS Partitioning feature)
Report group
CICS reports
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Source
CICS_S_DB2ENTRY_D (CICS_S_DB2ENTRY_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, DB2, Entries, Performance
Variables
MVS system ID, CICS system ID, From date, To date
CICS DB2 Entries: Performance Statistics
MVS ID ='MV2C'
CICS ID ='IYK2Z1V2'
Date: '2003-03-21' to '2003-12-03'
DB2
DB2entry
DB2entry
DB2entry
DB2entry
DB2entry
DB2entry
DB2entry
DB2entry
DB2entry
DB2entry
entry
thread
thread
thread protected protected protected
task
task
curtasks peaktasks
name
limit
cur
peak
thrlimit
thrcur
thrpeak
peak
tot on readyq on readyq
-------- ---------- ---------- ---------- ---------- ---------- ----------- ---------- ---------- ---------- ----------SAMPLE
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
SAMPLE2
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
0.000
Tivoli Decision Support for z/OS Report: CICS822
Figure 78. Example of a CICS DB2 Entries: Performance Statistics report
The report contains this information:
DB2 entry name
Name of the installed DB2ENTRY.
DB2entry thread limit
Maximum number of threads that are allowed for the DB2ENTRY.
DB2entry thread cur
Current number of active threads that are using this DB2ENTRY.
DB2entry thread peak
Peak number of active threads for this DB2ENTRY.
DB2entry protected thrlimit
Maximun number of protected threads that are allowed for this
DB2ENTRY.
DB2entry protected thrcur
Current number of protected inactive threads for this DB2ENTRY.
DB2entry protected thrpeak
Peak number of protected inactive threads for this DB2ENTRY.
DB2entry task peak
Peak number of CICS tasks that are using this DB2ENTRY.
DB2entry task tot
Current total number of tasks that have used this DB2ENTRY.
DB2entry curtasks on readyq
Current number of CICS tasks that are waiting for a thread to become
available on this DB2ENTRY.
DB2entry peaktasks on readyq
Peak number of CICS tasks that waited for a thread to become available on
this DB2ENTRY.
CICS Shared TS queue server: Buffer Pool Statistics
This report shows CICS Shared TS queue server statistics related to buffer pool.
These statistics are for the queue index pool that is used to read and write queue
Chapter 7. Reports
353
Reports in the CICS statistics component
index entries and associated data, if the total queue size is not greater than 32
kilobytes. This report describes the state of the buffer pool.
This information identifies the report:
Report ID
CICS823 (CICS823P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TS_BPOOL_D (CICS_S_TS_BPOOL_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TS, Queue, Server, Bufferpool
Variables
MVS system ID, CICS system ID, From date, To date
CICS Shared TS queue server: BPOOL Statistics
MVS ID ='MV2C'
CICS ID ='DFHXQ'
Date: '2000-03-21' to '2000-03-25'
Max
Pool
buffers
Buffers
Get
Put
Keep
Free
Purge
Got
Got
Got
Got
buffers
used
reused
buffers
buffers
buffers
buffers
buffers
hit
free
new
LRU
---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ------ -----1.200E+03 3.000
0.000
4.780E+02 4.380E+02 0.000
4.000E+01 0.000
4.380E+02 3.200E+01 8.000 0.000
Get
Not
Not
Not
pool
waiting
No
freed
purged
owned
lock
buffer
buffer
buffer
buffer
buffer
waits
lock
--------- --------- --------- --------- --------- ---------0.000
0.000
0.000
0.000
0.000
2.000
Tivoli Decision Support for z/OS Report: CICS823
Figure 79. Example of a CICS Shared TS queue server: Buffer Pool Statistics report
The report contains this information:
Pool buffers
Number of buffers in the pool.
Max buffers used
Maximum number of buffers already used (not affected by reset).
Buffers reused
Number of valid buffers on LRU chain to allow reuse.
Get buffers
Number of requests to get a buffer.
Put buffers
Number of requests to put back buffer with valid contents.
Keep buffers
Number of keep requests (put back buffer as modified).
Free buffers
Number of requests to put back a buffer as empty.
Purge buffers
Number of requests to discard contents of a previously valid buffer.
Got hit
Number of requests to put back a buffer with valid contents.
Got free
Number of requests to put back a buffer with modified contents.
(Currently this function is not used by the queue server.)
354
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Got new
Number of requests that obtained a previously unused buffer.
Got LRU
Number of requests that caused a discard and reuse of the oldest valid
buffer.
No buffer
Number of GET requests that returned no buffer.
Not freed buffer
Number of errors caused by requests that attempted to release a buffer
they did not own. (This can occur during error recovery.)
Not purged buffer
Number of errors caused by purge requests that did not find a matching
buffer.
Not owned buffer
Number of errors caused by purge requests that found a buffer owned by
another task.
Pool lock waits
Number of waits on buffer pool lock.
Get waiting buffer lock
Number of GET waits on buffer lock.
CICS Shared TS queue server: Storage Statistics
This report shows CICS Shared TS queue server statistics related to storage. These
statistics are for the named storage page pool (in the AXMPGANY and
AXMPGLOW) produced since the most recent statistics. Each of the storage
statistics is shown in kilobytes and as a percentage of the total size.
This information identifies the report:
Report ID
CICS824 (CICS824P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TS_STOR_D (CICS_S_TS_STOR_DP for CICS Partitioning
feature)
Attributes
Statistics, CICS, TS, Queue, Server, Storage
Variables
MVS system ID, CICS system ID, From date, To date
CICS Shared TS queue server: Storage Statistics
MVS ID ='MV2C'
CICS ID ='DFHXQ'
Date: '2000-03-21' to '2000-03-25'
Totpage
Storage
Storage
in
Storage
Storage
Storage
Storage
Storage
Storage
pool
pool
storage
get
get
release
get
release
get
name
size
pool
reqs
fails
reqs
fails
reqs
retries
-------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------AXMPGANY 3.165E+07 7.726E+03 8.690E+02 5.170E+02 0.000
5.170E+0 0.000
0.000
AXMPGLOW 4.506E+05 1.100E+02 9.000
0.000
0.000
0.000
0.000
0.000
Tivoli Decision Support for z/OS Report: CICS824
Figure 80. Example of a CICS Shared TS queue server: Storage Statistics report
The report contains this information:
Chapter 7. Reports
355
Reports in the CICS statistics component
Storage pool name
Name of the storage pool. AXMPGANY (for LOC=ANY storage pool) or
AXMPGLOW (for LOC=BELOW storage pool).
Storage pool size
Total size of the storage pool.
Totpage in storage pool
Total pages in the storage pool.
Storage get requests
Number of storage GET requests.
Storage get fails
Number of times that a storage request was unable to obtain the requested
amount of storage even after a retry.
Storage release reqs
Number of requests to release storage within the pool.
Storage get retries
Number of times that a storage request initially failed and was retried after
merging any adjacent small free areas to form larger areas.
CICS TCP/IP Global statistics
This report shows CICS TCP/IP Global statistics.
This information identifies the report:
Report ID
CICS832 (CICS832P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_GLB_TCPIP_D (CICS_S_GLB_TCP_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, TCPIP, Global
Variables
Date, MVS system ID, CICS system ID
CICS TCP/IP Global Statistics
MVS ID ='MV2C'
CICS ID ='DFHXQ'
Date: '2005-05-01'
SSLCACHE
setting
--------CICS
Inbound
sockets
-------28
Outbound
sockets
-------0
Persistent
Outbound
sockets
---------0
MAXSOCKETS
limit
--------24
MAXSOCKETS
reached
---------8
Create
Create MAXSOCKETS
sockets
sockets delay
timed out delayed time (sec)
--------- ------- ---------0
0
0
Tivoli Decision Support for z/OS Report: CICS832
Figure 81. Example of a CICS Global Statistics report
The report contains this information:
SSLCACHE setting
Reports whether SSL caching is taking place locally within a CICS region,
or across a sysplex. From SSLCACHE_SETTING.
Inbound sockets
Current number of inbound sockets. Calculated as maximum of
IN_SOCK_CUR.
356
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Outbound sockets
Number of non-persistent inbound sockets. Calculated as maximum of
OUT_SOCK_CUR.
Persistent Outbound sockets
Number of persistent inbound sockets. Calculated as maximum of
OUT_PSOCK_CUR.
MAXSOCKETS limit
The maximum number of IP sockets that can be managed by the CICS
sockets domain. From MAXSOCKETS.
MAXSOCKETS reached
Number of times the MAXSOCKETS value was reached. From
MAXSOCKETS_REACHED.
Create Socket timed out
Number of create socket requests that were timed out whilst delayed
because the system had reached the MAXSOCKETS limit. From
TOUT_MAXSOCKETS.
Create Socket delayed
Number of create socket requests delayed because the system was at the
MAXSOCKETS limit. From DLY_AT_MAXSOCKETS.
MAXSOCKETS delay time (sec)
Time that create socket requests were delayed because the system had
reached the MAXSOCKETS limit. From MAXSOCK_DLY_TIME.
CICS TCP/IP Service Statistics
This report shows CICS TCP/IP Service statistics.
This information identifies the report:
Report ID
CICS825 (CICS825P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TCPIP_T (CICS_S_TCPIP_TP for CICS Partitioning feature)
Attributes
Statistics, CICS, TCPIP
Variables
Date, MVS system ID, CICS system ID
The report contains this information:
TCPIP service name
Name of the TCP/IP service installed.
Port number
Number of the port on which CICS is listening on behalf of this service.
IP address
The TCP/IP address defined for the TCP/IP stack used for this TCP/IP
service.
SSL type
Level of secure sockets being used for the service.
SSL encryption
The level of SSL encryption support that applies to the TCP/IP service.
From PRIVACY.
Chapter 7. Reports
357
Reports in the CICS statistics component
Authentication Scheme
The authentication and identification scheme specified for the TCP/IP
service. From AUTHENTICATE.
Backlog
Port backlog for the TCP/IP service.
Local open date
Date when the TCP/IP was opened. If this field is null, the status of the
connection is CLOSED.
Local open time
Time when the TCP/IP was opened. If this field is null, the status of the
connection is CLOSED.
Maxdata
Indicates the setting for the maximum length of data that may be received
by CICS as an HTTP server. From MAXDATA.
Status Status of the connection. It is OPEN when TCPIP_LOCOPEN_DATE and
TCPIP_LOCOPEN_TIME are not null. It is CLOSED when
TCPIP_LOCOPEN_DATE and TCPIP_LOCOPEN_TIME are null.
CICS TCP/IP Service Requests Statistics
This report shows CICS TCP/IP service requests statistics.
This information identifies the report:
Report ID
CICS826 (CICS826P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TCPIP_T (CICS_S_TCPIP_TP for CICS Partitioning feature)
Attributes
Statistics, CICS, TCPIP, Requests, Daily
Variables
Date, MVS system ID, CICS system ID
The report contains this information:
TCPIP service name
Name of the TCP/IP service installed.
Port number
Number of the port on which CICS is listening on behalf of this service.
IP address
TCP/IP address defined for the TCP/IP stack used for this TCP/IP service.
Current connections
Number of connections for the TCP/IP service.
Peak connections
Peak number of connections for the TCP/IP service. Calculated as
maximum of TCPIP_CONNECT_PEAK.
Attached transactions
Number of transactions attached.
Send requests
Number of send requests issued for the TCP/IP service.
358
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Average bytes sent
Average number of bytes sent. Calculated as sum of TCPIP_BYTES_SENT/
TCPIP_SEND_NUM.
Receive requests
Number of receive requests issued for the TCP/IP service.
Average bytes received
Average number of bytes received. Calculated as sum of
TCPIP_BYTES_RECV/TCPIP_RECV_NUM.
CICS TCP/IP Service Requests: Daily Trend
This report shows a daily trend for CICS TCP/IP service requests statistics.
This information identifies the report:
Report ID
CICS827 (CICS827P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TCPIP_T (CICS_S_TCPIP_TP for CICS Partitioning feature)
Attributes
Statistics, CICS, TCPIP, Requests, Daily
Variables
Date, MVS system ID, CICS system ID
The report contains this information:
TCPIP service name
Name of the TCP/IP service installed.
Port number
Number of the port on which CICS is listening on behalf of this service.
IP address
TCP/IP address defined for the TCP/IP stack used for this TCP/IP service.
Current connections
Number of connections for the TCP/IP service.
Peak connections
Peak number of connections for the TCP/IP service. Calculated as
maximum of TCPIP_CONNECT_PEAK.
Attached transactions
Number of transactions attached.
Send requests
Number of send requests issued for the TCP/IP service.
Average bytes sent
Average number of bytes sent. Calculated as sum of TCPIP_BYTES_SENT/
TCPIP_SEND_NUM.
Receive requests
Number of receive requests issued for the TCP/IP service.
Average bytes received
Average number of bytes received. Calculated as sum of
TCPIP_BYTES_RECV/TCPIP_RECV_NUM.
Chapter 7. Reports
359
Reports in the CICS statistics component
CICS CFDT Server Statistics
This report shows CFDT server statistics on the CF structure and the data tables
that the CFDT server supports.
This information identifies the report:
Report ID
CICS828 (CICS828P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_CFDT_SERV_D (CICS_S_CFDT_SER_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, CFDT, Server, Daily
Variables
Date, MVS system ID, CICS system ID
The report contains this information:
Structure name
Name of the list structure.
Connection name
Name of the connection to the structure.
Structure max size allocated
Maximum size allocated for the list structure.
Structure max size allowed
Maximum size to which the list structure can be altered.
Structure element size
Maximum element size used for the list structure.
Lists max total
Maximum number of list headers in the structure.
Lists max for control
Maximum number of headers used for the control list.
Lists max for data
Maximum number of headers available for table data.
Lists max used
Maximum number of entries on the used list.
Entries max total
Maximum number of entries in the currently allocated structure.
Entries max used
Maximum number of entries in use.
Entries min free
Minimum number of free entries.
Elements max total
Maximum number of elements in the structure.
Elements max used
Maximum number of elements in use.
Elements min free
Minimum number of free elements.
360
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
CICS CFDT Storage Statistics
This report shows CFDT storage statistics.
This information identifies the report:
Report ID
CICS829 (CICS829P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_CFDT_STOR_T (CICS_S_CFDT_STO_TP for CICS
Partitioning feature)
Attributes
Statistics, CICS, CFDT, Storage
Variables
From date, To date, MVS system ID, CICS system ID
The report contains this information:
CF storage page pool
CF storage pool names (AXMPGANY or AXMPGLOW).
Date
Date to which the statistics refer.
Maximum size
Maximum size of the storage pool area.
Maximum total pages
Maximum number of pages in the storage pool.
Maximum used pages
Maximum number of used pages in the storage pool.
Maximum free pages
Maximum number of free pages in the storage pool.
Minimum free pages
Lowest number of free pages in the storage pool.
Gets
Number of storage GET requests.
Fail gets
Number of GET requests that failed to obtain storage.
Free
Number of storage FREE requests.
Compress
Number of compress (defragmentation) attempts.
CICS NC Storage Statistics
This report shows NC storage statistics.
This information identifies the report:
Report ID
CICS830 (CICS830P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_CFDT_STOR_T (CICS_S_CFDT_STO_TP for CICS
Partitioning feature)
Attributes
Statistics, CICS, NC, Storage
Variables
From date, To date, MVS system ID, CICS system ID
The report contains this information:
Chapter 7. Reports
361
Reports in the CICS statistics component
NC storage page pool
NC storage pool names (AXMPGANY or AXMPGLOW).
Date
Date to which the statistics refer.
Maximum size
Maximum size of the storage pool area.
Maximum total pages
Maximum number of pages in the storage pool.
Maximum used pages
Maximum number of used pages in the storage pool.
Maximum free pages
Maximum number of free pages in the storage pool.
Minimum free pages
Lowest number of free pages in the storage pool.
Gets
Number of storage GET requests.
Fail gets
Number of GET requests that failed to obtain storage.
Free
Number of storage FREE requests.
Compress
Number of compress (defragmentation) attempts.
CICS URIMAP Global statistics
This report shows summary global statistics about CICS TS URIMAP definitions.
This information identifies the report:
Report ID
CICS834 (CICS834P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_GLBURIMAP_D (CICS_S_GLBURIMA_DP for CICS
Partitioning feature)
Attributes
Statistics, CICS, URIMAP, Global
Variables
Date, MVS system ID, CICS system ID
CICS URIMAP Global Statistics
MVS ID = 'MV2C' CICS ID 'DFHXQ'
Date: '2005-05-01' to: '2005-05-05'
Reference
Host/Path
count
Disabled Redirected no match
--------- -------- ---------- --------0
0
0
0
Host/Path
match
--------0
Pipeline
requests
-------0
HTTP
requests
------0
HTTPS
requests
-------0
VHost
disabled
-------0
Tivoli Decision Support for z/OS Report: CICS834
Figure 82. Example of a CICS URIMAP Global statistics report
The report contains this information:
Reference count
Number of times a search for a matching URIMAP definition was made.
From URIMAP_REF_COUNT.
362
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
Disabled
Number of times a URIMAP definition with a matching host and path was
found, but the URIMAP definition was disabled. From
URIMAP_DISABLED.
Redirected
Number of times a URIMAP definition with a matching host and path was
found, and the request was redirected. From URIMAP_REDIRECTED.
Host/Path no match
Number of times a search for a matching URIMAP definition was made,
but no URIMAP definition with a matching host and path was found.
From HOST_PATH_NOMATCH.
Host/Path match
Number of times a search for a matching URIMAP definition was made,
and a URIMAP definition with a matching host and path was found. From
HOST_PATH_MATCH.
Pipeline requests
Number of times a URIMAP definition with a matching host and path was
found, and the request was handled by a Web service. From
PIPELINE_REQS.
HTTP requests
Number of times a URIMAP definition with a matching host and path was
found, and the scheme was HTTP. From SCHEME_HTTP_REQS.
HTTPS requests
Number of times a URIMAP definition with a matching host and path was
found, and the scheme was HTTPS (HTTP with SSL). From
SCHEME_HTTPS_REQS.
VHost disabled
Number of times a URIMAP definition with a matching host and path was
found, but the virtual host was disabled. From VHOST_DISABLED.
CICS URIMAP Resource statistics
This report shows gives details of various attribute settings of each URIMAP
definition.
This information identifies the report:
Report ID
CICS835 (CICS835P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_URIMAP_T (CICS_S_URIMAP_TP for CICS Partitioning
feature)
Attributes
Statistics, CICS, URIMAP, Resource, Details
Variables
Date, MVS system ID, CICS system ID, Urimpap name
Chapter 7. Reports
363
Reports in the CICS statistics component
CICS URIMAP Resource Statistics
MVS ID = 'MV2C' CICS ID 'DFHXQ'
Date: '2005-05-01'
Urimap
name
-----SAMPLE
Urimap
usage
-----SERVER
Urimap
scheme
-----HTTP
Urimap
host
------------------www.hursley.ibm.com
Urimap
path
-------/wsibusp
Tcpservice
name
---------CHRIS
WebService
name
-------------JavaExProvider
Pipeline
name
-------BOBPIPE
Program
name
-------DFH0STAT
Reference
count
Disabled Redirected
--------- -------- ---------0
0
0
Tivoli Decision Support for z/OS Report: CICS834
Figure 83. Example of a CICS URIMAP Global statistics report
The report contains this information:
Urimap name
The name of the installed URIMAP definition. From URIMAP_NAME.
Urimap usage
The intended use of this URIMAP:
SERVER
The URIMAP definition is used to locate the resources for CICS to
produce an HTTP response to the request identified by HOST and
PATH.
CLIENT
The URIMAP definition is used to specify information for making
an HTTP request from CICS as an HTTP client.
PIPELINE
The URIMAP definition is used to locate the resources for CICS to
produce an XML response to the request identified by HOST and
PATH. From URIMAP_USAGE.
Urimap scheme
The scheme for the HTTP request, HTTP with SSL(HTTPS) or without
(HTTP). From URIMAP_SCHEME.
Urimap host
For USAGE (CLIENT), the host name of the target URL to which the HTTP
request is to be sent. For any other USAGE, the host name on the incoming
HTTP request that is used to select this URIMAP definition. From
URIMAP_HOST.
Urimap path
For USAGE(CLIENT), the path of the target URL to which the HTTP
request is to be sent. For any other USAGE, the path on the incoming
HTTP request that is used to select this URIMAP definition. From
URIMAP_PATH.
TCPIPSERVICE name
The TCPIPSERVICE to which this URIMAP definition applies. From
TCPSERVICE_NAME.
WEBSERVICE name
The name of the WEBSERVICE resource definition for the Web service that
handles the incoming HTTP request. From WEBSERVICE_NAME.
PIPELINE name
The name of the PIPELINE resource definition for the Web service that
handles the incoming HTTP request. From PIPELINE_NAME.
364
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
PROGRAM name
The name of the application program that processes the incoming HTTP
request. From PROGRAM_NAME.
Reference count
Number of times this URIMAP definition was referenced. From
URIMAP_REF_CNT.
Disabled
The Number of times this URIMAP host and path were matched, but the
URIMAP definition was disabled. From URIMAP_DISABLED.
Redirected
Number of times this URIMAP host and path were matched, and the
request was redirected. From URIMAP_REDIRECTED.
CICS JVM Profile Statistics, Daily
This report shows details about statistics for each JVM profile in each execution
key.
This information identifies the report:
Report ID
CICS831 (CICS831P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_S_JVM_PROF_D
Attributes
Statistics, CICS, Profile, Daily
Variables
From date, To date, MVS System ID, CICS System ID
CICS JVM Profile Statistics, Daily
MVS ID ='IPO2'
CICS ID ='CFGTV1'
Date: '2004-03-01' to '2004-03-08'
Profile
Name
--------PM23
DD01
VAO2
PM97
RST7
Storage
Key
-------User
User
CICS
User
CICS
Profile
Requests
-------2000
0
18
257
3700
Current
Peak
JVMs in
Number
JVM Pool
of JVMs
---------- --------45
70
12
32
34
78
78
25
23
10
New
JVMs
---0
4
10
6
28
Tivoli Decision Support for z/OS Report: CICS831
Figure 84. Example of a CICS JVM Profile Statistics, Daily report
The report contains this information:
Profile Name
The name of the JVM profile. From PROF_NAME.
Storage Key
The execution key to which these statistics apply. From STORAGE_KEY.
Profile Requests
The number of requests that applications have made to run a Java program
in a JVM with this execution key and profile. From PROF_REQUESTS.
Current JVMs in JVM Pool
The number of JVMs with this execution key and profile that are currently
in the JVM pool. From CURR_PROF_USE.
Chapter 7. Reports
365
Reports in the CICS statistics component
Peak Number of JVMs
The peak number of JVMs with this execution key and profile that the JVM
pool has contained. From PEAK_PROF_USE.
New JVMs
The number of new JVMs that were created with this execution key and
profile. From NEW_JVM_CREATED.
CICS Transaction Processor Utilization, Daily
This report shows the average number of transactions in a CICS/ESA or CICS/TS
system per MVS processor second. The number of transactions is measured by
CICS, and the processor usage (TCB and SRB) is measured by MVS. For
information on how to use this report, see “Monitoring processor use” on page 32.
The report provides information for CICS running on MVS working both in
toleration and goal modes.
This information identifies the report:
Report ID
CICSA06 (CICSA06P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TRAN_D (CICS_S_TRAN_DP for CICS Partitioning
feature), MVS_WORKLOAD_D, MVS_WORKLOAD2_M
Attributes
CICS, Performance, Transaction, Daily, Detail
Variables
MVS system ID, CICS system ID, From date, To date
Figure 85. Example of a CICS Transaction Processor Utilization, Daily report
The report contains this information:
Date
There is one bar for each day in the specified range.
Tran count/CPU sec
Number of transactions per processor second. The processor time is the
366
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
sum of TCB_SECONDS and SRB_SECONDS. The transaction count is from
CICS/ESA or CICS/TS transaction statistics.
CICS Transaction Processor Utilization, Monthly
This report shows the average number of transactions in a CICS/ESA or CICS/TS
system per MVS processor second. The number of transactions is measured by
CICS, and the processor usage (TCB and SRB) is measured by MVS. For
information on how to use this report, see “Monitoring processor use” on page 32.
The report provides information for CICS running on MVS working both in
toleration and goal modes.
This information identifies the report:
Report ID
CICSA04 (CICSA04P for CICS Partitioning feature)
Report group
CICS reports
Source
CICS_S_TRAN_M (CICS_S_TRAN_MP for CICS Partitioning
feature), MVS_WORKLOAD_M MVS_WORKLOAD2_M
Attributes
CICS, Performance, Transaction, Monthly, Detail
Variables
MVS system ID, CICS system ID, From date, To date
Figure 86. Example of a CICS Transaction Processor Utilization, Monthly report
The report contains this information:
Date
There is one bar for each month in the specified range.
Tran count/CPU sec
Number of transactions per processor second. The processor time is the
sum of TCB_SECONDS and SRB_SECONDS. The transaction count is from
CICS/ESA or CICS/TS transaction statistics.
Chapter 7. Reports
367
Reports in the CICS statistics component
CICS Availability Reports
CICS availability reports show you the availability of the CICS subsystem and
CICS-DB2 Connection over a specific time period.
CICS_DB2 Connection Availability, Daily Overview report
This report gives you a daily overview of the availability of the CICS-DB2
Connection (DB2CONN resource) in a CICS subsystem.
This information identifies the report:
Report ID
CICSA08 (CICSA08P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_AVAIL_D (CICS_AVAIL_DP)
Attributes
CICS, Availability, Daily, Overview
Variables
CICS_System_ID, Date
CICS DB2 Connection Availability, Daily Overview
Date: 2002-09-27
CICS System: 'CICS3T87'
Up In
Up In
DB2CONN
Up
Schedule
Schedule
Objective
Name
Hours
Hours
%
%
---------- ---------- ---------- ---------- ---------DB23T8X
12
9
100.00
95.00
Tivoli Decision Support for z/OS Report: CSQA02
Figure 87. Example of a CICS-DB2 Connection Availability, Daily Overview report
The report contains this information:
Date
The date of the day for the measurement.
CICS System ID
The name of the CICS subsystem.
DB2CONN Name
The name of the DB2CON resource.
Up Hours
The total time, in hours, when the CICS-DB2 Connection was available.
Up In Schedule (Hours)
The time within the schedule, in hours, when the CICS-DB2 Connection
was available running. The CICS_AVAIL_RES is used to specify the
schedule name.
Up In Schedule (%)
The time within the schedule, in percent of scheduled hours, when the
CICS-DB2 Connection was available. The CICS_AVAIL_RES is used to
specify the schedule name.
Objective (%)
Availability objective for this resource in the scheduled hours.
CICS Subsystem Availability, Daily Trend report
This report shows availability for one CICS subsystem in a daily trend between the
FROM_DATE and TO_DATE specified.
368
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS statistics component
This information identifies the report:
Report ID
CICSA09 (CICSA09P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_AVAIL_D (CICS_AVAIL_DP)
Attributes
CICS, Availability, Daily, Trend
Variables
CICS System ID, From Date, To Date
CICS Subsystem Availability, Daily Trend
Date: '2002-09-27' to '2002-09-30'
CICS System: 'CICS3T87'
Date
---------2002-09-27
2002-09-28
2002-09-29
2002-09-30
Up In
Up In
Up
Schedule
Schedule
Objective
Hours
Hours
%
%
---------- ---------- ---------- ---------12
9
100.00
95.00
24
9
100.00
95.00
24
9
100.00
95.00
3
3
33.33
95.00
Tivoli Decision Support for z/OS Report: CICS831
Figure 88. Example of an CICS Subsystem Availability, Daily Trend report
The report contains this information:
Date
The date of the day for the measurement.
CICS System ID
The name of the CICS subsystem.
Up Hours
The total time, in hours, when the CICS subsystem was up and running.
Up In Schedule (Hours)
The time within the schedule, in hours, when the CICS subsystem was up
and running. The CICS_AVAIL_RES is used to specify the schedule name.
Up In Schedule (%)
The time within the schedule, in percent of scheduled hours, when the
CICS subsystem was up and running. The CICS_AVAIL_RES is used to
specify the schedule name.
Objective (%)
Availability objective for this resource in the scheduled hours.
Reports in the CICS transaction and unit-of-work analysis component
If you install the CICS transaction and unit-of-work analysis component, Tivoli
Decision Support for z/OS provides the reports described in this section. See
“Evaluating the CICS transaction and unit-of-work analysis component” on page
16, for more information.
CICS UOW Response Times
This report shows a response-time analysis for transactions that run on several
CICS systems. The data from each CICS system is consolidated using the
unit-of-work ID as a key. Do not specify too great a time interval for this report,
Chapter 7. Reports
369
Reports in the CICS transaction and UOW analysis component
because it can generate many lines of output. The response times are adjusted by
removing the long-running CICS mirror tasks. For information on how to use this
report, see “Understanding CICS unit-of-work reporting” on page 38.
This information identifies the report:
Report ID
CICS902 (CICS902P for CICS Partitioning feature)
Report group
CICS Reports
Source
CICS_T_TRAN_T, CICS_T_UOW_TV1, CICS_T_UOW_TV2
(CICS_T_TRAN_TP, CICS_T_UOW_TV1P, CICS_T_UOW_TV2P for
CICS Partitioning feature)
Attributes
CICS, UOW, Response, Transaction, Tran
Variables
Date, From time, To time, Exclude program add list
CICS UOW Response Times
Time: '09.59.25' to '10.00.00'
Date: 2000-03-10
Adjusted
UOW
start
Tran
time
ID
-------- ---09.59.25 OP22
OP22
CICS
ID
-------CICSPROD
CICSPRDC
UOW Response
Program tran
time
name
count (sec)
-------- ----- -------DFHCRP
2
0.436
OEPCPI22
09.59.26 AP63 CICSPRDE APPM00
AP63 CICSPROD DFHCRP
2
0.045
09.59.26 ARUS CICSPROD DFHCRP
CSM5 CICSPRDB DFHMIR
ARUS CICSPRDC AR49000
3
0.158
09.59.26 CSM5 CICSPRDB DFHMIR
GCS6 CICSPROD GCSCPS20
2
0.068
09.59.27 CSM5
CSM5
MQ01
MQ01
4
0.639
CICSPRDB
CICSPRDB
CICSPROD
CICSPRDD
DFHMIR
DFHMIR
DFHCRP
CMQ001
...
Tivoli Decision Support for z/OS Report: CICS902
Figure 89. Example of a CICS UOW Response Times report
The report contains this information:
Adjusted UOW start time
Start time of the first transaction, excluding long-running mirror
transactions. This is from START_TIMESTAMP in CICS_T_UOW_TV2
(CICS_T_UOW_TV2P for CICS Partitioning feature).
Tran ID
Transaction name. This is from TRANSACTION_ID in CICS_T_TRAN_T
(CICS_T_TRAN_TP for CICS Partitioning feature).
CICS ID
The CICS system name. This is from CICS_SYSTEM_ID in
CICS_T_TRAN_T (CICS_T_TRAN_TP for CICS Partitioning feature).
Program name
Program name. This is from PROGRAM_NAME in CICS_T_TRAN_T.
(CICS_T_TRAN_TP for CICS Partitioning feature).
370
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports in the CICS transaction and UOW analysis component
UOW tran count
Number of tasks involved, including long-running tasks. This is from
TRAN_COUNT in CICS_T_UOW_TV1P.
Response time (sec)
Response time, excluding long-running mirror tasks. This is from
RESPONSE_TIME_SEC in CICS_T_UOW_TV2P.
Reports common to all components
The following reports are common to all components:
v “CICS Exceptions”
v “CICS Incidents” on page 372
CICS Exceptions
This report shows CICS exceptions that have been logged to the common
EXCEPTION_T table.
This information identifies the report:
Report ID
CICS001
Report group
CICS Reports
Source
EXCEPTION_T
Attributes
CICS, Exception, Problem
Variables
From date, To date, CICS system list
1 15
CICS Exceptions
DATE: '2000-03-17' to '2000-06-17'
Date
---------2000-03-17
2000-03-17
2000-03-17
2000-03-17
2000-06-10
2000-06-10
2000-06-10
2000-06-10
Time
-------17.12.13
17.12.13
17.37.28
17.37.28
16.59.16
17.03.26
17.03.26
17.03.26
Exception
description
--------------------------------------------BUFFER FULL 12 TIMES ON JOURNAL 1
THE MXT VALUE 50
WAS REACHED 2
TIMES
BUFFER FULL 12 TIMES ON JOURNAL 1
THE MXT VALUE 50
WAS REACHED 6
TIMES
WAIT FOR TEMP STORAGE
19
SEC CEDF
DTB OVERFLOWED 2
TIMES
BUFFER FULL 12 TIMES ON JOURNAL 1
CICS TRANSACTION ABEND DHTC
Terminal
operator User
ID
ID
-------- -------SYSTEM
SYSTEM
SYSTEM
SYSTEM
T0D2
CICSUSER
SYSTEM
SYSTEM
SYSTEM
Exception
ID
-----------------JOURNAL_BUFFERFULL
MXT_REACHED
JOURNAL_BUFFERFULL
MXT_REACHED
CMF_TSTORAGE_WAIT
DTB_OVERFLOW
JOURNAL_BUFFERFULL
TRANSACTION_ABEND
Sev
--04
04
04
04
04
04
04
03
Tivoli Decision Support for z/OS Report: CICS001
Figure 90. Example of a CICS Exceptions report
The report contains this information:
Date
Date when the exception occurred.
Time
Time when the exception occurred.
Exception description
A description of the exception, including the ABEND code in case of CICS
transaction abend.
Terminal operator ID
When the exception comes from CMF records, this is the 4-byte terminal
ID and the 4-byte operator ID, stored in the 8-byte field
RESOURCE_NAME1. Otherwise, this field is set to ’SYSTEM’.
Chapter 7. Reports
371
Reports common to all components
User ID
When the exception comes from CMF records, this is the 8-byte user ID,
stored in the 8-byte field RESOURCE_NAME2. Otherwise, this field is
blank.
Exception ID
Exception ID, from EXCEPTION_ID.
Severity of the exception. CICS exceptions are classified from 1 (highest) to
4 (lowest).
Sev
CICS Incidents
This report shows records from the EXCEPTION_T table that have a severity of 3
or higher.
This information identifies the report:
Report ID
CICS002
Report group
CICS Reports
Source
EXCEPTION_T
Attributes
CICS, Incident, Problem
Variables
From date, To date, CICS system list
CICS Incidents
DATE: '2000-02-01' to '2000-02-02'
Sev
--03
03
03
03
Date
---------2000-02-01
2000-02-02
2000-02-02
2000-02-02
Time
-------15.42.03
00.00.00
17.37.28
17.12.03
Terminal
operator User
ID
ID
-------- -------SYSTEM
SYSTEM
SYSTEM
SYSTEM
Exception
ID
-----------------TRANSACTION_ABEND
TRANSACTION_ABEND
SHORT_OF_STORAGE
SHORT_OF_STORAGE
Exception
description
----------------------CICS TRANSACTION ABEND AZTS
CICS TRANSACTION ABEND APCT
CICS SOS IN PAGEPOOL
CICS SOS IN PAGEPOOL
Tivoli Decision Support for z/OS Report: CICS002
Figure 91. Example of a CICS Incidents report
The report contains this information:
Sev
Severity of the exception. CICS exceptions are classified from 1 (highest) to
4 (lowest). See the CICS Exceptions report for severity 4 exceptions.
Date
Date when the exception occurred.
Time
Time when the exception occurred.
Terminal operator ID
When the exception comes from CMF records, this is the 4-byte terminal
ID and the 4-byte operator ID, stored in the 8-byte field
RESOURCE_NAME1. Otherwise, this field is set to ’SYSTEM’.
User ID
When the exception comes from CMF records, this is the 8-byte user ID,
stored in the 8-byte field RESOURCE_NAME2. Otherwise, this field is
blank.
Exception ID
Exception ID, from EXCEPTION_ID.
372
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Reports common to all components
Exception description
A description of the exception.
Chapter 7. Reports
373
374
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Part 3. Appendixes
© Copyright IBM Corp. 1994, 2009
375
376
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Appendix. Support information
If you have a problem with your IBM software, you want to resolve it quickly. This
section describes the following options for obtaining support for IBM software
products:
v
v
v
v
“Searching knowledge bases”
“Obtaining fixes”
“Receiving weekly support updates” on page 378
“Contacting IBM Software Support” on page 379
Searching knowledge bases
You can search the available knowledge bases to determine whether your problem
was already encountered and is already documented.
Searching the information center
IBM provides extensive documentation that can be installed on your local
computer or on an intranet server. You can use the search function of this
information center to query conceptual information, instructions for completing
tasks, and reference information.
Searching the Internet
If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem.
To search multiple Internet resources for your product, use the Web search topic in
your information center. In the navigation frame, click Troubleshooting and
support Searching knowledge bases and select Web search. From this topic, you
can search a variety of resources, including the following:
v
v
v
v
v
IBM technotes
IBM downloads
IBM developerWorks®
Forums and newsgroups
Google
Obtaining fixes
A product fix might be available to resolve your problem. To determine what fixes
are available for your IBM software product, follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/software/
support/.
2. Click Downloads and drivers in the Support topics section.
3. Select the Software category.
4. Select a product in the Sub-category list.
5. In the Find downloads and drivers by product section, select one software
category from the Category list.
6. Select one product from the Sub-category list.
© Copyright IBM Corp. 1994, 2009
377
7. Type more search terms in the Search within results if you want to refine your
search.
8. Click Search.
9. From the list of downloads returned by your search, click the name of a fix to
read the description of the fix and to optionally download the fix.
For more information about the types of fixes that are available, see the IBM
Software Support Handbook at http://techsupport.services.ibm.com/guides/
handbook.html.
Receiving weekly support updates
To receive weekly e-mail notifications about fixes and other software support news,
follow these steps:
1. Go to the IBM Software Support Web site at http://www.ibm.com/support/
us/.
2. Click My support in the upper right corner of the page.
3. If you have already registered for My support, sign in and skip to the next
step. If you have not registered, click register now. Complete the registration
form using your e-mail address as your IBM ID and click Submit.
4. Click Edit profile.
5. In the Products list, select Software. A second list is displayed.
6. In the second list, select a product segment, for example, Application servers.
A third list is displayed.
7. In the third list, select a product sub-segment, for example, Distributed
Application & Web Servers. A list of applicable products is displayed.
8. Select the products for which you want to receive updates, for example, IBM
HTTP Server and WebSphere Application Server.
9. Click Add products.
10. After selecting all products that are of interest to you, click Subscribe to email
on the Edit profile tab.
11. Select Please send these documents by weekly email.
12. Update your e-mail address as needed.
13. In the Documents list, select Software.
14. Select the types of documents that you want to receive information about.
15. Click Update.
If you experience problems with the My support feature, you can obtain help in
one of the following ways:
Online
Send an e-mail message to erchelp@ca.ibm.com, describing your problem.
By phone
Call 1-800-IBM-4You (1-800-426-4968).
378
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Contacting IBM Software Support
IBM Software Support provides assistance with product defects.
Before contacting IBM Software 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:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2 and WebSphere products that
run on Windows, or UNIX operating systems), enroll in Passport Advantage® in
one of the following ways:
Online
Go to the Passport Advantage Web site at http://www.lotus.com/
services/passport.nsf/ WebDocs/Passport_Advantage_Home and click
How to Enroll.
By phone
For the phone number to call in your country, go to the IBM Software
Support Web site at http://techsupport.services.ibm.com/guides/
contacts.html and click the name of your geographic region.
v For customers with Subscription and Support (S & S) contracts, go to the
Software Service Request Web site at https://techsupport.services.ibm.com/
ssr/login.
v For customers with IBMLink™, CATIA, Linux, S/390®, iSeries®, pSeries®,
zSeries®, and other support agreements, go to the IBM Support Line Web site at
http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries, pSeries, and iSeries environments), you
can purchase a software maintenance agreement by working directly with an
IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web site at http://www.ibm.com/servers/eserver/
techsupport.html.
If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go to
the contacts page of the IBM Software Support Handbook on the Web at
http://techsupport.services.ibm.com/guides/contacts.html and click the name of
your geographic region for phone numbers of people who provide support for
your location.
To contact IBM Software support, follow these steps:
1. “Determining the business impact”
2. “Describing problems and gathering information” on page 380
3. “Submitting problems” on page 380
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:
Appendix. Support information
379
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 problems and gathering information
When describing a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can you re-create the problem? If so, what steps were performed to re-create the
problem?
v Did you make any changes to the system? For example, did you make changes
to the hardware, operating system, networking software, and so on.
v Are you currently using a workaround for the problem? If so, be prepared to
explain the workaround when you report the problem.
Submitting problems
You can submit your problem to IBM Software Support in one of two ways:
Online
Click Submit and track problems on the IBM Software Support site at
http://www.ibm.com/software/support/probsub.html. Type your
information into the appropriate problem submission form.
By phone
For the phone number to call in your country, go to the contacts page of
the IBM Software Support Handbook at http://techsupport.services.ibm.com/
guides/contacts.html and click the name of your geographic region.
If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround that you can implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
Software Support Web site daily, so that other users who experience the same
problem can benefit from the same resolution.
380
Tivoli Decision Support for z/OS: CICS Performance Feature 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 give 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:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
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 might not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements and
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 Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
© Copyright IBM Corp. 1994, 2009
381
Notices
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 wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases payment of a fee.
The licensed program described in this document and all licensed 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 measurement 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.
All IBM prices shown are IBM’s suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
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.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
382
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Notices
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM‘s application programming interfaces.
If you are viewing this information in softcopy form, the photographs and color
illustrations might not display.
Trademarks
Listed below are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both.
IBM
IBM logo
ibm.com
3090
AIX
AS/400
DB2
CICS
CICS/ESA
CICS/MVS
CICSplex
developerWorks
DFSMS
eServer
IBMLink
IMS
iSeries
Language Environment
Lotus
MVS
OMEGAMON
OS/390
Passport Advantage
pSeries
QMF
Rational
RMF
S/390
System/370
Tivoli
Tivoli logo,
VSE/ESA
VTAM
WebSphere
z/OS
z/Series
z/VM
Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered
trademarks or trademarks of Adobe Systems Incorporated in the United States,
and/or other countries.
Java and all Java-based trademarks and logos are
trademarks or registered trademarks of Sun
Microsystems, Inc. in the United States, other countries,
or both.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft, Windows and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.
Notices
383
Trademarks
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
384
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Glossary
C
I
COLLECT. A process used by Tivoli Decision Support
for z/OS to read data from input log data sets,
interpret records in the data set, and store the data in
DB2 tables in the Tivoli Decision Support for z/OS
database.
intersystem communication (ISC). Communication
between separate systems by means of SNA facilities or
by means of the application-to-application facilities of
an SNA access method.
component. An optionally installable part of a Tivoli
Decision Support for z/OS feature. Specifically in Tivoli
Decision Support for z/OS, a component refers to a
logical group of objects used to collect log data from a
specific source, to update the Tivoli Decision Support
for z/OS database using that data, and to create reports
from data in the database.
control table. A predefined Tivoli Decision Support
for z/OS table that controls results returned by certain
log collector functions.
D
data table. A Tivoli Decision Support for z/OS table
that contains performance data used to create reports.
distributed transaction processing. The distribution of
processing among transactions that communicate
synchronously with each other over intersystem or
interregion links.
J
Java virtual machine. A software implementation of a
central processing unit that runs compiled Java code
(applets and applications).
K
key columns. The columns of a database table that
together constitute the key.
key value. Value used to sort records into groups.
L
local shared resources (LSR). A VSAM facility that
provides users with the capability of sharing buffers
and strings of VSAM data sets.
log. Any sequential data set used as input to Tivoli
Decision Support for z/OS.
dynamic transaction backout (DTB). The process of
canceling changes made to stored data by a transaction
following the failure of the transaction.
log collector. A Tivoli Decision Support for z/OS
program that processes log data sets and provides
other Tivoli Decision Support for z/OS services.
E
log collector language. Tivoli Decision Support for
z/OS statements used to supply definitions to and
invoke services of the log collector.
environment data. See 385.
environment information. Information that is added
to the log data to create reports. This includes data
such as performance groups, shift periods, installation
definitions, and so on.
F
function request shipping. The process, transparent to
the application program, by which CICS accesses
resources when those resources are actually held on
another CICS system.
log data set. Any sequential data set used as input to
Tivoli Decision Support for z/OS.
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.
logical unit (LU). A port through which a user gains
access to the services of a network.
lookup expression. An expression that specifies how a
value is obtained from a lookup table.
lookup table. A Tivoli Decision Support for z/OS DB2
table that contains grouping, translation, or substitution
information.
© Copyright IBM Corp. 1994, 2009
385
Glossary
M
resource information. Information that describes the
elements in a system (for example, a network).
multiregion operation (MRO). Communication
between CICS systems in the same processor without
the use of SNA networking facilities.
S
section. A structure within a record that contains one
or more fields and may contain other sections.
O
object. An integral part of a feature component
needed for data collection (for example, record
definitions, record procedures, and update definitions).
source. In an update definition, the record or DB2
table that contains the data used to update a Tivoli
Decision Support for z/OS DB2 table.
subcomponent. An optionally installable part of a
Tivoli Decision Support for z/OS feature component.
P
Tivoli Decision Support for z/OS database. A set of
DB2 tables that includes data tables, lookup tables,
system tables, and control tables.
purge condition. Instruction for removing unneeded
data from the Tivoli Decision Support for z/OS
database.
R
sysplex. A set of systems communicating and
cooperating with each other, through certain
multisystem hardware components and software
services, in order to process customer workloads.
system table. A DB2 table that stores information for
controlling log collector processing, Tivoli Decision
Support for z/OS dialogs, and reporting.
T
record definition. The description of a record type
contained in the log data sets used by Tivoli Decision
Support for z/OS, including detailed record layout and
data formats.
record procedure. A program module that is called to
process certain types of log records.
record type. The classification of records in a log data
set.
region. A section of the dynamic area that is allocated
to a job step or system task. In the CICS product
library, the term also includes partitions and address
spaces.
target. In an update definition, the DB2 table in which
Tivoli Decision Support for z/OS stores data from the
source record or table.
threshold. In Tivoli Decision Support for z/OS, 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.
report definition language. Tivoli Decision Support
for z/OS statements used to define reports and report
groups.
updates. Instructions in Tivoli Decision Support for
z/OS on how to process data from log data sets to DB2
tables.
report group. A collection of Tivoli Decision Support
for z/OS reports that can be referred to by a single
name.
V
reporting dialog. A set of host or workstation
windows used to request reports.
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.
resource. Any facility of the computing system or
operating system required by a job or task, including
central storage, input/output devices, the processing
unit, data sets, and control or processing programs.
resource group. A collection of resources identified as
belonging to a particular department or division.
Resources are organized into groups to reflect the
structure of an organization.
386
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Bibliography
Tivoli Decision Support
publications
Administration Guide and Reference, SH19-6816
Resource Accounting for z/OS, SH19-4495
AS/400 System Performance Feature Guide and
Reference, SH19-4019
CICS Performance Feature Guide and Reference,
SH19-6820
Distributed Systems Performance Feature Guide
and Reference, SH19-4018
Guide to Reporting, SH19-6842
IMS Performance Feature Guide and Reference,
SH19-6825
Language Guide and Reference, SH19-6817
Messages and Problem Determination, SH19-6902
Network Performance Feature Installation and
Administration, SH19-6901
Network Performance Feature Reference,
SH19-6822
Network Performance Feature Reports, SH19-6821
System Performance Feature Guide, SH19-6818
System Performance Feature Reference Volume I,
SH19-6819
System Performance Feature Reference Volume II,
SH19-4494
Usage and Accounting Collector User Guide,
SC23-7966
© Copyright IBM Corp. 1994, 2009
387
388
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Index
A
accessibility xiii
accounting class data, CMF 318
Application CPU Utilization, Trend report (CICS404) 311
Application DLI Call Utilization, Trend report (CICSA51) 317
Application I/O Wait Times, Detail report (CICS405) 312
Application Main Response Times, Detail report
(CICS406) 314
Application Response Times, Detail report (CICS403) 309
Application Response Times, Overview report (CICS401) 307
Application Response Times, Trend report (CICS402) 308
Application Wait Times, Detail report (CICS407) 316
area, dynamic storage 335
attributes, report 302
availability data
CICS 27
resource 27
with XRF 28
B
backout, dynamic transaction 331
basic (subcomponent 1) data tables
CICS_TRANSACTION_H, _D, _W 104
CICSBTS_TRAN_USR_H, _D, _W 72
CICSCHN_A_BASIC_H, _W 98
CICSCHN_TRAN_USR_H, _D, _W 73
CICSCHN_TRANSACT_H, _D, _W 106
CICSDOC_TRAN_USR_H, _D, _W 74
CICSWEB_TRAN_USR_H, _D, _W 75
basic (subcomponent 1) reports
CICS Transaction Performance, Detail 302, 368
basic application analysis (subcomponent 4) data tables
CICS_A_BASIC_H, _W 97
CICSBTS_A_BASIC_H, _W 98
CICSDOC_A_BASIC_H, _W 99
CICSWEB_A_BASIC_H, _W 100
basic application analysis (subcomponent 4) reports
CICS Application CPU Utilization, Trend 311
CICS Application I/O Wait Times, Detail 312
CICS Application Main Response Times, Detail 314
CICS Application Response Times, Detail 309
CICS Application Response Times, Overview 307
CICS Application Response Times, Trend 308
CICS Application Wait Times, Detail 316
basic application user (subcomponent 11) data tables
CICS_A_USR_H, _W 111
CICSBTS_A_USR_H, _W 111
CICSCHN_A_USR_H, _W 112
CICSDOC_A_USR_H, _W 113
CICSWEB_A_USR_H, _W 113
basic transaction (subcomponent 8) data tables
CICS_TRAN_USR_H, _D, _W 71, 118, 119, 120
CICSBTS_TRANSACT_H, _D, _W 105
CICSDOC_TRANSACT_H, _D, _W 106
CICSWEB_TRANSACT_H, _D, _W 107
Batch, Global IRC statistics report (CICS806) 332
books
See publications
books for Administration Guide and Reference 387
© Copyright IBM Corp. 1994, 2009
BTS, common fields 89
Buffer Pool, DB2 Connection, Statistics report (CICS818)
Buffer Pool, Shared TS queue server, Statistics report
(CICS823) 353
347
C
call rate, database 317
categories of Tivoli Decision Support for z/OS-collected
data 27
CFDT: CICS Server Statistics report (CICS828) 360
CFDT: CICS Storage Statistics report (CICS829) 361
CHN, common fields 90
CICS Application Channel Performance, Detail 305
CICS ISC/IRC Function Shipping by Connection 337
CICS Monitoring Facility (CMF) requirements, CICS/ESA 16
CICS OMEGAMON database/file avg command response,
daily report 324
CICS OMEGAMON database/file avg request response, daily
report 324
CICS OMEGAMON database/file total commands, hourly
report 323
CICS OMEGAMON database/file total requests, hourly
report 322
CICS OMEGAMON monitoring component
description 15
report 322
tables 124
CICS OMEGAMON transaction database/file commands,
daily report 326
CICS OMEGAMON transaction database/file requests, daily
report 325
CICS OMEGAMON transaction DB2 averages, hourly
report 327
CICS performance, using Tivoli Decision Support for z/OS to
monitor 27
CICS Transaction Channel Performance, Detail 304
CICS Transaction Processor Utilization, Daily report
(CICSA06) 366
CICS Transaction Processor Utilization, Daily report
(CICSA07) 319
CICS Transaction Processor Utilization, Monthly report
(CICSA04) 367
CICS Transaction Processor Utilization, Monthly report
(CICSA05) 319
CICS_A_BASIC_H, _W data tables 97
CICS_A_DBCTL_H, _W data tables 100
CICS_A_DBCTL_USR_H, _W data tables 114
CICS_A_DLI_H, _W data tables 102
CICS_A_DLI_USR_H, _W data tables 116
CICS_A_USR_H, _W data tables 111
CICS_DBCTL_TRAN_H, _D, _W data tables 108
CICS_DBCTL_USR_H, _D, _W data tables 94
CICS_DICTIONARY, control table 299
CICS_DLI_TRAN_H, _D, _W data tables 109
CICS_DLI_USR_H, _D, _W data tables 96
CICS_DOCT_RES_D 138, 139
CICS_FIELD, control table 300
CICS_LOOKUP_APPL lookup table 24, 295
CICS_LOOKUP_SYSTEM lookup table 25, 296
CICS_M_ACCOUNT_H, _D, _W, _M data tables 103
389
CICS_MVSTCB_D 135
CICS_MVSTCB_H 135
CICS_MVSTCB_RES_D 136
CICS_MVSTCB_RES_H 137
CICS_O_A_FL_H,_D,_W data tables 127
CICS_O_A_USR_FL_ H,_D,_W data tables 128
CICS_O_FL_DTL_H, _D, _W data tables 129
CICS_O_FL_H, _D, _W data tables 125
CICS_O_TRAN_FL_ H,_D,_W data tables 127
CICS_OMEG_FIELD lookup table 296
CICS_RMI_PERF_T 121
CICS_S_AUTO_TERM_D data table 142
CICS_S_AUTO_TERM_T data table 140
CICS_S_CFDT_GREQ_D data table 144
CICS_S_CFDT_GREQ_T data table 143
CICS_S_CFDT_SERV_D data table 147
CICS_S_CFDT_SERV_T data table 145
CICS_S_CFDT_STOR_T data table 150
CICS_S_CFDT_TBAC_D data table 151
CICS_S_CFDT_TBAC_T data table 150
CICS_S_DB2CONN_D data table 155
CICS_S_DB2CONN_T data table 152
CICS_S_DB2ENTRY_D data table 159
CICS_S_DB2ENTRY_T data table 157
CICS_S_DBCTL_D data table 162
CICS_S_DBCTL_T data table 160
CICS_S_DISPATCH_D data table 164
CICS_S_DISPATCH_T data table 162
CICS_S_DLI_D data table 167, 169, 170
CICS_S_DLI_T data table 166
CICS_S_DUMP_D data table 172
CICS_S_DUMP_T data table 171
CICS_S_ENQUE_MGR_D data table 174
CICS_S_ENQUE_MGR_T data table 172
CICS_S_FEPI_D data table 178
CICS_S_FEPI_T data table 176
CICS_S_FILE_D data table 182
CICS_S_FILE_T data table 179
CICS_S_GLB_TCPIP_D 185
CICS_S_GLB_TCPIP_T 184
CICS_S_GLBURIMAP_D 188
CICS_S_GLBURIMAP_T 186
CICS_S_GLOBAL_D data table 193
CICS_S_GLOBAL_T data table 189
CICS_S_INTERCOM_D data table 202
CICS_S_INTERCOM_T data table 197
CICS_S_JOURNAL_D data table 208
CICS_S_JOURNAL_D2 data table 175, 209, 210, 211, 212
CICS_S_JOURNAL_T data table 207
CICS_S_JOURNAL_T2 data table 207
CICS_S_LOGSTREAM_D data table 214
CICS_S_LOGSTREAM_T data table 213
CICS_S_LSR_POOL_D data table 217
CICS_S_LSR_POOL_T data table 215
CICS_S_LSRP_FILE_D data table 220
CICS_S_LSRP_FILE_T data table 219
CICS_S_MONITOR_D data table 224
CICS_S_MONITOR_T data table 222
CICS_S_NC_LSTRUC_D data table 226
CICS_S_NC_LSTRUC_T data table 225
CICS_S_NCS_STOR_T data table 227
CICS_S_PIPELINE_T data table 228
CICS_S_PROGRAM_D data table 230
CICS_S_PROGRAM_T data table 228
CICS_S_RECOV_MGR_D data table 233
CICS_S_RECOV_MGR_T data table 232
CICS_S_STOR_DOM_D data table 236
390
CICS_S_STOR_DOM_T data table 235
CICS_S_STOR_DSA_D data table 239
CICS_S_STOR_DSA_T data table 236
CICS_S_STOR_TASK_D data table 242
CICS_S_STOR_TASK_T data table 241
CICS_S_TCLASS_D data table 244
CICS_S_TCLASS_T data table 243
CICS_S_TCPIP_D data table 245, 247
CICS_S_TERMINAL_D data table 250
CICS_S_TERMINAL_T data table 248
CICS_S_TRAN_D, _M data tables 252
CICS_S_TRAN_T data table 251
CICS_S_TRANSIENT_D data table 255
CICS_S_TRANSIENT_T data table 253
CICS_S_TS_BPOOL_D data table 258
CICS_S_TS_BPOOL_T data table 257
CICS_S_TS_CF_D data table 261
CICS_S_TS_CF_T data table 259
CICS_S_TS_STOR_D data table 264
CICS_S_TS_STOR_T data table 263
CICS_S_URIMAP_T 265
CICS_S_WEBSERV_T 266
CICS_SMD_SUBP_D 221
CICS_SMD_SUBP_H 222
CICS_T_TRAN_T data table 270
CICS_T_UOW_TV1 view table 291
CICS_T_UOW_TV2 view table 133, 134, 291
CICS_TCPIP_CONN_D 267
CICS_TCPIP_CONN_H 269, 293
CICS_TIMEZONES lookup table 24, 294, 299
CICS_TRAN_USR_H, _D, _W data tables 71, 118, 119, 120
CICS_TRANSACTION_H, _D, _W data tables 104
CICS/MVS (global + accounting)
subcomponent 7 data tables
CICS_M_ACCOUNT_H, _D, _W, _M 103
subcomponent 7 reports
CICS Transaction Processor Utilization, Daily 319
CICS Transaction Processor Utilization, Monthly 319
CICS/MVS CMF Transaction Statistics 318
CICS/MVS CMF Transaction Statistics report (CICS701) 318
CICS101 (Transaction Performance, Detail report) 302, 368
CICS401 (Application Response Times, Overview report) 307
CICS402 (Application Response Times, Trend report) 308
CICS403 (Application Response Times, Detail report) 309
CICS404 (Application CPU Utilization, Trend report) 311
CICS405 (Application I/O Wait Times, Detail report) 312
CICS406 (Application Main Response Times, Detail
report) 314
CICS407 (Application Wait Times, Detail report) 316
CICS701 (CICS/MVS CMF Transaction Statistics report) 318
CICS801 (Global Loader statistics report) 320, 321, 328, 365
CICS802 (Global Temporary Storage statistics report) 329
CICS803 (Global VTAM statistics report) 330
CICS804 (Global DTB statistics report) 331
CICS806 (Global IRC Batch statistics report) 332
CICS807 (Transaction Usage statistics report) 333
CICS808 (Program Usage statistics report) 334
CICS809 (Dynamic Storage [DSA] Usage statistics report) 335
CICS810 (File Statistics report) 336
CICS811 (ISC/IRC Global statistics report) 338
CICS812 (ISC/IRC Mode Entries statistics report) 339
CICS813 (ISC/IRC System Entries by Connection statistics
report) 341
CICS814 (TS Recovery Manager statistics report) 342
CICS815 (TS Enqueue Manager statistics report) 343
CICS816 (TS Logstreams statistics report) 345
CICS817 (DB2 Connection: TCB Statistics report) 346
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
CICS818 (DB2 Connection: Buffer Pool Statistics report) 347
CICS819 (DB2 Connection: Command Statistics report) 349
CICS820 (DB2 Entries: Resource Info statistics report) 350
CICS821 (DB2 Entries: Request Statistics report) 351
CICS822 (DB2 Entries: Performance Statistics report) 352
CICS823 (Shared TS queue server: Buffer Pool Statistics
report) 353
CICS824 (Shared TS queue server: Storage Statistics
report) 355
CICS825 (TCP/IP: Service Statistics report) 357
CICS826 (TCP/IP: Service Requests Statistics report) 358
CICS827 (TCP/IP: Service Requests, Daily Trend report) 359
CICS828 (CFDT: Server Statistics report) 360
CICS829 CFDT: Storage Statistics report) 361
CICS830 (NC:Storage Statistics report) 361
CICS831 (JVM Profile Statistics, Daily statistics report) 365
CICS832 (TCP/IP: Global Statistics report) 356
CICS834 (URIMAP: Global Statistics report) 362
CICS835 (URIMAP: Resource Statistics report) 363
CICS902 (UOW Response Times report) 369
CICSA04 (Transaction Processor Utilization, Monthly
report) 367
CICSA05 (Transaction Processor Utilization, Monthly
report) 319
CICSA06 (Transaction Processor Utilization, Daily report) 366
CICSA07 (Transaction Processor Utilization, Daily report) 319
CICSA51 (Application DLI Call Utilization, Trend report) 317
CICSBTS_A_BASIC_H, _W data tables 98
CICSBTS_A_USR_H, _W data tables 111
CICSBTS_T_TRAN_T data table 284
CICSBTS_TRAN_USR_H, _D, _W data tables 72
CICSBTS_TRANSACT_H, _D, _W data tables 105
CICSCHN_A_BASIC_H, _W data tables 98
CICSCHN_A_USR_H, _W data tables 112
CICSCHN_T_TRAN_T data table 286
CICSCHN_TRAN_USR_H, _D, _W data tables 73
CICSCHN_TRANSACT_H, _D, _W data tables 106
CICSDOC_A_BASIC_H, _W data tables 99
CICSDOC_A_USR_H, _W data tables 113
CICSDOC_T_TRAN_T data table 288
CICSDOC_TRAN_USR_H, _D, _W data tables 74
CICSDOC_TRANSACT_H, _D, _W data tables 106
CICSJ01 (Enterprise Java Beans Details, Daily monitoring
report) 321
CICST01 (Transactions Resources Details, Daily monitoring
report) 320
CICSWEB_A_BASIC_H, _W data tables 100
CICSWEB_A_USR_H, _W data tables 113
CICSWEB_T_TRAN_T data table 290
CICSWEB_TRAN_USR_H, _D, _W data tables 75
CICSWEB_TRANSACT_H, _D, _W data tables 107
class data, CMF accounting 318
CMF accounting class data 318
CMF performance records 302, 309
CMF Transaction Statistics report, CICS/MVS (CICS701) 318
collection optimization, data 19
combinations
FILE_DB_TYPE and FILE_DB_ACTION 125, 130
FILE_DB_TYPE and FILE_DB_SUBTYPE 130
Command, DB2 Connection, Statistics report (CICS819) 349
common fields
for BTS 89
for CHN 90
for DOC 92
for subcomponents 1,4,8, and 11 76
for WEB 92
communication, intersystem and interregion 202, 332, 338,
340, 341
component installation 20
Connection, ISC/IRC System Entries by (CICS813) statistics
report 341
control tables 299
CICS_DICTIONARY 299
CICS_FIELD 300
conventions
typeface xiv
CPU utilization 311, 312, 314, 316
CPU Utilization Trend report, Application 311
customer support
See Software Support
customization, CICS Partitioning feature 41, 49
customization, CICS Performance feature 9
D
daily average response time, for the total commands, per
database/file type 324
daily average response time, per command, per database/file
type 324
daily reports
CICS Transaction Processor Utilization (CICSA06) 366
CICS Transaction Processor Utilization (CICSA07) 319
daily total requests, per database/file type 325, 326
data
CMF accounting class 318
dictionary 66, 299
types
CICS availability 27
CICS availability using XRF 28
performance (dispatch time) 35
performance (response time) 29, 32
resource availability 27
data categories, Tivoli Decision Support for z/OS 27
data collection, optimizing 19
data tables
CICS_O_A_FL_H,_D,_W 127
CICS_O_A_USR_FL_ H,_D,_W 128
CICS_O_FL_DTL_H, _D, _W 129
CICS_O_FL_H, _D, _W 125
CICS_O_TRAN_FL_ H,_D,_W 127
in the CICS monitoring component
CICS_A_BASIC_H, _W 97
CICS_A_DBCTL_H, _W 100
CICS_A_DBCTL_USR_H, _W 114
CICS_A_DLI_H, _W 102
CICS_A_DLI_USR_H, _W 116
CICS_A_USR_H, _W 111
CICS_DBCTL_TRAN_H, _D, _W 108
CICS_DBCTL_USR_H, _D, _W 94
CICS_DLI_TRAN_H, _D, _W 109
CICS_DLI_USR_H, _D, _W 96
CICS_M_ACCOUNT_H, _D, _W, _M 103
CICS_TRAN_USR_H, _D, _W 71, 118, 119, 120
CICS_TRANSACTION_H, _D, _W 104
CICSBTS_A_BASIC_H, _W 98
CICSBTS_A_USR_H, _W 111
CICSBTS_TRAN_USR_H, _D, _W 72
CICSBTS_TRANSACT_H, _D, _W 105
CICSCHN_A_BASIC_H, _W 98
CICSCHN_A_USR_H, _W 112
CICSCHN_TRAN_USR_H, _D, _W 73
CICSCHN_TRANSACT_H, _D, _W 106
CICSDOC_A_BASIC_H, _W 99
Index
391
data tables (continued)
in the CICS monitoring component (continued)
CICSDOC_A_USR_H, _W 113
CICSDOC_TRAN_USR_H, _D, _W 74
CICSDOC_TRANSACT_H, _D, _W 106
CICSWEB_A_BASIC_H, _W 100
CICSWEB_A_USR_H, _W 113
CICSWEB_TRAN_USR_H, _D, _W 75
CICSWEB_TRANSACT_H, _D, _W 107
in the CICS Resource Manager Interface subcomponent
CICS_RMI_PERF_T 121
in the CICS statistics component
CICS_DOCT_RES_D 138, 139
CICS_MVSTCB_D 135
CICS_MVSTCB_RES_D 136
CICS_MVSTCB_RES_H 137
CICS_PIPELINE_T 137
CICS_S_AUTO_TERM_D 142
CICS_S_AUTO_TERM_T 140
CICS_S_CFDT_GREQ_D 144
CICS_S_CFDT_GREQ_T 143
CICS_S_CFDT_SERV_D 147
CICS_S_CFDT_SERV_T 145
CICS_S_CFDT_STOR_T 150
CICS_S_CFDT_TBAC_D 151
CICS_S_CFDT_TBAC_T 150
CICS_S_DB2CONN_D 155
CICS_S_DB2CONN_T 152
CICS_S_DB2ENTRY_D 159
CICS_S_DB2ENTRY_T 157
CICS_S_DBCTL_D 162
CICS_S_DBCTL_T 160
CICS_S_DISPATCH_D 164
CICS_S_DISPATCH_T 162
CICS_S_DLI_D 167, 169, 170
CICS_S_DLI_T 166
CICS_S_DUMP_D 172
CICS_S_DUMP_T 171
CICS_S_ENQUE_MGR_D 174
CICS_S_ENQUE_MGR_T 172
CICS_S_FILE_D 182
CICS_S_FILE_T 179
CICS_S_GLB_TCPIP_D 185
CICS_S_GLB_TCPIP_T 184
CICS_S_GLBURIMAP_D 188
CICS_S_GLBURIMAP_T 186
CICS_S_GLOBAL_D 193
CICS_S_GLOBAL_T 189
CICS_S_INTERCOM_D 202
CICS_S_INTERCOM_T 197
CICS_S_JOURNAL_D 208
CICS_S_JOURNAL_D2 175, 209, 210, 211, 212
CICS_S_JOURNAL_T 207
CICS_S_JOURNAL_T2 207
CICS_S_LOGSTREAM_D 214
CICS_S_LOGSTREAM_T 213
CICS_S_LSR_POOL_D 217
CICS_S_LSR_POOL_T 215
CICS_S_LSRP_FILE_D 220
CICS_S_LSRP_FILE_T 219
CICS_S_MONITOR_D 224
CICS_S_MONITOR_T 222
CICS_S_NC_LSTRUC_D 226
CICS_S_NC_LSTRUC_T 225
CICS_S_NCS_STOR_T 227
CICS_S_PIPELINE_T 228
CICS_S_PROGRAM_D 230
392
data tables (continued)
in the CICS statistics component (continued)
CICS_S_PROGRAM_T 228
CICS_S_RECOV_MGR_D 233
CICS_S_RECOV_MGR_T 232
CICS_S_STOR_DOM_D 236
CICS_S_STOR_DOM_T 235
CICS_S_STOR_DSA_D 239
CICS_S_STOR_DSA_T 236
CICS_S_STOR_TASK_D 242
CICS_S_STOR_TASK_T 241
CICS_S_TCLASS_D 244
CICS_S_TCLASS_T 243
CICS_S_TCPIP_D 247
CICS_S_TCPIP_T 245
CICS_S_TERMINAL_D 250
CICS_S_TERMINAL_T 248
CICS_S_TRAN_D, _M 252
CICS_S_TRAN_T 251
CICS_S_TRANSIENT_D 255
CICS_S_TRANSIENT_T 253
CICS_S_TS_BPOOL_D 258
CICS_S_TS_BPOOL_T 257
CICS_S_TS_CF_D 261
CICS_S_TS_CF_T 259
CICS_S_TS_STOR_D 264
CICS_S_TS_STOR_T 263
CICS_S_URIMAP_T 265
CICS_S_WEBSERV_T 266
CICS_SMD_SUBP_D 221
CICS_SMD_SUBP_H 222
CICS_TCPIP_CONN_D 267
CICS_TCPIP_CONN_H 269
in the CICS transaction and unit-of-work analysis
component
CICS_T_TRAN_T 270
CICS_T_UOW_TV1 291
CICS_T_UOW_TV2 133, 134, 291
CICS_TCPIP_CONN_H 293
CICSBTS_T_TRAN_T 284
CICSCHN_T_TRAN_T 286
CICSDOC_T_TRAN_T 288
CICSWEB_T_TRAN_T 290
naming standard 69
summarization-level suffixes 69
data tables, CICS Partitioning feature
in the CICS statistics component
CICS_S_FEPI_D 178
CICS_S_FEPI_T 176
naming standard 47
summarization-level suffixes 47
database call rate 317
database/file type
daily average response time, for the total commands 324
daily average response time, per command 324
daily total requests 325, 326
hourly total command count 322, 323
dataspaces, I/O wait and expanded storage 35
DB2 Connection: Buffer Pool Statistics report (CICS818) 347
DB2 Connection: Command Statistics report (CICS819) 349
DB2 Connection: TCB Statistics report (CICS817) 346
DB2 Entries: Performance Statistics report (CICS822) 352
DB2 Entries: Request Statistics report (CICS821) 351
DB2 Entries: Resource Info Statistics report (CICS820) 350
DBCTL (subcomponent 2) data tables
CICS_DBCTL_TRAN_H, _D, _W 108
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
DBCTL application analysis (subcomponent 5) data tables
CICS_A_DBCTL_H, _W 100
DBCTL application analysis (subcomponent 5) reports
CICS Application DLI Call Utilization, Trend 317
DBCTL application user (subcomponent 12) data tables
CICS_A_DBCTL_USR_H, _W 114
DBCTL transaction (subcomponent 9) data tables
CICS_DBCTL_USR_H, _D, _W 94
detail report
CICS Application Channel Performance 305
CICS ISC/IRC Function Shipping by Connection 337
CICS Transaction Channel Performance 304
detail reports
CICS Application I/O Wait Times, Detail 312
CICS Application Main Response Times, Detail 314
CICS Application Response Times, Detail 309
CICS Application Wait Times, Detail 316
CICS Transaction Performance, Detail 302, 368
DFHJCT (journaling control table) macro 18
DFHMCT (monitoring control table) macro 17
DFHMNDUP utility program 66
DFHSIT (system initialization table) macro 16
dictionary data 66, 299
dispatch time 35
DL/I (subcomponent 3) data tables
CICS_DLI_TRAN_H, _D, _W 109
DL/I application analysis (subcomponent 6) data tables
CICS_A_DLI_H, _W 102
DL/I application user (subcomponent 13) data tables
CICS_A_DLI_USR_H, _W 116
DL/I transaction (subcomponent 10) data tables
CICS_DLI_USR_H, _D, _W 96
DLI Call Utilization Trend report, Application (CICSA51) 317
DOC, common fields 92
documentation
TDS 387
domain, loader 328
DRL1CIEX utility program 66
DRLJCIEX JCL 66
DTB, Global statistics report (CICS804) 331
Dynamic Storage (DSA) Usage statistics report (CICS809) 335
dynamic transaction backout 331
E
education
See Tivoli technical training
Enqueue Manager, TS, statistics report (CICS815) 343
Entries by Connection statistics report (CICS813), ISC/IRC
System 341
Entries, ISC/IRC Mode statistics report (CICS812) 339
environment restrictions, CICS Partitioning feature 48
evaluation and planning 10
evaluation and planning, CICS Partitioning feature 41
exception data 37
expanded storage and I/O wait dataspaces 35
extended recovery facility (XRF) 28
format, Tivoli Decision Support for z/OS report
301
G
Global DTB statistics report (CICS804) 331
Global IRC Batch statistics report (CICS806) 332
Global ISC/IRC statistics report (CICS811) 338
Global Loader statistics report (CICS801) 320, 321, 328, 365
Global Temporary Storage statistics report (CICS802) 329
Global VTAM statistics report (CICS803) 330
Global, TCP/IP, Statistics report (CICS832) 356
Global, URIMAP, Statistics report (CICS834) 362
glossary 385
groups, report 301
H
hourly average DB2 information, per transaction 327
hourly total command count, per database/file type 323
hourly total request count, per database/file type 322
I
I/O wait and expanded storage dataspaces 35
I/O Wait Times Detail report, Application 312
identifiers, report 301
incident data 37
information centers, searching for problem resolution
installation
CICS Partitioning feature 41
CICS Performance feature 9
component 20
requirements
CICS/ESA 16, 17
CICS/MVS 17
making input data available 16
optimizing data collection 19
putting feature into production 26
testing the installation 26
updating lookup tables 23
internal response time 29, 307, 308
Internet
searching for problem resolution 377
interregion communication (IRC) 332, 338, 340, 341
intersystem communication (ISC) 338, 340, 341
IRC Batch, Global statistics report (CICS806) 332
ISC/IRC
Global statistics report (CICS811) 338
Mode Entries statistics report (CICS812) 339
System Entries by Connection statistics report
(CICS813) 341
377
J
JCL, DRLJCIEX 66
JCT (journaling control table) 18
journaling control table macro (DFHJCT)
18
F
file and data base usage, monitoring 29
File Statistics report (CICS810) 336
FILE_DB_TYPE and FILE_DB_ACTION combinations 125,
130
FILE_DB_TYPE and FILE_DB_SUBTYPE combinations 130
fixes, obtaining 377
K
knowledge bases, searching for problem resolution
377
Index
393
L
list of terms used in this book 385
Loader, Global statistics report (CICS801) 320, 321, 328, 365
Logstreams, TS, statistics report (CICS816) 345
LookAt message retrieval tool xii
lookup tables 294
CICS_LOOKUP_APPL 295
CICS_LOOKUP_SYSTEM 296
CICS_OMEG_FIELD 296
CICS_TIMEZONES 24, 294, 299
updating CICS_LOOKUP_APPL 24
updating CICS_LOOKUP_SYSTEM 25
updating CICS_TIMEZONES 24
with System Performance feature installed 26
M
macros
journaling control table (DFHJCT) 18
monitoring control table (DFHMCT) 17
system initialization table (DFHSIT) 16
Main Response Times Detail report, Application 314
manuals
See publications
TDS 387
MCT (monitoring control table) 17
measuring response time 32
message retrieval tool, LookAt xii
mirror tasks 291
Mode Entries, ISC/IRC statistics report (CICS812) 339
monitoring component
CICS OMEGAMON
description 15
description 13
description, CICS Partitioning feature 42
report 302, 368
tables 70
tables, CICS Partitioning feature 47
monitoring control table macro (DFHMCT) 17
monitoring file and data base usage 29
monthly reports
CICS Transaction Processor Utilization (CICSA04) 367
CICS Transaction Processor Utilization (CICSA05) 319
multiregion operation (MRO) 202, 341
MVS_WORKLOAD_TYPE lookup table 26
N
NC: CICS Storage Statistics report (CICS830)
361
O
OMEGAMON
report 324
OMEGAMON
report 324
OMEGAMON
report 323
OMEGAMON
OMEGAMON
report 326
OMEGAMON
report 325
OMEGAMON
394
database/file avg command response, daily
database/file avg request response, daily
database/file total commands, hourly
database/file total requests, hourly report 322
transaction database/file commands, daily
transaction database/file requests, daily
transaction DB2 averages, hourly report
327
online publications
accessing xiii
ordering publications xiii
overview reports
CICS Application Response Times, Overview
307
P
performance
CICS monitored using Tivoli Decision Support for
z/OS 27
records, CMF 302, 309
Performance Detail report, Transaction (CICS101) 302, 368
Performance, DB2 Entries, Statistics report (CICS822) 352
problem determination
describing problems 380
determining business impact 379
submitting problems 380
processor second, CICS transactions per 319
Processor Utilization, CICS Transaction
daily reports
CICSA06 366
CICSA07 319
monthly reports
CICSA04 367
CICSA05 319
Program Usage statistics report (CICS808) 334
programs, utility (DRL1CIEX and DFHMNDUP) 66
publications x
accessing online xiii
ordering xiii
TDS 387
R
rate, database call 317
records, CMF performance 302, 309
recovery facility, extended (XRF) 28
Recovery Manager, TS, statistics report (CICS814) 342
report
attributes 302
CICS Application Channel Performance, Detail 305
CICS ISC/IRC Function Shipping by Connection 337
CICS OMEGAMON database/file avg command response,
daily 324
CICS OMEGAMON database/file avg request response,
daily 324
CICS OMEGAMON database/file total commands,
hourly 323
CICS OMEGAMON database/file total requests,
hourly 322
CICS OMEGAMON monitoring component 322
CICS OMEGAMON transaction database/file commands,
daily 326
CICS OMEGAMON transaction database/file requests,
daily 325
CICS OMEGAMON transaction DB2 averages, hourly 327
CICS Transaction Channel Performance, Detail 304
format and general description 301
identifiers, unique 301
in the CICS monitoring component
CICS Application CPU Utilization, Trend 311
CICS Application DLI Call Utilization, Trend 317
CICS Application I/O Wait Times, Detail 312
CICS Application Main Response Times, Detail 314
CICS Application Response Times, Detail 309
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
report (continued)
in the CICS monitoring component (continued)
CICS Application Response Times, Overview 307
CICS Application Response Times, Trend 308
CICS Application Wait Times, Detail 316
CICS Transaction Performance, Detail 302, 368
CICS Transaction Processor Utilization, Daily 319
CICS Transaction Processor Utilization, Monthly 319
CICS/MVS CMF Transaction Statistics 318
in the CICS statistics component
CICS CFDT: Server Statistics 360
CICS CFDT: Storage Statistics 361
CICS DB2 Connection: Buffer Pool Statistics 347
CICS DB2 Connection: Command Statistics 349
CICS DB2 Connection: TCB Statistics 346
CICS DB2 Entries: Performance Statistics 352
CICS DB2 Entries: Request Statistics 351
CICS DB2 Entries: Resource Info Statistics 350
CICS Dynamic Storage (DSA) Usage 335
CICS File Statistics 336
CICS Global DTB 331
CICS Global IRC Batch 332
CICS Global Loader 320, 321, 328, 365
CICS Global Temporary Storage 329
CICS Global VTAM 330
CICS ISC/IRC Global 338
CICS ISC/IRC Mode Entries 339
CICS ISC/IRC System Entries by Connection 341
CICS NC: Storage Statistics 361
CICS Program Usage 334
CICS Shared TS queue server: Buffer Pool
Statistics 353
CICS Shared TS queue server: Storage Statistics 355
CICS TCP/IP: Global Statistics 356
CICS TCP/IP: Service Requests Statistics 358
CICS TCP/IP: Service Requests, Daily Trend 359
CICS TCP/IP: Service Statistics 357
CICS Transaction Processor Utilization, Daily 366
CICS Transaction Processor Utilization, Monthly 367
CICS Transaction Usage 333
CICS TS Enqueue Manager statistics 343
CICS TS Logstreams statistics 345
CICS TS Recovery Manager statistics 342
CICS URIMAP: Global Statistics 362
CICS URIMAP: Resource Statistics 363
in the CICS transaction and unit-of-work analysis
component
CICS UOW Response Times 369
OMEGAMON database/file avg command response,
daily 324
OMEGAMON database/file avg request response,
daily 324
OMEGAMON database/file total commands, hourly 323
OMEGAMON database/file total requests, hourly 322
OMEGAMON transaction database/file commands,
daily 326
OMEGAMON transaction database/file requests,
daily 325
OMEGAMON transaction DB2 averages, hourly 327
predefined groups 301
source tables 301
variables 302
report IDs
CICS101 (Transaction Performance, Detail report) 302, 368
CICS401 (Application Response Times, Overview
report) 307
CICS402 (Application Response Times, Trend report) 308
report IDs (continued)
CICS403 (Application Response Times, Detail report) 309
CICS404 (Application CPU Utilization, Trend report) 311
CICS405 (Application I/O Wait Times, Detail report) 312
CICS406 (Application Main Response Times, Detail
report) 314
CICS407 (Application Wait Times, Detail report) 316
CICS701 (CICS/MVS CMF Transaction Statistics
report) 318
CICS801 (Global Loader statistics report) 320, 321, 328,
365
CICS802 (Global Temporary Storage statistics report) 329
CICS803 (Global VTAM statistics report) 330
CICS804 (Global DTB statistics report) 331
CICS806 (Global IRC Batch statistics report) 332
CICS807 (Transaction Usage statistics report) 333
CICS808 (Program Usage statistics report) 334
CICS809 (Dynamic Storage [DSA] Usage statistics) 335
CICS810 (File Statistics report) 336
CICS811 (ISC/IRC Global statistics report) 338
CICS812 (ISC/IRC Mode Entries statistics report) 339
CICS813 (ISC/IRC System Entries by Connection statistics
report) 341
CICS814 (TS Recovery Manager statistics) 342
CICS815 (TS Enqueue Manager statistics) 343
CICS816 (TS Logstreams statistics) 345
CICS817 (DB2 Connection: TCB Statistics) 346
CICS818 (DB2 Connection: Buffer Pool Statistics) 347
CICS820 (DB2 Entries: Resource Info Statistics) 350
CICS821 (DB2 Entries: Request Statistics) 351
CICS822 (DB2 Entries: Performance Statistics) 352
CICS823 (Shared TS queue server: Buffer Pool
Statistics) 353
CICS824 (Shared TS queue server: Storage Statistics) 355
CICS825 (TCP/IP: Service Statistics) 357
CICS826 (TCP/IP: Service Requests Statistics) 358
CICS827 (TCP/IP: Service Requests, Daily Trend) 359
CICS828 (CFDT: Server Statistics) 360
CICS829 (CFDT: Storage Statistics) 361
CICS830 (NC: Storage Statistics) 361
CICS831( JVM Profile Statistics, Daily report) 365
CICS832 (TCP/IP: Global Statistics) 356
CICS834 (URIMAP: Global Statistics) 362
CICS835 (URIMAP: Resource Statistics) 363
CICS902 (UOW Response Times report) 369
CICSA04 (Transaction Processor Utilization, Monthly
report) 367
CICSA05 (Transaction Processor Utilization, Monthly
report) 319
CICSA06 (Transaction Processor Utilization, Daily
report) 366
CICSA07 (Transaction Processor Utilization, Daily
report) 319
CICSA51 (Application DLI Call Utilization, Trend
report) 317, 349
CICSJ01 (Enterprise Java Beans Details, Daily report) 321
CICST01 (Transactions Resources Details, Daily
report) 320
Request, DB2 Entries, Statistics report (CICS821) 351
requirements, installation
CICS/ESA 16, 17
CICS/MVS 17
making input data available 16
optimizing data collection 19
putting feature into production 26
testing the installation 26
updating lookup tables 23
Index
395
resource availability 28
Resource Info, DB2 Entries, Statistics report (CICS820) 350
Resource, URIMAP, Statistics report (CICS835) 363
response time 32
by unit-of-work ID 291
internal 29, 307, 308
Response Times Detail report, Application (CICS403) 309
Response Times Overview report, Application (CICS401) 307
Response Times report, UOW (CICS902) 369
Response Times Trend report, Application (CICS402) 308
S
second, processor 319
Server, CICS CFDT, Statistics report (CICS828) 360
Service Requests, TCP/IP, Statistics report (CICS826) 358
Service, TCP/IP, Daily Trend, Statistics report (CICS827) 359
Service, TCP/IP, Statistics report (CICS825) 357
Shared TS queue server: Buffer Pool Statistics report
(CICS823) 353
Shared TS queue server: Storage Statistics report
(CICS824) 355
SIT (system initialization table) 16
Software Support
contacting 379
describing problems 380
determining business impact 379
receiving weekly updates 378
submitting problems 380
source tables, report 301
statistics component
description 16
description, CICS Partitioning feature 44
report 328
tables 133
statistics data tables
CICS_S_AUTO_TERM_D 142
CICS_S_AUTO_TERM_T 140
CICS_S_CFDT_GREQ_D 144
CICS_S_CFDT_GREQ_T 143
CICS_S_CFDT_STOR_T 150
CICS_S_CFDT_TBAC_D 151
CICS_S_CFDT_TBAC_T 150
CICS_S_DB2CONN_D 155
CICS_S_DB2CONN_T 152
CICS_S_DB2ENTRY_D 159
CICS_S_DB2ENTRY_T 157
CICS_S_DBCTL_D 162
CICS_S_DBCTL_T 160
CICS_S_DCFDT_SERV_D 147
CICS_S_DCFDT_SERV_T 145
CICS_S_DISPATCH_D 164
CICS_S_DISPATCH_T 162
CICS_S_DLI_D 167, 169, 170
CICS_S_DLI_T 166
CICS_S_DUMP_D 172
CICS_S_DUMP_T 171
CICS_S_ENQUE_MGR_D 174
CICS_S_ENQUE_MGR_T 172
CICS_S_FEPI_D 178
CICS_S_FEPI_T 176
CICS_S_FILE_D 182
CICS_S_FILE_T 179
CICS_S_GLOBAL_D 193
CICS_S_GLOBAL_T 189
CICS_S_INTERCOM_D 202
CICS_S_INTERCOM_T 197
396
statistics data tables (continued)
CICS_S_JOURNAL_D 208
CICS_S_JOURNAL_D2 175, 209, 210, 211, 212
CICS_S_JOURNAL_T 207
CICS_S_JOURNAL_T2 207
CICS_S_LOGSTREAM_D 214
CICS_S_LOGSTREAM_T 213
CICS_S_LSR_POOL_D 217
CICS_S_LSR_POOL_T 215
CICS_S_LSRP_FILE_D 220
CICS_S_LSRP_FILE_T 219
CICS_S_MONITOR_D 224
CICS_S_MONITOR_T 222
CICS_S_NC_LSTRUC_D 226
CICS_S_NC_LSTRUC_T 225
CICS_S_NCS_STOR_T 227
CICS_S_PIPELINE_T 228
CICS_S_PROGRAM_D 230
CICS_S_PROGRAM_T 228
CICS_S_RECOV_MGR_D 233
CICS_S_RECOV_MGR_T 232
CICS_S_STOR_DOM_D 236
CICS_S_STOR_DOM_T 235
CICS_S_STOR_DSA_D 239
CICS_S_STOR_DSA_T 236
CICS_S_STOR_TASK_D 242
CICS_S_STOR_TASK_T 241
CICS_S_TCLASS_D 244
CICS_S_TCLASS_T 243
CICS_S_TCPIP_D 245, 247
CICS_S_TERMINAL_D 250
CICS_S_TERMINAL_T 248
CICS_S_TRAN_D, _M 252
CICS_S_TRAN_T 251
CICS_S_TRANSIENT_D 255
CICS_S_TRANSIENT_T 253
CICS_S_TS_BPOOL_D 258
CICS_S_TS_BPOOL_T 257
CICS_S_TS_CF_D 261
CICS_S_TS_CF_T 259
CICS_S_TS_STOR_D 264
CICS_S_TS_STOR_T 263
statistics reports 345, 347
CICS CFDT: Server Statistics 360
CICS CFDT: Storage Statistics 361
CICS DB2 Connection: Command Statistics 349
CICS DB2 Connection: TCB Statistics 346
CICS DB2 Entries: Performance Statistics 352
CICS DB2 Entries: Request Statistics 351
CICS DB2 Entries: Resource Info Statistics 350
CICS NC: Storage Statistics 361
CICS Shared TS queue server: Buffer Pool Statistics 353
CICS Shared TS queue server: Storage Statistics 355
CICS TCP/IP: Global Statistics 356
CICS TCP/IP: Service Requests Statistics 358
CICS TCP/IP: Service Requests, Daily Trend 359
CICS TCP/IP: Service Statistics 357
CICS Transaction Processor Utilization, Daily 366
CICS Transaction Processor Utilization, Monthly 367
CICS TS Enqueue Manager statistics 343
CICS TS Recovery Manager statistics 342
CICS URIMAP: Global Statistics 362
CICS URIMAP: Resource Statistics 363
CICS/ESA Dynamic Storage (DSA) Usage 335
CICS/ESA File Statistics 336
CICS/ESA Global DTB 331
CICS/ESA Global IRC Batch 332
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
statistics reports (continued)
CICS/ESA Global Loader 320, 321, 328, 365
CICS/ESA Global Temporary Storage 329
CICS/ESA Global VTAM 330
CICS/ESA ISC/IRC Global 338
CICS/ESA ISC/IRC Mode Entries 339
CICS/ESA ISC/IRC System Entries by Connection 341
CICS/ESA Program Usage 334
CICS/ESA Transaction Usage 333
CICS/MVS CMF Transaction Statistics 318
statistics requirements, CICS/ESA 17
Statistics, File report (CICS810) 336
storage stress 34
Storage Usage, Dynamic (DSA) statistics report
(CICS809) 335
Storage, CICS CFDT, Statistics report (CICS829) 361
Storage, CICS NC, Statistics report (CICS830) 361
storage, expanded 35
Storage, Global Temporary statistics report (CICS802) 329
Storage, Shared TS queue server, Statistics report
(CICS824) 355
stress, storage 34
subcomponent 1 (basic) data tables
CICS_TRANSACTION_H, _D, _W 104
CICSBTS_TRAN_USR_H, _D, _W 72
CICSCHN_A_BASIC_H, _W 98
CICSCHN_TRAN_USR_H, _D, _W 73
CICSCHN_TRANSACT_H, _D, _W 106
CICSDOC_TRAN_USR_H, _D 74
CICSWEB_TRAN_USR_H, _D 75
subcomponent 1 (basic) reports
CICS Transaction Performance, Detail 302, 368
subcomponent 10 (DL/I transaction) data tables
CICS_DLI_USR_H, _D, _W 96
subcomponent 11 (basic application user) data tables
CICS_A_USR_H, _W 111
CICSBTS_A_USR_H, _W 111
CICSCHN_A_USR_H, _W 112
CICSDOC_A_USR_H, _W 113
CICSWEB_A_USR_H, _W 113
subcomponent 12 (DBCTL application user) data tables
CICS_A_DBCTL_USR_H, _W 114
subcomponent 13 (DL/I application user) data tables
CICS_A_DLI_USR_H, _W 116
subcomponent 2 (DBCTL) data tables
CICS_DBCTL_TRAN_H, _D, _W 108
subcomponent 3 (DL/I) data tables
CICS_DLI_TRAN_H, _D, _W 109
subcomponent 4 (basic application analysis) data tables
CICS_A_BASIC_H, _W 97
CICSBTS_A_BASIC_H, _W 98
CICSDOC_A_BASIC_H, _W 99
CICSWEB_A_BASIC_H, _W 100
subcomponent 4 (basic application analysis) reports
CICS Application CPU Utilization, Trend 311
CICS Application I/O Wait Times, Detail 312
CICS Application Main Response Times, Detail 314
CICS Application Response Times, Detail 309
CICS Application Response Times, Overview 307
CICS Application Response Times, Trend 308
CICS Application Wait Times, Detail 316
subcomponent 5 (DBCTL application analysis) data tables
CICS_A_DBCTL_H, _W 100
subcomponent 5 (DBCTL application analysis) reports
CICS Application DLI Call Utilization, Trend 317
subcomponent 6 (DL/I application analysis) data tables
CICS_A_DLI_H, _W 102
subcomponent 7 (CICS/MVS [global + accounting]) data
tables
CICS_M_ACCOUNT_H, _D, _W, _M 103
subcomponent 7 (CICS/MVS [global + accounting]) reports
CICS Transaction Processor Utilization, Daily 319
CICS Transaction Processor Utilization, Monthly 319
CICS/MVS CMF Transaction Statistics 318
subcomponent 8 (basic transaction) data tables
CICS_TRAN_USR_H, _D 71, 118, 119, 120
CICSBTS_TRANSACT_H, _D, _W 105
CICSDOC_TRANSACT_H, _D, _W 106
CICSWEB_TRANSACT_H, _D, _W 107
subcomponent 9 (DBCTL transaction) data tables
CICS_DBCTL_USR_H, _D, _W 94
suffixes, data-table 69
suffixes, data-table, CICS Partitioning feature 47
System Entries by Connection, ISC/IRC statistics report
(CICS813) 341
system initialization table macro (DFHSIT) 16
T
tables
CICS_LOOKUP_APPL 24
CICS_LOOKUP_SYSTEM 25
CICS_TIMEZONES 24
control 299
lookup 294
with System Performance feature installed 26
reports’ source 301
updating lookup 23
TCB, DB2 Connections, Statistics report (CICS817) 346
TCP/IP: Global Statistics report (CICS832) 356
TCP/IP: Service Requests Statistics report (CICS826) 358
TCP/IP: Service Requests, Daily Trend report (CICS827) 359
TCP/IP: Service Statistics report (CICS825) 357
Temporary Storage, Global statistics report (CICS802) 329
terms used in this book 385
time, internal response 29, 307, 308
Tivoli Decision Support for z/OS data, categories of 27
Tivoli Decision Support for z/OS’s role in monitoring and
analyzing CICS performance 27
Tivoli software information center xiii
Tivoli technical training xiv
training, Tivoli technical xiv
transaction and unit-of-work analysis component
description 16
description, CICS Partitioning feature 44
report 369
tables 270
tables, CICS Partitioning feature 48
transaction and unit-of-work analysis component data tables
CICS_T_TRAN_T 270
CICS_T_UOW_TV1 291
CICS_T_UOW_TV2 133, 134, 291
CICSBTS_T_TRAN_T 284
CICSCHN_T_TRAN_T 286
CICSDOC_T_TRAN_T 288
CICSWEB_T_TRAN_T 290
transaction backout, dynamic 331
transaction performance data 29
Transaction Performance, Detail report (CICS101) 302, 368
Transaction Processor Utilization, Daily report (CICSA06) 366
Transaction Processor Utilization, Daily report (CICSA07) 319
Transaction Processor Utilization, Monthly report
(CICSA04) 367
Index
397
Transaction Processor Utilization, Monthly report
(CICSA05) 319
Transaction Statistics report, CICS/MVS CMF (CICS701)
Transaction Usage statistics report (CICS807) 333
trend reports
CICS Application CPU Utilization, Trend 311
CICS Application DLI Call Utilization, Trend 317
CICS Application Response Times, Trend 308
TS Enqueue Manager statistics report (CICS815) 343
TS Logstreams statistics report (CICS816) 345
TS Recovery Manager statistics report (CICS814) 342
typeface conventions xiv
318
U
unit-of-work analysis component, transaction and
description 16
description, CICS Partitioning feature 44
report 369
tables 270
tables, CICS Partitioning feature 48
unit-of-work response times 369
UOW Response Times report (CICS902) 369
updating lookup tables 23
URIMAP: Global Statistics report (CICS834) 362
URIMAP: Resource Statistics report (CICS835) 363
Usage, Dynamic Storage (DSA) statistics report
(CICS809) 335
Usage, Program statistics report (CICS808) 334
Usage, Transaction statistics report (CICS807) 333
use, processor 311
utility programs (DRL1CIEX and DFHMNDUP) 66
utilization report, DL/I call 317
Utilization, Daily report, CICS Transaction Processor
(CICSA06) 366
Utilization, Daily report, CICS Transaction Processor
(CICSA07) 319
Utilization, Monthly report, CICS Transaction Processor
(CICSA04) 367
Utilization, Monthly report, CICS Transaction Processor
(CICSA05) 319
V
variables, report 302
Verifying OMEGAMON XE for CICS requirements 18
view tables for the CICS transaction and unit-of-work analysis
component
CICS_T_UOW_TV1 291
CICS_T_UOW_TV2 133, 134, 291
VTAM, Global statistics report (CICS803) 330
W
Wait Times Detail report, Application
wait, I/O 35
WEB, common fields 92
316
X
XRF performance
398
28
Tivoli Decision Support for z/OS: CICS Performance Feature Guide and Reference
Program Number: 5698-B06
Printed in USA
SH19-6820-10
Tivoli Decision Support for z/OS
Spine information:
Version 1.8.1
CICS Performance Feature Guide and Reference