Network Performance Feature Referencepublib.boulder.ibm.com/tividd/td/TDS390/SH19-6822-08/en... ·...

Tivoli® Decision Support for z/OS®

Network Performance Feature Reference Version 1.7

SH19-6822-08

��

Note

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

Ninth Edition (November 2004)

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

This edition replaces SH19-6822-07.

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

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

Contents

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

Preface . . . . . . . . . . . . . . . ix Who should read this book . . . . . . . . . ix What this book contains . . . . . . . . . . ix Publications . . . . . . . . . . . . . . x

IBM Tivoli Decision Support for z/OS . . . . . x Using LookAt to look up message explanations xii Accessing publications online . . . . . . . xii Ordering publications . . . . . . . . . . xii

Accessibility . . . . . . . . . . . . . . xii Tivoli technical training . . . . . . . . . . xiii Contacting IBM Software Support . . . . . . xiii

Determine the business impact of your problem xiii Describe your problem and gather background information . . . . . . . . . . . . . xiv Submit your problem to IBM Software Support xiv Searching knowledge bases . . . . . . . . xiv

Search the information center on your local system or network . . . . . . . . . . xv Search the Internet . . . . . . . . . . xv

Obtaining fixes . . . . . . . . . . . . xv Updating support information . . . . . . . xvi

Conventions used in this book . . . . . . . . xvi Typeface conventions . . . . . . . . . . xvi

Changes in this edition . . . . . . . . . . xvii

Part 1. Tables and logs . . . . . . . 1

Chapter 1. Component tables . . . . . 3 Naming standard for data tables . . . . . . . . 3 Table descriptions . . . . . . . . . . . . 3

NW_ALERT_BASIC_H, _D, _W . . . . . . . 5 NW_ALERT_GENERIC_H, _D, _W . . . . . . 6 NW_CONFIG_HARDWARE . . . . . . . . 8 NW_CONFIG_SOFTWARE . . . . . . . . 10 NW_FRRYL_UTIL_H, _D, _W . . . . . . . 12 NW_FRRYLM_UTIL_H, _D, _W . . . . . . 15 NW_FRRYP_UTIL_H, _D, _W . . . . . . . 17 NW_FRRYPS_UTIL_H, _D, _W . . . . . . . 20 NW_FTP_REQUEST_H, _D, _M . . . . . . 22 NW_FTP_REQUEST_T . . . . . . . . . 24 NW_FTP_TRANSMIT_H, _D, _M . . . . . . 26 NW_LANB_UTIL_H, _D, _W . . . . . . . 27 NW_LANS_UTIL_H, _D, _W . . . . . . . 30 NW_LINE_UTIL_H, _D, _W . . . . . . . . 32 NW_NCP_UTIL_H, _D, _W . . . . . . . . 36 NW_NEO_UTIL_H, _D, _W . . . . . . . . 39 NW_NPMIP_PERFORM_H, _D . . . . . . . 42 NW_NPMIP_PERFVOL_H, _D . . . . . . . 43 NW_NPMIP_WRKLOAD_H, _D . . . . . . 44 NW_NPM_TRANSIT_H, _D, _W, _M . . . . . 45 NW_NPM_TRANS_IP_H, _D, _W, _M . . . . 51 NW_NPM_TRANS_SUM_H, _D, _W, _M . . . 57

NW_NPM_UTIL_H, _D, _W . . . . . . . . 63 NW_NTRIL_UTIL_H, _D, _W . . . . . . . 66 NW_NTRIP_UTIL_H, _D, _W . . . . . . . 69 NW_ODLCL_UTIL_H, _D, _W . . . . . . . 72 NW_ODLCP_UTIL_H, _D, _W . . . . . . . 74 NW_PU_UTIL_H, _D, _W . . . . . . . . 76 NW_ROUT_CISCIP_H, _D, _W . . . . . . . 78 NW_ROUT_CISCO_H, _D, _W . . . . . . . 82 NW_ROUT_CISPOOL_H, _D, _W . . . . . . 83 NW_ROUT_IBM_H, _D, _W . . . . . . . . 84 NW_ROUT_INTTRAF_H, _D, _W . . . . . . 87 NW_RTM_RESPONSE_H, _D, _W, _M . . . . 89 NW_SESSION_FAIL_H, _D, _W . . . . . . 91 NW_SM_UTIL_H, _D, _W . . . . . . . . 93 NW_VTAM_ADDSPACE_H, _D, _W . . . . . 95 NW_VTAM_APPL_H, _D, _W . . . . . . . 96 NW_VTAM_APPN_H, _D, _W . . . . . . . 98 NW_VTAM_BFR_H, _D, _W . . . . . . . 100 NW_VTAM_DEV_H, _D, _W . . . . . . . 104 NW_VTAM_GLOBAL_H, _D, _W . . . . . 108 NW_VTAM_RTP_H, _D, _W . . . . . . . 111 NW_VTAM_VR_H, _D, _W . . . . . . . 112 NW_X25LN_UTIL_H, _D, _W . . . . . . . 114 NW_X25NI_UTIL_H, _D, _W . . . . . . . 118 NW_X25PU_UTIL_H, _D, _W . . . . . . . 121

Chapter 2. Lookup tables . . . . . . 125 Naming standard for lookup tables . . . . . . 125 Table descriptions . . . . . . . . . . . . 125

NW_ALERT_DESC . . . . . . . . . . 126 Example of table contents . . . . . . . 126

NW_ALERT_TYPE . . . . . . . . . . 126 Example of table contents . . . . . . . 126

NW_FAILURE_CODE . . . . . . . . . 126 Example of table contents . . . . . . . 127

NW_GENERAL_CAUSE . . . . . . . . 127 Example of table contents . . . . . . . 127

NW_PROBABLE_CAUSE . . . . . . . . 127 Example of table contents . . . . . . . 128

NW_PRODUCT_ID . . . . . . . . . . 128 Example of table contents . . . . . . . 128

NW_RESOURCE . . . . . . . . . . . 128 NW_SPECIFIC_CAUSE . . . . . . . . . 130

Example of table contents . . . . . . . 130 NW_THRESHOLD . . . . . . . . . . 130

Example of table contents . . . . . . . 130

Chapter 3. Supported log records . . 133 SMF Type 28 . . . . . . . . . . . . . 133 SMF Type 37 . . . . . . . . . . . . . 135 SMF Type 39 . . . . . . . . . . . . . 135 SMF Type 251 . . . . . . . . . . . . . 135 SMF Type 252 or user-defined . . . . . . . . 135

Part 2. Data flow reference . . . . 137

iii

||

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

| |

| |

Chapter 4. Basic data flows . . . . . 141 Understanding Network Performance feature data processing . . . . . . . . . . . . . . 141

NetView, NPM, and NetView FTP capture network data . . . . . . . . . . . . 142 External log collects availability data . . . . 142 NetView and NPM write data to the SMF log 142 Tivoli Decision Support for z/OS collects SMF data . . . . . . . . . . . . . . . 143 Feature adds environment data to tables . . . 145

Looking up period information . . . . . 146 Tivoli Decision Support for z/OS creates reports 147

How the Network Performance feature records time . . . . . . . . . . . . . . . . 147

Chapter 5. Availability component data flows . . . . . . . . . . . . . 149 How the Network Performance feature measures availability . . . . . . . . . . . . . . 149

SNA availability . . . . . . . . . . . 149 End-user and NCP availability . . . . . 149 Application availability . . . . . . . . 150 Cross-connection availability . . . . . . 150

External availability . . . . . . . . . . 150 Availability processing . . . . . . . . . . 151

Capturing SNA availability data . . . . . . 152 Capturing external availability data . . . . . 152 Collecting data . . . . . . . . . . . . 152 Looking up resource information . . . . . . 152

Looking up information for APPL, NCP, or PU resource types . . . . . . . . . . 152 Looking up information for cross-connection resources . . . . . . . . . . . . . 153

Looking up schedule information . . . . . . 154 Looking up the schedule name . . . . . 154 Looking up schedule data . . . . . . . 155

Adding data to the AVAILABILITY_D, _W, and _M tables . . . . . . . . . . . . . . 156 Looking up resource data for reports . . . . 156 Creating reports . . . . . . . . . . . 157

Measuring resource uptime . . . . . . . . . 157 NetView session monitor restart . . . . . . 158

Measuring resource downtime . . . . . . . . 158 Unavailable resources when SMF is switched 159

Measuring switched resource availability . . . . 160

Chapter 6. Configuration component data flows . . . . . . . . . . . . . 161 Configuration . . . . . . . . . . . . . 161 Configuration data collection . . . . . . . . 161 Hardware device configuration data flow . . . . 161

Collecting hardware configuration information 162 Collecting SMF data and updating the NW_CONFIG_HARDWARE table . . . . . 162 Creating reports . . . . . . . . . . . 166

Software product configuration data flow . . . . 166 Collecting software configuration information 166 Collecting SMF data and updating the NW_CONFIG_SOFTWARE table . . . . . . 167 Creating reports . . . . . . . . . . . 169

Chapter 7. NetView FTP component data flows . . . . . . . . . . . . . 171 NetView FTP performance . . . . . . . . . 171 Processing steps for FTP data . . . . . . . . 171

Capturing NetView FTP data . . . . . . . 172 Collecting SMF data . . . . . . . . . . 172

Collecting FTP request data . . . . . . 172 Collecting FTP transmit data . . . . . . 172

Looking up period information . . . . . . 172 Creating reports . . . . . . . . . . . 173

Chapter 8. Problem component data flows . . . . . . . . . . . . . . . 175 Basic and generic alerts . . . . . . . . . . 175

Problem categories . . . . . . . . . . 175 Basic-alert data flow . . . . . . . . . . . 175

Capturing basic-alert data . . . . . . . . 176 Collecting SMF data . . . . . . . . . . 177 Looking up product ID information . . . . . 177

Error conditions . . . . . . . . . . 178 Looking up period information . . . . . . 178 Looking up problem cause information . . . . 178

Error conditions . . . . . . . . . . 179 Creating reports . . . . . . . . . . . 179

Generic alert data flow . . . . . . . . . . 179 Capturing generic alert data . . . . . . . 181 Collecting SMF data . . . . . . . . . . 181 Looking up resource information . . . . . . 181

Error conditions . . . . . . . . . . 182 Looking up period information . . . . . . 183 Looking up probable-cause information . . . 183

Error conditions . . . . . . . . . . 183 Looking up alert description information . . . 183

Error conditions . . . . . . . . . . 184 Looking up alert type information . . . . . 184

Error conditions . . . . . . . . . . 185 Creating reports . . . . . . . . . . . 185

Chapter 9. Session failure component data flows . . . . . . . . . . . . . 187 Session failures . . . . . . . . . . . . . 187 Session failure data flow . . . . . . . . . . 187

Capturing session failure data . . . . . . . 188 Collecting SMF data . . . . . . . . . . 189 Looking up period information . . . . . . 189 Looking up failure descriptions . . . . . . 189 Creating reports . . . . . . . . . . . 190

Chapter 10. RTM response time component data flow . . . . . . . . 191 Response-time reporting based on RTM . . . . 191

RTM response-time definition . . . . . . . 191 RTM response-time data flow . . . . . . . . 192

Capturing RTM response-time data . . . . . 193 Collecting SMF data . . . . . . . . . . 193 Looking up resource information . . . . . . 193

Error conditions for PU resources . . . . 194 Error conditions for application resources 194

Looking up period information . . . . . . 194

iv Tivoli Decision Support for z/OS: Network Performance Feature Reference

Looking up resource description information 195 Creating reports . . . . . . . . . . . 195

Chapter 11. NPM transit time component data flow . . . . . . . . 197 Measuring workstation-to-application transactions 197

Transit-time logging . . . . . . . . . . 198 NPM transit-time objectives . . . . . . . 199

NPM transit-time data flow . . . . . . . . 199 Capturing NPM transit-time data . . . . . . 200 Collecting SMF data . . . . . . . . . . 201 Looking up resource information . . . . . . 201 Looking up period information . . . . . . 202 Looking up resource description information 202 Creating reports . . . . . . . . . . . 203

Chapter 12. Service component data flows . . . . . . . . . . . . . . . 205 Network Performance feature service reports . . . 205 Service data flow . . . . . . . . . . . . 205

Looking up resource information . . . . . . 206 Creating reports . . . . . . . . . . . 207

Chapter 13. NCP utilization component data flows . . . . . . . 209 Utilization . . . . . . . . . . . . . . 209 Collecting utilization data . . . . . . . . . 209 NCP utilization data flow . . . . . . . . . 209

Capturing NCP utilization data . . . . . . 210 Collecting SMF data . . . . . . . . . . 210 Looking up period information . . . . . . 211 Looking up resource information . . . . . . 211 Creating reports . . . . . . . . . . . 211

Chapter 14. Line utilization component data flows . . . . . . . 213 Utilization . . . . . . . . . . . . . . 213 Collecting utilization data . . . . . . . . . 213

Threshold values . . . . . . . . . . . 213 Line utilization data flow . . . . . . . . . 213

Capturing line utilization data . . . . . . . 214 Collecting SMF data . . . . . . . . . . 214 Looking up period information . . . . . . 215 Looking up threshold information . . . . . 215 Creating reports . . . . . . . . . . . 215

Chapter 15. PU utilization component data flows . . . . . . . . . . . . . 217 Utilization . . . . . . . . . . . . . . 217 Collecting utilization data . . . . . . . . . 217 PU utilization data flow . . . . . . . . . . 217

Capturing PU utilization data . . . . . . . 218 Collecting SMF data . . . . . . . . . . 218 Looking up period information . . . . . . 219 Creating reports . . . . . . . . . . . 219

Chapter 16. NPM internal utilization component data flows . . . . . . . 221

NPM internal utilization . . . . . . . . . . 221 NPM internal utilization data flow . . . . . . 222

Capturing NPM utilization data . . . . . . 222 Collecting SMF data . . . . . . . . . . 222 Looking up period information . . . . . . 223 Creating reports . . . . . . . . . . . 223

Chapter 17. NV/SM internal utilization component data flows . . . . . . . 225 Utilization . . . . . . . . . . . . . . 225 NV/SM internal utilization . . . . . . . . . 225 NV/SM internal utilization data flow . . . . . 225

Capturing NV/SM utilization data . . . . . 226 Collecting SMF data . . . . . . . . . . 226 Looking up period information . . . . . . 227 Creating reports . . . . . . . . . . . 227

Chapter 18. NTRI utilization component data flows . . . . . . . 229 Utilization . . . . . . . . . . . . . . 229 Collecting utilization data . . . . . . . . . 229 NTRI utilization data flow . . . . . . . . . 229

Capturing NTRI utilization data . . . . . . 230 Collecting SMF data . . . . . . . . . . 230 Looking up period information . . . . . . 230 Looking up resource information . . . . . . 230 Creating reports . . . . . . . . . . . 231

Chapter 19. NEO utilization component data flows . . . . . . . 233 Utilization . . . . . . . . . . . . . . 233 Collecting utilization data . . . . . . . . . 233

Threshold values . . . . . . . . . . . 233 NEO utilization data flow . . . . . . . . . 233

Capturing NEO utilization data . . . . . . 234 Collecting SMF data . . . . . . . . . . 234 Looking up period information . . . . . . 235 Looking up resource information . . . . . . 235 Looking up threshold information . . . . . 235 Creating reports . . . . . . . . . . . 236

Chapter 20. X.25 utilization component data flows . . . . . . . 237 Collecting utilization data . . . . . . . . . 237

Threshold values . . . . . . . . . . . 237 X.25 link utilization data flow . . . . . . . . 237

Capturing X.25 link utilization data . . . . . 238 Collecting SMF data . . . . . . . . . . 238 Looking up period information . . . . . . 238 Looking up resource information . . . . . . 238 Looking up threshold information . . . . . 239 Creating reports . . . . . . . . . . . 239

X.25 PU and VC utilization data flow . . . . . 239 Capturing X.25 utilization data . . . . . . 240 Collecting SMF data . . . . . . . . . . 240 Looking up period information . . . . . . 241 Looking up resource information . . . . . . 241 Creating reports . . . . . . . . . . . 241

Contents v

Chapter 21. LAN utilization component data flows . . . . . . . 243 Utilization . . . . . . . . . . . . . . 243 Collecting utilization data . . . . . . . . . 243

Threshold values . . . . . . . . . . . 243 LAN bridge thresholds . . . . . . . . 243 LAN segment thresholds . . . . . . . 243

LAN utilization data flow . . . . . . . . 244 Capturing LAN utilization data . . . . . 244 Collecting SMF data . . . . . . . . . 245

Looking up period information . . . . . . 245 Creating reports . . . . . . . . . . . 245

Chapter 22. VTAM utilization component data flows . . . . . . . 247 Utilization . . . . . . . . . . . . . . 247 Collecting utilization data . . . . . . . . . 247

VTAM utilization data flow . . . . . . . 247 Capturing VTAM utilization data . . . . . 248 Collecting SMF data . . . . . . . . . 248

Looking up period information . . . . . . 249

Chapter 23. Frame Relay utilization component data flow . . . . . . . . 251 Utilization . . . . . . . . . . . . . . 251 Collecting utilization data . . . . . . . . . 251 Frame Relay utilization data flow . . . . . . 251

Capture Frame Relay data . . . . . . . . 252 Collect SMF data . . . . . . . . . . . 252 Looking up period information . . . . . . 252 Looking up resource information . . . . . . 252 Creating reports . . . . . . . . . . . 253

Chapter 24. ODLC utilization component data flow . . . . . . . . 255 Utilization . . . . . . . . . . . . . . 255

Collecting utilization data . . . . . . . . . 255 ODLC utilization data flow . . . . . . . . . 255

Capture ODLC data . . . . . . . . . . 256 Collect SMF data . . . . . . . . . . . 256 Looking up period information . . . . . . 257 Looking up resource information . . . . . . 257 Creating reports . . . . . . . . . . . 257

Chapter 25. SNMP routers component data flow . . . . . . . . . . . . . 259 Utilization . . . . . . . . . . . . . . 259 Collecting utilization data . . . . . . . . . 259 SNMP routers utilization data flow . . . . . . 259

Capturing SNMP routers utilization data . . . 261 Collecting SMF data . . . . . . . . . . 261 Creating reports . . . . . . . . . . . 261

Chapter 26. NPM/IP Component Data Flows . . . . . . . . . . . . . . . 263 NPM/IP performance and workload . . . . . 263 Processing steps for NPM/IP data . . . . . . 263

Capturing NPM/IP data . . . . . . . . . 264 Collecting SMF data . . . . . . . . . . 264 Creating reports . . . . . . . . . . . 264

Part 3. Appendixes . . . . . . . . 265

List of abbreviations . . . . . . . . 267

Notices . . . . . . . . . . . . . . 269 Trademarks . . . . . . . . . . . . . . 271

Glossary . . . . . . . . . . . . . 273

Index . . . . . . . . . . . . . . . 275

vi Tivoli Decision Support for z/OS: Network Performance Feature Reference

Figures

1. Basic Network Performance feature data flow 141 2. Collecting SMF data . . . . . . . . . 144 3. Example of a PERIOD_PLAN table . . . . 146 4. Looking up period information . . . . . 147 5. Recording time in the Network Performance

feature . . . . . . . . . . . . . . 147 6. Example using a long NetView collect period 148 7. Connection types . . . . . . . . . . 149 8. Availability component data flow . . . . . 151 9. Looking up resource data for APPL, NCP, or

PU resources . . . . . . . . . . . . 153 10. Looking up data for cross-domain connection

resources . . . . . . . . . . . . . 154 11. Looking up schedule name . . . . . . . 155 12. Looking up schedule information . . . . . 156 13. Looking up resource information for reports 157 14. Calculating uptime . . . . . . . . . . 157 15. NetView session monitor restart . . . . . 158 16. Calculating downtime . . . . . . . . 159 17. Last event is a session stop . . . . . . . 159 18. Timing of SMF switch and Tivoli Decision

Support for z/OS collect jobs . . . . . . 160 19. Process for hardware device configuration

data . . . . . . . . . . . . . . . 162 20. NW_CONFIG_HARDWARE table . . . . 164 21. Collecting hardware configuration data 165 22. Process for software product configuration

data . . . . . . . . . . . . . . . 166 23. NW_CONFIG_SOFTWARE table . . . . . 167 24. Collecting software configuration data 168 25. Process for FTP data . . . . . . . . . 171 26. Basic-alert data flow . . . . . . . . . 176 27. Looking up product ID information for basic

alerts . . . . . . . . . . . . . . 178 28. Looking up problem cause information for

basic alerts . . . . . . . . . . . . 179 29. Generic alert data flow . . . . . . . . 180 30. Looking up product ID information for

generic alerts . . . . . . . . . . . . 182 31. Lookup process for probable cause

information . . . . . . . . . . . . 183 32. Lookup process for alert description

information . . . . . . . . . . . . 184 33. Lookup process for alert type information 184 34. Process for session failure data . . . . . . 188 35. Lookup process for session failure description

information . . . . . . . . . . . . 190 36. Process for RTM response time . . . . . 192 37. Looking up resource information for PU

resources . . . . . . . . . . . . . 194 38. Looking up resource information for

application resources . . . . . . . . . 194

39. Looking up resource description information using resource name as key . . . . . . . 195

40. Life cycle of a workstation-to-application transaction . . . . . . . . . . . . 197

41. Process for NPM transit time . . . . . . 200 42. Looking up resource information for PU

resources . . . . . . . . . . . . . 201 43. Looking up resource information for

application resources . . . . . . . . . 202 44. Looking up resource description information

using the resource name as key . . . . . 203 45. Creating service reports (1) . . . . . . . 205 46. Creating service reports (2) . . . . . . . 206 47. Looking up resource information for service

reports using resource name as key . . . . 207 48. Process for NCP utilization data . . . . . 210 49. Looking up resource information for NCP

utilization . . . . . . . . . . . . . 211 50. Process for line utilization data . . . . . 214 51. Looking up threshold information for line

resources . . . . . . . . . . . . . 215 52. Process for PU utilization data . . . . . . 217 53. NPM internal utilization data flow . . . . 222 54. NV/SM internal utilization data flow 226 55. Process for NTRI utilization data . . . . . 229 56. Looking up resource information for NTRI

utilization . . . . . . . . . . . . . 231 57. Process for NEO utilization data . . . . . 234 58. Looking up resource information for NEO

utilization . . . . . . . . . . . . . 235 59. Looking up threshold information for NEO

resources . . . . . . . . . . . . . 236 60. Process for X.25 link utilization data . . . . 237 61. Looking up resource information for X.25 link

utilization . . . . . . . . . . . . . 239 62. Looking up threshold information for X.25

link resources . . . . . . . . . . . 239 63. Process for X.25 PU and VC utilization data 240 64. Looking up resource information for X.25 PU

and VC utilization . . . . . . . . . . 241 65. Process for LAN utilization data . . . . . 244 66. Process for VTAM utilization data . . . . 248 67. Process for frame relay utilization data 251 68. Looking up resource information for frame

relay utilization . . . . . . . . . . . 253 69. Process for ODLC utilization data . . . . . 255 70. Looking up resource information for ODLC

utilization . . . . . . . . . . . . . 257 71. IP Performance Data Collection by NPM 260 72. Process for SNMP routers utilization data 261 73. Processing NPM/IP data . . . . . . . . 263

vii

viii Tivoli Decision Support for z/OS: Network Performance Feature Reference

Preface

The Network Performance Feature Reference manual provides reference information for the Network Performance Feature of IBM® Tivoli® Decision Support for z/OS®

(hereafter referred to as Tivoli Decision Support for z/OS).

This book describes the component tables and lookup tables associated with the feature, and provides a detailed explanation of how the feature processes each type of network performance data.

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

The following terms are used interchangeably throughout this book: v Tivoli Decision Support for z/OS and Tivoli Decision Support for OS/390 v MVS™, OS/390, and z/OS

Who should read this book The Network Performance Feature Reference is intended for network analysts or programmers who are responsible for setting up the network reporting environment.

What this book contains Use this book as a reference to understand how the Network Performance feature collects and processes network data. The book contains two parts:

Part I contains these chapters: v “Chapter 1, “Component tables”” provides detailed information about the tables

used by each component. v “Chapter 2, “Lookup tables”” provides detailed information about the tables

used by all of the Network Performance feature components. v “Chapter 3, “Supported log records”” contains information about the SMF record

types and subtypes used by the Network Performance feature components.

Part II contains these chapters: v “Chapter 4, “Basic data flows”” provides an overview of the procedure the

feature uses to process data. v “Chapter 5, “Availability component data flows”” describes the procedure the

feature uses to process network availability data. v “Chapter 6, “Configuration component data flows”” describes the procedure the

feature uses to process network configuration data. v “Chapter 7, “NetView FTP component data flows”” describes the procedure the

feature uses to process NetView® file transfer program (FTP) data. v “Chapter 8, “Problem component data flows”” describes the procedure the

feature uses to process network problem data. v “Chapter 9, “Session failure component data flows”” describes the procedure the

feature uses to process network session failure data.

ix

||

|

|

|

v “Chapter 10, “RTM response time component data flow”” describes the procedure the feature uses to process response-time data from the response time monitor (RTM).

v “Chapter 11, “NPM transit time component data flow”” describes the procedure the feature uses to process NPM transit-time data.

v “Chapter 12, “Service component data flows”” describes the procedure the feature uses to process network service data.

v “Chapter 13, “NCP utilization component data flows”” describes the procedure the feature uses to process NCP utilization data.

v “Chapter 14, “Line utilization component data flows”” describes the procedure the feature uses to process line utilization data.

v “Chapter 15, “PU utilization component data flows”” describes the procedure the feature uses to process physical unit (PU) utilization data.

v “Chapter 16, “NPM internal utilization component data flows”” describes the procedure the feature uses to process NPM internal utilization data.

v “Chapter 17, “NV/SM internal utilization component data flows”” describes the procedure the feature uses to process NetView session monitor (NV/SM) internal utilization data.

v “Chapter 18, “NTRI utilization component data flows”” describes the procedure the feature uses to process NCP/Token-Ring interconnection (NTRI) utilization data.

v “Chapter 19, “NEO utilization component data flows”” describes the procedure the feature uses to process network extension option (NEO) utilization data.

v “Chapter 20, “X.25 utilization component data flows”” describes the procedure the feature uses to process X.25 utilization data.

v “Chapter 21, “LAN utilization component data flows”” describes the procedure the feature uses to process LAN utilization data.

v “Chapter 22, “VTAM utilization component data flows”” describes the procedure the feature uses to process VTAM® utilization data.

v “Chapter 23, “Frame Relay utilization component data flow”” describes the procedure the feature uses to process frame relay utilization data.

v “Chapter 24, “ODLC utilization component data flow”” describes the procedure the feature uses to process ODLC utilization data.

v “Chapter 25, “SNMP routers component data flow”” describes the procedure the feature uses to process SNMP routers utilization data.

A list of abbreviations, a glossary, and index follow these chapters.

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 and how to order Tivoli publications.

IBM Tivoli Decision Support for z/OS The following documents are available in the Tivoli Decision Support for z/OS: v Accounting Feature 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 the Accounting Feature for z/OS.

v Administration Guide, SH19-6816

Preface

x Tivoli Decision Support for z/OS: Network Performance Feature Reference

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 byoperating systems and applications running on a workstation.

v Guide to the Reporting Dialog, 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 byInformation Management System (IMS™).

v Language Guide and Reference, SH19-6817 Provides information for adminstrators, 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 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 information for network analysts or programmers who are responsible for setting up the network reporting environment.

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

v System Performance Feature Guide, SH19-6818 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 Vol. 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 Multiple Virtual Storage (MVS), or Virtual Machine (VM).

v System Performance Feature Reference Vol. 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 Multiple Virtual Storage (MVS), or Virtual Machine (VM) performance data.

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

Preface

Preface xi

Using LookAt to look up message explanations LookAt is an online facility that lets you look up explanations for most messages you encounter, as well as for some system abends 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 access LookAt from the Internet at: http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/ or from anywhere in z/OS or z/OS.e where you can access a TSO/E command line (for example, TSO/E prompt, ISPF, z/OS UNIX® System Services running OMVS).

The LookAt Web site also features a mobile edition of LookAt for devices such as Pocket PCs, Palm OS, or Linux™-based handhelds. So, if you have a handheld device with wireless access and an Internet browser, you can now access LookAt message information from almost anywhere.

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://publib.boulder.ibm.com/tividd/td/tdprodlist.html

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/public/applications/publications/ cgibin/pbi.cgi

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

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

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

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.

Preface

xii Tivoli Decision Support for z/OS: Network Performance Feature Reference

|

||||

|

|||

|||

http://www.ibm.com/servers/eserver/zseries/zos/bkserv/lookat/lookat.htmlhttp://publib.boulder.ibm.com/tividd/td/tdprodlist.htmlhttp://www.elink.ibmlink.ibm.com/public/applications/publications/http://www.elink.ibmlink.ibm.com/public/applications/publications/http://www.ibm.com/software/tivoli/order-lit/

For additional information, see the Accessibility Appendix in the Administration Guide.

Tivoli technical training For Tivoli technical training information, refer to the following IBM Tivoli Education Web site:

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

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 page

(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 (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region.

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 page (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 or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (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.

Follow the steps in this topic to contact IBM Software Support: 1. “Determine the business impact of your problem” 2. “Describe your problem and gather background information” on page xiv 3. “Submit your problem to IBM Software Support” on page xiv

Determine the business impact of your problem 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 you are reporting. Use the following criteria:

Preface

Preface xiii

|

||

|

|

|

||||

||||

|||

||||

||||||

||||||

|

|

|

|

|

|||

http://www.ibm.com/software/tivoli/education/http://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Homehttp://www.lotus.com/services/passport.nsf/WebDocs/Passport_Advantage_Homehttp://techsupport.services.ibm.com/guides/contacts.htmlhttp://www.ibm.com/servers/eserver/techsupport.htmlhttp://techsupport.services.ibm.com/guides/contacts.html

Severity 1 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 Significant business impact: The program is usable but is severely limited.

Severity 3 Some business impact: The program is usable with less significant features (not critical to operations) unavailable.

Severity 4 Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented.

Describe your problem and gather background information When explaining 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 the problem be recreated? If so, what steps led to the failure? v Have any changes been made to the system? (For example, hardware, operating

system, networking software, and so on.) v Are you currently using a workaround for this problem? If so, please be

prepared to explain it when you report the problem.

Submit your problem to IBM Software Support You can submit your problem in one of two ways: v Online: Go to the ″Submit and track problems″ page on the IBM Software

Support site (http://www.ibm.com/software/support/probsub.html). Enter your information into the appropriate problem submission tool.

v By phone: For the phone number to call in your country, go to the contacts page of the IBM Software Support Handbook on the Web (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 for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions.

For more information about problem resolution, see “Searching knowledge bases” and “Obtaining fixes” on page xv.

Searching knowledge bases If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available knowledge bases to determine whether the resolution to your problem is already documented.

Contacting IBM Software Support

xiv Tivoli Decision Support for z/OS: Network Performance Feature Reference

|||||

|||

|||

|||||

|

|||

|

||

|

||

||

|

|

|||

||||

|||||||

||

|

|||

http://www.ibm.com/software/support/probsub.htmlhttp://techsupport.services.ibm.com/guides/contacts.html

Search the information center on your local system or network IBM provides extensive documentation that can be installed on your local machine or on an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, reference information, and support documents.

Search 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, expand the product folder in the navigation frame to the left and select Support on the Web. From this topic, you can search a variety of resources including: v IBM technotes v IBM downloads v IBM Redbooks™

v IBM DeveloperWorks v Forums and newsgroups v Google

Obtaining fixes A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site: 1. Go to the IBM Software Support Web site

(http://www.ibm.com/software/support). 2. Under Products A - Z, select your product name. This opens a product-specific

support site. 3. Under Self help, follow the link to All Updates, where you will find a list of

fixes, fix packs, and other service updates for your product. For tips on refining your search, click Search tips.

4. Click the name of a fix to read the description and optionally download the fix.

To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps: 1. From the support page for any IBM product, click My support in the

upper-right corner of the page. 2. If you have already registered, skip to the next step. If you have not registered,

click register in the upper-right corner of the support page to establish your user ID and password.

3. Sign in to My support. 4. On the My support page, click Edit profiles in the left navigation pane, and

scroll to Select Mail Preferences. Select a product family and check the appropriate boxes for the type of information you want.

5. Click Submit. 6. For e-mail notification for other products, repeat Steps 4 and 5.

For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).


Preface xv

|||||

||||||

|

|

|

|

|

|

|

|||

||

||

|||

|

||

||

|||

|

|||

|

|

||

http://www.ibm.com/software/supporthttp://techsupport.services.ibm.com/guides/handbook.html

Updating support information Information centers typically include one or more support information plug-ins. These plug-ins add IBM technotes and other support documents to the information center. The following steps describe how to update your support information plug-ins: 1. Go to the IBM Software Support Web site

(http://www.ibm.com/software/support). 2. Under Products A - Z, select your product name. This opens a product-specific

support site. 3. Under Search support for this product, type the keyword phrase:

com.ibm.support. Click the Download check box, and click Submit. 4. Check the search results for updates to support information plug-ins. All

support information plug-ins follow the naming convention, ″com.ibm.support.product.doc.″ If an update is available, select it from the list and view the download instructions.

5. Save the attached zip file to a temporary location on your hard drive. 6. Unzip the downloaded file, making sure that you retain the subfolders. 7. From the location where you unzipped the file, copy the support information

plug-in folder to your Eclipse plug-ins folder. For example, if your IBM software product is installed at c:\IBM\WebSphere\, copy the updated plug-in folder (com.ibm.support.product.doc) to c:\IBM\WebSphere\eclipse\plugins.

8. To see the updated support information, start the information center (or shut it down and restart it), and expand the Support information node in the navigation tree.

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 terms MVS, OS/390, and z/OS are used interchangeably throughout this book

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 Citations (titles of books, diskettes, and CDs) v Words defined in text v Emphasis of words (words as words) v Letters as letters v New terms in text (except in a definition list)


xvi Tivoli Decision Support for z/OS: Network Performance Feature Reference

|

||||

||

||

||

||||

|

|

||||

|||

|

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

v Variables and values you must provideMonospace

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

Changes in this edition This edition is an updated version that replaces the previous edition of the same book. The changes are: v The name of the product has been changed to Tivoli Decision Support for z/OS

(except in figures). v The supported log records described in table “SMF Type 28” on page 133 have

been updated. v The following data tables have been added:

– “NW_VTAM_APPN_H, _D, _W” on page 98 – “NW_VTAM_RTP_H, _D, _W” on page 111

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


Preface xvii

||

||

|||

xviii Tivoli Decision Support for z/OS: Network Performance Feature Reference

Part 1. Tables and logs

Chapter 1. Component tables . . . . . . . . 3 Naming standard for data tables . . . . . . . . 3 Table descriptions . . . . . . . . . . . . 3

NW_ALERT_BASIC_H, _D, _W . . . . . . . 5 NW_ALERT_GENERIC_H, _D, _W . . . . . . 6 NW_CONFIG_HARDWARE . . . . . . . . 8 NW_CONFIG_SOFTWARE . . . . . . . . 10 NW_FRRYL_UTIL_H, _D, _W . . . . . . . 12 NW_FRRYLM_UTIL_H, _D, _W . . . . . . 15 NW_FRRYP_UTIL_H, _D, _W . . . . . . . 17 NW_FRRYPS_UTIL_H, _D, _W . . . . . . . 20 NW_FTP_REQUEST_H, _D, _M . . . . . . 22 NW_FTP_REQUEST_T . . . . . . . . . 24 NW_FTP_TRANSMIT_H, _D, _M . . . . . . 26 NW_LANB_UTIL_H, _D, _W . . . . . . . 27 NW_LANS_UTIL_H, _D, _W . . . . . . . 30 NW_LINE_UTIL_H, _D, _W . . . . . . . . 32 NW_NCP_UTIL_H, _D, _W . . . . . . . . 36 NW_NEO_UTIL_H, _D, _W . . . . . . . . 39 NW_NPMIP_PERFORM_H, _D . . . . . . . 42 NW_NPMIP_PERFVOL_H, _D . . . . . . . 43 NW_NPMIP_WRKLOAD_H, _D . . . . . . 44 NW_NPM_TRANSIT_H, _D, _W, _M . . . . . 45 NW_NPM_TRANS_IP_H, _D, _W, _M . . . . 51 NW_NPM_TRANS_SUM_H, _D, _W, _M . . . 57 NW_NPM_UTIL_H, _D, _W . . . . . . . . 63 NW_NTRIL_UTIL_H, _D, _W . . . . . . . 66 NW_NTRIP_UTIL_H, _D, _W . . . . . . . 69 NW_ODLCL_UTIL_H, _D, _W . . . . . . . 72 NW_ODLCP_UTIL_H, _D, _W . . . . . . . 74 NW_PU_UTIL_H, _D, _W . . . . . . . . 76 NW_ROUT_CISCIP_H, _D, _W . . . . . . . 78 NW_ROUT_CISCO_H, _D, _W . . . . . . . 82 NW_ROUT_CISPOOL_H, _D, _W . . . . . . 83 NW_ROUT_IBM_H, _D, _W . . . . . . . . 84 NW_ROUT_INTTRAF_H, _D, _W . . . . . . 87 NW_RTM_RESPONSE_H, _D, _W, _M . . . . 89 NW_SESSION_FAIL_H, _D, _W . . . . . . 91 NW_SM_UTIL_H, _D, _W . . . . . . . . 93 NW_VTAM_ADDSPACE_H, _D, _W . . . . . 95 NW_VTAM_APPL_H, _D, _W . . . . . . . 96 NW_VTAM_APPN_H, _D, _W . . . . . . . 98 NW_VTAM_BFR_H, _D, _W . . . . . . . 100 NW_VTAM_DEV_H, _D, _W . . . . . . . 104 NW_VTAM_GLOBAL_H, _D, _W . . . . . 108 NW_VTAM_RTP_H, _D, _W . . . . . . . 111 NW_VTAM_VR_H, _D, _W . . . . . . . 112 NW_X25LN_UTIL_H, _D, _W . . . . . . . 114 NW_X25NI_UTIL_H, _D, _W . . . . . . . 118 NW_X25PU_UTIL_H, _D, _W . . . . . . . 121

Chapter 2. Lookup tables . . . . . . . . . 125 Naming standard for lookup tables . . . . . . 125 Table descriptions . . . . . . . . . . . . 125

NW_ALERT_DESC . . . . . . . . . . 126 Example of table contents . . . . . . . 126

NW_ALERT_TYPE . . . . . . . . . . 126 Example of table contents . . . . . . . 126

NW_FAILURE_CODE . . . . . . . . . 126 Example of table contents . . . . . . . 127

NW_GENERAL_CAUSE . . . . . . . . 127 Example of table contents . . . . . . . 127

NW_PROBABLE_CAUSE . . . . . . . . 127 Example of table contents . . . . . . . 128

NW_PRODUCT_ID . . . . . . . . . . 128 Example of table contents . . . . . . . 128

NW_RESOURCE . . . . . . . . . . . 128 NW_SPECIFIC_CAUSE . . . . . . . . . 130

Example of table contents . . . . . . . 130 NW_THRESHOLD . . . . . . . . . . 130

Example of table contents . . . . . . . 130

Chapter 3. Supported log records . . . . . . 133 SMF Type 28 . . . . . . . . . . . . . 133 SMF Type 37 . . . . . . . . . . . . . 135 SMF Type 39 . . . . . . . . . . . . . 135 SMF Type 251 . . . . . . . . . . . . . 135 SMF Type 252 or user-defined . . . . . . . . 135

1

||

||

2 Tivoli Decision Support for z/OS: Network Performance Feature Reference

Chapter 1. Component tables

This chapter describes the data tables for the components of the Network Performance feature of IBM Tivoli Decision Support for z/OS (hereafter referred to as Tivoli Decision Support for z/OS) and explains their naming standards. For descriptions of common data tables used by the Network Performance feature components and other Tivoli Decision Support for z/OS features and components, refer to the Administration Guide.

Naming standard for data tables Names of the Network Performance feature tables use this format:

NW_content_suffix

Where: v NW is short for network v content is a description (for example, NW_NEO_UTIL for NEO utilization data) v suffix indicates a summarization level of the data in the table (for example,

NW_NEO_UTIL_D for NEO utilization data 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 data).

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.

Key columns are marked with a k.

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

The descriptions of most key columns and data columns contain references to the fields from which they are derived in the SMF record, such as “From BRFFLRTY.” For an explanation of such fields, refer to the applicable IBM NetView Performance Monitor, IBM NetView, or IBM NetView File Transfer Program book.

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

Note: Tables with similar contents (that is, tables with the same name but different suffixes) are described under one heading. For example, “NW_ALERT_BASIC_H, _D, _W” on page 5 contains information about these similar tables: NW_ALERT_BASIC_H NW_ALERT_BASIC_D NW_ALERT_BASIC_W

3

Except for the DATE column and TIME column, the contents of these tables are identical. For _W tables, the DATE column contains the first day of the week (weeks start on Monday). For _M tables, the DATE column contains the first day of the month. Differences in the contents of similar tables are explained in the column descriptions.

The DATE and TIME information is stored in the standard SQL format and displayed in the local format.

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

Component tables


NW_ALERT_BASIC_H, _D, _W These tables provide hourly, daily, and weekly statistics on basic alerts in the network. They contain basic-alert data from records with event sections written to SMF by the NetView hardware monitor as SMF Type 37 records.

These tables are updated by the NW_PRODUCT_ID lookup table.

The default retention periods for these tables are: NW_ALERT_BASIC_H 7 days NW_ALERT_BASIC_D 30 days NW_ALERT_BASIC_W 375 days

Column name Data type Description

DATE k DATE Date when the record was written to SMF. For the _W table, this is the date of the first day of the week. From BRFRDTE.

TIME k TIME Time (rounded down to the nearest hour) when the record was written to SMF. This applies only to the _H table. From BRFRTME.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields BRFRSID, BRFRDTE, and BRFRTME from the record as parameters in the PERIOD function.

PRODUCT_NAME k CHAR(9) Name of the product. This is the product identifier. From PRODUCT_NAME in the NW_PRODUCT_ID lookup table. This is derived using field BRFBLKID from the record as key. If PRODUCT_NAME is blank, this column gets its value from BRFBLKID.

RESOURCE_CATEGORY k CHAR(4) Resource category. This can have the default value HOST, COMM, CTRL, or APPL. From RESOURCE_CATEGORY in the NW_PRODUCT_ID lookup table. This is derived using field BRFBLKID from the record as key. If no match is found, this column is set to a question mark (?).

OWNING_RESOURCE k CHAR(8) Owner of the failing resource. From BRFHINM2, BRFHINM3, BRFHINM4, or BRFHINM5 if RESOURCE_HIERARCHY in the NW_PRODUCT_ID lookup table (derived using field BRFBLKID as key) equals 2, 3, 4, or 5, respectively; otherwise, from BRFHINM1.

RESOURCE_NAME k CHAR(8) Name of the resource. This is the name of the failing resource. From BRFFLRNM.

RESOURCE_TYPE k CHAR(4) Type of the resource. This is the type of the failing resource. From BRFFLRTY.

ALERT_TYPE_CODE k CHAR(2) Alert type code. From BRFALRTT. If BRFALRTT is blank, this column is set to 40.

GENERAL_CAUSE_CODE k CHAR(2) General cause of the alert. From BRFGENCA. If BRFGENCA is blank, this column is set to 40.

SPEC_CAUSE_CODE k CHAR(2) Specific-component code. This is the specific cause of the alert. From BRFSPECA. If BRFSPECA is blank, this column is set to 40.

EVENTS INTEGER Number of events. This is the count of records represented by BRFRDTE.

Component tables

Chapter 1. Component tables 5

NW_ALERT_GENERIC_H, _D, _W These tables provide hourly, daily, and weekly statistics on generic alerts in the network. They contain generic-alert data from records with generic-event sections written to SMF by the NetView hardware monitor as SMF Type 37 records.

These tables are updated by the NW_PRODUCT_ID, NW_ALERT_DESC, and NW_PROBABLE_CAUSE lookup tables.

The default retention periods for these tables are: NW_ALERT_GENERIC_H 7 days NW_ALERT_GENERIC_D 30 days NW_ALERT_GENERIC_W 375 days


DATE k DATE Date when the record was written to SMF. For the _W table, this is the date of the first day of the week. From BRFRDTE.

TIME k TIME Time (rounded down to the nearest hour) when the record was written to SMF. This applies only to the _H table. From BRFRTME.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields BRFRSID, BRFRDTE, and BRFRTME from the record as parameters in the PERIOD function.

PRODUCT_NAME k CHAR(9) Name of the product. This is the product identifier. From PRODUCT_NAME in the NW_PRODUCT_ID lookup table. This is derived using field BRFPROID from the record as key. If PRODUCT_NAME is blank, this column gets its value from BRFPROID.

RESOURCE_CATEGORY k CHAR(4) Resource category. This can have the default value HOST, COMM, CTRL, or APPL. From RESOURCE_CATEGORY in the NW_PRODUCT_ID lookup table. This is derived using field BRFPROID from the record as key. If no match is found, this column is set to a question mark (?).

OWNING_RESOURCE k CHAR(8) Owner of the failing resource. From BRFHINM2, BRFHINM3, BRFHINM4, or BRFHINM5 if RESOURCE_HIERARCHY in the NW_PRODUCT_ID lookup table (derived using field BRFPROID as key) equals 2, 3, 4, or 5, respectively; otherwise, from BRFHINM1.

RESOURCE_NAME k CHAR(8) Name of the resource. This is the name of the failing resource. From BRFFLRNM.

RESOURCE_TYPE k CHAR(4) Type of the resource. This is the type of the failing resource. From BRFFLRTY.

ALERT_TYPE_CODE k CHAR(2) Alert-type code. From BRFETYPE. If BRFETYPE is blank, this column is set to 40.

ALERT_DESC_CODE k CHAR(4) Alert-description code. From ALERT_DESC_CODE in the NW_ALERT_DESC lookup table. This is derived using field BRFDESC from the record as key. If no match is found, this column is set to X'FFFF'.

FIRST_CAUSE_CODE k CHAR(4) Code for the first probable cause of the alert. From FIRST_CAUSE_CODE in the NW_PROBABLE_CAUSE lookup table. This is derived using field BRFCAUS1 from the record as key. If no match is found, this column is set to X'FFFF'.

ALERT_DESC CHAR(40) Alert description. From BRFDESC.

Component tables



EVENTS INTEGER Number of events. This is the count of records represented by BRFRDTE.

FIRST_CAUSE_DESC CHAR(40) Description of the first probable cause of the alert. From BRFCAUS1.

Component tables


NW_CONFIG_HARDWARE This table provides information about the hardware characteristics of a PU. It contains PU hardware configuration data from records written by the network asset management function of NetView as SMF Type 37, subsystem ID=VPD, subtype P records.

The default retention period for this table is 765 days.


DOMAIN_NAME k CHAR(8) Domain identifier. From VPDPDID.

RESOURCE_NAME k CHAR(8) Name of the resource. This is set to the value in the DOMAIN_NAME, VTAM_NCP, PU_NAME, or LU_NAME column. If no valid name is found, this is set to the character string ERROR.

CA_LINE CHAR(8) Channel address or line name. From VPDPLKN.

CA_LINE_NEW CHAR(8) New channel address or line name. This is not used for reporting. From VPDPLKN.

CA_LINE_OLD CHAR(8) Old channel address or line name. This is not used for reporting. From VPDPLKN.

DATE DATE Date when the record was written to SMF. From VPDRDTE.

DATE_ADDED DATE Date when data about the resource was initially added to this table.

DATE_CHANGED DATE Date when data about the resource was last changed in a collect.

DATE_REFERENCED DATE Date when data about the resource was collected.

EC_LEVEL CHAR(10) Engineering change level. From VPDPECL.

EC_LEVEL_NEW CHAR(10) New engineering change level. This is not used for reporting. From VPDPECL.

EC_LEVEL_OLD CHAR(10) Old engineering change level. This is not used for reporting. From VPDPECL.

LU_NAME CHAR(8) Name of the LU. From VPDPLUN.

LU_NAME_NEW CHAR(8) New LU name. This is not used for reporting. From VPDPLUN.

LU_NAME_OLD CHAR(8) Old LU name. Not used for reporting. From VPDPLUN.

MACHINE_TYPE CHAR(5) Machine type. From VPDPTPE.

MACHINE_TYPE_NEW CHAR(5) New machine type. This is not used for reporting. From VPDPTPE.

MACHINE_TYPE_OLD CHAR(5) Old machine type. This is not used for reporting. From VPDPTPE.

MANUFACTURER CHAR(3) Manufacturer ID. From VPDPMAN.

MANUFACTURER_NEW CHAR(3) New manufacturer ID. This is not used for reporting. From VPDPMAN.

MANUFACTURER_OLD CHAR(3) Old manufacturer ID. This is not used for reporting. From VPDPMAN.

MODEL CHAR(3) Machine model. From VPDPMOD.

MODEL_NEW CHAR(3) New machine model. This is not used for reporting. From VPDPMOD.

MODEL_OLD CHAR(3) Old machine model. This is not used for reporting. From VPDPMOD.

Component tables



NEW_IND CHAR(1) Indicates that the resource was referenced in the last collect run. This is set to Y (yes) if it was referenced; otherwise, this is set to blank.

PORT_NUMBER CHAR(6) Attached-port number. From VPDPPRTN.

PORT_NUMBER_NEW CHAR(6) New attached-port number. This is not used for reporting. From VPDPPRTN.

PORT_NUMBER_OLD CHAR(6) Old attached-port number. This is not used for reporting. From VPDPPRTN.

PU_NAME CHAR(8) Name of the PU. From VPDPSPUN.

PU_NAME_NEW CHAR(8) New PU name. This is not used for reporting. From VPDPSPUN.

PU_NAME_OLD CHAR(8) Old PU name. This is not used for reporting. From VPDPSPUN.

RESOURCE_TYPE CHAR(8) Depending on the type of resource, this is set to the character string NCP, CA/LINE, PU, or LU. If no valid type is found, this is set to ERROR.

RESOURCE_TYPE_NEW CHAR(8) New resource type. Depending on the type of resource, this is set to the character string NCP, CA/LINE, PU, or LU.

RESOURCE_TYPE_OLD CHAR(8) Old resource type. This is not used for reporting.

SERIAL_NUMBER CHAR(7) Serial number of the device. From VPDPSEQ.

SERIAL_NUMBER_NEW CHAR(7) New serial number. This is not used for reporting. From VPDPSEQ.

SERIAL_NUMBER_OLD CHAR(7) Old serial number. This is not used for reporting. From VPDPSEQ.

TIME TIME Time when the record was written to SMF. From VPDRTME.

TIME_ADDED TIME Time when data about the resource was initially added to this table.

TIME_CHANGED TIME Time when data about the resource was last changed in a collect.

TIME_REFERENCED TIME Time when data about the resource was collected.

VTAM_NCP CHAR(8) VTAM or NCP name. From VPDPPPUN.

VTAM_NCP_NEW CHAR(8) New VTAM or NCP name. From VPDPPPUN.

VTAM_NCP_OLD CHAR(8) Old VTAM or NCP name. This is not used for reporting. From VPDPPPUN.

Component tables


NW_CONFIG_SOFTWARE This table provides information about the software characteristics of a PU. It contains PU software configuration data from records written by the network asset management function of NetView as SMF Type 37, subsystem ID=VPD, subtype F records.

The default retention period for this table is 765 days.


DOMAIN_NAME k CHAR(8) Domain ID. From VPDFDID.

RESOURCE_NAME k CHAR(8) Name of the resource. This is set to the value in the DOMAIN_NAME, VTAM_NCP, PU_NAME, or LU_NAME column. If no valid name is found, this is set to the character string ERROR.

CA_LINE CHAR(8) Channel address or line name. From VPDFLKN.

CA_LINE_NEW CHAR(8) New channel address or line name. This is not used for reporting. From VPDFLKN.

CA_LINE_OLD CHAR(8) Old channel address or line name. This is not used for reporting. From VPDFLKN.

COMPONENT_ID CHAR(9) Component ID. From VPDFCOMP.

COMPONENT_ID_NEW CHAR(9) New component ID. This is not used for reporting. From VPDFCOMP.

COMPONENT_ID_OLD CHAR(9) Old component ID. This is not used for reporting. From VPDFCOMP.

CUSTOMIZE_DATE CHAR(6) Date when the customization was done, in the format YY/DDD. From VPDFCDTE.

CUSTOMIZE_DATE_NEW CHAR(6) New customization date, in the format YY/DDD. This is not used for reporting. From VPDFCDTE.

CUSTOMIZE_DATE_OLD CHAR(6) Old customization date, in the format YY/DDD. This is not used for reporting. From VPDFCDTE.

CUSTOMIZE_TIME CHAR(5) Time when the customization was done, in the format HH:MM. From VPDFCTME.

CUSTOMIZE_TIME_NEW CHAR(5) New customization time, in the format HH:MM. This is not used for reporting. From VPDFCTME.

CUSTOMIZE_TIME_OLD CHAR(5) Old customization time, in the format HH:MM. This is not used for reporting. From VPDFCTME.

DATE DATE Date when the record was written to SMF. From VPDRDTE.

DATE_ADDED DATE Date when data about the resource was initially added to this table.

DATE_CHANGED DATE Date when data about the resource was last changed in a collect.

DATE_REFERENCED DATE Date when data about the resource was collected.

LU_NAME CHAR(8) Name of the LU. From VPDFLUN.

LU_NAME_NEW CHAR(8) New LU name. This is not used for reporting. From VPDFLUN.

LU_NAME_OLD CHAR(8) Old LU name. This is not used for reporting. From VPDFLUN.

NEW_IND CHAR(1) Indicates that the resource was referenced in the last collect run. This is set to Y (yes) if it was referenced; otherwise, this is set to blank.

PU_NAME CHAR(8) Name of the PU. From VPDFSPUN.

PU_NAME_NEW CHAR(8) New PU name. This is not used for reporting. From VPDFSPUN.

Component tables



PU_NAME_OLD CHAR(8) Old PU name. This is not used for reporting. From VPDFSPUN.

RELEASE CHAR(3) Release level of the program product. From VPDFREL.

RELEASE_NEW CHAR(3) New release level. This is not used for reporting. From VPDFREL.

RELEASE_OLD CHAR(3) Old release level. This is not used for reporting. From VPDFREL.

RESOURCE_TYPE CHAR(8) Depending on the type of resource, this is set to the character string NCP, CA/LINE, PU, or LU. If no valid type is found, this is set to ERROR.

RESOURCE_TYPE_NEW CHAR(8) New resource type. Depending on the type of resource, this is set to the character string NCP, CA/LINE, PU, or LU.

RESOURCE_TYPE_OLD CHAR(8) Old resource type. This is not used for reporting.

TIME TIME Time when the record was written to SMF. From VPDRTME.

TIME_ADDED TIME Time when data about the resource was initially added to this table.

TIME_CHANGED TIME Time when data about the resource was last changed in a collect.

TIME_REFERENCED TIME Time when data about the resource was collected.

VTAM_NCP CHAR(8) VTAM or NCP name. From VPDFPPUN.

VTAM_NCP_NEW CHAR(8) New VTAM or NCP name. This is not used for reporting. From VPDFPPUN.

VTAM_NCP_OLD CHAR(8) Old VTAM or NCP name. This is not used for reporting. From VPDFPPUN.

Component tables


NW_FRRYL_UTIL_H, _D, _W These tables provide hourly, daily, and weekly statistics on the utilization on Frame Relay logical links. They contain utilization data from records written by NPM as SMF Type 28, subtype X'83' records. These tables are updated by the NW_RESOURCE lookup table. The default retention periods for these tables are: NW_FRRYL_UTIL_H 7 days NW_FRRYL_UTIL_D 30 days NW_FRRYL_UTIL_W 375 days


DATE k DATE Date when the record was written to SMF. From SMF28DTE.

LINE_NAME k CHAR(8) Name of the line. This is the name of the logical link. From LNCDSLNK.

NCP_NAME k CHAR(8) Name of the NCP. From RESOURCE_SYNONYM in the NW_RESOURCE lookup table. This is derived using LNCDSSAP as key. If no match is found, this is from LNCDSSAP.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF28SID, SMF28DTE, and SMF28TME from the record as parameters in the PERIOD function.

TIME k TIME Time (rounded down to the nearest hour) when the record was written to SMF. From SMF28TME.

BYTES_RCV FLOAT Total number of bytes received. This is the sum of LFRPBYTR.

BYTES_RCV_MAX FLOAT Maximum number of bytes received. This is the maximum of LFRPBYTR.

BYTES_RCV_MIN FLOAT Minimum number of bytes received. This is the minimum of LFRPBYTR.

BYTES_RXMIT FLOAT Total number of bytes retransmitted. This is the sum of LFRPXBYT.

BYTES_RXMIT_MAX FLOAT Maximum number of bytes retransmitted. This is the maximum of LFRPXBYT.

BYTES_RXMIT_MIN FLOAT Minimum number of bytes retransmitted. This is the minimum of LFRPXBYT.

BYTES_SENT FLOAT Total number of bytes sent. This is the sum of LFRPBYTS.

BYTES_SENT_MAX FLOAT Maximum number of bytes sent. This is the maximum of LFRPBYTS.

BYTES_SENT_MIN FLOAT Minimum number of bytes sent. This is the minimum of LFRPBYTS.

BYTES_TOTAL FLOAT Total number of bytes sent and received. Calculated as the sum of LFRPBYTR + LFRPBYTS.

BYTES_TOTAL_MAX FLOAT Maximum number of bytes sent and received. Calculated as the maximum of LFRPBYTR + LFRPBYTS.

BYTES_TOTAL_MIN FLOAT Minimum number of bytes sent and received. Calculated as the minimum of LFRPBYTR + LFRPBYTS.

ERRORS_TOTAL FLOAT Total number of errors. Calculated as the sum of LFRPTERR.

FRAMES_RCV FLOAT Total number of frames received. This is the sum of LFRPTFRR.

FRAMES_RCV_MAX FLOAT Maximum number of frames received. This is the maximum of LFRPTFRR.

FRAMES_RCV_MIN FLOAT Minimum number of frames received. This is the minimum of LFRPTFRR.

Component tables



FRAMES_SENT FLOAT Total number of frames sent. This is the sum of LFRPTFRS.

FRAMES_SENT_MAX FLOAT Maximum number of frames sent. This is the maximum of LFRPTFRS.

FRAMES_SENT_MIN FLOAT Minimum number of frames sent. This is the minimum of LFRPTFRS.

FRAMES_TOTAL FLOAT Total number of frames sent and received. Calculated as the sum of LFRPTFRS + LFRPTFRR.

FRAMES_TOTAL_MAX FLOAT Maximum number of frames sent and received. Calculated as the maximum of LFRPTFRS + LFRPTFRR.

FRAMES_TOTAL_MIN FLOAT Minimum number of frames sent and received. Calculated as the minimum of LFRPTFRS + LFRPTFRR.

IFRAMES_RCV FLOAT Total number of I-frames received. This is the sum of LFRPIFRR.

IFRAMES_RCV_MAX FLOAT Maximum number of I-frames received. This is the maximum of LFRPIFRR.

IFRAMES_RCV_MIN FLOAT Minimum number of I-frames received. This is the minimum of LFRPIFRR.

IFRAMES_RXMIT FLOAT Total number of I-frames retransmitted. This is the sum of LFRPXIFR.

IFRAMES_RXMIT_MAX FLOAT Maximum number of I-frames retransmitted. This is the maximum of LFRPXIFR.

IFRAMES_RXMIT_MIN FLOAT Minimum number of I-frames retransmitted. This is the minimum of LFRPXIFR.

IFRAMES_SENT FLOAT Total number of I-frames sent. This is the sum of LFRPIFRS.

IFRAMES_SENT_MAX FLOAT Maximum number of I-frames sent. This is the maximum of LFRPIFRS.

IFRAMES_SENT_MIN FLOAT Minimum number of I-frames sent. This is the minimum of LFRPIFRS.

IFRAMES_TOTAL FLOAT Total number of I-frames sent and received. Calculated as the sum of LFRPIFRR + LFRPIFRS.

IFRAMES_TOTAL_MAX FLOAT Maximum number of I-frames sent and received. Calculated as the maximum of LFRPIFRR + LFRPIFRS.

IFRAMES_TOTAL_MIN FLOAT Minimum number of I-frames sent and received. Calculated as the minimum of LFRPIFRR + LFRPIFRS.

MEASURED_OURS FLOAT Measured time period, in hours. Calculated as LFRPCTIM/36000.

MEASURED_SEC FLOAT Measured time period, in seconds. Calculated as LFRPCTIM/10.

NETWORK_NAME CHAR(8) Name of the network for this resource. From LNCDSNET.

OUTQUEUE_MAX_PIU FLOAT Maximum outbound queue length, in path information units. This is the maximum of LFRPOBQL.

OUTQUEUE_TOTAL_PIU FLOAT Total outbound queue length, in path information units. This is the sum of LFRPOBQL.

RECORDS_COLLECTED INTEGER Number of Frame Relay records collected. This is the count of SMF28TME.

REPLY_TIMEOUTS FLOAT Total number of reply time-outs. This is the sum of LFRPRPTO

REPLY_TIMEOUTS_MAX FLOAT Maximum number of reply time-outs. This is the maximum of LFRPRPTO.

REPLY_TIMEOUTS_MIN FLOAT Minimum number of reply time-outs. This is the minimum of LFRPRPTO.

Component tables



UTILIZATION_PCT FLOAT Utilization for the line in percentage. From the work variable W_UTIL_TOTAL.

W_UTIL_RCV - Work variable used to calculate the receive line utilization. Calculated as (LFRPBYTR/((LFRPTLSP*(LFRPCTIM/10)/8000000))/10000).

W_UTIL_SENT - Work variable used to calculate the send line utilization. Calculated as (LFRPBYTS/((LFRPTLSP*(LFRPCTIM/10)/8000000))/10000).

W_UTIL_TOTAL - Work variable used to set the utilization for the line. Is set to the highest in W_UTIL_RCV or W_UTIL_SENT.

Component tables


NW_FRRYLM_UTIL_H, _D, _W These tables provide hourly, daily, and weekly statistics on the utilization on Frame Relay Local Management Interface (LMI) physical unit. They contain utilization data from records written by NPM as SMF Type 28, subtype X'85' records. These tables are updated by the NW_RESOURCE lookup table. The default retention periods for these tables are: NW_FRRYLM_UTIL_H 7 days NW_FRRYLM_UTIL_D 30 days NW_FRRYLM_UTIL_W 375 days


DATE k DATE Date when the record was written to SMF. From SMF28DTE.

PU_NAME k CHAR(8) Name of the PU. This is the name of the frame relay LMI physical unit. From LNCDSPUN.

NCP_NAME k CHAR(8) Name of the NCP. From RESOURCE_SYNONYM in the NW_RESOURCE lookup table. This is derived using LNCDSSAP as key. If no match is found, this is from LNCDSSAP.

PERIOD_NAME k CHAR(8) Name of the period. This is derived using fields SMF28SID, SMF28DTE, and SMF28TME from the record as parameters in the PERIOD function.

TIME k TIME Time (rounded down to the nearest hour) when the record was written to SMF. From SMF28TME.

BYTES_RCV FLOAT Total number of bytes received. This is the sum of LFRPBYTR.

BYTES_RCV_MAX FLOAT Maximum number of bytes received. This is the maximum of LFRPBYTR.

BYTES_RCV_MIN FLOAT Minimum number of bytes received. This is the minimum of LFRPBYTR.

BYTES_RXMIT FLOAT Total number of bytes retransmitted. This is the sum of LFRPXBYT.

BYTES_RXMIT_MAX FLOAT Maximum number of bytes retransmitted. This is the maximum of LFRPXBYT.

BYTES_RXMIT_MIN FLOAT Minimum number of bytes retransmitted. This is the minimum of LFRPXBYT.

BYTES_SENT FLOAT Total number of bytes sent. This is the sum of LFRPBYTS.

BYTES_SENT_MAX FLOAT Maximum number of bytes sent. This is the maximum of LFRPBYTS.

BYTES_SENT_MIN FLOAT Minimum number of bytes sent. This is the minimum of LFRPBYTS.

BYTES_TOTAL FLOAT Total number of bytes sent and received. Calculated as the sum of LFRPBYTR + LFRPBYTS.

BYTES_TOTAL_MAX FLOAT Maximum number of bytes sent and received. Calculated as the maximum of LFRPBYTR + LFRPBYTS.

BYTES_TOTAL_MIN FLOAT Minimum number of bytes sent and received. Calculated as the minimum of LFRPBYTR + LFRPBYTS.

ERRORS_TOTAL FLOAT Total number of errors. Calculated as the sum of LFRPTERR.

FRAMES_DISC FLOAT Total number of frames discarded. Calculated as the sum of LFRPPDF.

FRAMES_DISC_MAX FLOAT Maximum number of frames discarded. Calculated as the maximum of LFRPPDF.

Component tables



FRAMES_DISC_MIN FLOAT Minimum number of frames discarded. Calculated as the minimum of LFRPPDF.

FRAMES_RCV FLOAT Total number of frames received. This is the sum of LFRPTFRR.

FRAMES_RCV_MAX FLOAT Maximum number of frames received. This is the maximum of LFRPTFRR.

FRAMES_RCV_MIN FLOAT Minimum number of frames received. This is the minimum of LFRPTFRR.

FRAMES_SENT FLOAT Total number of frames sent. This is the sum of LFRPTFRS.

FRAMES_SENT_MAX FLOAT Maximum number of frames sent. This is the maximum of LFRPTFRS.

FRAMES_SENT_MIN FLOAT Minimum number of frames sent. This is the minimum of LFRPTFRS.

FRAMES_TOTAL FLOAT Total number of frames sent and received. Calculated as the sum of LFRPTFRS + LFRPTFRR.

FRAMES_TOTAL_MAX FLOAT Maximum number of frames sent and received. Calculated as the maximum of LFRPTFRS + LFRPTFRR.

FRAMES_TOTAL_MIN FLOAT Minimum number of frames sent and received. Calculated as the minimum of LFRPTFRS + LFRPTFRR.

LINE_NAME CHAR(8) Name of the line. This is the name of the logical link. From LNCDSLNK.

MEASURED_HOURS FLOAT Measured time period, in hours. Calculated as LFRPCTIM/36000.

MEASURED_SEC FLOAT Measured time period, in seconds. Calculated as LFRPCTIM/10.

NETWORK_NAME CHAR(8) Name of the network for this resource. From LNCDSNET.

RECORDS_COLLECTED FLOAT Number of Frame Relay records collected. This is the count of SMF28TME.

Component tables


NW_FRRYP_UTIL_H, _D, _W These tables provide hourly, daily, and weekly statistics on the utilization on Frame Relay physical link. They contain utilization data from records written by NPM as SMF Type 28, subtype X'82' records. These tables are updated by the NW_RESOURCE lookup table. The default retention periods for th

Network Performance Feature Referencepublib.boulder.ibm.com/tividd/td/TDS390/SH19-6822-08/en... ·...

Documents

Transcript of Network Performance Feature Referencepublib.boulder.ibm.com/tividd/td/TDS390/SH19-6822-08/en... ·...