NPM Concepts and Planning - IBMpublib.boulder.ibm.com/tividd/td/perfmon/SH19-6961... · Contents Figures..... vii Tables..... ix

NetView® Performance MonitorConcepts and PlanningVersion 2 Release 7 GH19-6961-06

NetView® Performance MonitorConcepts and PlanningVersion 2 Release 7 GH19-6961-06

NetView Performance Monitor Concepts and Planning Version 2.7

Copyright Notice

© Copyright IBM Corporation 1984, 2001. All rights reserved. May only be used pursuant to a Tivoli Systems Software LicenseAgreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. Nopart of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without priorwritten permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions ofany machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporationcopyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document isnot intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.

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

Trademarks

IBM, Tivoli, the Tivoli logo, APPN, CICS, ESCON, IBMLink, MVS, NetView, OpenEdition, OS/390, RACF, VTAM, z/OS aretrademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States,other countries, or both.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.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available inall countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended toimply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or otherlegally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead ofthe referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, exceptthose expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents orpending patent applications covering subject matter in this document. The furnishing of this document does not give you any licenseto these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive,Armonk, New York 10504-1785, U.S.A.

ISO 9001 Certification

This product was developed using an ISO 9001 certified quality system.

Certification has been awarded by Bureau Veritas Quality International (BVQI) (Certification No. BVQI - 92086 / A).

BVQI is a world leader in quality certification and is currently recognized by more than 20 accreditation bodies.

Contents

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

Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiWho Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

What This Book Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Using LookAt to Look Up Message Explanations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Conventions Used in This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Changes in This Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Changes in the Previous Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Part I. NPM Functions and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Introduction to NPM Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Overview of NPM User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Overview of Version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Session Manager Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

VTAM Statistics Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Updated Host User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Updated Network Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

NetWare Resources Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

NPM Enhancements in Version 2 Release 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

NPM Enhancements in Version 2 Release 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Overview of the NPM Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2. Collecting and Monitoring Performance Data . . . . . . . . . . . . . . . . 17Collecting IP Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Collecting and Monitoring Network Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Collecting and Monitoring Session Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Collecting and Monitoring LAN Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Collecting Response Time Monitor (RTM) Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Collecting and Monitoring VTAM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Collecting and Monitoring NetWare Resource Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

iiiNPM Concepts and Planning

||

||

||

Chapter 3. Collecting Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Collecting Network Session and Gateway Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Collecting Data from the VTAM Session Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Collecting Dynamic Network Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Collecting Accounting Data from NetView Access Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Recording and Viewing Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 4. Tuning and Expanding the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . 69Creating Reports with the FNMREPRT Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Examining the Reports for Tuning the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Part II. Planning for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 5. Managing NPM Support Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Functions that Require Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Functions that Do Not Require Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 6. Working with NPM Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Working with Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Allocating NPM Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 7. Managing NPM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Logon Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Functional Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Console Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Defining Security for NPM-to-NPM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Using RACF with NPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Part III. Planning for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 8. Migrating to NPM Version 2 Release 7. . . . . . . . . . . . . . . . . . . . . . . . 89Modified VSAM Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Updating FNMINIT for NPM Version 2 Release 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Updating FNMSTRT and Other NPM EXECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Updating the User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Part IV. User Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 9. Isolating Performance Problems in a Network . . . . . . . . . . . . . . . 95Example: Isolating the Problem to the Host or the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

iv Version 2 Release 7

Example: Examining a Line for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Example: Examining an NCP for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Isolating Problems in an IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Chapter 10. Isolating Poor Response Time on a LAN. . . . . . . . . . . . . . . . . . . 119Example: Examining a LAN Network for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Example: Examining a TIC for Potential Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Chapter 11. Isolating Performance Problems in the Host. . . . . . . . . . . . . . . 141Example: Examining an Application for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Example: Examining an Application Using VTAM Statistics Data . . . . . . . . . . . . . . . . . . . . . . . . . 147

Example: Examining VTAM for Problems in the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Example: Determining if There is a Blocked Virtual Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Chapter 12. Reviewing Network Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Example: Using a Network Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 13. Isolating Problems on a Novell NetWare Network . . . . . . . . . 175Using NetWare Counters and Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Example: Tuning and Load Balancing a NetWare Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Example: Monitoring a NetWare Network for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Chapter 14. Managing NPM Data Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Example: No Data Found (Error Message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Example: Resetting a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Example: Preparing a File for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Example: Managing Data Files with the System Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Example: Available Actions Based on File Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Part V. Appendixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Bibliography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221NPM Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Other Network Program Products Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Operating System Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

NPM Publications on CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

vNPM Concepts and Planning

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

vi Version 2 Release 7

Figures

1. Sample Network for NPM Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42. Sources of Performance Data Collected by NPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193. Destinations of Performance Data Collected by NPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204. IP Performance Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215. Network Performance Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246. Session Collection of VTAM Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397. Transit Time Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408. Session Collection of IP Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429. Session Collection for Session Manager Relay Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

10. Session Collection for Session Manager Control Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4911. LAN Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5412. RTM Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5813. Network Accounting Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6414. Example Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9515. Start Session Panel (FNM02SCL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9716. Session Monitor Selection Panel (FNM03SAS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9817. NPM LU Detail Analysis Panel (FNM02DNM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10018. NPM Session Analysis Summary - LU Panel (FNM03SMN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10119. Session Monitor Review Panel (FNM02SAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10220. Session Monitor Event Messages Panel (FNM03SAE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10321. Session Status/Stop (Active) Resource Panel (FNM03SSA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10422. Session Status/Stop (Active) Details Panel (FNM04SSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10423. Example Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10524. Resource List Panel (FNM02RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10625. Resource List Panel (FNM02RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10626. Network Start Panel (FNM03STD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10727. Network Start Panel (FNM03STM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10828. Network Review Panel (FNM02RVM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10929. Network Review Data Panel (FNM03RVL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11030. Command List Panel (FNM03NCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11131. Example Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11232. Network Start Panel (FNM03STD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11233. Network Start Panel (FNM03STM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11334. Network Start Panel (FNM03STM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11435. Network Review Panel (FNM02RVM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11536. Network Review Data Panel (FNM03RVP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11637. Example Token Ring Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11938. LAN Bridge Control Panel (FNM02LBB). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12039. LAN Bridge Selection Panel (FNM02LBS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12140. LAN Bridge Collection Control Panel (FNM03LBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12241. LAN Segment Control Panel (FNM02LSB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12342. LAN Segment Selection Panel (FNM02LSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12543. LAN Segment Collection Control Panel (FNM03LSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12544. LAN Review Panel (FNM02LBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12745. LAN Bridge Data Detail Panel (FNM03LBR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12846. LAN Bridge Lost Frames Detail Panel (FNM03LB2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12847. LAN Review Panel (FNM02LBM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13048. LAN Segment Data Detail Panel (FNM03LSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13149. LAN Segment Data Detail Panel (FNM03LSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

viiNPM Concepts and Planning

||||

50. LAN Bridge Selection Panel (FNM02LBS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13351. LAN Segment Selection Panel (FNM02LSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13352. Example Token Ring Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13453. Network Start Panel (FNM03STD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13554. Network Start Panel (FNM03STM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13655. Network Review Panel (FNM02RVM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13756. Network Review Data for NTRI Resources Panel (FNM03RVN). . . . . . . . . . . . . . . . . . . . . . . . . . . 13857. Network Stop Panel (FNM03STD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13958. Example Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14159. Start Session Panel (FNM02SCL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14260. Session Monitor Selection Panel (FNM03SAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14461. Session Analysis Panel (FNM02SAN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14562. NPM Session Analysis Summary - Application Panel (FNM03SMN). . . . . . . . . . . . . . . . . . . . . . . . 14663. NPM Session Summary LU List - Application Panel (FNM04LTN). . . . . . . . . . . . . . . . . . . . . . . . . 14664. Session Status/Stop (Active) Resource Panel (FNM03SSA). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14765. VTAM Application Selection Panel (FNM02PS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14866. VTAM Start Panel (FNM03VTD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14867. VTAM Start Panel (FNM03VT2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14968. VTAM Application Current Data Panel (FNM02PS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15069. Command List Panel (FNM03VCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15170. VTAM Global Data Selection Panel (FNM02GS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15271. VTAM Start Panel (FNM03VTD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15272. VTAM Start Panel (FNM03VTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15373. VTAM Global Current Data Panel (FNM02GS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15474. VTAM Global Current Data Panel (FNM02GS3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15475. VTAM Global Current Data Panel (FNM02GS4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15576. Command List Panel (FNM03VCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15677. VTAM Buffer Pool Selection Panel (FNM02BS1). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15678. VTAM Start Panel (FNM03VTD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15779. VTAM Start Panel (FNM03VTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15880. VTAM Buffer Pool Current Data Panel (FNM02BS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15981. VTAM Buffer Pool Current Data Panel (FNM02BS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15982. Destination Subarea Selection Panel (FNM02SS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16083. Virtual Route Selection Panel (FNM03VS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16184. VTAM Start Panel (FNM03VTD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16185. VTAM Data Collection Panel (FNM03VTC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16286. Virtual Route Current Data Panel (FNM03VS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16387. Virtual Route Current Data Panel (FNM03VS3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16488. Destination Subarea Selection Panel (FNM02SS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16589. Virtual Route Selection Panel (FNM03VS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16590. VTAM Data Analysis Panel (FNM03VAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16691. Virtual Route Detail Data Panel (FNM04VD1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16692. Virtual Route Detail Data Panel (FNM04VD2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16793. Network Start Panel (FNM03STD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17094. Network Start Panel (FNM03STM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17195. Network Review Panel (FNM02RVM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17296. Review Monitor Event Messages Panel (FNM03RVE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17397. Data File Display and Management Panel (FNM02OFL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18498. Data File Display and Management Panel (FNM02OFL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

viii Version 2 Release 7

Tables

1. Monitors for SNMP Router Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112. Renamed Labeled Items in 3270 Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133. Supported Data per Network Element Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224. Collection Interval Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245. SNA, BSC, and CCU Performance Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266. LAN (NTRI, Ethernet, and ODLC) Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297. X.25 and Frame Relay Network Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318. NEO Network Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329. 3746 Line Processor Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

10. Example of Network Monitor with Monitor Exception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3411. Example of Network Monitor with Resolution Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3512. Collection Matrix for Session Manager Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5213. NPM data sets in MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8114. SMF28PSS Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8915. Sample Checklist for Determining High CPU Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15116. NetWare Counter Group and Resource Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17517. NetWare Counter Group and Monitor Type Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17618. Examples of File Management Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

ixNPM Concepts and Planning

x Version 2 Release 7

Preface

This book serves as a guide to understanding the basic concepts of the Tivoli®NetView®

Performance Monitor (NPM) product and to help you plan for its installation and migrationfrom a previous release.

Who Should Read This BookThis book is designed for planners, system administrators, and system programmersresponsible for understanding the capabilities of NPM and choosing the functions to installto meet their needs.

The readers of this book should be knowledgeable about networking and system concepts toensure the best use of this book.

What This Book ContainsThis book contains the following sections:

Part I. NPM Functions and Features

Part I contains the following chapters:

¶ Chapter 1, “Introduction to NPM Concepts”

Provides an overview of how NPM enables you to control and monitortelecommunication networks.

¶ Chapter 2, “Collecting and Monitoring Performance Data”

Describes how NPM collects performance data to help you assess how efficiently thenetwork operates.

¶ Chapter 3, “Collecting Accounting Data”

Describes how NPM collects and stores accounting data for your accounting or billingapplication from a network control program (NCP).

¶ Chapter 4, “Tuning and Expanding the Network”

Describes how to use the data collection and monitoring capabilities of NPM forgathering the information that you need to tune your network and plan for its growth.

Part II. Planning for Installation

Part II contains the following chapters:

¶ Chapter 5, “Managing NPM Support Functions”

Provides an overview of the additional NPM functions that support data collection.

¶ Chapter 6, “Working with NPM Data Sets”

Describes how, when installing NPM, you update statements both in sample data setsand in data sets that you create.

¶ Chapter 7, “Managing NPM Security”

Provides an overview of NPM security management and the security procedures that areperformed when an operator logs on.

xiNPM Concepts and Planning

Note: If you are already familiar with NPM, you do not need to read all of Part I and PartII. See “Changes in This Edition” on page xv and “NPM Enhancements in Version 2Release 7” on page 8 to learn about the new and changed functions in this version.

Part III. Planning for Migration

Part III contains the following chapter:

¶ Chapter 8, “Migrating to NPM Version 2 Release 7”

Provides information about migrating to NPM Version 2 from a previous release ofNPM.

Part IV. User Scenarios

Part IV contains the following chapters:

¶ Chapter 9, “Isolating Performance Problems in a Network”

Contains user scenarios to help new users of NPM gain experience in using the productto isolate performance problems in a network.

¶ Chapter 10, “Isolating Poor Response Time on a LAN”

Contains user scenarios to help new users of NPM gain experience in using the productto isolate poor response time on a LAN.

¶ Chapter 11, “Isolating Performance Problems in the Host”

Contains user scenarios to help new users of NPM gain experience in using the productto isolate performance problems in the host.

¶ Chapter 12, “Reviewing Network Performance”

Contains user scenarios to help new users of NPM gain experience in using the productto review network performance.

¶ Chapter 13, “Isolating Problems on a Novell NetWare Network”

Contains user scenarios to help new users of NPM gain experience in using the productto isolate problems on a Novell NetWare network.

¶ Chapter 14, “Managing NPM Data Files”

Contains user scenarios to help new users of NPM gain experience in using the productto manage NPM data files.

Part V. Appendixes

Part V contains a glossary for this book, a product bibliography for NPM, and an indexspecific to this book.

PublicationsThis section lists publications in the NPM library and any other related documents. It alsodescribes how to access Tivoli publications online, how to order Tivoli publications, andhow to make comments on Tivoli publications.

NPM LibraryThe following documents are available in the NPM library:

¶ NetView Performance Monitor Concepts and Planning, GH19-6961

Preface

xii Version 2 Release 7

Provides information about the basic concepts of NPM and helps you plan for installingNPM and migrating from a previous release.

¶ NetView Performance Monitor Installation and Customization, SH19-6964

Provides information about installing, customizing, and tuning NPM.

¶ NetView Performance Monitor Console User’s Guide, SH19-4522

Explains how to use the graphical interface for NPM.

¶ NetView Performance Monitor Reference, SH19-6965

Provides information for operators, system programmers, and system planners who wantto produce reports nad write applications using data collected by NPM.

¶ NetView Performance Monitor Messages and Codes, SH19-6966

Provides information to help operators and system programmers understand, interpret,and respond to NPM messages and codes.

¶ NetView Performance Monitor User’s Guide, SH19-6962

Provides information for new and experienced operators who use NPM on a daily basisto manage a communication network.

¶ NetView Performance Monitor Diagnosis, LY19-6381

Provides information about ananlyzing an NPM problem, classifying it as a specific typeof failure, collecting data, and describing the problem to the Customer Support.

¶ IBM Online Library Omnibus Edition OS/390 Collection Kit, SK2T-6700(available December 2001)

CD containing all OS/390® documentation.

¶ IBM Online Library z/OS Software Products Collection Kit, SK3T-4270(available December 2001)

CD containing all z/OS documentation.

Related PublicationsA product bibliography is included in this book.

Accessing Publications OnlineYou can access many Tivoli publications online at the Tivoli Customer Support Web site:http://www.tivoli.com/support/documents/

These publications are available in PDF or HTML format, or both. Translated documents arealso available for some products.

Ordering PublicationsYou can order many Tivoli publications online at the following Web site:http://www.ibm.com/shop/publications/order

You can also order by telephone by calling one of these numbers:

¶ In the United States: 800-879-2755

¶ In Canada: 800-426-4968

¶ In other countries, for a list of telephone numbers, see the following Web site:http://www.tivoli.com/inside/store/lit_order.html

Preface

xiiiNPM Concepts and Planning

http://www.tivoli.com/support/documents

http://www.ibm.com/shop/publications/order

http://www.tivoli.com/inside/store/lit_order.html

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:

¶ Send an e-mail to [email protected].

¶ Complete our customer feedback survey at the following Web site:http://www.tivoli.com/support/survey

Contacting Customer SupportIf you have a problem with any Tivoli product, you can contact Tivoli Customer Support.See the Tivoli Customer Support Handbook at the following Web site:http://www.tivoli.com/support/handbook/

The handbook provides information about how to contact Tivoli Customer Support,depending on the severity of your problem, and the following information:

¶ Registration and eligibility

¶ Telephone numbers and e-mail addresses, depending on the country you are in

¶ What information you should gather before contacting support

Note: For Tivoli NetView for OS/390 customers only, additional support is available on theNETVIEW CFORUM (Customer Forum) through the IBMLink™ system. This forumis monitored by NetView developers who answer questions and provide guidance.When a problem with the code is found, you are asked to open an official problemmanagement record (PMR) to get resolution.

Using LookAt to Look Up Message ExplanationsLookAt is an online facility that allows you to look up explanations for z/OS™ messages,system abends, and some codes. Using LookAt to find information is faster than aconventional search because in most cases LookAt goes directly to the explanation.

You can access LookAt from the Internet at:

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

or from anywhere in z/OS where you can access a TSO command line (for example, TSOprompt, ISPF, z/OS UNIX® System Services running OMVS).

To find a message explanation on the Internet, go to the LookAt Web site and simply enterthe message identifier (for example, IAT1836 or IAT*).

To use LookAt as a TSO command, LookAt must be installed on your host system. You canobtain the LookAt code for TSO from a disk on your z/OS Collection Kit, SK3T-4269 orfrom the LookAt Web site. To obtain the code from the LookAt Web site, do the following:

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

2. Click the News button.

Preface

xiv Version 2 Release 7

|

|||

|

|

||

||

|||

|

|

http://www.tivoli.com/support/survey/

http://www.tivoli.com/support/handbook



3. Scroll to Download LookAt Code for TSO and VM.

4. Click the ftp link, which will take you to a list of operating systems. Select theappropriate operating system. Then select the appropriate release.

5. Find the lookat.me file and follow its detailed instructions.

To find a message explanation from a TSO command line, simply enter: lookat message-id.LookAt will display the message explanation for the message requested.

Note: Some messages have information in more than one book. For example, IEC192I hasrouting and descriptor codes listed in z/OS MVS Routing and Descriptor Codes,SA22-7624. For such messages, LookAt prompts you to choose which book to open.

Conventions Used in This BookThe term data set is used in this book to refer to members of partitioned data sets.

In NPM panels, statements, and commands, the term LU means a terminal. Unlike the SNAdefinition, this definition of LU does not include applications. In NPM, the abbreviationAPPL means application program.

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

Changes in This EditionThe following changes have been made to this book for NPM Version 2 Release 7 (V2R7):

¶ NPM version numbers have been updated throughout this book.

¶ LookAt information has been added to this preface.

¶ Chapter 1, “Introduction to NPM Concepts” has been updated to include a description ofthe enhancements for this release of NPM.

¶ Chapter 8, “Migrating to NPM Version 2 Release 7” has been updated to includechanges to the FNMINIT member.

Changes in the Previous EditionThe following changes were made to this book for NPM Version 2 Release 6 (V2R6):

¶ Chapter 1, “Introduction to NPM Concepts” was updated to include a description of theenhancements for this release of NPM.

¶ Chapter 8 was updated to include migration of user profiles.

¶ Chapter 9, “Isolating Performance Problems in a Network” was updated to include thesection on isolating problems in an IP network from the old Chapter 4 (“DeterminingProblems in the Network”) and the old Chapter 4 was deleted.

¶ New PF keys were added to the panels in the following chapters:

v Chapter 9, “Isolating Performance Problems in a Network”

v Chapter 10, “Isolating Poor Response Time on a LAN”

v Chapter 11, “Isolating Performance Problems in the Host”

Preface

xvNPM Concepts and Planning

|

||

|

||

|||

|

||

|

|

|

|

||

||

|

v Chapter 12, “Reviewing Network Performance”

Preface

xvi Version 2 Release 7

Part I. NPM Functions and FeaturesChapter 1. Introduction to NPM Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Overview of NPM User Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Collect and Monitor Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Collect Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Determine Problems in the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Tune and Expand the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Overview of Version 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Session Manager Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5VTAM Statistics Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Updated Host User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Updated Network Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7NetWare Resources Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7NPM Enhancements in Version 2 Release 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Dynamic NPM Configuration Discovery using RODM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8New SESSAPPL Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8New Counters for 3746 NNP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8NPM Collection for All MPC Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Integration between Tivoli Business Systems Manager and NPM GUI . . . . . . . . . . . . . . . . . . . . . . . . . . 9Add Start, Stop, Alter Collection Support on NPM Console and NMC-NPM Console. . . . . . . . . . . . . . . 9Add DataView and Profiling Support on NMC-NPM Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

NPM Enhancements in Version 2 Release 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10SNMP Router Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10APPN Support for SNMP Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123270 panels: Dynamic Data Display and PF keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Recovery of SNMP Router Collection on TCP/IP Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Cisco IP to LU Mapping Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Rename Cryptic Labeled Items in 3270 Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Recovery of GUI Interface Connection on TCP/IP Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Cisco Channel Interface Processor Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Overview of the NPM Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2. Collecting and Monitoring Performance Data . . . . . . . . . . . . . . . . 17Collecting IP Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Collecting and Monitoring Network Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Collecting Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Examples of Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25ISDN Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Monitoring 3746 Line Processor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Monitoring Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Controlling Network Data Collection and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Specifying Intervals for ODLC LAN Resource Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Recording and Viewing Network Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Collecting and Monitoring Session Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Collecting Session Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Types of Session Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Monitoring Session Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Controlling Session Data Collection and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

1NPM Concepts and Planning

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

Recording and Viewing Session Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Collecting Session Data from Session Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Collecting and Monitoring LAN Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Collecting LAN Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Types of LAN Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Monitoring LAN Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Controlling LAN Data Collection and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Recording and Viewing LAN Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Collecting Response Time Monitor (RTM) Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Types of RTM Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Controlling RTM Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Recording and Viewing RTM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Collecting and Monitoring VTAM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59VTAM Statistics Collection Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Controlling VTAM Data Collection and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Recording and Viewing VTAM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Collecting and Monitoring NetWare Resource Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Controlling NetWare Resources Data Collection and Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Recording and Viewing NetWare Resources Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 3. Collecting Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Collecting Network Session and Gateway Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Backup NPALUs and NPALU Takeovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Controlling Network Accounting Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Collecting Data from the VTAM Session Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Collecting Dynamic Network Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Collecting Accounting Data from NetView Access Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Recording and Viewing Accounting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 4. Tuning and Expanding the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . 69Creating Reports with the FNMREPRT Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Examining the Reports for Tuning the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

2 Version 2 Release 7

Introduction to NPM Concepts

Tivoli NetView Performance Monitor (NPM) enables you to control and monitortelecommunication networks. NPM aids network support personnel in managing theperformance and growth of Virtual Telecommunications Access Method (VTAM®)-basedcommunication networks. NPM runs as a VTAM application program on an OS/390-basedprocessor.

Overview of NPM User TasksYou can use NPM to perform the following main tasks:¶ Collect and monitor performance data¶ Collect accounting data¶ Determine problems in the network¶ Tune and expand the network

Collect and Monitor Performance DataYou can collect data from your network to monitor the utilization and the performance ofvarious resources. NPM provides extensive statistics on network traffic, queue length, bufferutilization, communication controller activity, and many other attributes of networkresources. NPM also enables you to collect data for resources that reside on non-SystemsNetwork Architecture (non-SNA) networks, such as local area networks (LANs), networksusing Novell’s NetWare product, or packet-switching networks. Figure 1 on page 4 shows theconfiguration of a general network on which NPM can collect data.

1


1.In

trod

uctio

nto

NP

MC

on

cepts

You can display the collected data either in table or graphic format. You can also store thecollected data and generate batch reports by using tools provided with NPM or your ownreport generators.

See “Collecting and Monitoring Performance Data” on page 17 for more information.

NPM uses OpenEdition® sockets for collecting IP (SNMP) performance data. OpenEditiondetermines the actual transport to use based on the destination (target) address unless anapplication binds itself to a particular transport (physical file system) via a setibmopt callprior to issuing the socket call to open a socket.

OpenEdition is composed of three basic layers:The top layer (or Logical File System) is the layer that NPM enters when using eitherOpenEdition sockets or POSIX services.The lowest layer is composed of whatever physical file systems (PFSs) configured toOpenEdition. TCP/IP is defined to OpenEdition as an INET PFS. OpenEdition cansupport various INET PFSs and can support more than one TCP/IP.When more than one INET PFS is defined, you must also configure a middle layer toOpenEdition called the INET router.

For IP performance support, there are no reasons for NPM to bind its sockets to a particularPFS. The actual transport needed to reach a target is handled by OpenEdition. Refer to theOpenEdition and OS/390 TCP/IP documentation for further information.

Collect Accounting DataYou can use NPM to collect accounting data and store it in system files. These files can beaccessed by your applications to allocate the costs of operating the network among the users.

PU

PU

LU

LU

OtherNCPs

NCP

X.25Resources

EthernetLAN

Frame RelayNetwork

NetWareResources

Token Ring

Token Ring

Token Ring

Token Ring

Bridge

LANmanager

IP Client

Router

IP Client

CS/390

TelnetServer

NPM

NetworkData

LANData

NetView

3746

NetViewAlertsSession

Data

SNMPData

VTAMData

IPNetwork

Figure 1. Sample Network for NPM Data Collection

Overview of NPM User Tasks


See “Collecting Accounting Data” on page 63 for more information.

Determine Problems in the NetworkThe most frequent complaint of network users is slow response time. With NPM, you cancollect data on the session between the user’s terminal and the host application. NPMprovides an actual value for the response time and divides it into two major components:¶ Network transit time¶ Host transit time

NPM also provides the capability to collect performance data from IP network elements.This data can used to determine which part of an IP network is over-utilized. You can useNPM to monitor the network resources, determine the cause of the problem, and take theproper action to return the system to normal operation.

Tune and Expand the NetworkYou can use NPM to analyze your network’s utilization of available resources and plan for abalanced growth of the system. You can collect and store performance data, and byreviewing batch reports created from the stored data, you can discover trends in use thatjustify changes or expansion in the network. See “Tuning and Expanding the Network” onpage 69 for more information.

Overview of Version 2NPM Version 2 provides the following functions and features:¶ VTAM statistics collection¶ Updated host user-interface¶ Updated network collection¶ Online help for messages and panels¶ NetWare resources data collection¶ Multisession manager support enhancement¶ LU6.2 support for session collection¶ TELNET session collection

Session Manager SupportNPM's ability to collect session statistics from multisession managers has been increased byadding support for the Terminal Productivity Executive (TPX) even in a cross-domainenvironment.

VTAM Statistics CollectionNPM manages the internal performance of VTAM by collecting statistical data about keyfunctions of VTAM and providing information for tuning and optimizing the overallperformance of your network. NPM dynamically displays the data collected withoutrequiring any system definitions. This VTAM statistics collection feature enables you tocollect and view information, including:¶ APPN® topology data¶ APPN directory services data¶ Buffer use¶ Central processing unit utilization¶ Channel-attached activity data¶ Common storage area use

Overview of NPM User Tasks


1.In

trod

uctio

nto

NP

MC

on

cepts

¶ Communications Storage Manager (CMS) data¶ Environmental data¶ Multinode Persistent sessions (MNPS) data¶ Multipath channel device data¶ MVS™ jobname data¶ Rapid Transport Protocol (RTP) statistics¶ Storage data¶ Virtual route data

NPM provides two types of data collection intervals for collecting dynamic VTAM data:

¶ The refresh interval is the interval at which NPM displays the most recent datacollected from VTAM.

¶ The sampling interval is the interval at which NPM updates its own counters. Thisupdated data is not displayed until the next refresh interval. If a sampling interval is sethigher than a refresh interval, the sampling interval is automatically reset to the refreshinterval.

Attention: Small refresh and sampling intervals can adversely affect performance. TheINTERVAL command enables you to change these sampling intervals dynamically.

You can set specific monitor thresholds for VTAM data collection to alert you whenexception conditions occur and when these conditions are resolved. You can use this VTAMmonitor data, along with other performance data, to provide a more complete picture of yournetwork’s performance.

The VTAM statistics collection collects VTAM information, correlates the information toother information collected by NPM about network control programs (NCPs) and SystemsNetwork Architecture (SNA) sessions, and provides the same types of functions for real-timemonitoring, data logging, and reporting that NPM provides for other types of data.

The VTAM information collected by NPM, combined with information about NCP and SNAsession performance that NPM collects, enables you to have a complete picture of yournetwork, enhancing problem detection and isolation capabilities.

The VTAM statistics data is written to NPM files. You can run batch programs againstsequential log files to generate sample reports for analysis.

Updated Host User InterfaceThe ability to display VTAM resources and to perform actions on these resources has beenadded to the host user interface. The Primary Options menu is now divided by type of datacollection rather than by type of task. The NCP Management and Session Managementoptions on this menu have been renamed as Network Management and Response TimesManagement respectively. The panel flows have also been changed for improved usability.Resources, such as buffer pools and virtual routes, are shown on selection lists. Once youchoose the type of data collection and select a resource from a list, you can:¶ Start a new collection¶ Stop an existing collection¶ Modify an existing collection¶ Request an updated list of all active and deferred collections for a resource¶ Scroll through a collection using common scroll commands

Overview of Version 2


¶ View data about the resource

Updated Network CollectionNetwork collection has been updated for NPM Version 2. The following characteristics arenow applicable:

¶ NPM provides seven collection intervals for network collection on the host.

¶ NPM allows you to choose data destinations on an individual basis.

¶ NPM provides you with multiple deferred collections.

¶ NPM allows you to start collections from the consolidated network collection commandsof the NETCOLL command.

NetWare Resources Data CollectionWith the NPM NetWare Resources Performance Data Collection feature, you can collectdata about various resources on a NetWare network, for example, data about:

¶ NetWare server connections

¶ NetWare IPX communications

¶ NetWare routers

¶ NetWare LAN boards

¶ NetWare SPX communications

¶ NetWare SPX connections

¶ NetWare volumes

NPM provides two types of data collection intervals for collecting NetWare resourcesperformance data:

¶ The refresh interval is the interval at which NPM displays the most recent datacollected from NetWare resources.


Note: Small refresh and sampling intervals can create some performance problems.

You can set specific monitor thresholds for NetWare resources data collection to alert youwhen exception conditions occur and when these conditions are resolved. You can use thisNetWare resources monitor data, along with other performance data, to provide a morecomplete picture of your network’s performance.

As with other types of NPM data collection, the NPM NetWare Resources Performance DataCollection feature allows real-time monitoring, data logging, and reporting functions. Thedata is written to NPM files, so you can run batch programs against sequential logfiles togenerate reports for analysis. You can use this data for making decisions about tuning theperformance of these resources.



1.In

trod

uctio

nto

NP

MC

on

cepts

NetWare resource data is not available for analysis from NPM’s 3270 panels. The data canbe viewed by NPM’s batch reporting facility and on the NPM Console.

NPM Enhancements in Version 2 Release 7The enhancements made to NPM in Version 2 Release 7 (V2R7) are described below underthe following headings:

¶ Dynamic NPM Configuration Discovery using Resource Object Data Manager (RODM)

¶ New SESSAPPL command

¶ New counters for 3746 NNP support

¶ NPM collection for all MPC devices

¶ Integration between Tivoli Business Systems Manager and NPM GUI

¶ Add Start, Stop, Alter collection support on NPM Console and NMC-NPM Console

¶ Add DataView and Profiling support on NMC-NPM Console

Dynamic NPM Configuration Discovery using RODMThis enhancement enables NPM to gather information about network configuration for SNA,IP, and Applications resource by dynamically reading the information from the RODMrepository and adding the information into the NPM environment. NPM also manages thedynamic changes in the network configuration during the run.

Configuration information is gathered from the RODM repository and defined to NPM for:

¶ CCUs

¶ Routers

¶ Applications

New SESSAPPL CommandWith this enhancement, in addition to defining applications at initialization time, you candefine applications using a new SESSAPPL command using an NPM EXEC or the systemconsole, or both. This new SESSAPPL command contains all the parameters that you nowhave to specify in the APPL statement of the FNMINIT member and a new OPTION field.The new OPTION field allows you to Add, Delete, or Replace an application definition.

See the SESSAPPL command in the NetView Performance Monitor User’s Guide for adetailed description of all the supported parameters.

New Counters for 3746 NNP SupportThis enhancement enables NPM to support new counters coming from 3746 NNP.

Currently, in NPM V2R6, the processor utilization is reported to NPM only using a Subareapath (NCP) and using the APPN DLUR/DLUS path (NNP). In NPM V2R7, the NPAcomponent in the NNP sends the processor utilization for the NPM session managing theAPPN resources.

The new counters are:

Processor Type: NNP = X'51'

Processor Utilization Value in percentage of the NNP microprocessor



|

||

|

|

|

|

|

|

|

|

||||

|

|

|

|

|

|||||

||

|

|

||||

|

||

||

APPN Buffers Utilization Value in percentage of the Current APPN Buffers

APPN Memory Utilization Value in percentage of the Current APPN Memory

NPM Collection for All MPC DevicesNPM V2R6 provides collection for Subarea MPC devices with an FID4 channel connectiontype.

This enhancement enables NPM to gather statistics for the other MPC types, that is, AHHCand HPDT FID2 connection types.

NPM V2R7 supports all types of MPC devices and can collect VTAM statistics for the MPCgroup and for the MPC devices.

See the NetView Performance Monitor User’s Guide for information about collecting anddisplaying VTAM device data, that is, a description of the type of information that you canget for the MPC group and devices on the VTAM online management panels.

See the NetView Performance Monitor Reference for a description of the sample reports thatyou can use for batch reporting, that is, FNMVMPCD (VTAM MPC Device Data) andFNMVMPCG (VTAM MPC Group Statistics).

Integration between Tivoli Business Systems Manager and NPM GUIThis enhancement allows you to access the Tivoli Business Systems Manager console. Byselecting a resource (right-click) that is managed also by NPM, you can start theTBSM-NPM Console. On this console, you can:

¶ Logon to one or more NPMs.

¶ Send a QuickView request for the selected resource to a specified NPM. This commandshows real-time performance data.

¶ Send a DataView request for the selected resource to a specified NPM. This commandshows historical performance data.

¶ Save the QuickView or DataView settings as a profile.

¶ Start a collection for the selected resource to a specified NPM.

¶ View the collections list showing all the collections that are defined for the selectedresource. For each collection, you can stop the collection or alter the collectionparameters.

Add Start, Stop, Alter Collection Support on NPM Console andNMC-NPM Console

In NPM V2R7, from the NPM Console, you can:

¶ Send a Start Collection request for the selected resource to a specified NPM. Thiscommand sends a collection request to the NPM for the resource that is specified in theresource text field.

¶ Send a List Collection request for the selected resource to a specified NPM. Thiscommand sends a request to all collections (Active and Deferred) that are defined forthe selected resource. For each collection, you can stop the collection or alter thecollection parameters.

Enhancements to NPM


||

||

|

||

||

||

|||

|||

|

|||

|

||

||

|

|

|||

|

|

|

|||

||||

1.In

trod

uctio

nto

NP

MC

on

cepts

In NPM V2R7, you can select an NPM-managed resource from the NMC-NPM Console,and thereby effect the following:

¶ Send a Start Collection request for the selected resource to a specified NPM.

¶ Send a List Collection request for the selected resource to a specified NPM. Thiscommand sends a request to all collections (Active and Deferred) that are defined forthe selected resource. For each collection, you can stop the collection or alter thecollection parameters.

¶ Send a DataView request for the selected resource to a specified NPM. This commandshows historical performance data.

Add DataView and Profiling Support on NMC-NPM ConsoleIn NPM V2R7, from the NMC-NPM Console, you can:

¶ Send a DataView request for a selected resource to a specified NPM. This commandshows historical performance data.

¶ Save the QuickView or DataView settings as profiles. The profiles will be saved for userand type of resource.

NPM Enhancements in Version 2 Release 6The enhancements that were made to NPM in Version 2 Release 6 are described belowunder the following headings:

¶ SNMP router alerts

¶ APPN support for SNMP routers

¶ 3270 panels: Dynamic Data Display and PF keys

¶ Recovery of SNMP router collection on TCP/IP failure

¶ Cisco IP-to-LU mapping support

¶ Rename cryptic labeled items in 3270 panels

¶ GUI

¶ Recovery of GUI interface collection on TCP/IP failure

¶ Cisco Channel Interface Processor (CIP) support

SNMP Router AlertsThis enhancement generates alerts when thresholds on routers are triggered.

The following counters are monitored:

¶ CPU usage (percentage) for IBM® NHD routers

¶ CPU busy (percentage) for Cisco routers

¶ Application memory usage (percentage) for IBM NHD routers

¶ Global buffers usage (percentage) for IBM NHD routers

¶ Memory pool usage (percentage) for Cisco routers (individual Cisco memory poolusage)

¶ Percentage of interface utilization (individual interface throughput)

Enhancements to NPM


||

|

||||

||

|

|

||

||

|

¶ Percentage of packets received by the interface and discarded

¶ Percentage of packets sent by the interface and discarded

¶ Percentage of CIP utilization (only for Cisco routers)

In addition to collecting the IP performance data, NPM can also monitor the collected datain relation to specified thresholds. This IP monitoring function is available from consolesupport and from 3270 panels. New router alerts are also forwarded to the NPM Console, aswith all other alerts generated by NPM.

Table 1 shows the available monitors for the SNMP router resources.

Table 1. Monitors for SNMP Router ResourcesResources Monitor Keyword for

IPCOLLDescription Record field

NHD 2210NHD 2216NHD 6611MSS8210NETUNHD 2212NHD 3746

CPUUTIL CPU load NRTTCLS

Cisco CPUUTIL CPU busy percentage NRTCCBP


APPNMEMU Memory utilization NRTMMUP


GLOBUFUT Global buffers utilization NRTPBGP

Cisco POOLUTIL Pool memory utilization NRPCPUTI

Cisco CIPUTIL Cisco CIP CPU utilization NRCIPCUT

All SNMP routers IFUTIL Interface utilization (seeNote 1)

NITIFUTI

All SNMP routers INDISC Percentage of InboundDiscarded Packets (seeNote 2)

NITIFIDP

All SNMP routers OUTDISC Percentage of OutboundDiscarded Packets (seeNote 2)

NITIFODP

Enhancements to NPM


1.In

trod

uctio

nto

NP

MC

on

cepts

Table 1. Monitors for SNMP Router Resources (continued)Resources Monitor Keyword for

IPCOLLDescription Record field

Note:

1. Interface utilization is the percentage of the total link capacity that is used for receiving andsending data. The objects ifInOctets and ifOutOctets give the total number of bytes received andsent on an interface. Calculating the deltas for these objects and dividing by the bandwidth givesthe interface utilization percentage.

2. The objects ifInDiscards and ifOutDiscards contain the number of packets that were chosen to bediscarded by the system even though no errors had been detected on input or output. Calculatingthe deltas for these objects and dividing by the collection interval time gives the rate of discards(input and output) on an interface. The objects ifInUcastPkts and ifInNUcastPkts give the totalinput unicast and nonunicast packets on an interface. The objects ifOutUcastPkts andifOutNUcastPkts give the total output unicast and nonunicast packets on an interface. Calculatingthe deltas for these objects and dividing by the collection interval time gives the packet rates(input and output) on an interface. Dividing the discard rate by the packet rate gives thepercentage of inbound and outbound discarded packets for an interface.

APPN Support for SNMP RoutersMost routers that handle APPN have implemented the APPN-MIB. This enhancement allowsNPM to retrieve the number of XID bytes received and sent and the number of message(I-frame) bytes received and sent.

3270 panels: Dynamic Data Display and PF keysThe Dynamic Data Display function allows you to display network and response times dataon 3270 panels without waiting for collection interval end and for NPM to write the datainto the review files. Real-time data is collected and displayed on the screen using therefresh interval (as in the NPM console) and is automatically refreshed at your request.

Note: If you are using a Personal Communication 3270 emulator, the recommended versionis 4.3. For version 4.1 or earlier versions, it is recommended that you disable theKeystroke Buffering function (Assist menu, Keyboard Setup option).

You can access the Dynamic Data Display using one of the following paths:

¶ One of the new PF keys and commands: NCP, ROUTER, LINE, APPL, TERMINAL

¶ The new DYN (Dynamic) command on the Network Management and Response Timesoutput review panels

¶ Fast path =1.8 or fast path =2.4 (renamed to Dynamic Data Display from Last IntervalAnalysis)

The following predefined PF keys and commands are provided:

¶ NCP (PF15), for NCPs

¶ ROUTER (PF16), for IBM, NT, and Cisco routers

¶ LINE (PF17), for SDLC lines

¶ APPL (PF20), for VTAM applications

¶ TERMINAL (PF24), for SNA LU and TCP/IP terminals

Enhancements to NPM


To support these functions these new PF keys (15, 16, 17, 20, and 24) are always displayedon each NPM panel.

To use the new PF keys with old NPM operators, you need to migrate the user profile (see“Updating the User Profile” on page 91).

Recovery of SNMP Router Collection on TCP/IP FailureThis enhancement restarts SNMP support functions when TCP/IP is recovered after a failureand, if any SNMP router collection was active, recovers the collection.

Cisco IP to LU Mapping SupportThis enhancement allows NPM to retrieve IP to LU mapping information forTN3270/TN3270E clients connected into an OS/390 through a Cisco TN3270(E) server. Thisfunctionally was previously only available for IBM NHD routers.

Rename Cryptic Labeled Items in 3270 PanelsTable 2 shows the cryptic labeled items in the 3270 panels that have been renamed.

Table 2. Renamed Labeled Items in 3270 PanelsPanel Old label New label

FNM00PRI 2 Network Data Collection and Analysis9 NPM Control

2 NCP/Router Data Collection & Analysis9 NPM Control Functions & Exec

FNM00PRM 4 Session Accounting Data 4 User Session Accounting Data

FNM02SL2 Subnet Mask Subnet Mask (wildcard)

FNM03RI2 Mtu status Max Datagram

FNM02RVMFNM02LBM

(REVIEW for active review file)

FNM01SES 2 Stop/Status Active3 Stop/Status Deferred

2 Active Collection - List/Stop/Alter3 Deferred Collection - List/Stop/Alter

FNM02SAMFNM02DNIFNM02DNMFNM02DRMFNM02SAR

(SESSION for active session file)

FNM02GS2FNM04GDI

Maximum Ever Maximum Used

FNM03VS3 Cur WindowInt Window

Current Window SizeInterval Window Size

FNM04ADI AS ID Address Space ID

FNM02OPM Session Number Session Buffers

GUIThe enhanced GUI console :enables you to view NPM online data that originated as anetwork resource displayed on the NetView Monitor Console (NMC) Topology Console. Theconsole includes descriptions of the new counters and code for the new major vectorassociated with the Cisco Channel Interface Processor support.

Recovery of GUI Interface Connection on TCP/IP FailureWith this enhancement, when TCP/IP is recovered after a failure, NPM allows you toreconnect to the GUI console. You do not need to stop and restart NPM.

Enhancements to NPM


1.In

trod

uctio

nto

NP

MC

on

cepts

Cisco Channel Interface Processor SupportThis enhancement allows NPM to use the existing SNMP router support to gathermanagement data for Cisco Channel Interface Processors (CIPs).

The following management data is collected for each Cisco CIP that is defined to NPM:

¶ CIP Card name, CIP Card revision number, CIP Card Index

¶ Time since last reset

¶ Memory, DMA, and CPU utilization

The new data is logged using a new NPM record type.

You can review the collected data using the 3270 panels, the NPM Console, and new samplebatch reports.

Overview of the NPM Installation ProcessBefore you load the program tape, you need to identify the functions you will use and theequipment you will need.

Before you begin to install NPM, you need to fully understand the wide variety of featuresand functions NPM offers so that you can make an informed decision about what to install.

After installation, you have further options for tailoring NPM and for optimizing networkperformance.

This book describes the NPM functions used for collecting data and the features andfunctions that support data collection and NPM operation. Some of the functions must beinstalled and others are optional. Use this book to decide which functions are important foryour situation. You should install only the NPM functions you need. The following listshows the required and optional tasks involved.

Planning

¶ Decide which NPM functions you want to use.

¶ Ensure that you have the required hardware and software. See the NPM ProgramDirectory for a list of the hardware and software requirements for this release ofNPM.

¶ Estimate your storage needs and ensure that you have enough storage available.

¶ Contact the Support Center for the most recent preventive service planning(PSP) information and high impact or pervasive authorized program analysisreport (HIPER APAR) list.

Installing

¶ Use the NPM Program Directory to install the program tape on your system.

¶ Use the program directory to apply all current program temporary fixes (PTFs)to your system, including any necessary fixes to related programs.

¶ Install exit routines to enable NPM to collect data from response time monitor(RTM), dynamic network collection (DNC), and VTAM session manager. Also,

Enhancements to NPM


install exit routines to control system management facilities (SMF). These areoptional tasks depending on the functions required.

¶ Download the NPM NetWare Agent code and associated code to NetWareservers to enable the NetWare Resources Collection feature. This is an optionaltask depending on whether the feature is used or not.

¶ Start NPM on the host and then verify that the installation is correct.

Customizing

¶ Customize NPM to fit your needs, such as starting data collection automatically,defining groups of logical units (LUs), or performing special processing with theNPM installation-wide exit. This is an optional task.

¶ Tune NPM for optimum performance. This is an optional task.

¶ Code applications to use the data you have written to log files, or use TivoliDecision Support for OS/390 (formerly known as Tivoli Performance Reporterfor OS/390) to create custom reports.

¶ You can also use the NPM batch reporting facility with the sample reportsprovided, which can be customized to meet your needs. These are optional tasks.

Note: If you have a previous release of NPM installed on your system, you can omit anumber of steps when installing and customizing Version 2. See the NPM Installationand Customization and “Migrating to NPM Version 2 Release 7” on page 89 foradditional information.

This book provides information to help you through the planning phase and samplescenarios of NPM utilization for network problem determination. See the NPM Installationand Customization and the NPM User’s Guide for information about tuning and using NPM.

It is recommended that you create an installation plan to document the decisions that youmake during the planning phase.

Installation Overview


1.In

trod

uctio

nto

NP

MC

on

cepts

Installation Overview


Collecting and Monitoring PerformanceData

NPM collects performance data to help you assess how efficiently the network operates.NPM data collection functions include the setting of monitoring criteria. For many types ofperformance data collected by NPM, you can set high and low criteria levels and therebyreceive a message or NetView alert to inform you when the data is outside these limits.

Performance data is categorized by its source, as shown in Figure 2 on page 19, and isgrouped in the following categories:

Routers dataIs Management Information Base (MIB) data that is retrieved from IP networkelements via the Simple Network Management Protocol (SNMP). This data isorganized into four categories: system identification, interface loads, memoryutilization, and CPU utilization. Not all network elements support the same MIBs.All should support the collection of system identification and interface load data,while memory and CPU utilization data is available from most IBM NHD and Ciscorouters (and from Channel Interface Processors of Cisco routers).

Network dataComes from a network control program (NCP) running on a communication controlunit (CCU). It includes statistics on resources defined to the NCP. NPM collects datafor Ethernet and token-ring LAN resources, or X.25 and frame relaypacket-switching network resources, provided that the resources are connectedthrough the proper adapters to the CCU. For example, NPM collects performancedata for physical and logical links on token-ring LANs connected to the CCUthrough the token-ring interface coupler (TIC).

NCP also sends performance data for resources attached to a 3746 Model 900expansion frame. Data can be collected for SDLC, ESCON®, frame relay, X.25, andLAN resources attached in this way.

Data for the same resource types can also be collected directly from 3746 Model900 or Model 950 APPN network nodes (NNs) when the resources are notNCP-controlled. 3746 attached resources are defined automatically to NPM by the3746.

Session dataComes from VTAM and provides statistics for each session managed by VTAM,including transit times and message volumes. Session data collection includes afunction for monitoring criteria.

In an OS/390 environment (V2R5 or later), you can collect session data for IPclients that use the TN3270E protocol.

2


2.C

ollectin

gan

dM

on

itorin

gD

ata

Session data can also come from session manager products such as NetView AccessServices or TPX. “Collecting Session Data from Session Managers” on page 47provides more information about this data.

LAN bridge and LAN segment dataCome from a LAN (Local Area Network) manager or LAN Network Manager. Youmust have LAN Network Manager V1.1, and LAN Station Manager, to collect LANsegment data. LAN bridge data includes statistics on bridge traffic (in number offrames) and on lost frames (including causes for lost frames). LAN segment dataprovides information about the utilization of the segment. Utilization data isavailable for token-ring segments, while LAN bridge data is available for local andremote bridges on token rings, IBM PC, Ethernet, or 3174 peer networks. LAN datacollection includes a function for monitoring criteria.

Response time monitor (RTM) dataComes from the IBM model 3X74 cluster controllers. The collection of this data isactually managed by the NetView program, and NPM obtains this data from theNetView program.

VTAM dataComes from VTAM. NPM collects data about the internal performance of VTAM bycollecting statistical data about key functions of VTAM. The data includes statisticson jobnames running active VTAM applications, active VTAM applications, bufferpools, channel activity, the VTAM environment, multipath channel devices, internalstorage, and virtual routes. VTAM data collection includes a function for monitoringcriteria.

NetWare resources dataIs collected from resources in a NetWare environment. The NPM NetWare Agentand associated code reside on NetWare servers and collect data about theperformance of the resources in the NetWare network. This data includes theconnection activity for servers, activities of routers, activities related to the IPXcommunications, SPX communications, SPX connections, LAN board activity, anddata for NetWare volumes.

Collecting and Monitoring Data


To control the collection of performance data, you can initialize NPM to collect performancedata automatically and then start, stop, and modify the collection using:¶ NPM’s online panels¶ NPM EXECs¶ The system console

You can view the performance data that NPM collects by using:

¶ Online NPM panels to display stored data in table format

¶ Reporting programs to generate and print reports from stored data (including NPM’sbatch reporting facility)

Figure 3 on page 20 shows the possible destinations for each type of performance datacollected by NPM.

PerformanceData

LAN manageror

LAN NetworkManager

NPMNetWare

Agent

NPM

SessionData

VTAMData

LANData

NetWare Resources Data

RTMData

SNMPData

NetworkData

NetViewSessionMonitor

NCPs

CS/390

TelnetServer

Figure 2. Sources of Performance Data Collected by NPM

Collecting and Monitoring Data


2.C

ollectin

gan

dM

on

itorin

gD

ata

Collecting IP Performance DataFigure 4 on page 21 shows how NPM collects IP performance data. NPM provides thecapability of retrieving IP performance data from any network element that supports theSMNP. The data that is collected is determined by the type of network element. The data isorganized into four categories: system identification, interface loads, memory utilization, andCPU utilization. Not all network elements support the same MIBs. All should support thecollection of system identification and interface load data, while memory and CPUutilization data is available from most IBM NHD and Cisco routers.

LAN, Network,Session, andNetWare Alerts

LAN, Network,and SessionExceptions

NPM

NPM OnlinePanels

NPMReports

OtherReportPrograms

SessionData

AllPerformanceData

AllPerformanceData

NetView

NPM Online Panelsor System Console

AllPerformanceData

PerformanceData(except NetWareResources Data)

NPMFiles

NPM Console

Figure 3. Destinations of Performance Data Collected by NPM

IP Performance Data Collection


For NPM to retrieve data from a target via SMNP, the target must:

¶ Have an IP address

Note: If a routed network is being used, make sure that you use an address for thenetwork element that returns a single value.

¶ Have an SNMP agent that is started and accessible via the specified IP address

¶ Be using the same SNMP agent as configured to NPM (defaults to 161)

¶ Have its SNMP administration configured to match when it is configured to enable NPMaccess.

Currently three security models are defined by the SNMP standards: SNMPv1, SNMPv2c,and SNMP v3. SNMPv1 and SNMPv2c are community-string (password) based and can bedefined directly to NPM or defined within the standard osnmp configuration file used by theIBM TCP/IP component of OS/390. SNMPv3 security configuration uses an OS/390 TCP/IPosnmp file that is either snmpv2.conf or osnmp.conf, depending on the version of OS/390eNetwork Communications Server IP Configuration:

¶ OS/390 V2R5.0 (SC31–8513–00), section 2.15.5.2: Configure the OE SNMP (osnmp)command. This version of TCP/IP supports SNMPv1, SNMPv2c and the experimentalprotocol SNMPv2u (USEC). In particular the snmpv2.conf file defined within thissection can be used by NPM for defining SNMP security parameters. The search pathfor this file is identical to that defined in this document with the exception that thesearch path using the TCP/IP jobname as a data set prefix is replaced with that ofNPM’s jobname.

¶ OS/390 V2R6.0 (SC31–8513–01): No change in this version with respect to SNMPsecurity support.

¶ OS/390 V2R7.0 (SC31–8513–02): This version of TCP/IP dropped support forexperimental protocol SNMPV2u and added support for the standard base protocolSNMPv3. A new osnmp-related configuration file (osnmp.conf) was added that issearched before the legacy configuration file (snmpv2.conf).

¶ OS/390 V2R8.0 (SC31–8513–03): No change in this version with respect to SNMPsecurity support.

NPM

OpenEdition

GenericRouter

IBMRouter

CiscoRouter

SNA/IP Network

Figure 4. IP Performance Data Collection



2.C

ollectin

gan

dM

on

itorin

gD

ata

NPM searches for security parameters in the osnmp.conf file before the snmpv2.conf file. Ifnone are found, base SNMPv1 security is assumed with a default community string of‘public’.

NPM can retrieve the following information:

¶ All network elements or routers, or both:

v System Group from RFC 1213. Used to determine the router type and provide basicrouter information.

v ifTable from RFC1213. Used to determine traffic rates per adapter or interface, orboth.

v ifStackTable from RFC2233. Used to determine interface layering.

¶ IBM NHD router specific data:

v MemMib. APPN memory usage.

v Proteon MIB. General router memory utilization.

v IBM CPU MIB. Router CPU utilization.

¶ Cisco router support:

v Old Cisco CPU MIB. Router CPU utilization.

v Cisco memory MIB. General router memory utilization.

v Cisco Channel MIB. Cisco Channel Interface Processor (CIP) utilization.

Not all versions of a particular network element support either the same set of MIBs or thesame MIB in the same manner. Table 3 shows which data NPM expects to be supported pernetwork element type and per version, if known.

Table 3. Supported Data per Network Element TypeData Generic 2210 2212 2216 6611 MSS8210 NETU Cisco

RFC1213system/ifTableobjects

Yes Yes Yes Yes Yes Yes Yes Yes

ibmcpu.mib (1) (10) (6) (9)

mem.mib (2) (10) (5) (8) (9)

proteon.mib (3) (10) (4) (7) (9)

TN3270E MIBs (1) (10) (6) (9)

Old Cisco CPUMIBs

Yes

Cisco memoryMIBs

Yes

Cisco channelMIBs

Yes

Key:(1) is 2210 Multiprotocol Routing Services 3.1.0.0.(2) is 2210 Multiprotocol Routing Services 2.1.0.0.(3) is 2210 Version 2 Release 2.(4) is 2216 Multiprotocol Access Services 1.1.0.0.(5) is 2216 Multiprotocol Access Services 1.1.1.0.



(6) is 2216 Multiprotocol Access Services 3.1.0.0.(7) is MSS Version 1 Release 0.(8) is MSS Version 2 Release 0.(9) is Network Utility MIB Multiprotocol Access Services 3.1.0.0.

Note: The NHD FTP site that contains the various supported MIBs shows only a 3.1.0.1version. The MIBs supported by this release are the same as the 3.1.0.0 release.

(10) is NWays Router V3.2 (CC4.0) / 2212. The 2212 is a new router version that usesthe same code base as the 2210 and 2216. It is approximately the same size as 2210 butfunctions in a similar manner to the 2216 because it is powerPC based and has up tofive slots for adapter cards. Most of the functions on 2210 and 2216 are available on2212.

Collecting and Monitoring Network DataNPM can collect data for the performance of the NCP itself or for the performance ofresources attached to the CCU and defined to the NCP, including lines, token-ring andEthernet resources, X.25 and frame relay resources, logical units (LUs), and physical units(PUs). NPM also provides performance data collection support for user-defined links or PUsattached to the CCU through the network extension option (NEO) interface.

Network data helps you analyze resource utilization, errors, and retransmissions, and isindependent of who is using the resource. For example, line utilization data givesinformation on the total traffic on a line, not on the terminals and applications that arecommunicating through the line.

Collecting Network DataFigure 5 on page 24 shows how NPM collects network data. To receive the data from theNCP, NPM uses an LU-to-LU session with a network performance analysis logical unit(NPALU) in the NCP.

The transfer of data between the NCP and NPM occurs at set time intervals. This means thatwhen you issue a command for network collection, you also specify an interval for NPM touse to determine the period of time during which it collects data. NPM then sends a requestto the NPALU to start the collection for specific resources, such as lines, LUs, and otherNCPs.

When the specified collection interval expires (or when you stop the collection throughanother command), NPM sends a forward request unit (RU) to the NPALU to request thecounters. When NPM receives the data that the NCP has collected in its counters, itcalculates and logs interval values for each resource. For example, if you specify an intervalof 30 seconds, NPM collects, summarizes, and records statistics on the selected resources foreach 30-second interval. Note that NPM can send the collection data to a terminal or tovarious data files.



2.C

ollectin

gan

dM

on

itorin

gD

ata

Network performance data can also be collected for resources attached to a 3746 APPNnetwork node (NN). Data for these resources is collected by some NPA code in the 3746 andis forwarded to NPM in a similar manner as data is forwarded for NCP-controlled resources.

Specifying the Network Collection IntervalNPM calculates collection intervals from a base interval, the shortest length of time that isused for collection during a particular NPM session. You define the base interval duringNPM installation. NPM calculates the additional intervals. Each interval is equal to twice theprevious interval. For example, Table 4 shows this calculation when the base interval is 225seconds.

Table 4. Collection Interval ExamplesInterval Time

1 (base interval) 225 seconds

2 450 seconds (7.5 minutes)

3 15 minutes

4 30 minutes

5 1 hour

6 2 hours

7 4 hours

Each interval is assigned a sequential number, 1 through 7, and when you issue thecommand to start network collection, you must specify one of the sequential intervalnumbers. For example, if you use a base interval of 225 seconds and you specify thecollection interval as 3, then each collection interval represents 15 minutes worth of data. Ifhourly measurements are required, only interval 5 can be used.

Figure 5. Network Performance Data Collection

Network Collection and Monitoring


Attention: Collection intervals longer than one hour are not recommended because afailure in the NCP, VTAM, or NPM could cause collected data to be lost.

Examples of Network DataThe following list shows the network resource performance data that NPM collects:

¶ NCP and CCU data

¶ SNA resourcesv Line datav PU datav LU data

¶ Binary synchronous communication (BSC) resourcesv Link datav Cluster datav Terminal data

¶ LAN resources

v NCP/Token-Ring Interconnect (NTRI)– NTRI physical link data– NTRI logical link data

¶ Ethernet Transmission Subsystem (ESS)v Ethernet physical link data

¶ Outboard data link control (ODLC) LANv ODLC physical link datav ODLC PU data

¶ Packet-switching network resources

v X.25 networks

– NCP Packet-Switching Interface (NPSI)¶ NPSI multichannel (MCH) link data¶ NPSI MCH PU data¶ NPSI virtual circuit (VC) data

– X.25 SNA Interconnection (XI)¶ XI MCH link data¶ XI MCH PU data

– 3746-attached X.25¶ X.25 physical link data¶ X.25 PU data¶ X.25 VC data

v Frame relay networks

– Frame relay data communication equipment (DCE)¶ Local management interface (LMI) PU data¶ Physical station data

v Frame relay data terminal equipment (DTE)– Physical link data– Logical link data

¶ NEO resources



2.C

ollectin

gan

dM

on

itorin

gD

ata

v Link datav PU data

¶ Router resourcesv Mapping data between LU name and IP addressv End-user response time datav Management data for Cisco Channel Interface Processors

The following sections describe some of the data that NPM collects for these resources. Youcan display this data on NPM’s online panels.

Each section includes a table that associates the resource types with the data that NPMcollects for them and a description of each data type.

Note: NPM also collects other data for each resource and stores this data in system files.See the NPM Reference for a complete description of all the data records written byNPM.

CCU, SNA, and BSC ResourcesTable 5 shows the data that NPM collects for CCUs, SNA lines (BSC links), SNA PUs (BSCclusters), and SNA LUs (BSC terminals).

Table 5. SNA, BSC, and CCU Performance DataResources Data Description

CCU CCU UTIL Percentage of the CCU capacity that was used duringthe interval

FREE BUFFER QLEN Number of free buffers in the outbound queue at the endof the interval

FREE BUFFER HIGH Highest number of free buffers available during theinterval

FREE BUFFER LOW Lowest number of free buffers available during theinterval

CHANNEL INTERM Number of messages queued in the NCP waiting to besent to the host at the end of the interval

CHANNEL HOLD Number of messages sent to the host but not yetacknowledged at the end of the interval

% IN SLOWDOWN Percentage of the collection interval during which theCCU was in slowdown because of buffer deficiency

Line (link) OUTBOUND QUEUELENGTH

Number of PDUs in the resource outbound queue at theend of the interval

MSGS/MIN Number of path information units (PIUs) sent orreceived per minute through the line

BYTES/SEC Number of bytes sent or received per second throughthe line

LINE-UT PRI Percentage of the total line capacity used during theinterval. For a duplex line, this is the usage of theprimary leg of the line. For a half-duplex line, this isthe usage of the primary line.



Table 5. SNA, BSC, and CCU Performance Data (continued)Resources Data Description

LINE-UT SEC Percentage of the total line capacity used during theinterval. For a duplex line, this is the usage of thesecondary leg of the line. For a half-duplex line, this iszero. NPM does not collect this data for bisynchronouslines.

POLLS/MIN RATE Number of responses to polling received per minute

POLLS/MIN %NEG Percentage of negative responses to polling received perminute

ERRORS Number of temporary errors or retries that occurredduring the interval

RETRANSMIT PIUS Number of messages that were retransmitted duringretries

RETRANSMIT BYTES Number of bytes in the retransmitted messages

PU (cluster) OUTBOUND QUEUELENGTH

Number of messages queued in the NCP for the PU atthe end of the interval

MSGS/MIN Number of PIUs sent or received per minute through theNCP for the PU

BYTES/SEC Number of bytes sent or received per second throughthe NCP for the PU

POLLS/MIN RATE Number of responses to polling received per minute

POLLS/MIN %NEG Percentage of negative responses to polling received perminute


RETRANSMIT PIUS Number of messages that were retransmitted duringretries

RETRANSMIT BYTES Number of bytes in the retransmitted messages

LU (terminal) OUTBOUND QUEUELENGTH

Number of messages queued in the NCP for the LU atthe end of the interval

MSGS/MIN Number of PIUs sent or received per minute through theNCP for the LU

BYTES/SEC Number of bytes sent or received per second throughthe NCP for the LU

The following sections provide you with more detailed information about the statisticsdescribed in Table 5 on page 26.

MessagesStatistics for messages are counted at two different points:

¶ Messages sent are counted as they are queued for transmission to their destination.

¶ Messages received are counted when they are queued for transmission to the host.

In NPM, a message is one of the following:

¶ For synchronous data link control (SDLC) links and PUs, a message is an FID1, FID2,FID3, or FID4 PIU or PIU segment. In SNA, path information units (PIUs) are



2.C

ollectin

gan

dM

on

itorin

gD

ata

classified according to the content of the field in their transmission header called theformat identification (FID) field. This field can contain a 0, 1, 2, 3, or 4. A count for alink includes counts for all PUs on the link. A count for a PU includes counts for allLUs on the PU.

¶ For SDLC logical units, a message is an FID1 or FID4 PIU. NPM counts these PIUswhen they are queued for transmission, before they are converted to FID2 or FID3 PIUs,and before they are segmented in NCP. Because collection occurs before PIUs aresegmented for LUs and after PIUs are segmented for PUs and links, collecting messageson a PU or link and on all the LUs under it provides an indication of how muchsegmentation is occurring. Increasing the Cluster Controller LINK BUFFERSIZE, wherepossible, decreases segmentation.

¶ For binary synchronous 3270s, a message is a FID0 PIU with one of the following basictransmission unit (BTU) command fields: INVITR, READ, or WRITE.

Line UtilizationLine utilization is the percentage of total line capacity used for sending and receiving data.NPM calculates line utilization as follows:Line utilization = number of bytes transmitted during an interval

(line speed × length of interval)

Line utilization = number of bytes transmitted during an interval(line speed × length of interval)

Because different line speeds are possible, NPM calculates two separate line utilizations forduplex lines. When duplex lines are monitored, NPM compares the lesser of the two lineutilization values with the low threshold, and the greater of the two utilization values withthe high threshold.

ErrorsNPM collects and logs the following error data:

¶ The number of temporary errors (retries), including time-outs and polling errors, thatoccurred during the interval. These errors are counted when the retry is attempted. Theerrors do not result in the retransmission of data.

¶ The number of messages retransmitted from the NCP during the interval. NPM increasesthe message count by one for each PIU present.

¶ The number of bytes retransmitted from the NCP during the interval. NPM increases thebyte count by the number of bytes in the retransmitted PIU.

Because of PIU segmentation in the NCP, byte counts are not an exact multiple of themessage count.

PollingNPM collects or counts the following polling information:

¶ The total number of polls for a particular resource during an interval. NPM displays thedata as polls per minute.

¶ The number of times a poll from the NCP to the resource does not receive data (anegative poll).

¶ The number of times a poll from the NCP to the resource receives data (a positive poll).



Transmission PrioritySDLC lines and PUs transmit data based on the transmission priority of the virtual route.Messages with a high priority virtual route are sent first, while lower priority messages arequeued. NPM reports network performance data by transmission priority for SDLC lines andPUs. The number of PIUs and bytes sent and received are reported by high, medium, andlow virtual route priority.

NPM stores transmission priority data in 12 fields, in line and PU interval records. PIUssent, PIUs received, bytes sent, and bytes received are each reported by high, medium, andlow virtual route priority.

You do not need to code any specific statements in NPM to use transmission prioritysupport. You must, however, code the NCP generation definition to enable this support. Ifthe NCP does not support transmission priority data, or if you have not enabled it, NPMcollects the other network data and the transmission priority fields are not included in therecord.

Note: With NPM, you can also collect performance data on Enterprise Systems Connection(ESCON) resources connected to the 3746 Model 900 or Model 950 expansion framefor the 3745 CCU.

LAN ResourcesTable 6 shows the network performance data that NPM collects for LANs attached to theCCU.

NTRI data is performance data collected for token-rings connected to the CCU through thetoken-ring interface coupler (TIC). NPM collects data for both NTRI physical and logicallinks.

Ethernet data is performance data collected for an Ethernet V2 or IEEE 802.3 LANconnected to the CCU through the ESS adapter. NPM collects data for Ethernet physicallinks.

ODLC LAN data is performance data collected for a token-ring connected to a 3746 Model900 or Model 950 expansion frame for a 3745 CCU. The collection of the data is performedin the 3746 by its internal licensed code. The data is then sent to NPM through an NCPrunning on a connected 3745 CCU. NPM collects the following two types of ODLC LANdata:

¶ Data about the total traffic through the adapter. This data represents the physical link.

¶ Data about each connection through the adapter. Each connection represents an SNAsession in this context, and a token-ring workstation with such a session is viewed as aPU by NPM.

Table 6. LAN (NTRI, Ethernet, and ODLC) Performance DataResources Data Description

NTRI OUTBOUND QUEUELENGTH

Number of PDUs in the resource outbound queue theend of the interval

IFRAMES/MIN Number of information (I) frames sent or received perminute

BYTES/SEC Number of bytes sent or received per second



2.C

ollectin

gan

dM

on

itorin

gD

ata

Table 6. LAN (NTRI, Ethernet, and ODLC) Performance Data (continued)Resources Data Description

TIME OUTS Number of reply time-outs that occurred for the logicallink during the interval

RETRANSMIT IFRAMES Number of I-frames retransmitted to the LAN duringretries

RETRANSMIT BYTES Number of bytes in the retransmitted I-frames

TIC UTIL Estimate of the percentage of an interval that the TICwas busy

CONGEST COUNT Number of frames destined for the physical link thatcould not be received because of TIC congestion

ACTIVE CONNS Number of active logical connections associated withthe physical link

Ethernet OUTBOUND QUEUELENGTH

Number of PDUs in the resource outbound queue forthe Ethernet LAN at the end of the interval

TRANSMIT BYTES/SEC Number of bytes sent (including retransmit andoverhead bytes) divided by the number of seconds inthe interval

RECEIVED BYTES/SEC Number of bytes received (including retransmit andoverhead bytes) divided by the number of seconds inthe interval

COLLISION ONE Number of times a collision occurred during thetransmission of a frame

COLLISION MORE Number of times more than one collision occurredduring the transmission of a frame

TRANSM DEFER Number of times the ESS had to defer the transmissionwhile trying to transmit a frame to the Ethernet LAN

ODLC IFRAMES/MIN Number of I-frames sent and received per minute forthe resource through the application.

BYTES/SEC Number of bytes sent and received per second for theresource through the application

RETRANSMIT IFRAMES Number of I-frames retransmitted from the applicationto the resource during retries

TOT. PDUS DISCARDED Number of protocol data units (PDUs) for the physicallink that were discarded because of buffer limitations,misaddressing, and unrecognized frames.

PU REPLY TIMEOUTS Number of reply time-outs for the LAN station PU

Packet-Switching Network ResourcesTable 7 on page 31 shows the network performance data that NPM collects forpacket-switching networks connected to the CCU.

X.25 data is performance data that is collected for X.25 networks connected to the CCUthrough the NPSI or XI adapters or to the 3746 Model 9x0.

Using NPM X.25 support, you can collect network performance statistics on:

¶ NCP Packet-Switching Interface (NPSI)v NPSI multichannel (MCH) link data



v NPSI MCH PU datav NPSI virtual circuit (VC) data

¶ X.25 SNA Interconnection (XI)v XI MCH link datav XI MCH PU data

¶ 3746-attached X.25v X.25 physical link datav X.25 PU datav X.25 VC data

Frame relay data is performance data that is collected for frame relay DTEs and frame relayDCEs. Frame relay is a high-speed, packet-switching technology, similar to the X.25standard, that defines an interface between the customer equipment (the DTE), and anetwork connection point (the DCE). Frame relay can transport any higher layer protocol(X.25, SNA, token ring, Ethernet, and so on) transparently. Frame relay is designed forhigh-speed, low-error-rate lines, with data verification being performed at the network endpoints. It does not guarantee error-free delivery, it merely discards bad frames. NPMsupports frame relay DTE for physical links and logical links and frame relay DCE for LMIPUs and physical stations.

Table 7. X.25 and Frame Relay Network Performance DataResources Data Description

X.25 OUTBOUND QUEUELENGTH

Number of PDUs in the resource outbound resourcequeue at the end of the interval

IFRAMES/MIN Number of I-frames sent and received per minute forthe resource through the application

BYTES/SEC Number of bytes sent and received per second for theresource through the application

PACKS/MIN Number of packets sent and received per minutethrough the application. NPM does not collect this datafor link-type resources.

LINE-UT % PRI Percentage of the total line capacity used during theinterval. For a duplex line, this is the usage of theprimary leg of the line. For a half-duplex line, this isthe use of the primary line.

LINE-UT SEC Percentage of the total line capacity used during theinterval. For a duplex line, this is the use for thesecondary leg of the line. For a half-duplex line, this iszero.

RNR-REJ SENT For link-type resources, this is the number of receivenot ready or request not ready (RNR-REJ) frames sentthrough the X.25 application for the resource. ForPU-type resources, this is the number of RNR packetssent.

NPM does not collect this data for VC-type resources.



2.C

ollectin

gan

dM

on

itorin

gD

ata

Table 7. X.25 and Frame Relay Network Performance Data (continued)Resources Data Description

RNR-REJ RCVD For link-type resources, this is the number of RNR-REJframes received through the X.25 application for theresource. For PU-type resources, this is the number ofRNR-REJ packets received.

NPM does not collect this data for VC-type resources.

RETRANSMITIFRAMES

Number of I-frames retransmitted from the applicationto the resource during retries

RETRANSMIT BYTES Number of bytes in the retransmitted messages orI-frames.

Frame relay OUTBOUND QUEUELENGTH

Number of messages queued in the NCP for the framerelay resource at the end of the interval

IFRAMES/MIN Number of I-frames sent and received per minute by theframe relay resource

BYTES/SEC Number of bytes sent and received per second by theframe relay resource

TIME OUTS The number of reply time-outs that occurred for thelogical link during the interval

RETRANSMITIFRAMES

Number of I-frames retransmitted from the applicationto the frame relay physical or logical link during retries

RETRANSMIT BYTES Number of bytes in the retransmitted I-frames

CONGESTION FORWD Number of frames that have the forward congestion bitset on by the frame relay physical station. This bitindicates to the DTE (NCP) that forward (inbound)traffic in the network has reached a predetermined levelof congestion. This notification enables the NCP tobegin congestion-avoidance procedures.

CONGESTION BACK Number of frames that have the backward congestionbit set on by the frame relay physical station. This bitindicates to the DTE (NCP) that backward (outbound)traffic in the network has reached a predetermined levelof congestion. This notification enables the NCP tobegin congestion-avoidance procedures.

FRAMES DISCARD Number of forward (inbound) and backward (outbound)frames that have been discarded by the frame relayresource because of network congestion

NEO ResourcesTable 8 shows the data that NPM collects for resources attached to the CCU through thenetwork extension option (NEO) interface. NEO data is performance data for user-definedlinks and PUs. You can also define your own NEO performance data. NPM will use 192bytes in its records to write this user-defined data.

Table 8. NEO Network Performance DataResources Data Description

NEO OUTBOUND QUEUELENGTH

Number of PDUs in the resource outbound queue atthe end of the interval



Table 8. NEO Network Performance Data (continued)Resources Data Description

PDUS/MIN Number of PDUs per minute sent and receivedthrough the NEO application

OCTETS/SEC Number of octets per second sent and receivedthrough the NEO application

LINE-UT PRI Percentage of the total line capacity used during aninterval. For a duplex line, this is the use of theprimary leg of the line. For a half-duplex line, this isthe use of the primary line.

LINE-UT % SEC Percentage of the total line capacity used during aninterval. For a duplex line, this is the use of thesecondary leg of the line. For a half duplex line, thisis zero.


RETRANSMIT PDUS Number of PDUs from the NEO application to theresource during retries

RETRANSMIT OCTETS Number of octets in the retransmitted PDUs

ISDN ResourcesNPM recognizes and defines ISDN physical and logical lines; and these lines can be seen onNPM’s network Resource List panels. When these lines are activated, a specific trafficprotocol is assigned, and NPM transforms the resource type to match the protocol beingused. The data that is collected is written as records in the format of that protocol.

At the current time, the only protocol being used across these ISDN links is frame relay.Thus, an ISDN link will be transformed into an frame relay link on NPM’s panels, and thedata that is collected is identical to that collected for statically-defined frame relay resources(described in “Packet-Switching Network Resources” on page 30).

Monitoring 3746 Line Processor DataTable 9 shows the data that NPM collects for 3746 line processors.

Table 9. 3746 Line Processor DataResources Data Description

3746 LineProcessors

Type The type of processor installed

Utilization The utilization of the processor expressed as apercentage

Shared Data StorageUtilization

The utilization of the shared data storage for aprocessor expressed as a percentage

Program Data StorageUtilization

The utilization of the program data storage for aprocessor expressed as a percentage

Monitoring Network DataIn addition to collecting network data, NPM can also monitor the collected data in relationto specified thresholds.



2.C

ollectin

gan

dM

on

itorin

gD

ata

To monitor network data NPM first begins network data collection, if not already active, andthen monitors a particular type of data for a selected resource. NPM monitors the data at theend of every interval and at the time the monitor ends. NPM compares the value of themonitored data against defined thresholds for the specified data type. If the value fallsoutside the thresholds, NPM generates a monitor event message. You can also choose tohave NPM send alerts to the NetView program using the NetView program-to-programinterface.

NPM provides two options for network monitoring:

¶ Monitor exceptions

NPM generates one monitor exception message per interval (FNM200I) if the value ofthe data has fallen outside the thresholds during the interval.

¶ Monitor resolution tracking

If you choose to monitor resolutions, NPM generates two kinds of messages. Itgenerates a monitor exception message (FNM200I) when the data first falls outside thethresholds. NPM generates the monitor resolution message (FNM201I) at the end of aninterval, if the data has fallen back within the thresholds.

Examples of Monitoring Network DataThe following two examples show how these two options work. In both examples, NPMwas monitoring the percentage of line utilization for line A04L01. The following parameterswere entered using either the NPM NETCOLL command or the start collection panels.¶ Interval = 3 (15 minutes)¶ Time = 08:30:00 ⁄ 17:00:00¶ Resource = A04L01¶ Monitor Data Type = Percent line utilization¶ Low Threshold = 10¶ High Threshold = 60¶ Destination Terminal = YES

Monitor exceptionsTable 10 shows the results of a network monitor with monitor exception on. NPM generatedonly exception messages.

Table 10. Example of Network Monitor with Monitor ExceptionTime Line Utilization

PercentageMessage Generated by NPM

14:45:00 53 No message is generated.


15:15:00 62 FNM200I FOR A04L01 LINEUTL OF 62 WAS ABOVE LIMIT OF60.




16:15:00 8 FNM200I FOR A04L01 LINEUTL OF 8 WAS BELOW LIMIT OF10.





Table 10. Example of Network Monitor with Monitor Exception (continued)Time Line Utilization


17:00:00 63 FNM200I FOR A04L01 LINEUTL OF 63 WAS ABOVE LIMIT OF60. The monitor stops because the end time is reached.

Monitor resolution trackingTable 11 shows the results of a network monitor when monitor resolution was turned on.NPM generated messages for both exceptions and resolutions.

Table 11. Example of Network Monitor with Resolution TrackingTime Line Utilization






15:45:00 54 FNM201I FOR A04L01 LINEUTL of 54 no longer above limit of 60.


16:15:00 8 FNM200I FOR A04L01 LINEUTL OF 8 WAS BELOW LIMIT OF 10.

16:30:00 74 FNM201I FOR A04L01 LINEUTL of 74 no longer below limit of 10.FNM200I FOR A04L01 LINEUTL OF 74 WAS ABOVE LIMIT OF60.


17:00:00 63 The monitor stops because the end time is reached.

Controlling Network Data Collection and MonitoringYou can control collection and monitoring of network data by:¶ Issuing commands at NPM initialization¶ Issuing commands from the system console¶ Placing commands in NPM EXECs¶ Using NPM’s online panels

All of these methods enable you to collect and monitor data automatically on a continuousbasis or intermittently.

Note: NPM EXECs allow NPM to perform a variety of NPM functions with a singlecommand simply by coding sequences of NPM commands in a data set. NETCOLLis the command for collecting and monitoring network data. It specifies:

¶ The NCP from which NPM is collecting or monitoring data

¶ The interval

¶ The type of data to collect or monitor

¶ The resource on which to collect or monitor data

¶ The high and low threshold criteria

¶ The time of day at which you want to start and stop the collection and monitoring

¶ Whether you want the collection or monitoring to occur daily



2.C

ollectin

gan

dM

on

itorin

gD

ata

¶ Where you want the data recorded

¶ Whether to send an alert to the NetView program

¶ Where you want the exception data recorded

¶ The type of monitor messages to send (exception or resolution)

An authorized NPM operator can use online panels for starting, stopping, and viewing thestatus of network data collection. You manage authorization levels by setting parameterswithin an operator’s security profile. The operator can either start a collection immediatelyor defer the collection to a specified time.

By using either commands or online panels, you can make collection or monitoringautomatic by specifying that you want the collection to be started and stopped every day atfixed times.

NPM can also execute commands at startup. If you code the NETCOLL command toautomatically collect data, then collection or monitoring is automated as soon as youinitialize NPM.

The following options are available from panels, the system console, or NPM executableprograms (EXECs):

¶ Receive a list of current network resources with details about the current collection andmonitoring status.

¶ From the list of current resources, perform any of the following actions on a selectedresource:v Start an immediate collection with monitors on any intervalv Stop the collectionv Display the collection parameters using any interval

¶ Start a collection on a dynamic resource

¶ View data stored in a review file for a resource not currently known to NPM

¶ Delete a deferred collection

The following options are available using the online panels:¶ Use the panels to modify the collection on a list of current resources¶ Use the panels to modify a deferred collection

Note: The NPM Primary Options menu (FNM00PRI) enables you to perform actions on aresource by going through paths categorized by collection type.

Specifying Intervals for ODLC LAN Resource CollectionThe 3746 Model-900 or Model-950 attached LAN resources send unsolicited data to NPM.

For these resources, it is important to understand that two different intervals exist. One, theNPM interval, is selected by the user when starting a collection on a resource. The other, theODLC interval, is contained in the 3746 microcode. The ODLC interval is currently set to225 seconds, matching NPM’s default base interval.

With traditional network collection, only the NPM interval exists. When it expires, NPMrequests the current counter values from the NCP. Thus, data is solicited at a frequencychosen by the user.



With ODLC network collection, the user interface is identical, and a collection interval canbe selected, but NPM has no control over when the data arrives. The NPM interval is usedto determine when the data is written.

There are three possible scenarios for data collection:1. The NPM interval is smaller than the ODLC interval2. The NPM interval is equal to the ODLC interval3. The NPM interval is greater than the ODLC interval

The following describe each scenario:

NPM interval is smaller than ODLC interval- In this case, the NPM interval expiresseveral times without any data being received from the 3746 Model-900 or Model 950. But,when an RU arrives, the data is written when the next NPM interval expires. The timesrecorded for the interval start and stop are taken from the ODLC interval and reflect thetime for which the data was actually collected.

Consider an example using an NPM interval of 60 seconds (remember that the ODLCinterval is always 225 seconds). When the first three NPM intervals expire, there is no datafrom the 3746 Model-900 or Model 950, and no record is written. Forty-five seconds intothe fourth interval, an RU arrives. The counter values are parsed out, the deltas arecalculated, and the data is stored until the next NPM interval expiration. After four minutesfrom the collection start, the NPM interval expires. The stored data is then written to theappropriate destinations (SMF, review file, alert). The interval time will be recorded as 225seconds. This process continues and a display of the review file will show all the recordscollected with an interval time of 225 seconds.

NPM interval is equal to ODLC interval- In this case, one RU arrives for each NPMinterval. The RU’s arrival might not coincide with the NPM interval expiration, but at theend of each interval, a record will be written using the data from a different RU. To the user,this scenario appears as a traditional network collection.

NPM interval is greater than ODLC interval- In this case, multiple RUs arrive for eachNPM interval. The counter values are parsed out of the RU, the deltas are calculated, andthe data is accumulated until the NPM interval expires. When the interval expires, the totalsare written in one record.

Consider an example of an NPM interval of 10 minutes. An RU arrives after 225 seconds,and the data is stored. A second arrives after 7.5 minutes, and the data is added to the datafrom the first RU. After 10 minutes, the NPM interval expires, and a record is written withan interval time of 7.5 seconds.

In every case, regardless of what interval is chosen, all the data sent by the 3746 Model-900or Model 950 will be recorded. The only difference from traditional network collection isthat the data is not necessarily written as it arrives.

Recording and Viewing Network DataWhen you start network collection or monitoring, you can specify a destination where thedata is recorded or displayed. NPM can send data to any or all of the following destinations:



2.C

ollectin

gan

dM

on

itorin

gD

ata

¶ The VSAM file (FNMREVx data sets), where the data, including monitor eventmessages, can be analyzed using online panels. NPM displays data on specific detailpanels for each resource. You can also view monitor event messages, both exceptionsand resolutions.

¶ The NPM log file, FNMLOGx, which can be used for generating reports with NPM’sbatch reporting program or other utility

¶ System management facility (SMF), which can also be used for generating reports

In addition, you can choose to have NPM send monitor event messages as alerts to theNetView program.

Network data collection records (as are all NPM records), are formatted as SMF type 28records. Reports of collected network data can be generated with the NPM batch reportingfacility (FNMREPRT) or other products, for example, Tivoli Decision Support for OS/390.See NPM Reference for specific details on the format of the records and the tools togenerate the reports.

Collecting and Monitoring Session Data

Session data is collected from VTAM and consists of session statistics such as transit timesand data volumes.

During installation, you define all the resources on which you want to collect transit timesand volume statistics. You can collect the data from either VTAM in the host or fromsession managers (such as NetView Access Services) or TPX, using the NetView synergyinterface (NSI).

Session data can also be collected when an IP network is connected to an OS/390 system.You can collect session data when an IP client that supports TN3270E connects to aTN3270E server over an IP network to reach an SNA-based application.

NPM’s session collection supports data collection by the IP address and port (TCP)associated with a TN3270E client. NPM can learn these mappings from either an OS/390eNetwork Communications Server that is running on the same MVS LPAR as NPM or anIBM NHD or Cisco router that supports the TN3270E–MIB.

Note: When running session collection on Telnet sessions, it could happen that NPMtransactions entered in the first interval (and sometimes the last interval) of the Telnetconnection are logged to the TCPIP LU (TCPIP pseudoterminal) instead of the IPaddress/port.

This scenario occurs because the task that updates the table mapping the LU-IPresources and the task managing the actual flow of recorded transactions duringsession collection cannot be synchronized.

Collecting Session DataFigure 6 on page 39 shows how NPM collects session performance data from VTAM. Whena request for session data comes from NPM, VTAM records data from sessions with LUs ornodes on the network and sends the data to NPM. VTAM can record data from across-domain LU, if the LU is in session with an application in the VTAM host where NPMis running.



||||

|||

The data can be recorded at any of the following times:

¶ When the specified interval ends

¶ When a transaction that started in a previous interval ends in the current interval

¶ When the session ends

The length of a session interval is derived from the base interval. The session interval is amultiple of the base interval. For example, if the base interval is 30 seconds and the sessioninterval number is 10, then the length of the session interval is 300 seconds, or 5 minutes.

Types of Session DataYou can choose to collect session performance data in either of two general ways:

¶ Collection by application in the NPM host

¶ Collection by one of the following:v LUv Cross-domain LUv LU groupv Node (NCP, cross-domain NCP, local host, or cross-domain host)

The advantage of collection by application is a saving in common storage area (CSA) use.The advantage of collection by LU, LU group, or node is that you can limit your collectionto specific LUs, reducing the amount of private storage used.

NPM collects the following session data:

¶ Transit times

Transit time measures the length of time it takes for inbound and outbound PIUs totravel from an operator, through the network, to the host, and back through the networkto the operator (operator response time).

¶ Volume statistics

NCP

PU

PU

LU

LU

Data

NPM

StorageBuffers

NetView

Session DataAlerts

NPMConsole NPM

LogSessionFile

VTAMLog

SMF

CS/390

TelnetServer

Figure 6. Session Collection of VTAM Performance Data

Session Collection and Monitoring


2.C

ollectin

gan

dM

on

itorin

gD

ata

Volume statistics count the number of PIUs sent and received for each LU, and includetheir average size in bytes and the total number of bytes.

Collecting Transit Time DataFor each session, NPM computes operator, host, and network transit times.

Host transit time Specifies the time that the transaction spends in the host.

Network transit time Specifies the time that the transaction spends in the network.

Operator transit time Specifies the host and network transit times added together.It is approximately what the operators experience as theirresponse time.

These transit times are meaningful for LU2 sessions. When you start session collection,NPM enables you to define high and low transit time thresholds for the operator, host, andnetwork transit times. When transit times fall outside of these limits, they are highlighted inthe session analysis displays. In addition, NPM enables you to define four transit timeboundary values. NPM reports the number of transactions that fall within each range definedby these thresholds.

Calculating Transit TimesFigure 7 shows how NPM calculates transit times.

Each PIU is intercepted as it passes through VTAM. The following sequence of eventsshows when a PIU is recorded and how the transit time is calculated.

1. The terminal (LU) operator enters data and presses CLEAR, ENTER, or a PF key. ThePU controller sends the data into the network to the host VTAM.

2. VTAM records the time the inbound PIU arrives (A) and passes the PIU on to theapplication.

3. The application generates one or more outbound PIUs for the terminal. VTAMintercepts the outbound PIUs and records the time (B).

4. The outbound PIUs are sent through the network to return to the terminal operator.

5. When an outbound PIU is received at an LU that specifies definite response, a responsePIU is sent back to the application.

6. VTAM records the time that this response PIU arrives (C).

NPM calculates the transit time for a transaction as follows:

APPL VTAM LU

(3)

(5)

(1)(2)A

(4)B

(6)C

Figure 7. Transit Time Calculation



Host transit time = B - A

Network transit time = C - B

Operator transit time (response time) = C - A

To NPM, a transaction is from the first inbound PIU with the first-in-chain indicator to thefirst outbound PIU with the first-in-chain indicator, even if it is a null RU PIU. The hosttransit time is the time from the first inbound PIU to the first outbound PIU. Network transittime is the time from the first outbound PIU to the next response received. Although NPMwrites a record when an application issues an unsolicited SEND, this is not an NPMtransaction because there is no inbound PIU request. It is, therefore, possible to see intervalswith records recorded but with no transactions.

NPM transactions are not based on the bracket protocol. If the LU from which data iscollected follows the bracket protocol, each application transaction can consist of one ormore NPM transactions.

Calculating TN3270 and TN3270E Transit TimeTN3270E is a set of extensions to the TN3270 protocol. For an IP network to be measured,both the TN3270 server and the client must support the TN3270E protocol and havenegotiated the TN3270E response option. Negotiating the TN3270E response option enablesthe SNA definite response request to be sent from the host to an IP client and enables the IPclient to respond to the request.

Response support for servers and clients is optional. For example, the PCOMM clientsalways request the response option (it is not a configuration option), while other clients, likeReflections, allow the response option to be either enabled or disabled at the client.

The TN3270E Server for OS/390 2.5 always requests the response option of its clients. Mostother TN3270E servers will support the responses option, but might not request it of theirclients automatically. Some TN3270E clients always request it while others make it optional,in the startup parameter. In addition, there are probably TN327OE clients that do notimplement the response option.

NPM can detect whether the response option has been negotiated. If you want to measureTN3270 and 3270E transit time, you should enable the response option at all the clientswhere it is possible. If you use a definite response flow to measure network transit times fora TN3270 or TN3270E client that has not negotiated the response option, you will receivemeaningless values.



2.C

ollectin

gan

dM

on

itorin

gD

ata

Calculating Transit Time in Special SituationsFor sessions with printers, cross-domain resource managers, NPALUs, andapplication-to-application sessions, the calculation of transit times and transaction counts haslittle meaning. NPM is designed to measure transactions with interactive terminals.

For TSO sessions, VTAM’s path router holds inbound response PIUs until another inboundPIU is sent from the TSO operator. Therefore, the calculation of TSO response times is notcompleted until VTAM releases the response PIU from its buffers because of an incomingPIU.

Using Definite Response TimeNPM uses the definite response time as the approximation of the inbound PIU time, tocalculate network transit time and, ultimately, the operator transit time. This method ofcalculating transit time results in the following possibilities:

¶ If a terminal LU sends long inbound PIUs to an application, the calculation made fornetwork transit time is not valid. This causes network transit times to be low. This is onereason why network transit times for application-to-application sessions can beinaccurate.

¶ Accurate transit times are more certain when there are many transactions specifying adefinite response. The higher the ratio of responses to transactions, the greater thecertainty will be, although accurate data is possible with even a relatively small ratio.

Because NPM can use PIU flows, which are not considered transactions for transit timecalculations, it is possible for the number of responses to exceed the transaction count.

To help you collect accurate transit times, NPM provides two functions:¶ Dynamic definite response (DDR)¶ Data flow control (DFC)

You can use either one or both of the functions to calculate network transit times forapplications, such as CICS®, that do not normally return a definite response.

IP Network

Target Host

Client Host

NPM

{SNANetwork}

Table

TN3270EServer

LocalIP

AddressSLU

TargetApplication

(PLU)

VTAM

IPClient

RemoteIP Address

Figure 8. Session Collection of IP Network Data



Using Dynamic Definite Response (DDR) and Data Flow Control (DFC)If your environment includes transactions that do not specify a definite response but that youwant to include in the average transit time figure, you can specify DDR, DFC, or both forsession data collection.

¶ DDR

You can request DDR responses for any resource eligible for session collection. Thedefinite responses caused by DDR do not appear in the NetView session monitor or theGTF traces.

The use of DDR increases the amount of message traffic in the network and NPMprocessing overhead in VTAM. You can use DDR for both LU2 and LU0 sessions, butnot for LU 6.2 sessions.

If you attempt to end NPM normally while DDR is active, NPM issues messageFNM324I to indicate that NPM is waiting for an outstanding dynamic definite response.NPM waits up to 2 minutes for such a response before ending. However, if NPM endsabnormally, it does not wait for any outstanding responses. Application sessions can beended in such cases because NPM definite responses are not filtered out.

¶ DFC

You can select to use this function by application. It is recommended that you use DFCinstead of DDR if you collect session data by application. However, the use of DFCdoes not preclude the use of DDR.

When you specify DFC, NPM calculates network transit times for user data PIUs withdefinite response and for DFC PIUs. For applications that send DFC PIUs but do notuse the definite response mode, such as CICS, it is recommended that DFC be used inconjunction with DDR.

DFC measurements provide only network times and have no effect on host transit timestatistics. NPM adds the separate network and host average transit to calculate theaverage of the operator transit times.

The accuracy of DFC measurements depends on how often DFC PIUs are sent andreceived by the application.

Note: NPM also provides you with the CICS Send Exit to collect transit time data forsessions between logical units and CICS applications while CICS is running inexception response mode.

DDR, DFC, and LU 6.2 SessionsLU 6.2 session collection is similar to LU2, with an important exception. NPM cannot useDDR or DFC for LU 6.2 sessions. Because the roles of the primary LU and secondary LUare not fixed, either LU can start a conversation.

If the LU 6.2 applications follow a transaction flow similar to LU2, in which one sessionpartner consistently starts each transaction and receives a response from the other, NPMaccurately measures response times. Most LU 6.2 applications adhere to this convention.However, if the applications behave differently, either with a reversed transaction flow orwith role reversal of the primary LU (PLU) and secondary LU (SLU) during a session, thedata can be inaccurate. NPM provides two methods for calculating transit times. They arecalled APPC1 and APPC2. APPC1 uses the CONFIRM and CONFIRMED commands tocompute network transit times.

For each LU 6.2 session, NPM computes the operator, host, and network transit times:



2.C

ollectin

gan

dM

on

itorin

gD

ata

Host transit time Reflects the time the host application was active and waitingfor a CONFIRM command.

Network transit time Reflects the sum of the elapsed times of the outbound PIUsthat requested a response. An APPC application issues aresponse when a confirmation has been requested.

Operator transit time Reflects the elapsed time from the start to the end of aconversation.

Network transit times are meaningful (that is, different from zero) only if the APPC protocoluses the CONFIRM command.

Using the CONFIRM command results in the sending of a definite response request. NPMwill then measure the time between the request and the response.

If both the CONFIRM and CONFIRMED commands are not used by the APPC protocol,then no LU 6.2 network time is measured. APPC2 is related to LU 6.2 acting in half-duplexflip-flop mode, without using the CONFIRM command. Data is sent to the host application,the host application sends data out until it has no more data to send, and then it begins toreceive data again. This exchange can continue for many flips before the transaction ends.

Host transit time Reflects the number of inbound requests (that start host time)and the time the inbound PIUs were processed by the hostuntil the next outbound PIU.

Network transit time Reflects the number of outbound requests (that start networktime) and the time the outbound PIUs were in the networkuntil an inbound PIU is received from the partner LU.

Operator transit time Reflects the elapsed time from the start to the end of aconversation.

Collecting Volume StatisticsIn addition to statistics for transit times, session data includes statistics on the volume ofPIUs sent and received during a session.

NPM gives the volume information according to the number of PIUs, the average PIU size,and the total number of bytes. The computation for average PIU size and total bytes includesthe request (or response) header (RH) and the request (or response) unit (RU), but does notinclude the transmission header (TH). Session volume data is divided into operator data(function management data) and system data. To avoid skewing the average PIU size, SNAacknowledgments (definite responses) are counted as system data. The information scannedby NPM is in FID4 format.

NPM collects the following volume data items:¶ Maximum inbound and outbound operator PIU size¶ Number of inbound and outbound messages¶ Maximum inbound and outbound message size¶ Number of messages sent and received¶ Maximum size of messages sent and received¶ Number of message bytes sent and received

NPM defines a message as all PIUs received until the last-in-segment flag in thetransmission header is on and the last-in-chain flag in the request header is on.



Note: If an LU is in session with an application for which you are already collectingstatistics, you can either collect only volume statistics for the LU or exclude the LUfrom session data. When you collect volume statistics only, the number oftransactions shown is zero.

Monitoring Session DataIn addition to collecting session data, NPM can also monitor the collected data in relation tospecified thresholds.

To monitor session data, NPM first begins session data collection, if not already active, andthen monitors a particular type of data for a selected resource. The data is monitored at theend of every interval and at the time the session ends. The value of the monitored data istested against thresholds specified for the data type. If the value falls outside the thresholds,NPM generates a monitor event message. You can also choose to have NPM send an alert tothe NetView program using the NetView program-to-program interface, or write a record tothe NPM session, log, or SMF files.

NPM provides two options for session monitoring:

¶ Monitor Exceptions

NPM generates one monitor exception message (FNM202I) per interval if the value ofthe data has fallen outside the thresholds during the interval.

¶ Monitor Resolution Tracking

If you choose to monitor resolutions, NPM generates two kinds of messages. Itgenerates a monitor exception message (FNM202I) when the data first falls outside thethresholds. NPM generates the monitor resolution message (FNM203I) at the end of aninterval, if the data has fallen back within the thresholds.

Controlling Session Data Collection and MonitoringYou can control collection and monitoring of session data by:¶ Issuing commands at NPM initialization¶ Issuing commands from the system console¶ Placing commands in NPM EXECs¶ Using online panels

All of these methods enable NPM to collect and monitor data automatically on a continuousbasis or intermittently.

Note: NPM EXECs allow you to perform a variety of NPM functions with a singlecommand simply by coding sequences of NPM commands in a data set.

SESSCOLL is the command for collecting and monitoring session data. It specifies:

¶ The LU, LU group, node, or application for which you want data

¶ The boundaries for the five time ranges (distribution groups) into which a transit timecan fall

¶ The time of day at which you want to start and stop collection

¶ Whether you want to collect data daily

¶ Whether you want to send PIUs to GTF for logging

¶ The high and low thresholds for host, network, and operator transit times



2.C

ollectin

gan

dM

on

itorin

gD

ata

¶ Whether you want to write minimum or complete PIUs to the VTAM log

¶ Whether you want to monitor session data

¶ The types of data you want to monitor

¶ The high and low monitoring criteria

An authorized operator can use online panels for starting, stopping, and viewing the status ofsession data collection. You manage authorizations by setting parameters in an operator’ssecurity profile. The operator can issue either active commands, which begin data collectionimmediately, or deferred commands, which begin data collection at a specified time.

By using either commands or online panels, you can automate collection or monitoring ofdata by specifying that you want the collection to be started and stopped every day at fixedtimes.

NPM also enables you to execute commands at its startup. If you code the SESSCOLLcommand to make the collection automatic, as described above, collection or monitoringbegins automatically as soon as you initialize NPM.

Session collection provides a combined collection and monitor command. For the hostinterface, all the options for session data collection are available from one menu,FNM01SES, which is accessible from the Primary Options menu (FNM00PRI).

Note: If more than one user starts a collection on the same resource, the last collectioncommand overrides the collection started by an earlier user. No warning is provided.

Recording and Viewing Session DataNPM can send data to any or all of the following destinations:

¶ The session file (FNMSESx data sets), which is a virtual storage access method (VSAM)key-sequenced data set for storing session data. It is available for viewing with NPM’sonline panels, where data for LUs, sessions, and performance is displayed. LU panelsprovide information about transit times, distribution, and volume. Session panelssummarize information about applications, lines, physical units, and virtual routes.Panels for performance data provide a hierarchical view of the network. Operators canview these panels if you authorize them in their security profiles.

¶ The VTAM log file (FNMVLOGx data sets). FNMVLOG is a basic sequential accessmethod (BSAM) sequential data set, where all PIUs collected for selected LUs can belogged as they pass through VTAM. The data from VTAM can be reformatted forteleprocessing network simulator (TPNS) script generation. You can collect volume andtransit time data on transactions between the host and the network, categorizing the databy LUs, applications, nodes, or group names.

¶ The NPM log (FNMLOGx data sets), which can be used for generating reports with theNPM batch reporting program or other utility.

¶ SMF, which can also be used for generating reports.

Session collection records (as are all NPM records), are formatted as SMF type 28 records.You can use the data from SMF or the NPM log file for generating reports with the batchreporting facility (FNMREPRT), NPM utilities, or other products such as Tivoli Decision



Support for OS/390 (formerly known as Tivoli Performance Reporter for OS/390). See theNPM Reference for specific details on the format of these records and the tools to generatethe reports.

Collecting Session Data from Session ManagersYou can collect session data from session managers, such as NetView Access Services orTPX. NPM uses the NetView synergy interface (NSI) to communicate with sessionmanagers such as NVAS, but NSI is not necessary with session managers such as TPX.

There are two types of sessions for which data is collected with a session manager:

¶ Relay session

A relay session is a session established between a terminal and an application by way ofthe session manager. It is comprised of two real sessions: one between the terminal andthe session manager, and one between the session manager and the application.

¶ Control session

A control session is a session established between an LU and the session manager. Itenables you to issue commands to the session manager to switch applications orcomplete other administrative tasks.

You have both a relay session for every application that you are accessing through a sessionmanager, and a control session with the session manager.

Data from Relay SessionsNPM provides session manager support to correlate statistics from each segment of a relaysession and then present them as data for one relay session. For example, if you areconnected to three applications through a session manager, NPM views the situation as threerelay sessions. NPM logs an LU detail record for each of the three sessions. The terminal isrecorded as the secondary logical unit (SLU) and the applications are recorded as theprimary logical unit (PLU). This SLU-PLU session through a session manager is the onlyrelay session supported by NPM.

Figure 9 on page 48 shows an LU connected through a session manager to an application inthe same host. NPM collects session data on the real sessions between the LU and thesession manager, and between the session manager and the application. NPM then reportstransit times and data volumes for the resulting relay session.



2.C

ollectin

gan

dM

on

itorin

gD

ata

Figure 9 shows how NPM collects session data for relay sessions in the same host. Thefollowing steps explain the process:

1. The LU generates an inbound PIU.

2. VTAM receives the inbound PIU from the LU. It is time stamped at A and passed tothe session manager.

3. The session manager generates an inbound PIU to the application.

4. VTAM receives the inbound PIU from the session manager. It is time stamped at B andis passed to the application.

5. The application receives the inbound PIU, processes the request, and generates anoutbound PIU.

6. VTAM receives the outbound PIU from the application. It is time stamped at C andpassed to the session manager.

7. The session manager generates an outbound PIU. VTAM receives the outbound PIU. Itis time stamped at D and passed to the LU.

8. At the same time, the session manager returns a definite response, which VTAMreceives. It is time stamped at E and passed to the application.

9. The LU receives the outbound PIU and generates a definite response.

10. VTAM receives the definite response from the LU. It is time stamped at F and passedto the session manager.

NPM gets data from two sources. VTAM sends session information to NPM, which includesthe time stamps, and the session manager sends NPM correlation data over the NSI. Usingthis data, NPM computes the transit times as:

VTAM SESSMGR

(PLU)APPL

NPM

Host A01

LU(SLU)

NSIData

OUT PIU

OUT PIU

BufferTraces

IN PIUIN PIU

DR

Figure 9. Session Collection for Session Manager Relay Session



Host transit time = D - A

Network transit time = F - D

Operator transit time = Host transit time + Network transit time

Data collection from session managers affects only those NPMs in the same host as thesession manager. When an application is accessed through a session manager in anotherdomain, the NPM in that application’s host views it as a normal session from the sessionmanager SLU to the application.

The session manager passes NPM information, giving the group and operator IDs and theaccount number for the session with the application (if the application is in the same host asthe session manager from which the pass was done). In this case, NPM records the operatorand group IDs and the account number for the session with the application.

Data from Control SessionsIn addition to one or more relay sessions, each LU has a control session with the sessionmanager. This session enables you to give commands to the session manager to switch to adifferent application or complete other administrative tasks. The performance informationrecorded for each control session reflects this information. When you use NPM’s sessionmanager support, NPM also collects transit times and data volumes for this control session.Figure 10 shows an LU in a control session with a session manager and how NPM collectssession data for control sessions in the same host.

The following steps explain the process:

1. The LU generates an inbound PIU.

2. VTAM receives the inbound PIU from the LU. It is time stamped at A and passed to thesession manager.

VTAM APPL

NPM

Host A01

LU(SLU)

BufferTraces

NSIData

DR

SESSMGR(PLU)

Figure 10. Session Collection for Session Manager Control Session



2.C

ollectin

gan

dM

on

itorin

gD

ata

3. The session manager processes the request and generates an outbound PIU.

4. VTAM receives the outbound PIU from the session manager. It is time stamped at B andpassed to the LU.

5. The LU receives the outbound PIU and generates a definite response to VTAM.

6. VTAM receives the definite response from the LU, and it is time stamped at C.

NPM again gets data from two sources. VTAM sends session information to NPM, whichincludes the time stamps, and the session manager sends NPM correlation data over the NSI.Using this data, NPM computes the transit times as:

Host transit time = B - A

Network transit time = C - B

Operator transit time = Host transit time + Network transit time

Session data collection on the control session is almost the same as session data collectionwithout session manager support; the only difference is that control session data is for thecontrol session only. It does not include any relay session data that flows over the same realsession from the LU to the session manager.

When you collect data from a session manager, NPM calculates some statistics differentlyfrom the way it does when collecting session data from VTAM.

Transit TimesAll transit times are taken at the network boundary between the operator terminal and thesession manager. This is true for control sessions, same-domain relay sessions, andcross-domain relay sessions.

The meanings of network transit time and host transit time for relay sessions are differentfrom what they are for conventional sessions. The meaning depends on whether theapplication is in the same host as the session manager or in a different one.

¶ If the application and session manager are in the same host, then the network transittime is calculated in the same way as it is normally (an estimation of the time spent inthe network, coming to and from this host). The host transit time includes all time spentin the host, including time in VTAM, time in the session manager, time flowing on thesession between the session manager and the application, and time in the application.

¶ If the application and session manager are in different hosts, and you use NetViewAccess Services, then network transit time includes only the time spent in the networkbetween the operator SLU and the host of the session manager. It excludes any timespent in the network between the session manager host and the application host. Thehost transit time includes the balance of the time spent processing the transaction,including the time in the session manager host, the time in the network between thesession manager host and application host, and the time in the application host.

¶ If the application and session manager are in different hosts, and you use TPX, thenNPM cannot collect data for the relay session. You will see only control session data.

If you want to know the time spent in the network portion between the two hosts, use theNPM in the application host. In that host, the NPM does not know that the SLU for thesession is really a session-manager SLU. In the case of NetView Access Services or TPX,the session manager gives a definite response as soon as it receives the reply from the



application host, rather than waiting until the operator SLU has given its definite response.Thus, the network transit time measured by the NPM in the application host is the networktransit time between the session manager and the application host.

Because you know the host transit time in the application host, both network transit times,and the total response time, you can derive the response time for the session manager host,and thus have all four response times. You can calculate the value of the four transit timeseither manually, by looking at NPM’s online panels, or by using the FNMREPRT batchreporting facility to generate a report.

Transit Time ThresholdsThe session transit time thresholds for a control session are the same as those in use for theunderlying terminal session. The thresholds for an extended session are the same as those forthe terminal session if collection was started for one of its LUs. If collection was not startedfor one of the terminal LUs, the thresholds are same as those for the application session.

Volume MeasurementsVolume measurements for relay sessions are based on the traffic flows through the sessionmanager and between the operator terminal and the end application. The volumemeasurement for relay sessions is taken at the network boundary between the operatorterminal and the session manager. Any data compression the session manager performs inpassing data between the operator terminal and end application is reflected in the volumemeasurement. However, any data compression performed by the end application in passingdata to the session manager is not reflected.

Volume measurements for control sessions are based on the traffic that flows between theoperator terminal and the session manager, including application switches, screen copies, andso on. The volume measurement for control sessions is taken at the network boundarybetween the operator terminal and the session manager. Any data compression the sessionmanager performs in passing data between the operator terminal and the session manager isreflected by the volume measurement.

Specifying Group IDsIn some session managers, such as NetView Access Services or TPX, the operator ID can bespecified as a member of one or more groups. In this case you must specify both theoperator ID and the group ID. NetView Access Services, TPX, and NPM regard the groupID as an extension of the operator ID, so that the two together uniquely identify theoperator.

Collecting Data with DDRThe SESSH parameter allows you to turn on the DDR when you start a session collection.

If you specify SESSH=R when you start collection for an LU in a terminal session, DDR isin effect for that session, and network transit time statistics are collected for all controlsessions and extended sessions involving that terminal session.

If you specify SESSH=R when you start collection for an LU in an application session, thereis no effect on the terminal session. If the terminal session is not running in definiteresponse mode, no network transit time statistics are collected for the control sessions or theextended sessions running on that terminal session.



2.C

ollectin

gan

dM

on

itorin

gD

ata

Supporting Multiple TerminalsNetView Access Services, TPX, and other session managers allow more than one terminal tolog on to a given group or operator ID. The session managers enable both terminals toaccess the same set of application sessions at the same time, although no two terminals canaccess the same application session at the same instant. NPM handles this kind of situationas follows:

¶ For each terminal logged on to the operator ID, NPM reports one control session, whichreflects the traffic between the particular terminal and the session manager itself.

¶ For each terminal application pair, NPM reports a relay session. This relay sessionreflects the traffic between the particular terminal and the particular application.

Supporting Cross-Domain ApplicationsSession managers can access applications in different hosts as well as the same host inwhich the session manager resides. NPM supports session collection on applications that areaccessed through NetView Access Services (NVAS) but reside in a different host from theone in which NetView Access Services and the session-collecting NPM reside.

Starting Session Collection with a Session ManagerTo collect session data from a session manager, you first need to code a SESSCOLLcommand to collect data on the session manager application. If the LU, application, node, orgroup that you specify is in a session established through a session manager, the data iscollected from the session manager. In addition, you can selectively start session collectionon terminals, same-domain applications, and cross-domain applications.

Note: Session collection for cross-domain applications is not supported for direct sessions(sessions established with VTAM).

Table 12 outlines the expected results obtained by starting session collection on variousresources.

Table 12. Collection Matrix for Session Manager UsersCollection Started On Results (NVAS/TPX)

Terminal Terminal control sessionTerminal extended sessions (any host)Terminal pass sessions (same host only)

Session manager All control sessions

Application All session manager SLU-to-application sessions (same host only)

Terminal and session manager All control sessionsTerminal extended sessions (any host)Terminal pass sessions (same host only)

Terminal and application All control sessionsAll extended sessions (any host)All pass sessions (same host only)

Session manager andapplication

Control sessionsExtended sessions (any host)Pass sessions (same host only)

You can use any of three methods for selective session collection:

¶ Starting collection on individual terminals



¶ Starting collection on the session manager and individual applications (same or differenthost)

¶ Starting collection on individual terminals and individual applications (same or differenthost)

Recording and Viewing Session Data from a Session ManagerData collected from a session manager can be recorded and viewed in the same manner assession data collected from VTAM. See “Recording and Viewing Session Data” on page 46for more information.

Collecting and Monitoring LAN DataThe term LAN data refers specifically to data that comes from a LAN manager. NPM doesnot collect LAN data directly, but sends a request through the NetView program-to-programinterface to the NetView program to collect the data. The NetView program collects the datafrom the LAN managers and sends the data through the program-to-program interface backto NPM.

When originally developed, a LAN was a stand-alone entity. One cable or set of cablesconnected all the workstations, and the communication between the workstations occurredaccording to a given protocol such as token ring or Ethernet. Today we call this stand-aloneentity a LAN segment. Two segments using the same protocol can be connected to eachother through a LAN bridge.

NPM collects and monitors performance data for both LAN bridges and LAN segments.LAN has a combined collection and monitor command. You can access LAN data from thePrimary Options menu (FNM00PRI).

Note: It is not possible for a user to override another user’s collection parameters withoutthe other user’s knowledge. A warning is provided.

Collecting LAN DataFigure 11 on page 54 shows how NPM collects LAN data. Collection of LAN bridgeperformance data occurs in the LAN bridge. Collection of LAN segment utilization dataoccurs at the segment level and it is performed by the Token-Ring Network 16/4 Adapter /Ashorty (half-sized) card, which then sends the data to the LAN station managers.

Notice that the half-sized card contains an engineering upgrade made in 1991 that supportssegment-utilization data collection. The older 16/4 Adapter/A full-sized andthree-quarter-sized cards do not support segment-utilization data collection.

There are also several other cards currently on the market which will provide this support.For example, the Token-Ring 16/4 Credit Card adapter (PCMCIA), the IBM 16/4 ISA-16Adapter (for ISA bus) card, or the LANSTREAMER card (with its LSM and NDISrequirements).

The LAN manager can request both LAN bridge and LAN segment data at any time. Youmust have LAN Network Manager to collect LAN segment data. In addition, you must havea copy of LAN Station Manager on each LAN segment. Data can be collected only on thosesegments that have LAN Station Manager installed.



2.C

ollectin

gan

dM

on

itorin

gD

ata

NPM tracks whether a collection is started, stopped, or deferred, and communicates with theLAN manager to transmit the data through the NetView program-to-program interface.

Whenever a bridge or segment is defined to more than one of the LAN managers defined toNPM, NPM chooses the optimum path for data collection, switching from one LANmanager to another, to improve the overall response time.

You can use NPM to collect performance data for LAN bridges, including local and remotebridges on token-ring, IBM PC, Ethernet, or 3174 peer networks. This data includes trafficand error statistics. NPM also collects data for the utilization of token-ring segments.

Defining LAN Managers to NPMYou define LAN managers to NPM by using the LANMGR command. The LANMGRcommand defines the LAN managers, their bridges, and segments to NPM. The LANMGRcommand instructs the LAN manager to query each of its bridges and send configurationinformation to NPM. NPM also checks, through the LANMGR command, whether it cancollect data on the segments. NPM can collect utilization data on a segment if the followingconditions are true:¶ The segment is a token-ring¶ The segment includes the Token-Ring Network 16/4 Adapter/A shorty (half-sized) card.¶ LAN Station Manager is installed.

You must issue the LANMGR command for each LAN manager before you can collect dataon that LAN Manager’s bridges and segments. You can issue the LANMGR command:¶ When you initialize NPM¶ After initialization using the NPM EXECs¶ After initialization from the system console

Host Terminal

NetView NPM

Token Ring

Token Ring

Bridge

LAN Manageror

LAN NetworkManager

ReviewFile

LANData

Alerts

NPMLog

NPM ConsoleSMF

Figure 11. LAN Data Collection

LAN Collection and Monitoring


Specifying LAN Collection IntervalsLAN data collection does not use the same base interval as network and session datacollections. Instead, you specify a LAN interval length when you install NPM, or later usingNPM’s LAN Collection Control Panel. Collection can occur every 5, 10, 15, 20, 30, or 60minutes.

Types of LAN DataThe LAN data transferred by the NetView program-to-program interface includes:¶ Bridge traffic in number of frames (broadcast and non-broadcast)¶ Lost frames¶ Segment utilization

NPM provides the total number of lost frames as well as the individual causes of loss (suchas congestion, inoperative segments, and link errors).

The LAN segment utilization data displayed on NPM’s online panels or stored in the systemfiles is actually an approximation of the real utilization of the segment. NPM uses asampling technique to collect this data, and the more samples it obtains, the more accuratethe utilization value is. However, NPM provides you, together with the utilization data, witha confidence level to indicate how confident you can be that the calculated value is theactual value.

Monitoring LAN DataIn addition to collecting LAN data, NPM can also monitor the collected data in relation tospecified thresholds.

To monitor LAN data, NPM first begins LAN data collection, if not already active, and thenmonitors a particular type of data for a selected resource. The value of the monitored data istested against thresholds specified for the data type. If the value falls outside the thresholds,NPM generates a monitor event message. You can also choose to have NPM send an alert tothe NetView program by using the NetView program-to-program interface, or write a recordto the NPM review, log, or SMF files.

NPM provides two options for LAN monitoring:

¶ Monitor exceptions

NPM generates one monitor exception message (FNM200I) per interval if the value ofthe data has fallen outside the threshold during the interval.

¶ Monitor resolution tracking

If you choose to monitor resolutions, NPM generates two kinds of messages. Itgenerates a monitor exception message (FNM200I) when the data first falls outside thethreshold. NPM generates the monitor resolution message (FNM201I) at the end of aninterval, if the data has fallen back within the thresholds.

Controlling LAN Data Collection and MonitoringYou can control collection and monitoring of LAN data by:¶ Issuing commands at NPM initialization¶ Issuing commands from the system console¶ Placing commands in NPM EXECs¶ Using online panels

All of these methods enable NPM to collect and monitor LAN data automatically on acontinuous basis or intermittently.



2.C

ollectin

gan

dM

on

itorin

gD

ata

LBRGCOLL is the command for collecting and monitoring LAN bridge data. It specifies thefollowing:¶ Whether the command affects one or more bridges or a LAN manager¶ The start and stop times for the collection¶ Whether the data should be collected daily¶ Whether to start or stop data collection¶ The high and low criteria to monitor

LSEGCOLL is the command for collecting and monitoring LAN segment data. It specifiesthe following:¶ Whether the command affects one or more segments or a LAN manager¶ The start and stop times for the collection¶ Whether the data should be collected daily¶ Whether to start or stop data collection¶ The high and low criteria to monitor data collection

By using commands or online panels, you can automate collection or monitoring byspecifying that you want the collection to start and stop every day at fixed times.

NPM also enables you to execute commands at startup. If you code the LBRGCOLL andLSEGCOLL commands to make the collection automatic, as described above, collection ormonitoring starts as soon as you initialize NPM.

Setting the appropriate parameters in the operator’s security profile gives the operatorauthorization to specify the following parameters online:

¶ The LAN bridge or the LAN segment for which data is collected

¶ Whether to start, stop, or alter data collection

¶ Whether to collect interval records and monitor messages, and where to route the data

¶ Whether to use monitor resolution

¶ The interval length in minutes

¶ The interval synchronization (the point at which data is to be collected)

The RECONFIG command enables NPM to update its list of LAN resources. NPM alsoreceives, through the RECONFIG command, detailed configuration information.

For bridges, this configuration information includes:¶ Segments¶ Bridge number¶ Limited broadcast segment number 1¶ Limited broadcast segment number 2¶ Hop count segment number 1¶ Hop count segment number 2¶ Maximum possible frame size

For segments, the configuration information includes:¶ Type¶ Status

You can issue a RECONFIG command when your LAN configuration changes.



Note: NPM automatically issues the RECONFIG command every four hours.

Recording and Viewing LAN DataWhen you start collecting or monitoring LAN data, you can specify a destination where thedata can be recorded or displayed. NPM can send data to any or all of the followingdestinations:

¶ The review file (FNMREVx data sets), where the data, including monitor eventmessages, can be analyzed using online panels

¶ The NPM log file, FNMLOGx, which can be used to generate reports with a batchprogram or other utility

¶ SMF, which can also be used to generate reports.

In addition, you can choose to send monitor event messages as alerts to the NetViewprogram.

LAN data collection records are formatted, like all NPM records, as SMF type 28 records.You can generate reports of LAN data with the batch reporting facility (FNMREPRT) orother products such as Tivoli Decision Support for OS/390 (formerly known as TivoliPerformance Reporter for OS/390). See the NPM Reference for information about thespecific format of the records and the tools available to generate the reports.

Collecting Response Time Monitor (RTM) DataYou can use NPM’s RTM function to collect performance data from 3174 and 3274 ClusterControllers or Communications Manager/2 through the NetView program. RTM datasupplements the transit time data collected from sessions. RTM measures total operatorresponse time, which is the time it takes to send a message and receive a response, includingboth network and host transit time. You can record and display the RTM data collected inthe NetView program in the same way as other NPM data.

To use RTM, you need to set up RTM data collection on the NetView program and installthe SMF exit provided with NPM. Figure 12 shows how NPM collects RTM data.



2.C

ollectin

gan

dM

on

itorin

gD

ata

The SMF exit routine intercepts RTM records from the NetView session monitor and copiesthem to NPM. The RTM record is reformatted into an NPM session record and is written tothe NPM session file. Summary records by NCP, line, PU, and application are also writtento the NPM session file.

RTM data collection provides the actual value of the response time for a transaction, withoutthe limitations and the approximations of session collection. On the other hand, sessioncollection can separate the operator transit time, corresponding logically to the RTMresponse time, into its two components (host and network transit times).

You can synchronize RTM data collection with NPM’s session data collection and then writean application to combine the collected data to take advantage of the strengths of eachcollection method.

You can access RTM from the Primary Options menu (FNM00PRI).

Types of RTM DataNPM enables you to analyze RTM data by LU detail or by session summary. The NPM’sLU detail analysis panels provide data for the interval by application, line, PU, virtual route,and transmission priority. You can see average response times and the number of transactionsfor each interval. The session summary panels provide information such as total transactionsand response times for each specific resource.

NPM

LU

PU

RTM Data

SessionFile

NetView SMF

IEFU84

IEFU83

NCP

VTAM

SMF

Figure 12. RTM Collection

RTM Data Collection


Controlling RTM Data CollectionYou can enable RTM data collection by using NPM commands at NPM initialization orfrom the system console. By setting the appropriate parameter in an operator’s securityprofile, you can also authorize levels of authority for an operator to enable and disable RTMdata collection from an NPM online panel.

Recording and Viewing RTM DataNPM can send data to any or all of the following destinations:

¶ The session file (FNMSESx data sets), where the data can be analyzed using onlinepanels

¶ The NPM log file, FNMLOGx, which can be used to generate reports with a batchprogram or other utility

¶ SMF, which can also be used to generate reports

Like all NPM records, RTM data collection records are formatted as SMF type 28 records.See the NPM Reference for the specific format of these records.

Collecting and Monitoring VTAM DataYou can use NPM’s VTAM statistics collection function to dynamically gather and viewconfiguration information about the following resources:¶ MVS jobname data¶ Buffer use¶ Central processing unit utilization¶ Channel-attached activity data¶ Common storage area use¶ Environmental data¶ Multipath channel device data¶ Storage data¶ Virtual route data

NPM provides two types of data collection intervals for collecting dynamic VTAM data:

¶ The refresh interval is the interval at which NPM displays the most recent data collectedfrom VTAM.


Attention: Small refresh and sampling intervals can adversely affect system performance.

You can set specific monitor thresholds for VTAM data collection to alert you whenexception conditions occur and when these conditions are resolved. You can use this VTAMmonitor data, along with other performance data, to provide a more complete picture of yournetwork’s performance.

VTAM Statistics Collection EnvironmentThe following list contains information about the VTAM statistics collection environment:

¶ More than one Cluster Controller, communication controller, and other hosts can beattached to the host.

RTM Data Collection


2.C

ollectin

gan

dM

on

itorin

gD

ata

¶ The number of attached hosts and communication controllers that can be attacheddepends on the host hardware limitations, VTAM’s storage availability, and the numberof subareas VTAM can handle. VTAM can currently handle 65535 subareas.

¶ Virtual routes (VRs) can be partially or completely mapped to the attached hosts orNCPs.

¶ VRs become active only when sessions are started.

¶ A maximum of 24 VRs (8 VR X 3 transmission priorities (TPs)) can be between thehost and any other destination subareas.

¶ The connection to an attached NCP or host can be activated without a system servicescontrol point-physical unit (SSCP-PU) or SSCP-SSCP session.

¶ Any application that opens an access method control block (ACB) with VTAM isconsidered an active VTAM application.

Controlling VTAM Data Collection and MonitoringYou can control collection and monitoring of VTAM data by:¶ Issuing commands at NPM initialization¶ Issuing commands from the system console¶ Placing commands in NPM EXECs¶ Using online panels

Use the following commands for collection of VTAM data:

Command Description

VADRCOLL Invokes collection of MVS jobname data in which active VTAMapplications run

VAPLCOLL Invokes collection of active VTAM application data

VAPNCOLL Invokes collection of VTAM APPN data

VBPLCOLL Invokes collection and monitoring of VTAM buffer pool data

VCSMCOLL Invokes collection and monitoring of VTAM APPN topology and directoryservices data

VDEVCOLL Invokes collection and monitoring of channel activity data

VGBLCOLL Invokes collection and monitoring of VTAM global data

VMNPCOLL Invokes collection and monitoring of VTAM MNPS application data

VRTPCOLL Invokes collection and monitoring of VTAM RTP data

VVRCOLL Invokes collection and monitoring of VR data

All of these commands, except VAPNCOLL, VCSMCOLL, VNMPCOLL, and VRTPCOLL,are available from the VTAM management option, which is accessible from the PrimaryOptions menu (FNM00PRI).

Recording and Viewing VTAM DataWhen you start collecting or monitoring VTAM data, you can specify a destination wherethe data can be recorded or displayed. NPM can send data to any or all of the followingdestinations:

VTAM Data Collection


¶ The review file (FNMREVx data sets) where you can analyze the data, includingmonitor event messages, using online panels

¶ The NPM log file (FNMLOGx), which you can use to generate reports with a batchprogram or other utility

¶ SMF, which you can also use to generate reports


VTAM data collection records are formatted, like all NPM records, as SMF type 28 records.You can generate reports of VTAM data with the batch reporting facility (FNMREPRT) orother products such as Tivoli Decision Support for OS/390 (formerly known as TivoliPerformance Reporter for OS/390). See the NPM Reference for information about thespecific format of the records and the tools available to generate the reports.

Collecting and Monitoring NetWare Resource DataYou can use NPM’s NetWare Resources Data Collection feature to dynamically gather andview performance information about the following resources in a NetWare environment:

Agent serversAre servers on which the NPM NetWare Agent is installed. The NPM NetWareAgent is a NetWare agent developed to collect performance data. The data collectedincludes:¶ Server Volume¶ Server Communications¶ Server Global¶ Router LAN Board¶ Router Global

ServersAre NetWare servers where the NPM NetWare Agent does not reside. Certain datacan still be collected about them via IPX:¶ Server Communications¶ Router LAN Board¶ Router Global

External routersIn a NetWare environment can be monitored by NPM. This data includes:¶ Server Communications¶ Router LAN board¶ Router Global

When you start a NetWare resources collection, the NPM NetWare Agent sends collectiondata to NPM on an unsolicited basis. The NPM NetWare Agent collects and forwards databy interval instead of NPM polling for NetWare data. If NPM is terminated without allactive collections being stopped or NPM abnormally ends, the NPM NetWare Agentcontinues to collect and forward data.

In this situation, NPM starts a checkpointing process by writing a record in the FNMLCOLLfile for each active NetWare collection. When NPM is started again, NPM uses theinformation in the FNMLCOLL file to attempt to restore the NetWare collections to thestatus they were in before NPM terminated.

VTAM Data Collection


2.C

ollectin

gan

dM

on

itorin

gD

ata

Controlling NetWare Resources Data Collection and MonitoringYou can control collection and monitoring of NetWare resources data by:¶ Issuing commands at NPM initialization¶ Issuing commands from the system console¶ Placing commands in NPM EXECs

At the host, you can use new NPM commands to define and collect information aboutNetWare resources or start and stop monitors:

Command Description

LWGRES Defines NetWare resources that are to be used for collection purposes.

LWGCOLL Starts and stops collections on NetWare resources defined by the LWGREScommand.

LWGSTOP Stops collections on all NetWare resources.

Recording and Viewing NetWare Resources DataWhen you start collecting or monitoring NetWare resources data, you can specify adestination where the data can be recorded or displayed. NPM can send data to any or all ofthe following destinations:

¶ The LAN work group file (FNMLWGx data sets) where you can analyze the data,including monitor event messages, using online panels

¶ The NPM log file (FNMLOGx), which you can use to generate reports with a batchprogram or other utility

¶ SMF, which you can also use to generate reports


NetWare resources data collection records are formatted, like all NPM records, as SMF type28 records. You can generate reports of NetWare resources data with the batch reportingfacility (FNMREPRT) or other products such as Tivoli Decision Support for OS/390(formerly known as Tivoli Performance Reporter for OS/390). See the NPM Reference forinformation about the specific format of the records and the tools available to generate thereports.

NetWare Resources Data Collection


Collecting Accounting Data

NPM collects and stores accounting data for your accounting or billing application from anetwork control program (NCP). You can collect data on sessions that originate or end inyour network, or on sessions that only pass through your network. This accounting datashows how much traffic each network operator generates.

NPM can collect accounting data using any of the following functions:¶ Network session accounting (NSA)¶ Network gateway accounting (NGA)¶ Session data collection¶ Dynamic network collection (DNC)

The following sections discuss network accounting (NSA and NGA), explaining how thedata is collected and transmitted and how the collection is controlled. You can use this datafor accounting purposes, because session collection provides volume statistics. See“Collecting Volume Statistics” on page 44 for additional information.

You can also use NPM to collect start-and-stop data for sessions from the VTAM sessionmanager. You can install this start-and-stop feature with DNC. This feature is brieflydescribed at the end of this chapter in “Collecting Data from the VTAM Session Manager”on page 66 and “Collecting Dynamic Network Data” on page 67. See the NCP, SSP, and EPResource Definition Guide for additional information about both session and gatewayaccounting in an NCP.

Collecting Network Session and Gateway Accounting DataNPM collects data for NSA and NGA from the NCP, as shown in Figure 13 on page 64. Thisfunction is similar to collection for network data.

3


3.C

ollectin

gA

ccou

ntin

gD

ata

For NSA, NPM collects accounting data for sessions involving low-entry networking (LEN)sessions and sessions involving boundary-attached Synchronous Data Link Control (SDLC),physical unit (PU) type 2.1, and NCP/Token-Ring Interconnect (NTRI) resources. NPM alsocollects accounting data for X.25 NCP Packet Switching Interface (NPSI) and networkextension option (NEO) resources.

For NGA, NPM collects accounting data for sessions that cross gateway NCPs. NGAprovides intermediate networks with accounting data on sessions when neither session endpoint resides in the intermediate network, or when only one of the session end points residesin the intermediate network.

The NCP transmits accounting data to NPM as a result of four different events:

¶ When a session starts

¶ When a session ends

¶ When the path information unit (PIU) or byte thresholds are exceeded

¶ When you use NPM’s panels or commands to solicit (request) the current networkaccounting data that the NCP is holding

The PIU and byte thresholds cause the NCP to send NPM network accounting data for eachsession when the number of PIUs or bytes exceeds the threshold. For example, if you set aPIU threshold of 10,000, the NCP sends network accounting data to NPM when more than10,000 PIUs cross each session. The threshold is compared with separate counters for sendand receive. The PIU and byte counters in the NCP are reset to zero after the data is sent toNPM.

Backup NPALUs and NPALU TakeoversNCP provides for backup network performance analysis logical units (NPALUs) and NPALUtakeovers to assure that network accounting data is even if a session between NPM and anNPALU is lost.

PU

LU

Data

VTAM NPM

NCP

Token Ring

NPALU

NPMLog

SMF

NSA and NGAAccounting Data

Figure 13. Network Accounting Data Collection



You can define one primary NPALU and up to seven backup NPALUs in the NCPgeneration. The first NPALU listed in the NCP generation is considered to be the primaryNPALU. You can use the primary NPALU for network collection and network accountingdata collection. You can use the backup NPALUs only for network accounting datacollection. A backup NPALU, if defined, takes over automatically when the NPM sessioncurrently receiving accounting data becomes unavailable.

Several NPALUs of one NCP can be in session with one or more NPMs. In this case, NSAdata flows over the first NPALU in the list that is in session with an NPM to which thisNCP was defined as a source of NSA data. NGA data flows over the first NPALU in the listthat is in session with an NPM to which this NCP was defined as a source of NGA data.When one NPM issues an NSA or NGA command to an NCP, the same command should beissued by all other NPMs that can collect accounting data from the NCP. Otherwise, attakeover, the accounting parameters are reset to the default values established when the NCPwas generated.

If the NPM-to-NPALU session that is transmitting accounting data becomes inactive, NCPstarts transmitting over a backup NPALU session. NCP scans the list of NPALUs for thehighest-ranked NPALU in session with any NPM. The NPM that is in session with thechosen NPALU then exchanges accounting parameters with the NCP. If the parameters donot match NPM’s definitions, NPM sets the accounting parameters as they are currentlyknown to NCP. Accounting data then starts to flow over this session. This situation is calledtakeover, and it assures that network accounting data is not lost if a session between NPMand an NPALU is lost. If a backup NPALU is not available, NCP does not transmitaccounting data until a backup NPALU becomes available.

If accounting data is flowing over a session between an NPM and an NPALU, and theprimary NPALU or a higher-ranked NPALU (defined to transmit the accounting data) isestablished, then the accounting data flow is switched to the reestablished, higher-rankedsession.

Controlling Network Accounting Data CollectionYou can control the transmission of accounting data from NCP and you can start and stopcollecting network accounting data, using the following commands:

ENABLE Allows NCP to send network accounting data to NPM. It does not actuallystart network accounting data collection in the NCP. It restarts the flow ofaccounting data to NPM after a DISABLE was requested.

DISABLE Prevents the NCP from sending network accounting data to NPM. It doesnot stop network accounting data collection in the NCP.

SOLICIT Instructs an NCP to immediately send all network accounting data to NPM.You can use the SOLICIT command to prevent the loss of networkaccounting data. Use the SOLICIT command before you deactivate an NCPto retrieve the network accounting data that has been collected but not yetsent to NPM.

When you issue a SOLICIT command, all of the data counters in the NCPare reset to zero. If you issue a SOLICIT command for an NCP that hasaccounting data transmission disabled, NPM enables accounting datatransmission for that NCP. The NCP sends the data to NPM. If no sessionshad data collected by the NCP, no accounting data is sent to NPM.



3.C

ollectin

gA

ccou

ntin

gD

ata

MODIFY Changes the PIU and byte thresholds and starts and stops networkaccounting data collection in the NCP.

These same commands are available as parameters on the NPM NGACNTL, NSACNTL,NGAMDFY, NSAMDFY, and NSASOLCT commands. You can give an operatorauthorization to use these commands by setting the appropriate parameter in the operator’ssecurity profile.

You can access accounting options from the Control Functions menu (FNM010MN), whichis available from the Primary Options menu (FNM00PRI).

You can start collecting network accounting data at NCP activation, at NPM activation, andat specific times using commands or NPM’s online panels.

Starting Collection at NCP ActivationYou can define the NCP so that it starts collecting network accounting data as soon as it isactivated. The NCP does not need to communicate with NPM to collect the data. Thenetwork accounting data is held in the NCP until the data can be sent to NPM. If there is along delay between the start of network accounting data collection and the transmission ofthe data to NPM, the NCP can run out of buffer space and enter slowdown.

Starting Collection at NPM ActivationYou can define the NCP to start collecting network accounting data as soon as NPM isactivated. In this case, you must also define NPM to issue an NGAMDFY or NSAMDFYcommand at initialization or from NPM’s online panels. Accounting collection starts whenthe NCP receives the NGAMDFY or NSAMDFY command. Accounting data is collectedonly on sessions that start after the NCP receives the NGAMDFY or NSAMDFY command.

Starting Collection at Specific TimesYou can define the NCP so that it starts collecting network accounting data at the request ofthe NPM operator, or during times specified by a clock value on the NGAMDFY orNSAMDFY commands. Accounting collection starts when the NCP receives the NGAMDFYor NSAMDFY command and only on sessions that start after the NCP receives one or bothof these commands.

Collecting Data from the VTAM Session ManagerYou can use the VTAM session manager to write a record each time a session starts orstops. The session start-and-stop data is collected by VTAM and can be written to thesystem management facilities (SMF) or to the NPM log (FNMLOGx).

To do this, allocate the FNMLOGx data sets (if you want to record data there) and installthe appropriate VTAM session manager exit provided with NPM. When you install the exit,you also select the data set to which records are written. Once the exit is installed, thesession stop and start records are automatically written to the data set. There are no NPMstatements or commands to enter.



Collecting Dynamic Network DataThe DNC function collects accounting data for sessions with at least one LU owned by theVTAM under which NPM is running. DNC enables accounting data collection from binarysynchronous devices.

To use DNC, install the appropriate VTAM session manager exit provided with NPM.

Collecting Accounting Data from NetView Access ServicesNPM can also collect accounting information directly from applications that can provideaccounting information.

This support enables the collection of group ID, operator ID, and account numbers directlyfrom these applications. NPM logs this information as provided by the subsystem. However,if NPM receives conflicting information from a session manager and an application (forexample, if the application is accessed through a session manager), the information from thesession manager is used.

This support also causes NPM to use the Time Sharing Option (TSO) job name as theoperator ID if no other accounting information is available (either from a session manager orfrom the application).

Recording and Viewing Accounting DataThe data for NSA, NGA, VTAM session manager, and DNC is logged to the NPM or SMFlog after it is received by NPM. It cannot be displayed using NPM’s online panels, but youcan run an accounting application after the data is collected and logged to generate reports.NSA, NGA, VTAM session manager, and DNC records, like all NPM records, are formattedas SMF type 28 records. See the NetView Performance Monitor Reference for specificdetails on the format of the records.



3.C

ollectin

gA

ccou

ntin

gD

ata


Tuning and Expanding the Network

Using the data collection and monitoring capabilities of NPM, you can gather theinformation that you need to tune your network and plan for its growth.

The problem determination scenarios provided in “Isolating Performance Problems in aNetwork” on page 95, describe some examples of possible actions you can take to improvenetwork performance after you have used NPM to isolate the source of a problem in thenetwork.

This section is focused on the ability that NPM gives you to examine trends in theperformance of your network resources. The analysis of trends in the utilization of a line, forexample, can help you decide to switch to a different type of line or add another line to yournetwork to decrease the traffic load on an existing line.

NPM stores the data that it collects into different BSAM, VSAM, and SMF files. You canuse tools such as the ones listed below to generate reports from the stored data:¶ Batch reporting program provided with NPM¶ Specific products, for example, Tivoli Decision Support for OS/390 (formerly known as

Tivoli Performance Reporter for OS/390)¶ Your own report generators

NPM provides the FNMREPRT batch reporting facility to help you create and print reportsfrom the data collected by NPM. FNMREPRT runs as a stand-alone batch program with nointerfaces or dependencies on NPM. The program processes records written to the NPM logor to SMF.

With FNMREPRT, you can select the type of report you need from sample reportdefinitions. For each type of report, you can choose the data to include by selectingresources and specifying criteria to filter the data to be included in the reports, and then usethe reports to tune your network. See the NPM Reference for specific details on usingFNMREPRT.

Creating Reports with the FNMREPRT ProgramNPM’s FNMREPRT reporting program provides sample report definitions that you can useto display the following types of information:¶ Network detail data for lines, LUs, and PUs¶ Session LU summary and LU volume detail data¶ Session LU operator transit times distribution data¶ Session application summary data¶ Session application volume detail data¶ Session application operator and host transit times distribution data

4


4.Tu

nin

gan

dE

xpan

din

gth

eN

etwo

rk

¶ LAN bridge and LAN segment data¶ Frame relay DTE logical and physical link detail data¶ Frame relay DCE LMI and physical station detail data¶ X.25 link, PU, and VC detail data¶ NTRI logical and physical link detail data¶ Ethernet detail data¶ ODLC LAN link and PU detail data¶ VTAM jobname data¶ VTAM application summary data¶ VTAM buffer pool start options and I/O use data¶ VTAM channel activity for NCP and local devices and CTC device data¶ VTAM CTC channel program trigger data¶ VTAM adapter channel data¶ VTAM SIO and device count data¶ VTAM CSA data¶ VTAM CPU, page I/O, and storage use data¶ VTAM virtual route data¶ NetWare server connection data¶ NetWare IPX communication data¶ NetWare LAN board data¶ NetWare router data¶ NetWare SPX communications data¶ NetWare SPX connections data¶ NetWare volume data¶ Router interface traffic data¶ Cisco router memory pool usage data¶ Cisco router CPU usage data¶ Cisco CIP CPU usage data¶ Cisco CIP memory and DMA usage data

You can select the type of report that you want and specify the resource for which you wantthe report and the criteria to determine whether FNMREPRT accepts or rejects input recordsfor the report. For instance, you might generate a report that provides data for all the lines inyour network that have been busy for more than ten percent of the time in the last twomonths.

Examining the Reports for Tuning the NetworkThis section describes the reports that you can generate using the FNMREPRT batchreporting facility.

Report Name Purpose

FNM25LK Network X.25 Link Details

You can use this report to find high volume and high congestion links.

FNM25PU Network X.25 PU Details

You can use this report to find high volume and high congestion PUs.

FNM25VC Network X.25 VC Details

You can use this report to find high volume VCs.

FNM25VCH Network X.25 VC HPR Details



This report details the HPR traffic flowing on an X.25 VC

FNM3746A Line Processor Utilization

This report details processor utilization, fast program storage utilization, andbuffer storage utilization for the line processors corresponding to the lineswith addresses 2080–2431.

FNM3746B Line Processor Utilization


FNM3746C Line Processor Utilization


FNM46CCU Line Processor Utilization

This report details processor utilization for each of the 3746 Model 900 lineprocessors.

FNMAPSUM Session Application Summary

You can use this report to find applications that frequently exceed responsetime thresholds.

FNMAPTD Session Application Times Distribution

You can use this report to find applications that frequently exceed responsetime thresholds.

FNMAPVOL Session Application Volume Details

You can use this report for accounting by application and for findinghigh-traffic applications.

FNMETHP Network Ethernet Physical Link Details

You can use this report to find Ethernet physical links with high trafficvolumes and high numbers of collisions.

FNMFRHPR HPR Data for Frame Relay Logical Link Details

This report details HPR data for each frame relay logical link.

FNMFRIP IP Data for Frame Relay Logical Link Details

This report details IP data for each frame relay physical link.

FNMFRLMI Network Frame Relay LMI PU Details

You can use this report to find local management interface (LMI) physicalunits (PUs) with high traffic volumes and high numbers of frames discardedbecause of network congestion.

FNMFRLYL Network Frame Relay Logical Link Details

You can use this report to find logical links with high traffic volumes orhigh numbers of retransmissions.

FNMFRLYP Network Frame Relay Physical Link Details



4.Tu

nin

gan

dE

xpan

din

gth

eN

etwo

rk

You can use this report to find physical links with high traffic volumes andhigh congestion counts.

FNMFRLYS Network Frame Relay Physical Station Details

You can use this report to find physical stations with high traffic volumesand high congestion counts.

FNMLANBR LAN Bridge Details

You can use this report to find bridges with high traffic volumes and highnumbers of lost frames.

FNMLANSG LAN Segment Details

You can use this report to find overutilized or underutilized segments in yournetwork.

FNMLNLK Network ODLC LAN Physical Link Details

You can use this report to find physical links with high traffic volumes andhigh error counts.

FNMLNLKH HPR Data for ODLC LAN Physical Link Details

This report details HPR performance data for ODLC LAN physical links.

FNMLNPU Network ODLC LAN Station PU Details

You can use this report to find LAN station PUs with high traffic volumesand high error counts.

FNMLNPUH HPR Data for ODLC LAN Station PU Details

This report details HPR performance data for ODLC LAN station PUs.

FNMLUGRP Summarized Session Data for LU Group Details

This report details summarized session data for each LU group defined usingthe LUGROUP command.

FNMLUOTD Session LU Operator Times Distribution

You can use this report to find logical units (LUs) that frequently exceedoperator response time thresholds.

FNMLUSUM Report Definition for Session LU Summary

You can use this report to find LUs that frequently exceed response timethresholds.

FNMLUVOL Report Definition for Session LU Volume Details

You can use this report for accounting by LU and for finding high-trafficLUs.

FNMLNDAT Network NTRI Physical Link Details

This report details SNA, IP, and frame relay data for each NTRI physicallink.

FNMNITOC Router Interface Traffic Usage Data

You can use this report to detail interface traffic data for each SNMP routerfor which you collected data.



FNMNCIPC Cisco Router CIP Card CPU Usage

This report details CPU usage data for each CIP card installed on the Ciscorouters for which you collected data.

FNMNCIPM Cisco Router CIP Card Memory and DMA Usage

This report details memory and DMA usage data for each CIP card installedon the Cisco routers for which you collected data.

FNMNRPPU Cisco Router Memory Pool Usage Data

This report details memory pool usage data for each Cisco router for whichyou collected data.

FNMNRTCC Cisco Router CPU Usage Data

This report displays CPU usage data for each Cisco router for which youcolected data.

FNMNTHPL Network NTRI Physical Link Details

This report details HPR data for each NTRI physical link.

FNMNTRIL Network NTRI Logical Link Details

You can use this report to find logical links with high traffic volumes orhigh numbers of retransmissions.

FNMNTRIP Network NTRI Physical Link Details

You can use this report to find physical links with high traffic volumes, highcongestion counts, or high TIC utilization.

FNMNWCCUDefinition for Network CCU Details

You can use this report to find communication control units (CCUs) withhigh utilization or with buffer use approaching the available limits.

FNMNWCN NetWare Server Connection

You can use this report to display the connection activity for servers in aNetWare environment.

FNMNWHPRSDLC Link Station HPR Data Details

This report details HPR data flowing through SDLC link stations. Total datavolumes and HPR data volumes are displayed together for comparison.

FNMNWIP NetWare IPX Communication

You can use this report to display the activity related to the IPXcommunications.

FNMNWLB NetWare LAN Board

You can use this report to display the LAN board activities in a NetWareenvironment.

FNMNWLN Network Line Details–Totals

You can use this report to find lines with high traffic and error volumes andhigh numbers of retransmissions.



4.Tu

nin

gan

dE

xpan

din

gth

eN

etwo

rk

FNMNWLNRNetwork Line Details–Totals/Second

You can use this report to find lines with high traffic, error, andretransmission rates.

FNMNWLTP Transmission Priority Data Details

This report details transmission priority data for lines.

FNMNWLU Network LU Details

You can use this report to find LUs with high traffic volumes or rates.

FNMNWPTP Network PU Transmission Priority Data Details

This report details transmission priority data for PUs.

FNMNWPU Network PU Details

You can use this report to find PUs with high traffic volumes or rates, highnumbers or rates of retransmissions, or high error volumes.

FNMNWRT NetWare Router

You can use this report to display the router activity in a NetWareenvironment.

FNMNWSC NetWare SPX Communications

You can use this report to display SPX communication activity in a NetWareenvironment.

FNMNWSP NetWare SPX Connections

You can use this report to display SPX connections activity in a NetWareenvironment.

FNMNWSV NetWare Volume

You can use this report to display data for NetWare volumes.

FNMPMTB Private Buffer Usage Details

This report displays NPM’s private buffer usage, including the currentpercentage of buffers used and the lowest percentage of buffers that wereavailable for that interval.

FNMPMTF NPM’s File Usage Details

This report displays statistics concerning NPM’s file usage, including thenumber of records written or lost for each file type and the number ofrecords written or lost based on record types.

FNMPMTM NPM’s Virtual Memory Usage Details

This report displays NPM’s virtual memory usage, including information onboth private and CSA allocations.

FNMPMTR NPM’s Record Usage Details

This report displays NPM’s record usage, including the number of recordswritten or lost based on record types.

FNMPMTS NPM’s Virtual Memory Usage Details



This report displays information about NPM’s virtual memory usage,including the number of RTM records, DNC records, buffer trace requests,and request failures.

FNMVAPDS VTAM APPN Directory Services Data Details

This report displays VTAM APPN directory services data.

FNMVAPSM VTAM Application Summary Data

You can use this report to see session related information about eachapplication defined to VTAM.

FNMVAPTP VTAM APPN Topology Data Details

You can use this report to display VTAM APPN topology data from aVTAM point of view.

FNMVASSM VTAM MVS Jobname Summary Data

You can use this report to display MVS jobname data.

FNMVBPDA VTAM Buffer Pool Data

You can use this report to display buffer pool data.

FNMVBPIO VTAM Buffer Pool IO Usage Data

You can use this report to display VTAM input/output (I/O) buffer use bytraffic count.

FNMVBPSO VTAM Buffer Pool Start Options Data

You can use this report to display buffer pool start options and the numberthat VTAM uses to contract the buffer pool when there are an excessivenumber of buffers.

FNMVCSBE VTAM CSM Buffer Pool in ECSA Storage Data

You can use this report to display information about CSM buffer pool usage(available, in use) in ECSA storage.

FNMVCSBS VTAM CSM Buffer Pool in Data Space Data

You can use this report to display information about CSM buffer pool usage(available, in use) in Data Space storage.

FNMVCSSU VTAM CSM Storage Usage Data

You can use this report to display information about the total usage of DataSpace and ECSA storage.

FNMVCTC VTAM CTC Channel Program Trigger Data

You can use this report to display channel program start data for any CTCattached to VTAM and to find the start reasons for channel programs issuedby the host.

FNMVDBSC VTAM CTC Adapter Channel Data

You can use this report to display adapter buffer data for CTC devicesattached to VTAM and to find channels that frequently exceed the slowdowntime.

FNMVDCOT VTAM NCP and Local Device Coattailing Data Details



4.Tu

nin

gan

dE

xpan

din

gth

eN

etwo

rk

This report displays coattailing data for channel-attached NCP and localSNA devices.

FNMVDCTC VTAM CTC Device (Channel Activity) Data

You can use this report to display channel activity data for CTC devicesattached to VTAM and to find channels that frequently exceed the slowdowntime.

FNMVDDAT VTAM NCP and Local Device (Channel Activity) Data

You can use this report to display channel activity data for channel-attachedNCP and local SNA devices and to find channels that frequently exceed theslowdown time.

FNMVGBL VTAM CPU, Page IN/OUT and Storage Usage Data

You can use this report to display VTAM global data.

FNMVGCSA VTAM and System CSA Data

You can use this report to display common service area (CSA) data.

FNMVGSIO VTAM SIO and Device Count

You can use this report to display start input/output (I/Os) and the devicecount.

FNMVMNPA VTAM MNPS Application Data

You can use this report to display information about the running MNPSapplications and MNPS application recovery.

FNMVMPCD VTAM MPC Device Data Details

This report displays channel activity data for any MPC device attached toVTAM.

FNMVMPCGVTAM MPC Group Statistics Details

This report displays statistical data for any MPC group attached to VTAM.

FNMVRTPA VTAM Rapid Transport Protocol

You can use this report to display information about RTP resources, such astheir status, the number of path switches that occurred for an RTP, and thenumber of bytes sent and received.

FNMVVR VTAM Virtual Route Data

You can use this report to display virtual route data for any virtual route thatends in the host collecting the virtual route data.



Part II. Planning for InstallationChapter 5. Managing NPM Support Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Functions that Require Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Installation-Wide Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Functions that Do Not Require Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Dynamic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Report Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80File Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Chapter 6. Working with NPM Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Working with Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Allocating NPM Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Review, Session, and LAN Work Group Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82NPM User Profile Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 7. Managing NPM Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Logon Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Minimal Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Normal Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84RACF Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84User-Defined Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Functional Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Console Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Defining Security for NPM-to-NPM Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Sending Console Commands to a Remote NPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Using Remote Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Using RACF with NPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Protecting NPM Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Controlling Access to NPM from Specific Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Controlling Access to NPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86



Managing NPM Support Functions

In addition to the basic functions that NPM performs (as described in Part I, “NPMFunctions and Features”), NPM provides a variety of additional functions that support datacollection. The functions are described in two categories:¶ Functions that require installation¶ Functions that do not require installation

Functions that Require InstallationThis section describes the installation-wide exits support function. This function requires thatyou code specific statements at NPM installation.

Installation-Wide ExitsYou can change or extend the way NPM works by using NPM’s installation-wide and PIUanalysis exits. These exits enable your code to receive control during NPM processing. Bycoding different exit functions, you can change the way NPM processes data to address thespecific needs of your installation. The NPM installation-wide exit is a general purpose exitthat you can use to perform special processing of NPM data. The PIU analysis exit is usedby NPM’s session collection function to determine the type of PIUs that are flowing throughthe network.

The NPM installation-wide exit and PIU analysis exit are optional. You only code them ifyou need the functions that they provide.

NPM Installation-Wide ExitThe NPM installation-wide exit enables your customized code to receive control whenevercertain events occur, for example, when a session starts or a message is generated.

You can use the NPM installation-wide exit for any of the following functions:¶ Preventing specific records from being written¶ Automating the archiving and resetting of full data sets¶ Providing additional security by validating operator logon requests

Or, you can create code for any customized processing you need.

The NPM installation-wide exit enables your code to receive control during any of thefollowing events that occur during NPM operation:

¶ Start and stop of NPM

¶ Logon and logoff of NPM operators

¶ Connect and disconnect of NPALUs

¶ Dynamic network collection (DNC) authorization

5


5.M

anag

ing

NP

MS

up

po

rtF

un

ction

s

¶ NPM message processing

¶ The writing of records to output data sets

NPM includes a sample installation-wide exit, FNMUEXIT, that you can modify to meetyour needs.

PIU Analysis ExitNPM uses the PIU analysis exit to determine the types of PIUs flowing through the networkfor session data collection. You can change the way NPM calculates transit times by writingyour own PIU analysis exit.

NPM allows you to specify a different PIU analysis exit for each application when youcollect session data by application. This is useful if an application requires special transittime calculations because it does not send the type of PIUs that NPM expects.

Functions that Do Not Require InstallationNPM provides other support functions that do not require installation. These functions donot require you to code any statements at the NPM installation phase, but, because of theirimpact on NPM performance and use, you must decide whether to include these functionsduring the planning phase. The following sections briefly describe these functions.

Dynamic ConfigurationNPM’s dynamic configuration support enables NPM to update network configurationinformation while NPM is running. Dynamic configuration provides the ability to redefinean NCP to NPM without taking NPM down. This eliminates the need to generate a resourceresolution table and restart NPM to update network configuration information.

Report GenerationNPM offers several ways to produce reports from collected data. You can use theFNMREPRT reporting program or you can use other programs such as Tivoli DecisionSupport for OS/390 (formerly known as Tivoli Performance Reporter for OS/390) or yourown application. See the NPM Reference for additional information about report generation.

File ManagementThe session data collected by NPM is useful for historical analysis as well as for immediateproblem solving. NPM provides archiving and rebuilding programs to archive the collecteddata for later analysis. Archiving and rebuilding session files enable you to tailor sessionfiles for modeling, capacity planning, or trend analysis, or for resolving problems ofconfiguration changes.

To archive session files, define more than one session (FNMSESx) file. When the currentsession file becomes full, NPM automatically switches to the next session file defined. Youcan then archive the full session file to the NPM archived file, using standard facilities ofVSAM access method services (AMS). The sample FNMARCHV in MVS helps youmanage your data sets. An NPM operator can also archive files that are not full, by forcingNPM to switch to the next file.

NPM Support Functions


Working with NPM Data Sets

When installing NPM, you update statements both in sample data sets and in data sets youcreate. The data set names used in this book are condensed from longer names that varydepending on the operating system you are using.

For example, FNMINIT is the FNMINIT member of the FNMPARM partitioned data set.You can find a sample for the FNMINIT member in the partitioned data setNPM.V2R7M0.SFNMJCL1, provided with NPM.

Working with SamplesTable 13 gives the locations of the partitioned data sets and members of partitioned data setsthat you will use most often. For each member, the table provides the following information:

¶ The name of the member

¶ The data definition (DD) statement, in the NPM startup job control language (JCL), thatpoints to the partitioned data set containing the member

¶ The name of the data set provided with NPM where you can find a sample for themember

For a complete list of samples and their contents, see NPM Installation and Customization.

Table 13. NPM data sets in MVSMember Name DD Statement Sample Name

FNMINIT FNMPARM NPM.V2R7M0.SFNMJCL1(FNMINIT)

FNMOPER FNMPARM NPM.V2R7M0.SFNMJCL1(FNMOPER)

FNMPROF FNMPARM NPM.V2R7M0.SFNMJCL1(FNMPROF)

FNMSTRT FNMPARM NPM.V2R7M0.SFNMJCL1(FNMSTRT)

FNMLUGRP FNMSCMDS NPM.V2R7M0.SFNMJCL1(FNMLUGRP)

FNMEXEC FNMSCMDS NPM.V2R7M0.SFNMJCL1(FNMEXEC)

FNMSMF FNMSCMDS NPM.V2R7M0.SFNMJCL1(FNMSMF)

The NPM startup JCL contains pointers to these samples. If you change the names of anysamples, you must modify the startup JCL as well.

Note: Sample startup JCL is provided in NPM.V2R7M0.SFNMJCL1(FNMSNPM).

Allocating NPM Data SetsYou need to allocate data sets or files that allow NPM to store the data you collect and theprofiles NPM uses. The following sections describe the data sets to allocate.

6


6.W

orkin

gw

ithN

PM

Data

Sets

Review, Session, and LAN Work Group Data SetsReview, session, and LAN work group data sets are Virtual Storage Access Method (VSAM)key-sequenced data sets (KSDS). These data sets must be defined with the VSAM AccessMethod Services (AMS) command DEFINE CLUSTER.

You can allocate up to 39 review data sets and 39 session data sets. The sample codesupplied with NPM allocates two of each. VSAM data sets are not unique data sets. WhenVSAM data sets are defined in a VSAM catalog, they are defined as reusable.

Use the Access Method Services DEFINE SPACE command to ensure that there is enoughdata space in the VSAM catalogs for the VSAM clusters. Allow enough space for theanticipated maximum number of measurements in the period for which the file is to bemaintained.

The allocation of the VSAM data sets for review and session data can have a major effecton NPM performance. See the NPM Installation and Customization for information abouttuning VSAM data sets.

NPM User Profile Data SetsWhen you log off, NPM saves the following NPM operator values or parameters for you:¶ Default scroll value¶ Date format¶ Time conversion¶ The NPM option¶ PF key set option¶ PF key format option¶ PF key values¶ National language for panels and messages

Note: The NPM option allows you to save the values entered in the fields of each panel soyou can retrieve these values when you reuse the panel.

These variables are collectively known as the user profile.

FNMPROFS is a partitioned data set. There is a member corresponding to the operator IDfor each NPM operator in the data set. FNMPROFS is optional.

When an operator logs on to NPM for the first time, NPM issues the following message:FNM097W operatorID NOT FOUND IN FILE FNMPROFS

NPM then creates a new member in the FNMPROFS data set for the new operator andsaves the user profile information when the operator logs off. The next time the operatorlogs on, the user profile is read from the FNMPROFS data set and the profile is set to thesaved values.

The user profile is not the same as the security profile, which is stored in the FNMPROFmember of the FNMPARM partitioned data set.

Working with NPM Data Sets


Managing NPM Security

NPM provides the means to control access to NPM facilities. This section provides anoverview of NPM security management and the security procedures that are performed whenan operator logs on. It also includes the following security information:¶ Functional security¶ Console security¶ NPM-to-NPM communications security¶ Special protection with Resource Access Control Facility (RACF®)

You manage NPM security at two levels:¶ Global¶ Operator

Global parameters for NPM security determine the types of checks performed by NPM whenan operator attempts to log on to NPM.

At the operator level, you define operator IDs and a set of security profiles for each operatorwho uses NPM, including operators who use NPM-to-NPM communication from remoteNPMs.

Each security profile defines a level of access to NPM functions. Each operator is definedwith one to eight profiles, although only one profile can be used per session. If an operatorwants to use a different profile, the operator must log off and then log on again to NPM,specifying the name of the new profile.

Logon ProcessingWhen an operator logs on to NPM, NPM verifies the logon according to the type of securityprocessing that you have defined. NPM then determines the profile to use for the operator. Ifthe operator does not enter a profile name when logging on, NPM uses the first profiledefined to the operator. If the operator specifies a profile name, NPM checks the list ofprofiles defined for the operator and verifies that the profile is correct. If the operator is notauthorized for the specified profile name, NPM rejects the logon attempt.

You can choose one of four different types of security processing:¶ Minimal¶ Normal¶ RACF¶ User-defined

The following sections explain the logon processing performed by NPM for each of thesesecurity types.

7


7.M

anag

ing

NP

MS

ecurity

Minimal SecurityOperators must enter both an operator ID and a password to log on. NPM verifies that theID is defined, but does not check the password.

Normal SecurityOperators must enter both an operator ID and a password.

If you change an operator’s password while NPM is running, the operator must use theupdated password on the next logon attempt. You do not need to restart NPM to changepasswords.

You do need to restart NPM if additional operator IDs are added. Operators who have beenadded can log on after the addition using their new IDs and passwords.

RACF SecurityRACF is a product that provides access control by:¶ Identifying and verifying the users to the system¶ Authorizing access to protected resources¶ Logging the detected unauthorized attempts to enter the system¶ Logging the detected accesses to protected resources

With RACF security, NPM does not perform the security check. The password check is doneby using the RACF service, RACROUTE. In addition to passing the operator ID andpassword to RACF, NPM also passes the terminal identifier and the NPM application name.The operator ID must be defined to RACF, and the password must agree with the passworddefined to RACF.

If the operator specifies a new password, it is automatically passed to RACF. After RACFaccepts the operator ID and password, the new password is in effect for the next logonattempt.

When the NPM operator ID is the same as the Time Sharing Option (TSO) operator ID,both NPM and TSO require the same RACF password. If a new password for RACF is usedand accepted by RACF, the new password is effective for all applications using the RACFoperator ID. You can also use RACF security to protect data sets from unauthorized access.See “Using RACF with NPM” on page 85.

Note: NPM provides logon control using RACF with OS/390 or the System AuthorizationFacility (SAF) feature. Because NPM uses the SAF interface, you can use any othersecurity product that conforms to the SAF interface rather than RACF, but alwaysspecify that you want NPM to perform RACF security, regardless of the product thatyou are using.

User-Defined SecurityYou can perform your own security check through the NPM installation-wide exit. Withuser-defined security, NPM calls the operator-connect function of the NPM installation-wideexit to verify the operator ID, password, and security profile name of the operator.

NPM Security


Functional SecurityNPM checks each request an operator makes to ensure that the operator is allowed toperform the requested function. The profile the operator specifies at logon lists whichfunctions are allowed. If operators attempt to perform a function not allowed by theirprofiles, NPM rejects the request and issues a specific message.

Console SecurityYou can specify the operator ID and profile of the system console, through the CONSOLEstatement. NPM accepts only the commands permitted by the profile.

You can add an additional level of security for console commands. Because an operator mustlog on to the system console in this version, you can specify that the operator’s profile,rather than the profile defined to the console, controls the commands that can be issued fromthe console. In this way, you can give operators different types of system consoleauthorization by coding several different profiles.

Defining Security for NPM-to-NPM CommunicationWhen an NPM operator makes requests from another NPM, the security level checks aredefined in the remote NPM.

First, the remote NPM checks that the operator ID is defined. If it is not, the request isrejected. If the operator ID is defined and if the security is minimal in the remote NPM, nofurther checking is done and the request is accepted. Otherwise, the remote NPM performsthe following checks:

¶ If a remote profile was specified for the operator, it is used to check the request.Otherwise, the operator must provide a profile name when sending the request.

¶ The profile name must be defined in the remote NPM and specified for the operator IDin the remote NPM.

¶ The profile must allow the operator to process the request.

If any of these checks fails, NPM sends an appropriate error message to the operator andrejects the request.

Sending Console Commands to a Remote NPMAn operator can send console commands to a remote NPM, but the commands are subject toNPM security at the remote NPM.

Using Remote ProfilesYou can reduce the number of profiles required by your system and also control the accessof remote operators to NPM functions by using remote profiles. You can also create one setof operator and profile definitions to be used by all NPMs in a complex environment andstill maintain control of all NPM-to-NPM communication.

Using RACF with NPMWith RACF, you can protect specific NPM data sets from unauthorized access or the entiresystem from unauthorized users. The following sections explain the optional uses of RACFwith NPM.

NPM Security


7.M

anag

ing

NP

MS

ecurity

Protecting NPM Data SetsYou can protect your NPM data sets from unauthorized access by using RACF. For example,if you are working with normal security, you should protect the NPM data set that containsNPM operator IDs and passwords.

Controlling Access to NPM from Specific TerminalsDuring logon processing, NPM always supplies the terminal identifier to RACF. TheRACROUTE service that NPM uses to verify the operator ID and password can also verifyuser access to the terminal. The return code supplied by RACF indicates whether access tothe terminal is allowed.

Controlling Access to NPMTo prevent any RACF-defined user from logging on to NPM, NPM passes an applicationidentifier to RACF during the logon procedure. RACROUTE checks the access list for theNPM application and grants or denies access accordingly. The Resource Access ControlFacility (RACF) Security Administrator’s Guide contains specific information forimplementing RACF security.

NPM Security


Part III. Planning for MigrationChapter 8. Migrating to NPM Version 2 Release 7 . . . . . . . . . . . . . . . . . . . . . . . . 89Modified VSAM Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Updating FNMINIT for NPM Version 2 Release 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Automatic Discovery Using RODM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Automatic Discovery Using RODM with a Mask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Updating FNMSTRT and Other NPM EXECS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Updating the User Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91


||||


Migrating to NPM Version 2 Release 7

This chapter provides you with the information about migrating to NPM Version 2 from aprevious release of NPM.

In this chapter, you can find information about:¶ Modified VSAM records¶ Updating FNMINIT for NPM Version 2 Release 7¶ Updating FNMSTRT and other NPM EXECs¶ Updating the user profile

Use the information in this chapter in conjunction with the migration information in theNPM Installation and Customization to plan for your migration. Also see the NPM ProgramDirectory for a list of the software and hardware requirements.

Modified VSAM RecordsThe VSAM records were modified in NPM Version 2 to include the product data section,SMF28PSS. SMF28PSS was added at the end of each record after the Volume Data Section.Table 14 shows the layout of SMF28PSS.

Table 14. SMF28PSS LayoutOffset(hex)

Length(dec)

Type Name Description

0000 0 Structure SMF28PSS Product section

0000 2 Signed SMF28TYP Subtype ID

0002 2 SignedX'0002'

SMF28PVN Product version and release:Version 2

0004 4 Character SMF28NPM Product name (‘NPM’)

0008 0 Structure PSS28END End of product section

NPM V1R6 VSAM records are compatible with NPM Version 2 releases with oneexception: Data collected by NPM V1R6 and stored in VSAM data sets cannot be displayedonline in NPM Version 2 releases.

See the NetView Performance Monitor Reference for more information about VSAM records.

8


8.M

igratin

gto

NP

MV

ersion

2R

elease7

Updating FNMINIT for NPM Version 2 Release 7To migrate to NPM Version 2 Release 6 or higher and maintain your initializationenvironment from NPM V1R6, some statements in FNMINIT must be updated. Thefollowing list shows the FNMINIT statements that need to be updated:¶ DEFAULTS¶ NPM¶ TASK¶ VTAM¶ FILE

See the NetView Performance Monitor Installation and Customization for more informationabout the added, deleted, and changed keywords for these statements.

Automatic Discovery Using RODMTo implement the automatic discovery using RODM in NPM Version 2 Release 7, the NPMstatement in FNMINIT must be updated to include three new parameters:

¶ RODMDISC=YES/NO

¶ RODMNAME=name_of_RODM

¶ RODMUSER=userid

See the NetView Performance Monitor Installation and Customization for more informationabout these parameters.

Automatic Discovery Using RODM with a MaskTo allow dynamic NPM Configuration Discovery using RODM in NPM Version 2 Release7, the FNMINIT member must be updated to include three new statements:

¶ NNET

¶ RNET

¶ APLM

These new statements represent masks used by the user to decide whether to have anautomatic discovery of a network portion.

See the NetView Performance Monitor Installation and Customization for more informationabout these statements.

Migrating to NPM V2R7


|

||

|

|

|

||

|

||

|

|

|

||

||

Updating FNMSTRT and Other NPM EXECSNPM Version 2 combined the START COLLECT and START MONITOR commands fornetwork collection into the NETCOLL command. The NETCOLL command is uniquelyidentified by the following parameters:¶ Resource name¶ NCP name (if coded)¶ Interval number¶ Start time¶ Stop time

All NPM V1R6 EXECs containing the START COLLECT and START MONITORcommands must be updated to contain the NETCOLL command.

See the NetView Performance Monitor Installation and Customization for more informationabout mapping the START COLLECT and START MONITOR keywords into NETCOLLkeywords. Also, see the NetView Performance Monitor User’s Guide for a description of theNETCOLL command syntax and keyword definitions.

Updating the User ProfileIf you want to use the new PF keys with old NPM operators, you need to do a migration ofthe user profile.

To update the user profile already defined in NPM Version 2 Release 5, you can choose to:¶ Delete the existing profile. NPM automatically creates the new profile at logon time

with the new PF keys defined.¶ Use the old profile. In this case, you have to change manually the Pfkey set (=0.1,

“Program function key definition”). If the set is using 12 PF keys, you need to select 24PF keys, reset all of the second group of PF keys, and set the new PF keys on thesecond group.

In either case you can also continue to use the old profile and to invoke the newfunctionalities related to the PF keys writing directly the new commands on the commandline.

If you are a new operator, or you have made the profile migration, NPM displays the newPF keys active on all panels, and always with the same PF key numbers.



8.M

igratin

gto

NP

MV

ersion

2R

elease7



Part IV. User ScenariosChapter 9. Isolating Performance Problems in a Network . . . . . . . . . . . . . . . 95Example: Isolating the Problem to the Host or the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Starting Session Collection by LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Displaying Session Data for the LU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Displaying Session Monitor Event Messages for the LU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Stopping Collection for the LU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Example: Examining a Line for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Starting Network Collection on a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Displaying Data for the Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Stopping Collection for the Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Example: Examining an NCP for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Collecting Network Data for the NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Displaying Network Data for the NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Isolating Problems in an IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Throughput Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116CPU Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Memory Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Cisco Channel Interface Processor (CIP) Card Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 10. Isolating Poor Response Time on a LAN. . . . . . . . . . . . . . . . . . . 119Example: Examining a LAN Network for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Setting Global LAN Bridge Collection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Starting LAN Bridge Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Setting Global LAN Segment Collection Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Starting LAN Segment Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Displaying Data for the LAN Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Displaying Data for the LAN Segment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Stopping Collection on the LAN Bridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Stopping Collection on the LAN Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Example: Examining a TIC for Potential Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Starting NTRI Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Displaying the NTRI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Stopping NTRI Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Chapter 11. Isolating Performance Problems in the Host. . . . . . . . . . . . . . . 141Example: Examining an Application for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Starting Session Collection on the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Displaying Data for the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Stopping Collection for the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Example: Examining an Application Using VTAM Statistics Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Stopping VTAM Statistics Collection on an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Example: Examining VTAM for Problems in the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Starting a VTAM Global Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Stopping a Global Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Collecting and Displaying VTAM Buffer Pool Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Stopping a VTAM Buffer Pool Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Example: Determining if There is a Blocked Virtual Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Analyzing Long-Term VR Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164


Chapter 12. Reviewing Network Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Example: Using a Network Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Starting a Network Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Displaying the Monitor Event Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Chapter 13. Isolating Problems on a Novell NetWare Network . . . . . . . . . 175Using NetWare Counters and Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Example: Tuning and Load Balancing a NetWare Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Example: Monitoring a NetWare Network for Potential Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Chapter 14. Managing NPM Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Example: No Data Found (Error Message) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Checking for Incorrect Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Determining Whether Data Was Collected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Determining Whether the Collected Data Has Been Saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Example: Resetting a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Example: Preparing a File for Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Example: Managing Data Files with the System Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Example: Available Actions Based on File Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186


Isolating Performance Problems in aNetwork

Now that you have been introduced to the mechanics of using NPM, you are ready to useNPM to accomplish specific tasks. This part of the NPM Concepts and Planning containsexamples showing how to use NPM panels and how to step through the procedures requiredto solve problems.

One of the most common problems that NPM can help you solve is poor response time. Thescenarios provided in this chapter explain how to isolate the cause of system responseproblems.

Each scenario starts with a description of the problem and provides step-by-step proceduresfor using NPM to research the problem. The procedures describe only one approach indetail, but they offer additional suggestions and hints to help you develop problem-solvingtechniques and use NPM more efficiently.

Example: Isolating the Problem to the Host or the NetworkSuppose a network customer has called you to complain about response time on a specificterminal. The customer tells you that the LU name of the terminal is LU032 and theapplication being used is CICS. You know from your network configuration (shown inFigure 14) that LU032 is connected to NCP01.

At this point, you cannot be sure whether the poor response time involves only the host orthe entire network. Your first step is to determine whether the host or the network is at fault.You can do this by collecting session data.

Session data provides statistics for each session with the host, including message volumesand transit times. Volume statistics count the number of PIUs sent and received for each LU.

Figure 14. Example Network

9


9.Iso

lating

Pro

blem

sin

aN

etwo

rk

Transit time measures the length of time it takes for inbound and outbound PIUs to travelthrough the host or network and make a round trip from and to an operator. Host transittime is the length of time the PIU spends in the host, and network transit time is thelength of time the PIU spends in the network. Operator transit time, also called responsetime, is the sum of the host transit time and the network transit time; the total length of timeit takes for an inbound and outbound PIU to be processed. By looking at session data, youcan see the breakdown of operator transit time into host and network transit times anddetermine where the PIU is being slowed down.

You can also set low and high thresholds to monitor session volume statistics (averagenumber of PIUs per minute and average number of bytes per second), and transit timestatistics such as average operator, host and network transit time, or the percentage ofoperator, host, and network transactions exceeding the transit time thresholds. When thethresholds are exceeded, NPM can send an alert to the NetView program and store monitormessages in a log file for later review.

The following sections provide step-by-step instructions to:

¶ Start a collection on the LU in question and set low and high criteria to monitor sessiondata for the same LU

¶ Display session data and session monitor messages for the same LU

Note: The numeric values used in the following example, such as high and low criteria forsession monitors, are only examples. You may want to change them to betterrepresent your network configuration and your specific needs.

Starting Session Collection by LUUse the following procedure to start session collection on the LU:

1. Select option 2 on the Primary Options panel (FNM00PRI) to display the ResponseTimes panel (FNM01SES).

2. Select option 1 on the Response Times panel to display the Start Session panel(FNM02SCL), shown in Figure 15 on page 97. You can also use fast path =2.1 todisplay the Start Session panel.

3. Complete the Start Session panel fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you are instructed to do so.

Isolating a Host or Network Problem


4. Type the name of the LU in the Resource Name field. �1�

The name you type should be the LU name of the terminal that is experiencing poorresponse time. The name of the LU is LU032 in this example.

5. Type the name of the NCP to which the LU is connected in the Node Name field. �2�

The name of the NCP is NCP01 in this example. This step is not necessary if the LUhas previously been defined to NPM.

6. Type LOCAL in the Host Name field. �3�

Although you interact primarily with the local NPM, you can communicate withanother NPM. For example, you would need to do this if the LU were on another host.Type =2.8 on the Command line and press ENTER to display a list of hosts. NPMdisplays the Performance Status Analysis panel (FNM02PDT). Verify that the HostName field is blank on this panel and press ENTER to display a list of hosts. Type=2.1 on the Command line and press ENTER to return to the Start Session panel(FNM02SCL).

7. Type Y in the Session Statistics field. �4�

This option writes the collected data to the current session file so that you can retrieveit later.

8. Type 0 in the VTAM Log field. �5�

9. Type YES in the Minimum PIU Trace field. �6�

10. Type NO in the GTF Trace field. �7�

11. Type .00 in the low Operator, Network, and Host Transit Threshold fields. �8�, �9�,and �10�

12. Type 3.50 in the high Operator Transit Threshold field. �8�

If the operator transit time exceeds the high threshold that you set (in this case, 3.5seconds) at the end of the data collection interval, any session data that falls outsidethis value is highlighted on the session analysis display.

13. Type 2.00 in the high Network and Host Transit Threshold fields. �9� and �10�

FNM02SCL NPM V2R7 5655-043RESPONSE TIMESSTART SESSION

Command ===>Resource Name ===> LU032 �1�Node Name ===> NCP01 �2�Host Name ===> LOCAL �3�Dynamic Resource ===> NO (Yes/No)Session Statistics ===> Y �4� (Yes/No/Vol/Xcl/Rsp)VTAM Log ===> 0 �5� (0/1/2/3)Minimum PIU Trace ===> YES �6� (Yes/No)GTF Trace ===> NO �7� (Yes/No)Transit ThresholdsOperator ===> .00 : 3.50 (Low:High) �8�Network ===> .00 : 2.00 (Low:High) �9�Host ===> .00 : 2.00 (Low:High) �10�

Distribution Bounds ===> 5.00 : 10.00 : 20.00 : 30.00 �11�Start Time ===> 00 : 00 : 00 (hh:mm:ss)Stop Time ===> 00 : 00 : 00Daily ===> NO �12� (Yes/No)

PF 1=HELP 3=END 12=RETURN 15=NCP 16=ROUTER 17=LINEPF20=APPL 24=TERMINAL

Figure 15. Start Session Panel (FNM02SCL)



9.Iso

lating

Pro

blem

sin

aN

etwo

rk

If the network or the host transit time exceeds the high thresholds that you set (in thiscase, 2 seconds) at the end of the data collection interval, any session data that fallsoutside this value is highlighted on the session analysis display.

14. Type 5.00, 10.00, 20.00, and 30.00 in the Distribution Bounds fields. �11�

15. Verify that the Start Time field is 00:00:00.

Collection starts immediately if you leave this field blank. Because you want to find thesource of the poor response time right away, you need to start collecting dataimmediately. If you wanted to start collecting later, you would specify a later time. Forexample, to start collecting at 8 a.m., type 08:00:00.

16. Verify that the Stop Time field is 00:00:00.

If you leave this field blank, NPM collects data until you tell it to stop. If you wantedto stop collection at a specific time, you would specify a stopping time. For example, tostop collecting at 5 p.m., type 17:00:00. Remember that the stop time must always begreater than the start time.

17. Type NO in the Daily field. �12�

This field specifies whether data should be collected daily. You type NO because you aretrying to isolate the problem immediately, you do not need to collect data on a dailybasis.

You would collect data daily if you wanted to determine trends. In this case, type YESin this field and specify both a start and a stop time in the two previous fields. NPMcollects data every day between the two times. For example, you could collect dataevery day between 08:00:00 and 17:00:00.

18. Press ENTER to display the Session Monitor Selection Panel (FNM03SAS), shown inFigure 16. This panel allows you to set up monitors for the displayed monitor data type.

Because we want to understand whether the problem is caused by bad networkperformance or bad host performance, we can monitor the average host and networktransit times. Complete the appropriate field as described in this section. Use the Tabkey to move from field to field. Do not press ENTER until you are instructed to do so.

FNM03SAS NPM V2R7 5655-043RESPONSE TIMES

SESSION MONITOR SELECTION

Command ===>Enter Monitor Criteria for Resource LU032 Criteria

Low : HighAverage Operator Transit Time ===> .00 : .00Average Host Transit Time ===> �13�.00 : 2.00Average Network Transit Time ===> �14�.00 : 2.00Maximum Operator Transit Time ===> .00 : .00Maximum Host Transit Time ===> .00 : .00Maximum Network Transit Time ===> .00 : .00% of Operator Trans Exceeding Transit Thresholds ===> 0 : 0% of Host Trans Exceeding Transit Threshold ===> 0 : 0% of Network Trans Exceeding Transit Threshold ===> 0 : 0Number of Active LUs in a Summary Record ===> 0 : 0Average Number of PIUs per Minute ===> 0 : 0Average Number of Bytes per Second ===> 0 : 0


Figure 16. Session Monitor Selection Panel (FNM03SAS)



19. Type 0.00 for low criterion and 2.00 for high criterion in the Average Host TransitTime fields. �13�

This causes NPM to generate a message if the average host transit time at the end ofthe collection interval is above 2 seconds.

20. Type 0.00 for low criterion and 2.00 for high criterion in the Average Network TransitTime fields. �14�

This causes NPM to generate a message if the average host transit time at the end ofthe collection interval is above 2 seconds.

21. Press ENTER to start session collection by LU.

NPM issues a message to indicate that it has started collection. If you change yourmind about the entries on the previous panels, you can use the Alter Session panel(FNM05ALT) to change collection parameters. See the NetView Performance MonitorUser’s Guide for information about altering session data collection parameters.

Displaying Session Data for the LUWait until NPM has collected enough data to help you determine the source of the problembefore displaying the LU data. Fifteen minutes of collection should be sufficient to averageout occasional spikes in the data. You are not able to see any data until at least onecollection interval has elapsed. You can determine the session collection interval by lookingat the Session Interval field in the Summary Display panel (FNM02OPS). You can displaythe Summary Display panel (FNM02OPS) by using fast path =9.4 and the NEXT command.

Use the following procedure to display NPM data:


2. Select option 6 on the Response Times panel to display the NPM LU Detail Analysispanel (FNM02DNM), shown in Figure 17 on page 100. You can also use fast path =2.6to display the NPM LU Detail Analysis panel.

3. Complete the NPM LU Detail Analysis panel fields as described in this section. Use theTab key to move from field to field. Do not press ENTER until you are instructed to doso.



9.Iso

lating

Pro

blem

sin

aN

etwo

rk

4. Type 4 in the Select Option field. �1�

The transit time summary shows the average operator, host, and network transit timesfor this LU.

5. Type the name of the LU in the LU Name field. �2�

This name should match the LU for which you collected data.


If the LU is on another host, type the name of that host.

7. Type SESSION in the File Name field. �4�

This option specifies the current session file containing the data you collected. If youwanted to look at data stored in another file, you would type the name of that file. See“Managing NPM Data Files” on page 179 for information about NPM files.

8. Type today’s date in the Date fields. �5�

Because you just collected the data, you can use today’s date. If you collected data onanother day, use that date.

9. Type a starting and stopping time in the Time fields. �6�

Use the time you started the collection for the starting time. Use the current time forthe stopping time.

10. Verify that the remaining fields on this panel are blank.

The remaining fields on this panel put restrictions on the data displayed on your screen.Because you are trying to isolate a problem, you want to see all the data collected.

11. Press ENTER to display the NPM Session Analysis Summary panel (FNM03SMN),shown in Figure 18 on page 101. See “Example: No Data Found (Error Message)” onpage 180 if you receive the following error message:FNM756E NO DATA FOUND FOR THIS REQUEST

FNM02DNM NPM V2R7 5655-043RESPONSE TIMES

LU DETAIL ANALYSIS

Select Option ===> 4 �1�1 Transit Time/Interval 3 Volumes/Interval2 Distribution/Interval 4 Transit Time Summary

LU Name ===> LU032 �2�Host Name ===> LOCAL �3�Data Qualifiers:Application ===>Line ===>Physical Unit ===>Virtual Route Number ===> (0-7)Transmission Priority ===> (0-2)

File Name ===> SESSION �4� (SESSION for active session file)Date from ===> 09 / 30 / 00 to ===> 09 / 30 / 00 �5� (mm/dd/yy)Time from ===> 08 : 00 : 00 to ===> 17 : 00 : 00 �6� (hh:mm:ss)


Figure 17. NPM LU Detail Analysis Panel (FNM02DNM)



The NPM Session Analysis Summary panel displays the data you have been collecting forthe LU. It summarizes the information you entered to collect the data and provides statisticson the number of transactions and the number and size of PIUs sent and received during thecollection period.

To isolate the source of the poor response time problem, compare the average and maximumtransit times for both the host and the network. The data displayed on the NPM SessionAnalysis Summary panel shows that the host transit time is greater than the network transittime. The average and maximum transit times for the operator and the host would behighlighted because the operator and host high thresholds that were set on the Start SessionCollection panel (FNM02SCL) have been exceeded. This data analysis indicates that theproblem is host-related. You can confirm this conclusion by looking at the Session MonitorReview panel (FNM02SAM), described in the following section.

Displaying Session Monitor Event Messages for the LUUse the following procedure to display session monitor event messages:


2. Select option 9 on the Response Times panel to display the Session Monitor Reviewpanel (FNM02SAM), shown in Figure 19 on page 102. You can also use fast path =2.9 todisplay the Session Monitor Review panel.

3. Complete the appropriate Session Monitor Review panel fields as described in thissection. Use the Tab key to move from field to field. Do not press ENTER until you areinstructed to do so.

FNM03SMN NPM V2R7 5655-043RESPONSE TIMES

NPM SESSION ANALYSIS SUMMARY - LOGICAL UNITCommand ===>Insert DYN to get dynamic (real time) dataHost Name = LOCAL Records = 357 VR/TP =Application = Line = PU =Group = Node = LU = LU032Requested Date/Time: from 09/30/00 00:00:00 to 9/30/00 01:00Actual Date/Time : from 09/30/00 00:00:00 to 9/30/00 01:00

Total ResponseTransactions 635 630

Operator Host NetworkAverage Transit 5.85 4.73 1.12Maximum Transit 80.19 80.15 16.70

PIU Count Avg Size Total BytesUser Data In 1131 19 21969User Data Out 1378 222 306403System Data In 1480 5 8012System Data Out 65 7 424

PF 1=HELP 3=END 4=TRANSIT 5=VOLUME 6=DISTRIB 12=RETURNPF15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 18. NPM Session Analysis Summary - LU Panel (FNM03SMN)



9.Iso

lating

Pro

blem

sin

aN

etwo

rk


Although you interact primarily with the local NPM, you can communicate with anotherNPM. You would do this if the LU is on another host. Type =2.8 on the Command lineand press ENTER to display a list of hosts on the Performance Status Analysis panel(FNM02PDT). Verify that the Host Name field is blank on this panel and press ENTERto display a list of hosts. Type =2.9 on the Command line and press ENTER to return tothe Session Monitor Review panel.

5. Type LU032 in the Resource Name field. �2�

Type the name of the resource for which you want to display monitor messages inResource Name field. If you want to display the session monitor messages for all theresources, type MONITOR.

6. Type SESSION in the Session File Name field. �3�

This option specifies the current session file that contains the data you collected. If youwanted to look at data stored in another file, you would type the name of that file. See“Managing NPM Data Files” on page 179 for information about NPM files.

7. Type today’s date in the Start and Stop Date fields. �4� and �5�


8. Type a starting and stopping time in the Start and Stop Time fields. �6� and �7�

Use the time you started the collection for the starting time. Use the current time for thestopping time.

9. Press ENTER to display the Session Monitor Event Messages panel (FNM03SAE),shown in Figure 20 on page 103. See “Example: No Data Found (Error Message)” onpage 180 if you receive the following error message:FNM756E NO DATA FOUND FOR THIS REQUEST

FNM02SAM NPM V2R7 5655-043RESPONSE TIMES

SESSION MONITOR REVIEW

Command ===>

Host Name ===> LOCAL �1�Resource Name ===> LU032 �2� (Name/Monitor)Session File Name ===> SESSION �3� (SESSION for active session file)

Start Date ===> 09 / 30 / 00 �4� (mm/dd/yy)Stop Date ===> 09 / 30 / 00 �5�

Start Time ===> 15 : 02 : 00 �6� (hh:mm:ss)Stop Time ===> 15 : 17 : 00 �7�


Figure 19. Session Monitor Review Panel (FNM02SAM)



The Session Monitor Event Messages panel (FNM03SAE) displays all the messages thatNPM generated for LU032 because the high threshold on the session monitors set onFNM03SAS was exceeded. In this example, the average host transit time (MONATMHT) isthe only session data that exceeds the fixed high threshold (2.00) in every collection interval.

Because no monitor messages were generated for the average network transit time, youknow that the average network transit time always fell within the set monitor thresholds.

Note: Monitor event messages are generated at the end of each collection interval when asession monitor falls outside the set thresholds.

Monitor resolution messages are generated when a session monitor returns within its setthresholds. Ask your system programmer to code the DEFAULT statement accordinglyduring the NPM installation process if you need to display monitor resolution messages.

The data displayed on the Session Monitor Event Messages panel confirms our initialconclusion: the problem is host-related. See the next scenario, “Example: Examining anApplication for Potential Problems” on page 141, to gather more information for theoperator.

If the network transit time shown in Figure 18 on page 101 were larger than the host transittime, and the average network transit time exceeded the high threshold, you would need tocollect more data to research the potential network problem. See “Example: Examining aLine for Potential Problems” on page 105 and “Example: Examining an NCP for PotentialProblems” on page 111 for more information.

Stopping Collection for the LUUse the following procedure to stop collection after you have viewed session data for theLU:


FNM03SAE NPM V2R7 5655-043RESPONSE TIMES

SESSION MONITOR EVENT MESSAGES

Command ===>

Host Name: LOCAL Resource Name: LU032Date/Time: from 09/30/00 15:02:30 to 09/30/00 15:17:00

Actual Resource Monitor ActualTime Name Type Value Monitor Event Description Limit15:05:00 LU032 MONATMHT 5.12 MONITOR VALUE ABOVE THE LIMIT OF 2.0015:08:00 LU032 MONATMHT 5.32 MONITOR VALUE ABOVE THE LIMIT OF 2.0015:11:00 LU032 MONATMHT 4.82 MONITOR VALUE ABOVE THE LIMIT OF 2.0015:14:00 LU032 MONATMHT 4.62 MONITOR VALUE ABOVE THE LIMIT OF 2.0015:17:00 LU032 MONATMHT 4.74 MONITOR VALUE ABOVE THE LIMIT OF 2.00

PF 1=HELP 3=END 8=FORWARD 12=RETURN 15=NCP 16=ROUTERPF17=LINE 20=APPL 24=TERMINAL

Figure 20. Session Monitor Event Messages Panel (FNM03SAE)



9.Iso

lating

Pro

blem

sin

aN

etwo

rk

2. Select option 2 on the Response Times panel to display the Session Status/Stop (Active)Resource panel (FNM03SSA), shown in Figure 21. You can also use fast path =2.2 todisplay the Session Status/Stop (Active) Resource panel.

3. Complete the Session Status/Stop (Active) Resource panel (FNM03SSA) fields asdescribed in this section. Use the Tab key to move from field to field. Do not pressENTER until you are instructed to do so.

4. Type S in the Option field �1� next to the name of the NCP to which the LU isconnected.

Option S allows you to select a resource (NCP01, in this example) to display itscollection details.

5. Press ENTER to display the Session Status/Stop (Active) Details panel (FNM04SSA),shown in Figure 22.

FNM03SSA NPM V2R7 5655-043RESPONSE TIMES

SESSION STATUS/STOP (ACTIVE) RESOURCE

Command ===>

Host Name = LOCALEnter Option: S=Detailed Status, P=STOP, Z=Stop All

Option Resource Resource Maximum SessionName Type Collected Collected Logging Data Forwd Monitors

=> A02MPU HOST 250 0 0 0 0=>S�1� NCP01 NCP 422 1 0 1 1=> A31C52A NCP 437 0 0 0 0=> A99M CDRM 50 0 0 0 0=> B63M CDRM 50 0 0 0 0=> TSO02 APPL 50 0 0 0 0


Figure 21. Session Status/Stop (Active) Resource Panel (FNM03SSA)


SESSION STATUS/STOP (ACTIVE) DETAILSCommand ===>

Host Name = LOCAL Resource Name = NCP01 Resource Type = NCPEnter option: A=Alter, P=STOP, Z=Stop All

Option Resource Session Data Operator Network HostName Stats Forwd Log Min GTF Thresholds Thresholds Thresholds

=> NCP01 Y 22 1 YES NO 0.00 3.50 0.00 2.00 0.00 2.00=>P �2� LU032 Y 12 0 YES NO 0.00 3.50 0.00 2.00 0.00 2.00=> T02D0102 Y 12 1 YES NO 0.00 3.50 0.00 2.00 0.00 2.00=> T02D0103 Y 12 1 YES NO 0.00 3.50 0.00 2.00 0.00 2.00

2.00


Figure 22. Session Status/Stop (Active) Details Panel (FNM04SSA)



6. Type P in the Option field �2� next to the name of the LU. Option P stops collection onthe selected resource (LU032 in this example).

7. Press ENTER to stop the collection. NPM issues a message indicating it has stoppedcollection for the LU.

Example: Examining a Line for Potential ProblemsIn the previous scenario, you investigated a customer’s complaint about poor response timefor a particular terminal (LU032) when using CICS. You collected session data to determinethat the problem was with the host and the terminal, not with the network or application. Inthis example, the customer has reported poor response for the same terminal, shown inFigure 23.

Note: This scenario shows the concept for network data provided by the NCP. The conceptfor network data provided by a router is similar.

As in the previous examples, begin by collecting session data on the LU corresponding tothat terminal. This time, however, you find that the network, rather than the host, is at fault.You can further isolate the cause of high network transit time by collecting network data.

Network data is provided by the NCP and includes performance statistics on each resource,percentage of line utilization, error counts, and polling information. To investigate theproblem of poor response time for a terminal on the network, start by examining the linebetween the terminal and the NCP.

First, determine the name of the line (LINE078 in this example). Second, collect and displaynetwork data on the line. The steps required to perform this process are explained in thefollowing sections.

Starting Network Collection on a LineUse the following procedure to start collection on the line:

1. Select option 1 and N for NCP on the Primary Options panel (FNM00PRI) to displaythe Network Resource Type Selection panel (FNM01NET).

2. Select option 1 from the Network Resource Type Selection panel to display theResource List panel (FNM02RSL), shown in Figure 24 on page 106. You can also usefast path =1.1 to display the Resource List panel.




9.Iso

lating

Pro

blem

sin

aN

etwo

rk

3. Type X in the Option field next to the appropriate NCP name (NCP01 in this example).

4. Press the ENTER key to display an expanded list of resources under NCP01, shown inFigure 25.

5. Type S in the Option field next to LINE078 on the Resource List panel and pressENTER to display the first Network Start panel (FNM03STD), shown in Figure 26 onpage 107.

FNM02RSL NPM V2R7 5655-043NETWORK MANAGEMENT

RESOURCE LIST

Command ===>

Host Name = LOCALEnter Command: LOCATE <Resource>, REFRESH, SORT <NAME/TYPE/STATUS>or Option: S=Start, R=Review, L=List, X=Expand, Z=Stop All

Resource Resource NCP Valid Data Collection MonitorOption Name Type Name Options Forwd Status Status=> X NCP01 NCP SRLXZ 0 STARTED EXCEEDED=> NCP02 NCP SRLXZ 0 DEFERRED=> NCP03 NCP SRLXZ 0 INACTIVE

PF 1=HELP 2=REFRESH 3=END 8=FORWARD 11=BOTTOM 12=RETURNPF15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 24. Resource List Panel (FNM02RSL)

FNM02RSL NPM V2R7 5655-043NETWORK MANAGEMENTRESOURCE LIST

Command ===>

Host Name = LOCALEnter Command: LOCATE <Resource>, REFRESH, SORT <NAME/TYPE/STATUS>or Option: S=Start, R=Review, L=List, X=Expand, Z=Stop All

Resource Resource NCP Valid Data Collection MonitorOption Name Type Name Options Forwd Status Status=> LINE077 LINK NCP01 SRLXZ 0 STARTED EXCEEDED=> S LINE078 LINK NCP01 SRLXZ 0 INACTIVE=> LINE079 LINK NCP01 SRLXZ 0 INACTIVE


Figure 25. Resource List Panel (FNM02RSL)

Examining a Line


6. Complete the Network Start panel fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you have completed all of thefollowing steps.

7. Type 1 in the Interval Number field. �1�

The interval number determines how long NPM waits each time it collects data. Bytyping 1 in this field, you request the shortest interval.

8. Verify that NCP01 is displayed in the NCP Name field. �2�

9. Verify that LINE078 is displayed in the Resource Name field. �3�

The resource name should be the name of the line connecting the NCP to the problemLU (LINE078 in this example.)

10. Type NO in the Dynamic Resource field. �4�

11. Verify that the Start Time field �5� displays all zeros.

The default for this field starts collection immediately. Because you want to find thesource of the poor response time right away, you need to start collecting dataimmediately.

12. Verify that the Stop Time field �6� displays all zeros.

The default for this field is for NPM to collect data until you tell it to stop.


Because you are trying to isolate the problem immediately, you do not need to collectdata on a daily basis. You would collect data daily if you wanted to establish trends.

14. Press ENTER to display the second Network Start panel (FNM03STM), shown inFigure 27 on page 108.

FNM03STD NPM V2R7 5655-043NETWORK MANAGEMENTNETWORK START

Command ===>

*---------------*Interval Number ===> 1 �1� <======| Interval |

| Num Time |NCP Name ===> NCP01 �2� | 1 00:03:45 |Resource Name ===> LINE078 �3� | 2 00:07:30 |Dynamic Resource ===> NO �4� (Yes/No) | 3 00:15:00 |

| 4 00:30:00 || 5 01:00:00 |

Start Time ===> 00 : 00 : 00 �5� (hh:mm:ss) | 6 02:00:00 |Stop Time ===> 00 : 00 : 00 �6� | 7 04:00:00 |Daily ===> NO (Yes/No) �7� *---------------*


Figure 26. Network Start Panel (FNM03STD)

Examining a Line


9.Iso

lating

Pro

blem

sin

aN

etwo

rk

15. Indicate where to send the data in the Data Destinations Detail fields. �8�

Because you want to review the data online, type YES in the Data Destinations DetailVSAM field. For the purposes of this example, it does not matter whether you send thedata to the other destinations. See the NPM Reference for information about the otherdestinations.

16. Because you do not need to monitor the collection, verify that the monitor criteria fieldsset to zero.

17. Press ENTER to start network data collection on the line. The Resource List panel(FNM02RSL) is redisplayed.

18. Use the REFRESH command to verify that the collection has started.

Displaying Data for the LineWait until NPM has collected enough data to help you determine the source of the problembefore displaying the data. Fifteen minutes of collection should be sufficient to average outoccasional spikes in the data. You are not able to see any data until at least one collectioninterval has elapsed.

Use the following procedure to display the collected line data:

1. Type R in the Option field next to LINE078 on the Resource List panel (FNM02RSL) todisplay the Network Review panel (FNM02RVM), shown in Figure 28 on page 109.

FNM03STM NPM V2R7 5655-043NETWORK MANAGEMENTNETWORK START

Command ===>

Host Name = LOCAL NCP Name = NCP01 Resource Name = LINE078

Data Destinations NPMLOG VSAM SMF ALERT GLOBAL �8�Detail ===> NO YES NO N/A N/AMonitor ===> NO NO NO NO NO

Resolve Monitors ===> NO (Yes/No)

Monitor Criteria LOW : HIGHNegative polls/minute (0-2147483646) ====> 0 : 0Positive polls/minute (0-2147483646) ====> 0 : 0PDUs/minute (0-2147483646) ====> 0 : 0Bytes/second (0-2147483646) ====> 0 : 0Line utilization (0-100) ====> 0 : 0Error count (0-2147483646) ====> 0 : 0

PF 1=HELP 3=END 7=BACKWARD 8=FORWARD 10=TOP 11=BOTTOMPF15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 27. Network Start Panel (FNM03STM)

Examining a Line


2. Verify that LOCAL is displayed in the Host Name field. �1�

If the line were on another host, the name of that host should be displayed.

3. Verify that LINE078 is displayed in the Resource Name field. �2�

The name should correspond to the line for which you collected data.

4. Verify that LINK is displayed in the Resource Type field. �3�

5. Verify that REVIEW is displayed in the Review File Name field. �4�

This option specifies the review file containing the data you collected. If you wanted tolook at data stored in another file, you would type the name of that file. See “ManagingNPM Data Files” on page 179 for more information about NPM files.

6. Verify that today’s date is displayed in the Date fields. �5� and �6�


7. Type a starting and stopping time in the Time fields. �7� and �8�

Use the time you started the collection for a starting time. Use the current time for astopping time.

8. Type DETAIL in the Data Type field. �9�

9. Press ENTER to display the Network Review Data panel (FNM03RVL), shown inFigure 29 on page 110. See “Example: No Data Found (Error Message)” on page 180 ifyou receive the following error message:FNM756E NO DATA FOUND FOR THIS REQUEST

FNM02RVM NPM V2R7 5655-043NETWORK MANAGEMENTNETWORK REVIEW

Command ===>

Host Name ===> LOCAL �1�Resource Name ===> LINE078 �2� (Name)Resource Type ===> LINK �3� (Name/ALL only for Data Type=MONITOR)Review File Name ===> REVIEW �4� (REVIEW for active review file)



Data Type ===> DETAIL �9� (Detail/Monitor)

PF 1=HELP 2=RESTYPE 3=END 9=SUMMARY 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 28. Network Review Panel (FNM02RVM)

Examining a Line


9.Iso

lating

Pro

blem

sin

aN

etwo

rk

The Network Review Data panel displays the data you have been collecting for the line. Youonly need to examine three fields for this scenario:¶ Line utilization (Line-Ut)¶ Errors (Error)¶ Retransmitted bytes (Retransmit Bytes, you can see this field by pressing PF5 (RIGHT))

There are three ways in which a line can cause poor response time:

1. High traffic: A line can cause poor response time because too much traffic is crossingit. You can identify this problem by high line utilization, low errors, or lowretransmission.

If the line has too much traffic, your system programmer could install an additional line.Or, if the line is an analog line, it could be replaced by a digital one. Before adding orchanging lines, however, the system programmer might consider redirecting traffic. Forthis last option, you need to identify the PUs or LUs that are creating high volume. Tosee network transit times for the PU or another LU, collect session data as described in“Example: Isolating the Problem to the Host or the Network” on page 95. To seeperformance statistics, collect network data for a PU or LU. Follow the steps describedin “Example: Examining a Line for Potential Problems” on page 105.

2. Noise: A line can cause poor response time because of noise. You can identify thisproblem by high line utilization and high errors. Noise can also be caused by mechanicalproblems; you might want to check your telecommunication equipment or contact yourtelephone company.

3. Dead: A line can cause poor response time because of a mechanical failure thatprevents traffic from crossing it. You can identify this problem by zero line utilization.Contact your telephone company if the line is dead.

If the line appears to be functioning correctly, as it is in this example, you need to continuecollecting data to locate the cause of the poor response time. See the following scenario,“Example: Examining an NCP for Potential Problems” on page 111, for more information.

Stopping Collection for the LineUse the following procedure to stop collection after you have viewed network data for theline:

FNM03RVL NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK REVIEW DATA

Command ===>Insert DYN to get dynamic (real time) dataHost Name = LOCAL Resource Name = LINE078 Data Type = LINE DETAILDate/Time: from 09/30/00 11:45:00 to 09/30/00 12:00:00

End Interval Resource Queue Msgs Bytes Line-Ut Polls/MinTime hh:mm:ss Name Length /Min /Sec Pri Sec Rate %Neg Errors12:00:00 3:45 LINE078 0 21 108 19 0 281 98 012:03:45 3:45 LINE078 0 76 244 41 0 216 91 012:07:30 3:45 LINE078 0 11 75 13 0 296 98 013:12:15 3:45 LINE078 0 44 161 28 0 257 95 013:16:00 3:45 LINE078 0 71 212 36 0 234 91 013:19:45 3:45 LINE078 0 60 195 33 0 239 93 013:23:30 3:45 LINE078 0 46 165 28 0 257 95 013:28:15 3:45 LINE078 0 9 87 15 0 287 100 013:32:00 3:45 LINE078 0 9 87 15 0 288 100 0PF 1=HELP 3=END 5=RIGHT 9=SUMMARY 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 29. Network Review Data Panel (FNM03RVL)

Examining a Line


1. Return to the Resource List panel (FNM02RSL) that displays the line resource. You canuse fast path =1.1 to display the Resource List panel.

2. Type L in the Option field next to a specific network resource (LINE078 in this example)on the Resource List panel. Press ENTER to display the Command List panel(FNM03NCL), shown in Figure 30.

3. Type P in the Option field next to the LINE078 collection you want to stop.

4. Press ENTER to stop the collection. The Resource List panel is redisplayed.

5. You can use the REFRESH command to confirm that the collection has been stopped.

Example: Examining an NCP for Potential ProblemsIn the previous scenarios you investigated the cause of poor response time for a particularterminal. By collecting session data on the terminal, you discovered that the network, not thehost, had high transit times. By collecting network data on the line between the terminal andthe NCP, you determined that traffic on the line appeared normal. Because the line is not theproblem, you need to determine if the NCP is the cause of the problem. The examplenetwork is shown Figure 31.

Note: This scenario shows the concept for network data provided by the NCP. The conceptfor network data provided by a router is similar.

FNM03NCL NPM V2R7 5655-043NETWORK MANAGEMENTCOMMAND LIST

Command ===>

Host Name = LOCAL NCP Name = NCP01 Resource Name = LINE078Enter Command: REFRESH or Option: A=Alter, P=Stop

Time Collect <--Detail--> <-----Monitor-------->Option Start Stop Status Daily Int LOG VSAM SMF LOG VSAM SMF ALERT GBL=> 00:00:00 00:00:00 STARTED NO 1 N Y N N Y N N N

PF 1=HELP 2=REFRESH 3=END 12=RETURN 15=NCP 16=ROUTERPF17=LINE 20=APPL 24=TERMINAL

Figure 30. Command List Panel (FNM03NCL)

Examining a Line


9.Iso

lating

Pro

blem

sin

aN

etwo

rk

The following sections explain how to collect network data for the NCP and to examinestatistics such as percentage of utilization, free buffer usage, and slowdown.

Collecting Network Data for the NCPUse the following procedure to start a collection on the NCP:

1. Select option 1 and N for NCP on the Primary Options panel (FNM00PRI) to displaythe Network Resource Type Selection panel (FNM01NET).

2. Select option 1 from the Network Resource Type Selection panel to display theResource List panel (FNM02RSL). You can also use fast path =1.1 to display theResource List panel.

3. Type S in the Option field next to NCP01 on the Resource List panel and press ENTERto display the first Network Start panel (FNM03STD), shown in Figure 32.

4. Complete the Network Start panel (FNM03STD) fields as described in this section. Usethe Tab key to move from field to field. Do not press ENTER until you have completedall of the following steps.




FNM03STD NPM V2R7 5655-043NETWORK MANAGEMENTNETWORK START

Command ===>


| Num Time |NCP Name ===> NCP01 �2� | 1 00:03:45 |Resource Name ===> NCP01 �3� | 2 00:07:30 |Dynamic Resource ===> NO �4� (Yes/No) | 3 00:15:00 |

| 4 00:30:00 || 5 01:00:00 |




Examining an NCP


6. Verify that NCP01 is displayed in the NCP Name field. �2�

7. Verify that NCP01 is displayed in the Resource Name field. �3�








12. Press ENTER to display the second Network Start panel (FNM03STM), shown inFigure 33. Use the FORWARD command to display the additional information on thethird Network Start panel (FNM03STM), shown in Figure 34 on page 114.

Note: The monitor criteria displayed on the FNM03STM panels varies, depending onthe type of resource you selected. .


Command ===>

Host Name = LOCAL NCP Name = NCP01 Resource Name = NCP01

Data Destinations NPMLOG VSAM SMF ALERT GLOBAL �8�Detail ===> YES YES NO N/A N/AMonitor ===> YES YES NO NO YES


Monitor Criteria LOW : HIGHFree buffers (0-2147483646) ====> 0 : 0CCU utilization (0-100) ====> 0 : 0% of time in slowdown (0-100) ====> 0 : 0Buffer utilization (0-100) ====> 0 : 0Processor utilization (0-100) ====> 0 : 0Shared data utilization (0-100) ====> 0 : 0

PF 1=HELP 3=END 7=BACKWARD 8=FORWARD 10=TOP 11=BOTTOMPF12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL


Examining an NCP


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

||

||

9.Iso

lating

Pro

blem

sin

aN

etwo

rk

Note: Monitor criteria entered in the HIGH column must be greater than the criteriaentered in the LOW column, with one exception. You can enter a zero in theHIGH column, regardless of what is entered in the LOW column. Entering azero in either the LOW or HIGH fields for a monitor turns off that portion of themonitor.

13. Indicate where to send the data in the Data Destinations Detail fields. �8�

Because you want to review the data online, type YES in the Data Destinations DetailVSAM field. For the purposes of this example, it does not matter whether you send thedata to the other destinations. See the NPM Reference for information about the otherdestinations.

14. Because you do not need to monitor the collection, leave the monitor criteria fields setto zero.

15. Press ENTER to start network data collection on the line. The Resource List panel(FNM02RSL) is redisplayed.

16. Use the REFRESH command to verify that the collection has been started.

Displaying Network Data for the NCPWait until NPM has collected enough data to help you determine the source of the problembefore displaying the data. Fifteen minutes of collection should be sufficient to average outoccasional spikes in the data. You are not able to see any data until at least one collectioninterval has elapsed.

Use the following procedure to display the data you collected for NCP01:

1. Type R in the Option field next to NCP01 on the Resource List panel (FNM02RSL).Press ENTER to display the Network Review panel (FNM02RVM), shown in Figure 35on page 115.


Command ===>

Host Name = LOCAL NCP Name = NCP01 Resource Name = NCP01

Data Destinations NPMLOG VSAM SMF ALERT GLOBAL �8�Detail ===> YES YES NO N/A N/AMonitor ===> YES YES NO NO YES


Monitor Criteria LOW : HIGHShared data utilization (0-100) ====> 0 : 0Program data utilization (0-100) ====> 0 : 0NNP Processor Util. (0-100) ====> 0 : 0NNP APPN Buffer Util. (0-100) ====> 0 : 0NNP APPN Memory Util. (0-100) ====> 0 : 0



Examining an NCP


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

||

2. Verify that LOCAL is displayed in the Host Name field. �1�

If the line were on another host, you would type the name of that host.

3. Verify that NCP01 is displayed in the Resource Name field. �2�

4. Verify that NCP is displayed in the Resource Type field. �3�


This option specifies the review file containing the data you collected. If you wanted tolook at data stored in another file, you would type the name of that file. See “ManagingNPM Data Files” on page 179 for information about NPM files.

6. Verify that today’s date is displayed in the Date fields. �5� and �6�




9. Press ENTER to display data for the resource specified on the Network Review panel(FNM02RVM). NPM displays the Network Review Data panel (FNM03RVP), shown inFigure 36 on page 116. See “Example: No Data Found (Error Message)” on page 180 ifyou receive the error message:FNM756E NO DATA FOUND FOR THIS REQUEST


Command ===>

Host Name ===> LOCAL �1�Resource Name ===> NCP01 �2� (Name)Resource Type ===> NCP �3� (Name/ALL only for Data Type=MONITOR)Review File Name ===> REVIEW �4� (REVIEW for active review file)






Examining an NCP


9.Iso

lating

Pro

blem

sin

aN

etwo

rk

The Network Review Data panel (FNM03RVP) is displayed when an NCP is specifiedon the Network Review panel (FNM02RVM). The panel data includes CCU utilization,slowdown, and buffer information.

For the purposes of this example, you need to look at only three fields:¶ CCU utilization (CCU Util)¶ Buffer usage (Free Buffer High)¶ Interval Slowdown (you can see this field by pressing PF5 (RIGHT))

If the CCU utilization is high, as in this example, the NCP is probably the source of thepoor response time problem. The NCP would also be indicated as the cause of theproblem if it had high buffer usage or if it was experiencing any slowdown.

10. Use the procedures described in “Stopping Collection for the Line” on page 110 to stopthe network collection on the NCP after you have reviewed the collected data.

Isolating Problems in an IP NetworkThe most critical resource in an IP network is a router. Router performance is the key todetermining the state of an IP network. NPM can be used to collect throughput data, CPUdata, and memory utilization rates.

Throughput Data CollectionStart data collection on a router and examine:

¶ ifInOctets, ifOutOctets, and ifSpeed. ifInOctets and ifOutOctets are counters that keeptrack of the number of octets (bytes) that are transported either into or out of aninterface layer. ifSpeed is represented as bits per second.

Note: Take care when doing this as there are types of interfaces whose speed (ifSpeed)is not a reflection of both in and out data transfer but applies only to one trafficdirection.

¶ ifInDiscards, ifInErrors, ifInUnknownProtos, ifOutDiscards, and ifOutErrors. The valuesof these counters or their deltas should be small.

FNM03RVP NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK REVIEW DATA

Command ===>Insert DYN to get dynamic (real time) dataHost Name = LOCAL Resource Name = NCP01 Data Type = NCPDate/Time: from: 09/30/00 08:45:00 to 09/30/00 09:00:00Slowdown Limit: 90

End Interval Resource CCU <- Free Buffer -> ChannelTime hh:mm:ss Name Util QLen High Low Interm Hold08:48:00 00:00:51 NCP01 63 1366 1366 1362 1 208:49:14 00:01:11 NCP01 63 1364 1365 1362 2 208:50:00 00:00:49 NCP01 63 1364 1364 1360 1 308:51:00 00:01:00 NCP01 63 1364 1365 1360 2 208:52:00 00:01:00 NCP01 63 1364 1364 1361 1 308:53:00 00:01:00 NCP01 63 1364 1365 1360 2 208:54:00 00:01:00 NCP01 63 1364 1364 1360 1 308:55:00 00:01:00 NCP01 63 1364 1365 1360 2 2

PF 1=HELP 3=END 5=RIGHT 9=SUMMARY 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 36. Network Review Data Panel (FNM03RVP)

Examining an NCP


¶ ifOutQLen. A large value for ifOutQLen implies that data is being queued up fortransfer possibly indicating either that an interface is being over utlized or that thesystem itself has a capacity problem.

CPU Data CollectionExamine the CPU data that is available for either Cisco or IBM NHD routers and make surethat CPU utilization does not reach too high a level. Acceptable levels of CPU utilizationrate depend on the router itself.

If ifOutQLen (outbound queue size per interface) becomes large, the reason could be eitherof the following:

¶ The system or the router, or both, is exceeding the capacity of the adapter or theinterface, or both (determined by calculating interface utilization).

¶ The system itself is becoming over utilized.

One symptom of this fact is a high CPU utilization rate.

Memory UtilizationAs with CPU utilization, memory availability and usage is important in determining whethera router is being over utilized. NPM can be used to collect this data for IBM NHD andCisco routers.

Cisco Channel Interface Processor (CIP) Card Data CollectionMany Cisco router installations have offloaded TN3270 processing onto the Cisco ChannelInterface Processor (CIP) processor.

Start a collection on a Cisco router that has CIP cards installed. NPM collects the Cisco CIPcard MIB data used to manage the Cisco Mainframe Channel Connection (CMCC) cards.Examine the CIP card performance data to determine the utilization of the card.

The list of values for the CIP card that can be obtained on a per CIP-card basis include thefollowing variables: Total Memory, Free Memory, CPU Utilization, CPU Load, Time SinceLast Reset, DMA Load, Major Software Revision, and Major Hardware Revision.

You can also set thresholds on the CIP card CPU utilization so as to monitor the CPUutilization and thus detect and react in a timely manner against critical utilization rates.

The CIP CPU Utilization is the average, over the last minute, of the percentage of time thatthis processor was running. This includes time spent on nonproductive polling and time usedby routine maintenance tasks. This value is not a measure of the processor’s ability tohandle more work, which is represented by the CPU Load information. The ability to handlemore work could also be affected by DMA Load.

Isolating an IP Network Problem


9.Iso

lating

Pro

blem

sin

aN

etwo

rk

Isolating an IP Network Problem


Isolating Poor Response Time on a LAN

By collecting session and network data NPM can help you isolate problems in an SNAnetwork. However, you may have additional architectures in your network. For example,your network may include several token rings linked by LAN bridges. You can use NPM tocollect NCP/Token Ring Interconnect (NTRI) data, LAN bridge data, and LAN segment datato determine the source of problems in these types of networks. The scenarios in this chapterstep you through the process you might follow to isolate the source of poor response timeon a LAN.

Example: Examining a LAN Network for Potential ProblemsSuppose that you need to isolate the source of poor response time for a terminal in sessionwith a CICS application over the network. The network contains two LAN segments (tokenrings A22 and BB5) linked by a LAN bridge. In this example, the name of the bridge isBRIDGE22. The user complaining of poor response time is on token ring A22, while thehost with the CICS application is on token ring BB5, shown in Figure 37.

You have collected session data on the CICS application. Your investigation uncovered datashowing high network transit time for CICS, but normal host transit time, indicating that thenetwork is the source of the problem. Now you need to isolate the problem to either theLAN bridge, token ring A22, or token ring BB5. You can do this by collecting LAN bridgedata and LAN segment data. LAN bridge data provides statistics for LAN bridge traffic,which includes lost frames and broadcast and non-broadcast frames per minute. LANsegment data provides the percentage of LAN segment utilization. The following sectionsexplain how to collect and display this data.

The numeric values used in the following scenarios as input data, such as high and lowthresholds for monitors, are provided as examples. You can change them according to yournetwork configuration and your specific needs.

Figure 37. Example Token Ring Network

10


10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

Setting Global LAN Bridge Collection ParametersIf you have not collected LAN bridge data before, you need to establish global conditionsbefore you start, such as destinations for the data and interval lengths. The parameters youspecify here apply globally to all LAN bridge collections until changed. You can choose touse the default parameters, or you can use the following procedure to change the parameters:

1. Select option 9 on the Primary Options panel (FNM00PRI) to display the ControlFunctions panel (FNM01OMN).

2. Select option 9 on the Control Functions panel to display the LAN Management Controlpanel (FNM02LMC).

Note: If the LAN bridge is not on your local host, enter the correct host name on theControl Functions panel before selecting option 9.

3. Select option 1 on the LAN Management Control panel to display the LAN Bridgecontrol panel (FNM02LBB), shown in Figure 38. You can also use fast path =9.9.1 todisplay the LAN Bridge control panel.

4. Complete the LAN Bridge Control fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you are instructed to do so.

5. Type YES in the VSAM column of the Data Destinations Detail and Monitor fields. �1�and �2�

Because you want to review the detail data and monitor events online, type YES in theVSAM field. For the purposes of this example, it does not matter whether you send thedata to any of the other destinations. See the NPM Reference for information about theother destinations.

6. Type NO in the Resolve Monitors field. �3�

Typing NO instructs NPM not to issue resolution messages. In this case, NPM issues amessage for each interval during which the data falls outside the thresholds. Thesemessages show the specific data that exceeded the threshold. Typing YES instructs NPMto issue an exception message when the data first falls outside the threshold and aresolution message when the data falls back within the thresholds.

FNM02LBB NPM V2R7 5655-043CONTROL FUNCTIONSLAN BRIDGE CONTROL

Command ===>

Host Name = LOCAL

Data Destinations NPMLOG VSAM ALERT GLOBALDetail ===> YES YES N/A N/A �1�Monitor ===> YES YES YES YES �2�

Resolve Monitors ===> NO �3� (Yes/No)

Interval Length (minutes) ===> 15 �4� (5,10,15,20,30,60)Interval Synch (minutes) ===> 0 �5� (Must be less than Interval Length)

To update the list of LAN resources, enter RECONFIG on command line


Figure 38. LAN Bridge Control Panel (FNM02LBB)

Examining a LAN Network


7. Type 15 in the Interval Length field. �4�

Specifying 15 minutes instructs NPM to collect data four times each hour. The exacttimes during the hour that data is collected is determined by the Interval Synch field.

8. Type 0 in the Interval Synch field. �5�

Typing a 0, the default for synchronizing LAN bridge collection, specifies that you wantcollection intervals to start on the hour. In this example, NPM collects data every 15minutes, the interval length, starting on the hour, and then 15 minutes, 30 minutes, and45 minutes after the hour.

9. Press ENTER to set the parameters for LAN bridge collection.

Starting LAN Bridge Data CollectionUse the following procedure to start collection on the bridge:

1. Use fast path =4.1 to display the LAN Bridge Selection panel (FNM02LBS), shown inFigure 39.

2. Locate the name of the LAN bridge that connects the two token rings.

If you cannot find the name easily, type LOCATE, a space, and a bridge name in theCommand field and press ENTER. The specified bridge name is displayed on the topline of the display area.

3. Type C in the Option field next to a bridge name. �1�

Option C allows you to change the collection status.

4. Press ENTER to display the LAN Bridge Collection Control panel (FNM03LBC),shown in Figure 40 on page 122.

This panel is used to specify, change, or view parameters for collecting LAN bridgedata, and to start or stop data collection. The Seg1/Br/Seg2 field shows that segment 1is token ring A22, the bridge is number 5 of the parallel bridges connecting the twosegments, and segment 2 is token ring BB5. Note that NPM always takes the lowestaddress for segment 1.

FNM02LBS NPM V2R7 5655-043LAN MANAGEMENT

LAN BRIDGE SELECTION

Command ===>

Host Name = LOCAL Bridge Count = 1Enter Command: LOCATE <Bridgename>, REFRESH, SORT <NAME/STATUS>or Option: C=Collection, P=Stop, D=Detail, R=Review, Z=Stop All

Bridge Collection Monitor Data BridgeOption Name Status Status Forwd Segments Number=>C�1� BRIDGE22 INACTIVE 0 A22 BB5 1


Figure 39. LAN Bridge Selection Panel (FNM02LBS)



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

5. Complete the LAN Bridge Collection Control (FNM03LBC) fields as described in thissection. Use the Tab key to move from field to field. Do not press ENTER until youare instructed to do so.

6. Type S in the Command field. �1�

Option S tells NPM to start collection.

7. Type 0 for the low threshold and 6000 for the high threshold in the Broadcast FramesThreshold fields. �2� and �3�

Broadcast frames are frames sent along all network paths, usually at NPM startup andduring routine communication. Set the broadcast frame thresholds for both token rings.

8. Type 0 for the low threshold and 6000 for the high threshold in the Non-BroadcastFrames Threshold fields. �4� and �5�

Non-broadcast frames are frames sent along a specific network path. These framesoccur more often and their numbers may vary more frequently than broadcast frames,depending on the network traffic. Set non-broadcast frame thresholds for both tokenrings.

9. Type 0 for low thresholds and type 60 for high thresholds in the Frames Lost Thresholdfields. �6� and �7�

Lost frames are frames that have been lost or discarded because of congestion orcorruption of the data. An ideal network has no lost frames, or sometimes, a very lownumber of lost frames.

10. Type 00:00:00 in the Start Time field. �8�

Typing 00:00:00 in this field causes collection to start immediately. Because you wantto find the source of the poor response time right away, you need to start collectingdata immediately. If you want to start collecting later, you need to specify a later time.For example, type 08:00:00 to start collecting at 8 a.m.

11. Type 00:00:00 in the Stop Time field. �9�

Typing 00:00:00 in this field causes NPM to collect data until you tell it to stop. Ifyou want to stop collection at a specific time, you need to enter that time. For example,type 17:30:00 to stop collecting at 5:30 p.m.

FNM03LBC NPM V2R7 5655-043LAN MANAGEMENT

LAN BRIDGE COLLECTION CONTROL

Command ===> S �1�Enter Option: S=Start, A=Alter, P=Stop, D=Detail, R=Review

Host Name = LOCAL Bridge Name = BRIDGE22 Collection Status = INACTIVEData Forwd = 0 Seg1/Br/Seg2 = A22 5 BB5 Monitor Status = N/A

Monitor Thresholds:Broadcast frames/minute from segment #1 ===> �2� 0 : 6000 (Low:High) �3�Broadcast frames/minute from segment #2 ===> �2� 0 : 6000 (Low:High) �3�Non-broadcast frames/minute from segment #1 ===> �4� 0 : 6000 (Low:High) �5�Non-broadcast frames/minute from segment #2 ===> �4� 0 : 6000 (Low:High) �5�Frames lost/minute from segment #1 ===> �6� 0 : 60 (Low:High) �7�Frames lost/minute from segment #2 ===> �6� 0 : 60 (Low:High) �7�

Start Time ===> 00 : 00 : 00 �8� (hh:mm:ss)Stop Time ===> 00 : 00 : 00 �9�Daily ===> YES �10� (Yes/No)PF 1=HELP 3=END 12=RETURN 15=NCP 16=ROUTER 17=LINEPF20=APPL 24=TERMINAL

Figure 40. LAN Bridge Collection Control Panel (FNM03LBC)




Because you are trying to isolate the problem immediately, you do not need to collectdata on a daily basis.

You would collect data daily if you wanted to establish trends. In this case, type YES inthis field and specify both a start and a stop time in the two previous fields.

13. Press ENTER to start the LAN bridge collection.

NPM issues a message to indicate that it has started collection. The collection status changesto ACTIVE while the monitor status changes to NORMAL.

Setting Global LAN Segment Collection ParametersIf you have not collected LAN segment data before, you need to establish global conditionsbefore you start, such as destinations for the data and interval lengths. The parameters youspecify here apply globally to all LAN segment collections until you change them. You canchoose to use the default parameters, or you can use the following procedure to change theparameters:

1. Select option 9 on the Primary Options panel (FNM00PRI) to display the ControlFunctions panel (FNM01OMN).

2. Select option 9 on the Control Functions panel to display the LAN ManagementControl panel (FNM02LMC).

Note: If the LAN segment is not on your local host, enter the correct host name on theControl Functions panel before selecting option 9.

3. Select option 2 on the LAN Management Control panel to display the LAN SegmentControl panel (FNM02LSB), shown in Figure 41. You can also use fast path =9.9.2 todisplay the LAN Segment Control panel.

4. Complete the LAN Segment Control panel fields as described in this section. Use theTab key to move from field to field. Do not press ENTER until you are instructed to doso.

FNM02LSB NPM V2R7 5655-043CONTROL FUNCTIONSLAN SEGMENT CONTROL

Command ===>

Host Name = LOCAL

Data Destinations NPMLOG VSAM ALERT GLOBALDetail ===> YES YES N/A N/A �1�Monitor ===> YES YES YES YES �2�

Resolve Monitors ===> NO (Yes/No) �3�

Interval Length (minutes) ====> 15 �4� (5,10,15,20,30,60)Interval Synch (minutes) ====> 0 �5� (Must be less than Interval Length)Sampling Interval (seconds) ====> 40 �6� (40-300)

To update the list of LAN resources, enter RECONFIG on command line


Figure 41. LAN Segment Control Panel (FNM02LSB)



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

5. Type YES in the VSAM column of the Data Destinations Detail and Monitor fields. �1�and �2�

Because you want to review the detail data and monitor events online, type YES in theVSAM fields. For the purposes of this example, it does not matter whether you sendthe data to any of the other destinations. See the NPM Reference for information aboutthe other destinations.

6. Type NO in the Resolve Monitors field. �3�

Typing NO instructs NPM not to issue resolution messages. In this case, NPM issues amessage for each interval during which the data falls outside the thresholds. Thesemessages show the specific data that exceeded the threshold. Typing YES instructs NPMto issue an exception message when the data first falls outside the threshold and aresolution message when the data falls back within the thresholds.

7. Type 15 in the Interval Length field. �4�

Specifying 15 minutes tells NPM to collect data four times an hour. The exact timesduring the hour that data is collected is determined by the Interval Synch field.

8. Type 0 in the Interval Synch field. �5�

Typing a 0, the default for synchronizing LAN segment collection, specifies that youwant collection intervals to start on the hour. In this example, NPM collects data every15 minutes, the interval length, starting on the hour, and then 15 minutes, 30 minutes,and 45 minutes after the hour.

9. Type 40 in the Sampling Interval field. �6�

Specifying 40 seconds instructs NPM to ask LAN Network Manager for segmentutilization samples every 40 seconds. NPM uses this sample data to calculate thesegment utilization percentage. You may encounter system performance problems if youare collecting data on a large number of segments. You can increase the size of thesampling interval to avoid these problems.

10. Press ENTER to set these parameters for LAN segment collection.

Starting LAN Segment Data CollectionUse the following procedure to start collection on the segments:

1. Use fast path =4.2 to display the LAN Segment Selection panel (FNM02LSS), shownin Figure 42 on page 125.



2. Locate the LAN segment number that corresponds to token ring A22.

If you cannot find the number easily, type LOCATE, a space, and a segment name in theCommand field and press ENTER. The specified segment is displayed on the top line.

3. Type C in the Option fields next to the A22 and BB5 segment numbers. Option Callows you to change the collection status.

4. Press ENTER to display the LAN Segment Collection Control panel (FNM03LSC),shown in Figure 43.

This panel is used to specify, change, or view parameters for collecting LAN segmentdata, and to start or stop data collection.

Verify that A22 is displayed in the segment number field, and complete the appropriatefields as described in this section. Use the Tab key to move from field to field. Do notpress ENTER until you are instructed to do so.

FNM02LSS NPM V2R7 5655-043LAN MANAGEMENT

LAN SEGMENT SELECTION

Command ===>

Display = 09:29:13 Interval = N/AHost Name = LOCAL Segment Count = 2Enter Command: LOCATE <Segment>, REFRESH, SORT <NUMBER/STATUS/UTIL>or Option: C=Collection, P=Stop, D=Detail, R=Review, Z=Stop All

Segment Collection Monitor Data <--- Segment Utilization ---->Option Number Status Status Forwd Previous Current Last Sample=> C A22 INACTIVE 0 26 % 35 % 8 %=> C BB5 INACTIVE 0 33 % 37 % 7 %


Figure 42. LAN Segment Selection Panel (FNM02LSS)

FNM03LSC NPM V2R7 5655-043LAN MANAGEMENT

LAN SEGMENT COLLECTION CONTROL

Command ===> S �1�Enter Option: S=Start, A=Alter, P=Stop, D=Detail, R=ReviewHost Name = LOCAL Segment Number = A22 Collection Status = INACTIVEData Forwd = 0 Utilization = Monitor Status = N/A

Monitor Thresholds:Segment Utilization Percentage �2� ===> 20 : 60 (Low:High)

Start Time ===> 00 : 00 : 00 �3� (hh:mm:ss)Stop Time ===> 00 : 00 : 00 �4�Daily ===> NO �5� (Yes/No)


Figure 43. LAN Segment Collection Control Panel (FNM03LSC)



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

5. Type S on the Command line. �1�

Option S tells NPM to start collection.

6. Type 20 for the low threshold and 60 for the high threshold in the Segment UtilizationPercentage field. �2�

Segment utilization percentage is a parameter that reflects how much your LANsegment is utilized.

7. Type 00:00:00 in the Start Time field. �3�

Typing 00:00:00 in this field causes collection to start immediately. Because you wantto find the source of the poor response time right away, you need to start collectingdata immediately. If you wanted to start collecting later, you would specify a later time.For example, type 08:00:00 to start collecting at 8 a.m.

8. Type 00:00:00 in the Stop Time field. �4�

Typing 00:00:00 in this field causes NPM to collect data until you tell it to stop. Ifyou wanted to stop collection at a specific time, you would enter that time. Forexample, type 17:30:00 to stop collecting at 5:30 p.m.


Because you are trying to isolate the problem immediately, you do not need to collectdata on a daily basis.

You would collect data daily if you wanted to establish trends. In this case, type YES inthis field and specify both a start and a stop time in the two previous fields. NPMwould collect data every day between these two times.

10. Press ENTER to start LAN segment collection.

Collection on token ring A22 is started at this point. NPM issues a message to indicatethat it has started collection. The collection status changes to ACTIVE and the monitorstatus changes to NORMAL.

11. Use the END command to redisplay the LAN Segment Collection Control panel(FNM03LSC). Token ring BB5 is displayed in segment number field. Repeat steps 5through 10 to start collection on token ring BB5.

Displaying Data for the LAN BridgeBefore viewing the data, you need to wait until NPM has collected enough data to help youdetermine the source of the problem. Fifteen minutes worth of collection should be sufficientto average out occasional spikes in the data. Data is not displayed until at least onecollection interval has elapsed.

Use the following procedure to display the LAN bridge data:

1. Use fast path =4.9 to display the LAN Review panel (FNM02LBM).



2. Complete the LAN Review panel fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you are instructed to do so.


4. Type BRIDGE22 in the LAN Resource Name field. �2�

5. Type 1 in the LAN Resource Type field. �3�

This tells NPM that the resource is a bridge. You would have typed 2 if it were asegment.

6. Type REVIEW in the Review File Name field. �4�

This instructs NPM to get the data from the current review file, the destination youspecified when setting the global parameters for LAN segment data collection.

7. Type today’s date in the Date fields. �5� and �6�





10. Press ENTER to display the data on the LAN Bridge Data Detail Panel (FNM03LBR),shown in Figure 45 on page 128. See “Example: No Data Found (Error Message)” onpage 180 if you receive the following error message:FNM756E NO DATA FOUND FOR THIS REQUEST

FNM02LBM NPM V2R7 5655-043LAN MANAGEMENTLAN REVIEW

Command ===>

Host Name ===> LOCAL �1�LAN Resource Name ===> BRIDGE22 �2� (Name/Monitor)LAN Resource Type ===> 1 �3� (1=Bridge, 2=Segment)Review File Name ===> REVIEW �4� (REVIEW for active review file)





Figure 44. LAN Review Panel (FNM02LBM)



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

The LAN Bridge Data Detail panel (FNM03LBR) displays the data you have been collectingfor the LAN bridge. Use the Seg1/Br/Seg2 field to determine which segment corresponds towhich token ring. Examine the data for unusually high or low values. If the number offrames transmitted or the number of frames lost is highlighted, that number exceedsthresholds you specified on the LAN Bridge Collection Control panel (FNM03LBC). SeeFigure 40 on page 122.

A second detail panel, the LAN Bridge Lost Frames Detail panel (FNM03LB2) categorizesthe number of lost frames by type of error. Use the RIGHT command to display this panel,shown in Figure 46. Use the LEFT command to return to the LAN Bridge Data Detail panel.

The LAN Bridge Data Detail and LAN Bridge Lost Frames Detail panels can help youisolate your problem to one of the following areas:

FNM03LBR NPM V2R7 5655-043LAN MANAGEMENT

LAN BRIDGE DATA DETAIL

Command ===>

Host Name = LOCALBridge Name = BRIDGE22 Review File = REVIEW Seg1/Br/Seg2 = A22 5 BB5

Date/Time: from 09/30/00 09:30:00 to 09/30/00 10:15:00

BC Frm/Min Non-BC Frm/Min Lost FramesDate Time Interval Seg#1 Seg#2 Seg#1 Seg#2 Seg#1 Seg#2

09/30/00 09:30:00 00:14:59 0 0 0 0 0 009/30/00 09:45:00 00:15:00 801 318 191 9 18 009/30/00 09:59:59 00:14:59 64 111 281 326 0 009/30/00 10:15:00 00:15:01 451 328 618 181 1 0


Figure 45. LAN Bridge Data Detail Panel (FNM03LBR)

FNM03LB2 NPM V2R7 5655-043LAN MANAGEMENT

LAN BRIDGE LOST FRAMES DETAIL

Command ===>

Host Name = LOCALBridge Name = BRIDGE22 Review File = REVIEW Seg1/Br/Seg2 = A22 5 BB5Date/Time: from 09/30/00 09:30:00 to 09/30/00 10:15:00

Inoperative Congestion Link Error OtherDate Time Interval Seg#1 Seg#2 Seg#1 Seg#2 Seg#1 Seg#2 Seg#1 Seg#209/30/00 09:30:00 00:14:59 0 0 0 0 ----- ----- 0 009/30/00 09:45:00 00:15:00 18 0 0 0 ----- ----- 0 009/30/00 09:59:59 00:14:49 0 0 0 0 ----- ----- 0 009/30/00 10:15:00 00:14:49 1 0 0 0 ----- ----- 0 0

PF 1=HELP 3=END 4=LEFT 9=SUMMARY 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 46. LAN Bridge Lost Frames Detail Panel (FNM03LB2)



¶ The LAN bridge: If the number of lost frames is high, determine if most of theframes are lost due to congestion. High congestion, especially when the number offrames transmitted is below the high threshold, indicates a problem with the LANbridge.

¶ Token ring A22: Token ring A22 may be the problem if token ring BB5 shows ahigh number of lost frames listed under INOPERATIVE. This statistic indicates that theframes could not be forwarded from token ring BB5 to token ring A22 because A22 wasinoperative. Check segment utilization on this token ring and whether the value seems tobe too high. There are probably problems with that segment if its utilization is greaterthan 80 percent. Alert your LAN administrator.

¶ Token ring BB5: Token ring BB5 may be the problem if token ring A22 shows ahigh number of lost frames listed under INOPERATIVE. This statistic indicates that theframes could not be forwarded from token ring A22 to token ring BB5 because BB5was inoperative. Check segment utilization on this token ring and whether the valueseems to be too high. There are probably problems with that segment if its utilization isgreater than 80 percent. Alert your LAN administrator.

¶ TIC (token-ring interface coupler) or the NCP: The TIC or the NCP may be causingpoor network response time if the LAN bridge statistics do not indicate high traffic or anunusually high number of lost frames, and token rings work correctly. Continue tocollect data to further isolate the problem.

In this example, the number of lost frames for token ring A22 indicates that the problemcould lie with token ring BB5. However, the number of lost frames is only 2 percent of theframes forwarded, and traffic does not exceed the specified high threshold, (6000 frames foreach token ring).

Continue your analysis by examining the collected data for the A22 and BB5 segments, asdescribed in “Displaying Data for the LAN Segment”.

Displaying Data for the LAN SegmentUse the following procedure to display the LAN segment utilization for token ring A22:

1. Use fast path =4.9 to display the LAN Review panel (FNM02LBM).



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

2. Complete the LAN Review panel fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you are instructed to do so.


4. Type A22 in the LAN Resource Name field. �2�

5. Type 2 in the LAN Resource Type field. �3�

This tells NPM that the resource is a segment. If it were a bridge you would have typed1.


This instructs NPM to get the data from the current review file, the destination youspecified when setting the global parameters for LAN segment data collection.






10. Press ENTER to display the data on the LAN Segment Detail Data panel(FNM03LSR), shown in Figure 48 on page 131. See “Example: No Data Found (ErrorMessage)” on page 180 if you receive the following error message:FNM756E NO DATA FOUND FOR THIS REQUEST

The LAN Segment Detail Data panel (FNM03LSR) displays segment utilization fortoken ring A22.

FNM02LBM NPM V2R7 5655-043LAN MANAGEMENTLAN REVIEW

Command ===>

Host Name ===> LOCAL �1�LAN Resource Name ===> A22 �2� (Name/Monitor)LAN Resource Type ===> 2 �3� (1=Bridge, 2=Segment)Review File Name ===> REVIEW �4� (REVIEW for active review file)





Figure 47. LAN Review Panel (FNM02LBM)



Segment utilization data reflects how much the LAN segment is being utilized. Astatistical degree of confidence is displayed next to the utilization percentage. This isthe probability that the utilization displayed differs from the actual segment utilizationvalue.

NPM calculates LAN segment utilization during a collection interval by using sampleutilization data gathered by the LAN Network Manager. The statistical degree ofconfidence is strictly related to the number of samples of data received during thecollection interval. If the number of samples that NPM receives from the LAN NetworkManager is high, the LAN segment utilization calculated is more precise and a verysmall statistical degree of confidence is displayed. If the number of samples available islow, it is more likely that the segment utilization calculated is different from the actualvalue.

High values of percentage utilization suggest that the token ring is overloaded, andheavy traffic is flowing on the LAN segment. If you notice that this is a recurrentsituation, it may be that too many stations are distributed on the ring, and you shouldbreak the segment into two separate segments.

Low values of the utilization percentage suggests that the token ring is under utilized,and very low traffic is flowing on the LAN segment. If you notice that this is arecurring situation, it may indicate that too few stations are distributed on the ring. Youshould delete that segment and redistribute the stations on other LAN segments.

The data displayed on this panel shows that the utilization percentage in each intervalfalls between the thresholds set on the LAN Segment Collection Control panel(FNM03LSC) shown in Figure 43 on page 125. Also, the high number of samples takenensure a very low statistical degree of confidence. This means you can be confident thatthe data displayed is very close to the actual values. These facts indicate that token ringA22 is working correctly. This conclusion is consistent with the findings at the end of“Displaying Data for the LAN Bridge” on page 126. That analysis of LAN bridge dataalready provided preliminary information about the correct operation of the token rings.

FNM03LSR NPM V2R7 5655-043LAN MANAGEMENT

LAN SEGMENT DATA DETAIL

Command ===>

Host Name = LOCALSegment Number = A22 Segment Type = TR-16M Review File = REVIEWDate/Time: from 09/30/00 09:30:00 to 09/30/00 10:15:00

Segment SamplesDate Time Interval Utilization Taken09/30/00 09:30:00 00:15:00 50 +/- 5% 2209/30/00 09:45:00 00:15:00 55 +/- 3% 2109/30/00 09:59:59 00:15:00 58 +/- 5% 2209/30/00 10:15:01 00:15:00 48 +/- 3% 21

PF 1=HELP 3=END 9=SUMMARY 12=RETURN 15=NCP 16=ROUTERPF17=LINE 20=APPL 24=TERMINAL

Figure 48. LAN Segment Data Detail Panel (FNM03LSR)



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

11. Use fast path =4.9 to redisplay the LAN Review panel (FNM02LBM). Complete thepanel using the same procedure described for token ring A22. Remember to type BB5 inthe Resource Name field.

12. Press ENTER to display utilization data for token ring BB5 on the LAN Segment DataDetail panel (FNM03LSR), shown in Figure 49.

If you look at the segment utilization percentage and the statistical degree of confidence youcan conclude that token ring BB5 is also working properly. This is consistent with what weconcluded at the end of “Displaying Data for the LAN Bridge” on page 126. In that section,the analysis of LAN bridge data provided preliminary information about the correctoperation of the token rings.

The LAN bridge and LAN segment data analysis show that the bridge and the two segmentsare operating correctly. Therefore, the problem could be the TIC or the NCP. You need tocollect more data to determine the cause of poor network response time.

Stopping Collection on the LAN BridgeUse the following procedure to stop LAN bridge data collection:

1. Use fast path =4.1 to display the LAN Bridge Selection panel (FNM02LBS), shown inFigure 50 on page 133.

FNM03LSR NPM V2R7 5655-043LAN MANAGEMENT

LAN SEGMENT DATA DETAIL

Command ===>

Host Name = LOCALSegment Number = BB5 Segment Type = TR-16M Review File = REVIEWDate/Time: from 09/30/00 09:30:00 to 09/30/00 10:15:00

Segment SamplesDate Time Interval Utilization Taken09/30/00 09:30:00 00:15:00 55 +/- 5% 2109/30/00 09:45:00 00:15:00 58 +/- 3% 2209/30/00 09:59:59 00:15:00 52 +/- 5% 2109/30/00 10:15:01 00:15:00 55 +/- 3% 22

PF 1=HELP 3=END 9=SUMMARY 12=RETURN 15=NCP 16=ROUTERPF17=LINE 20=APPL 24=TERMINAL

Figure 49. LAN Segment Data Detail Panel (FNM03LSR)



2. Type P in the Option field �1� next to the name of the LAN bridge and press ENTER.NPM issues a message indicating it has stopped collection.

Stopping Collection on the LAN SegmentUse the following procedure to stop LAN segment data collection:

1. Use fast path =4.2 to display the LAN Segment Selection panel (FNM02LSS), shown inFigure 51.

2. Type P in the Option field next to the names of the LAN segments and press ENTER.NPM issues a message indicating it has stopped collection.

FNM02LBS NPM V2R7 5655-043LAN MANAGEMENT

LAN BRIDGE SELECTION

Command ===>

Host Name = LOCAL Bridge Count = 1Enter Command: LOCATE <Bridgename>, REFRESH, SORT <NAME/STATUS>or Option: C=Collection, P=Stop, D=Detail, R=Review, Z=Stop All

Bridge Collection Monitor Data BridgeOption Name Status Status Forwd Segments Number=> P�1� BRIDGE22 STARTED NORMAL 0 A22 BB5 1


Figure 50. LAN Bridge Selection Panel (FNM02LBS)

FNM02LSS NPM V2R7 5655-043LAN MANAGEMENT

LAN SEGMENT SELECTION

Command ===>

Display = 10:35:00 Interval = 10:30:00Host Name = LOCAL Segment Count = 2Enter Command: LOCATE <Segment>, REFRESH, SORT <NUMBER/STATUS/UTIL>or Option: C=Collection, P=Stop, D=Detail, R=Review, Z=Stop All

Segment Collection Monitor Data <-- Segment Utilization -->Option Number Status Status Forwd Previous Current Last Sample=> P A22 STARTED NORMAL 0 48 % 41 % 43 %=> P BB5 STARTED NORMAL 0 53 % 47 % 54 %


Figure 51. LAN Segment Selection Panel (FNM02LSS)



10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

Example: Examining a TIC for Potential ProblemsIn the previous example, you investigated a complaint from a LAN customer who is gettingpoor response time while using CICS. The customer’s terminal is on token ring A22, and theCICS application is running on a host connected to token ring BB5, as shown in Figure 52.

Session data collected on CICS indicates a problem on the network. An analysis of the LANbridge and segment data, shows that the bridge and the token rings are working correctly.The problem might involve the token ring interface coupler (TIC) or the NCP. The name ofthe TIC in this example is TIC01. The name of the NCP (or CCU) is NCP01. You now needto collect NCP/Token Ring Interconnect (NTRI) data on the TIC to further isolate the causeof the problem. The following sections explain the steps in this process.

Note: Although NTRI collection relates to a connection to a token ring, it is a type ofnetwork collection. Therefore, the global collection parameters described in “SettingGlobal LAN Bridge Collection Parameters” on page 120, and in “Setting Global LANSegment Collection Parameters” on page 123 do not apply here.

Starting NTRI Data CollectionUse the following procedure to start NTRI collection on the TIC:

1. Use fast path =1.4 to display the Network Start panel (FNM03STD), shown inFigure 53 on page 135.

Figure 52. Example Token Ring Network

Examining a TIC


2. Complete the Network Start panel (FNM03STD) fields as described in this section. Usethe Tab key to move from field to field. Do not press ENTER until you are instructedto do so.


The interval number determines how long NPM waits each time it collects data. Yourequest the shortest interval by typing 1 in this field.

4. Type NCP01, the name of the CCU on token ring BB5 to which the CICS host isconnected, in the NCP Name field. �2�

5. Type TIC01, the name of the line (TIC) connecting the CCU and token ring BB5, in theResource Name field. �3�

By collecting data on the line connecting the CCU and token ring, you can determinewhether the NCP (CCU) or TIC (line) is the source of the poor response time.







Because you are trying to isolate the problem immediately, you do not need to collectdata on a daily basis. You would collect data daily if you want to establish trends.


FNM03STD NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK START

Command ===>


| Num Time |NCP Name ===> NCP01 �2� | 1 00:03:45 |Resource Name ===> TIC01 �3� | 2 00:07:30 |Dynamic Resource ===> NO �4� (Yes/No) | 3 00:15:00 |

| 4 00:30:00 || 5 01:00:00 |




Examining a TIC


10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

11. Indicate where to send the data in the Detail Data Destination fields. �8�

Because you want to review the data online, type YES in the data destination VSAMfields. For the purposes of this example, it does not matter whether you send the data tothe other destinations. See the NPM Reference for information about the otherdestinations.

12. Press ENTER to start NTRI collection on the TIC.

Displaying the NTRI DataPerform the following procedure when NPM has collected enough data. Fifteen minutesworth of collection should be sufficient to average out occasional spikes in the data. Data isnot displayed until at least one collection interval has passed.

Use the following procedure to display the NTRI data:

1. Use fast path =1.7 to access the Network Review Data panel (FNM02RVM), shown inFigure 55 on page 137.


Command ===>

Host Name = LOCAL NCP Name = NCP01 Resource Name = TIC01

Data Destinations NPMLOG VSAM SMF ALERT GLOBAL �8�Detail ===> NO YES NO N/A N/AMonitor ===> NO YES NO NO NO

Resolve Monitors ===> YES (Yes/No)

Monitor Criteria LOW : HIGHPDUs/minute (0-2147483646) ====> 0 : 0Bytes/second (0-2147483646) ====> 0 : 0Outbound queue length (0-2147483646) ====> 0 : 0% of PDUs retransmitted (0-100) ====> 0 : 0Bytes transmitted/second (0-2147483646) ====> 0 : 0Bytes received/second (0-2147483646) ====> 0 : 0



Examining a TIC


2. Complete the Network Review panel fields as described in this section. Use the Tabkey to move from field to field. Do not press ENTER until you are instructed to do so.

3. Type LOCAL in the Host field. �1�

4. Type the name of the TIC in the Resource Name field. �2�

5. Verify that PHYLINK is displayed in the Resource Type field. �3�


This option specifies the current, active review file. If you wanted to look at data storedin another file, you would type the name of that file.






10. Press ENTER to display the collected data on the Network Review Data for NTRIResources panel (FNM03RVS), shown in Figure 56 on page 138. Examine the statisticsfor any unusually high or low figures.


Command ===>

Host Name ===> LOCAL �1�Resource Name ===> TIC01 �2� (Name)Resource Type ===> PHYLINK �3� (Name/ALL only for Data Type=MONITOR)Review File Name ===> REVIEW �4� (REVIEW for active review file)




PF 1=HELP 2=RESTYPE 3=END 12=RETURN 15=NCP 16=ROUTERPF17=LINE 20=APPL 24=TERMINAL


Examining a TIC


10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

The information displayed on the Network Review Data for NTRI Resources panel can helpyou isolate your problem to one of the following areas:

¶ The TIC: If the TIC utilization (TIC Util field) or the congestion count (Congest Countfield) is high, the TIC is the probable cause of the poor response time. A TIC problem isalso indicated by a high number of timeouts accompanied by low TIC utilization.

¶ The Host or the NCP: The host or NCP may be causing the problem if the outboundqueue length (Queue Length field) or the number of retransmissions (Retransmit IFramesor Bytes fields) is too high. These statistics indicate that the TIC is having troublesending frames to the NCP.

In this example, the TIC is probably causing the problem because TIC utilization for bothintervals is very high. Alert your system programmer.

Stopping NTRI Data CollectionUse the following procedure to stop NTRI data collection after you have viewed networkdata for the TIC:

1. Use fast path =1.6 to display the Network Stop panel (FNM03STD), shown inFigure 57 on page 139.

FNM03RVS NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK REVIEW DATA FOR NTRI RESOURCES

Command ===>Insert DYN to get dynamic (real time) dataHost Name = LOCAL Resource Name = TIC01 Data Type: PHYLINK DETAILDate/Time: from 09/30/00 11:45:00 to 09/30/00 12:00:00

End Interval Resource Queue IFrames Bytes Time Retransmit TICTime hh:mm:ss Name Length /Min /Sec Outs IFrames Bytes Util10:45:00 00:15:00 TIC01 0 21 108 0 0 8311:00:00 00:15:00 TIC01 0 76 244 0 0 76


Figure 56. Network Review Data for NTRI Resources Panel (FNM03RVN)

Examining a TIC


2. Complete the Network Stop panel (FNM03STD) fields as described in this section. Usethe Tab key to move from field to field. Do not press ENTER until you have completedall of the following steps.


4. Type NCP01 in the NCP Name field. �2�

5. Type TIC01 in the Resource Name field. �3�


7. Type the start time of the collection you want to stop in the Start Time field. �5�

8. Type the stop time of the collection you want to stop in the Stop Time field. �6�


10. Press ENTER to stop the specified collection.

FNM03STD NPM V2R7 5655-043NETWORK MANAGEMENTNETWORK STOP

Command ===>


| Num Time |NCP Name ===> NCP01 �2� | 1 00:03:45 |Resource Name ===> TIC01 �3� | 2 00:07:30 |Dynamic Resource ===> NO �4� (Yes/No) | 3 00:15:00 |

| 4 00:30:00 || 5 01:00:00 |



Figure 57. Network Stop Panel (FNM03STD)

Examining a TIC


10.Iso

lating

Po

or

Resp

on

seTim

eo

na

LA

N

Examining a TIC


Isolating Performance Problems in theHost

The scenarios provided in this chapter describe how to use NPM to identify performanceproblems in the host.

Note: Before using the procedures described in this chapter, review the network and LANenvironment scenarios provided in “Isolating Performance Problems in a Network” onpage 95 and “Isolating Poor Response Time on a LAN” on page 119 to verify thatyou have a problem in the host.

Example: Examining an Application for Potential ProblemsThe scenario “Example: Isolating the Problem to the Host or the Network” on page 95investigated a customer’s complaint about poor response time for a terminal when usingCICS. You collected session data on the terminal, LU032, which is connected to NCP01 asshown in Figure 58.

The session data gathered in the earlier scenario indicated that host transit time wasconsiderably greater than network transit time.

You can use NPM to gather more information about the problem. For example, you cancollect information to determine whether the problem lies with the terminal, with VTAM, orwith the application in session with the terminal. The steps used to collect NPM session datafor an application are described in the following sections.

Starting Session Collection on the ApplicationUse the following procedure to start session collection on the application:



11


11.Iso

lating

Pro

blem

sin

the

Ho

st

2. Select option 1 on the Response Times panel to display the Start Session panel(FNM02SCL), shown in Figure 59. You can also use fast path =2.1 to display the StartSession panel.

3. Complete the Start Session panel fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you are instructed to do so.

4. Type the name of the application in the Resource Name field. �1�

The name you type should be the name of the application that is experiencing poorresponse time. The name of the application is CICS in this example.

5. Type the name of the NCP to which the LU is connected in the Node Name field. �2�

The name of the NCP is NCP01 in this example. This step is not necessary if the LUhas previously been defined to NPM.


Although you interact primarily with the local NPM, you can communicate withanother NPM. For example, you need to do this if the LU is on another host. Type=2.8 on the Command line and press ENTER to display the Performance StatusAnalysis panel (FNM02PDT). Verify that the Host Name field is blank on this paneland press ENTER to display a list of accessible hosts. Type =2.1 on the Command lineand press ENTER to return to the Start Session panel (FNM02SCL).

7. Type Y in the Session Statistics field. �4�

This option causes the collected data to be written to the current session file so that youcan retrieve it later.

8. Type 0 in the VTAM Log field. �5�

This option inhibits the logging of PIUs to the VTAM log.

9. Type YES in the Minimum PIU Trace field. �6�

This option causes minimum (abbreviated) PIUs to be written to the VTAM log.

10. Type NO in the GTF Trace field. �7�

FNM02SCL NPM V2R7 5655-043RESPONSE TIMESSTART SESSION

Command ===>Resource Name ===> CICS �1�Node Name ===> NCP01 �2�Host Name ===> LOCAL �3�Dynamic Resource ===> NO (Yes/No)Session Statistics ===> Y �4� (Yes/No/Vol/Xcl/Rsp)VTAM Log ===> 0 �5� (0/1/2/3)Minimum PIU Trace ===> YES �6� (Yes/No)GTF Trace ===> NO �7� (Yes/No)Transit ThresholdsOperator ===> .00 : 3.50 (Low:High) �8�Network ===> .00 : 2.00 (Low:High) �9�Host ===> .00 : 2.00 (Low:High) �10�

Distribution Bounds ===> 5.00 : 10.00 : 20.00 : 30.00 �11�Start Time ===> 00 : 00 : 00 (hh:mm:ss)Stop Time ===> 00 : 00 : 00Daily ===> NO �12� (Yes/No)


Figure 59. Start Session Panel (FNM02SCL)

Examining an Application


11. Type .00 in the low Operator, Network, and Host Transit Threshold fields. �8�, �9�,and �10�

12. Type 3.50 in the high Operator Transit Threshold field. �8�

If the operator transit time exceeds the high threshold that you set (in this case, 3.5seconds) at the end of the data collection interval, any session data that falls outsidethis value is highlighted on the session analysis display.

13. Type 2.00 in the high Network and Host Transit Threshold fields. �9� and �10�

If the network or the host transit time exceeds the high thresholds that you set (in thiscase, 2 seconds) at the end of the data collection interval, any session data that fallsoutside this value is highlighted on the session analysis display.

14. Type 5.00, 10.00, 20.00, and 30.00 in the Distribution Bounds fields. �11�

15. Verify that the Start Time field displays all zeros.

All zeros (the default) in this field causes NPM to start collection immediately. Becauseyou want to find the source of the poor response time right away, you need to startcollecting data immediately. Specify a later time if you want to start collecting later.For example, type 08:00:00 to start collecting at 8 a.m..

16. Verify that the Stop Time field displays all zeros.

All zeros (the default) in this field causes NPM to collect data until you tell it to stop.If you wanted to stop collection at a specific time, you would specify a stopping time.For example, type 17:00:00 to stop collecting at 5 p.m.. Remember that the stop timemust always be greater than the start time.



You would collect data daily if you wanted to determine trends. For example, youwould type YES in the Daily field, and specify both a start and stop time, to collect dataevery day between the two times.

18. Press ENTER to display the Session Monitor Selection Panel (FNM03SAS), shown inFigure 60 on page 144. This panel allows you to set up monitors for the displayedmonitor data type.



11.Iso

lating

Pro

blem

sin

the

Ho

st

19. Do not set any monitors in this example. Press ENTER to start session collection. NPMissues a message indicating it has started collection.

Displaying Data for the ApplicationBefore viewing the data, you need to wait until NPM has collected enough data to help youdetermine the source of the problem. Fifteen minutes of collection should be sufficient toaverage out occasional spikes in the data. You are not able to see any data until at least onecollection interval has elapsed.

Enter =9.4;down in the Select Option or Command field of any online panel to display theSummary Display panel (FNM02OPS). Review the Session Interval field on this panel todetermine the session collection interval for your system.

Use the following procedure to display data collected for an application:


2. Select option 7 on the Response Times panel to display the Session Analysis panel(FNM02SAN), shown in Figure 61 on page 145. You can also use fast path =2.7 todisplay the Session Analysis panel.

3. Complete the Session Analysis panel fields as described in this section. Use the Tab keyto move from field to field. Do not press ENTER until you are instructed to do so.

FNM03SAS NPM V2R7 5655-043RESPONSE TIMES

SESSION MONITOR SELECTION

Command ===>Enter Monitor Criteria for Resource LU032 Criteria

Low : HighAverage Operator Transit Time ===> .00 : .00Average Host Transit Time ===> .00 : .00Average Network Transit Time ===> .00 : .00Maximum Operator Transit Time ===> .00 : .00Maximum Host Transit Time ===> .00 : .00Maximum Network Transit Time ===> .00 : .00% of Operator Trans Exceeding Transit Thresholds ===> 0 : 0% of Host Trans Exceeding Transit Threshold ===> 0 : 0% of Network Trans Exceeding Transit Threshold ===> 0 : 0Number of Active LUs in a Summary Record ===> 0 : 0Average Number of PIUs per Minute ===> 0 : 0Average Number of BYTEs per Second ===> 0 : 0


Figure 60. Session Monitor Selection Panel (FNM03SAS)



4. Type 1 in the Select Option field. �1�

5. Type the name of the application in the Identifier field. �2�

This name should correspond to the CICS application for which you collected data.


If the application is on another host, type the name of that host.

7. Type SESSION in the File Name field. �4�

This option specifies the current session file to which NPM wrote the data. If you wantto see data from another file, type that file name. See “Managing NPM Data Files” onpage 179 for information about NPM files.

8. Type today’s date in the Date fields. �5�


9. Type a starting and stopping time in the Time fields. �6�


10. Verify that the remaining fields on this panel are blank.

The remaining fields on this panel put restrictions on the data displayed on the panel.Because you are trying to isolate a problem, you need to see all the data collected.

11. Press ENTER to display the NPM Session Analysis Summary - Application panel(FNM03SMN), shown in Figure 62 on page 146. See “Example: No Data Found (ErrorMessage)” on page 180 if you receive the following error message:FNM756E NO DATA FOUND FOR THIS REQUEST

FNM02SAN NPM V2R7 5655-043RESPONSE TIMESSESSION ANALYSIS

Select Option ===> 1 �1�1 Application 3 Physical Unit 5 Virtual Route2 Line 4 Group

Identifier ===> CICS �2�Host Name ===> LOCAL �3�Data QualifiersApplication ===>Line ===>Physical Unit ===>Virtual Route Number ===> (0-7)Transmission Priority ===> (0-2)

File Name ===> SESSION �4� (SESSION for active session file)Date: from ===> 09 / 30 / 00 to ===> 09 / 30 / 00 �5� (mm/dd/yy)Time: from ===> 15 : 25 : 00 to ===> 15 : 40 : 00 �6� (hh:mm:ss)

PF 1=HELP 3=END 12=RETURN 15=NCP 16=ROUTER 17=LINEPF20= 24=TERMINAL

Figure 61. Session Analysis Panel (FNM02SAN)



11.Iso

lating

Pro

blem

sin

the

Ho

st

The NPM Session Analysis Summary - Application panel displays the data you havebeen collecting for the application. The average and maximum transit times for the hostand network indicate a host-related problem, as you have already determined.

12. Use the LIST command to display the NPM Session Summary LU List panel(FNM04LTN), shown in Figure 63. Use this panel to determine whether the LU or theapplication is the cause of the poor response time problem.

The NPM Session Summary LU List - Application panel displays data for each LU usingthe application. Compare the average host and network transit times. In this example thehost transit time greatly exceeds the network transit time for most LUs.

FNM03SMN NPM V2R7 5655-043RESPONSE TIMES

NPM SESSION ANALYSIS SUMMARY - APPLICATION

Command ===>Insert DYN to get dynamic (real time) dataHost Name = LOCAL Records = 228 VR/TP = VR TPApplication = CICS Line = PU =Group = Node = LU =Requested Date/Time: from 09/30/00 15:25 to 09/30/00 15:40Actual Date/Time : from 09/30/00 15:25 to 09/30/00 15:40

Total ResponseTransactions 176 176

Operator Host NetworkAverage Transit 8.63 7.44 1.19Maximum Transit 82.89 80.15 16.70

PIU Count Avg Size Total BytesUser Data In 620 10 6053User Data Out 619 324 200588System Data In 683 5 3203System Data Out 76 5 380PF 1=HELP 2=LIST 3=END 4=TRANSIT 5=VOLUME 6=DISTRIBPF12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 62. NPM Session Analysis Summary - Application Panel (FNM03SMN)

FNM04LTN NPM V2R7 5655-043RESPONSE TIMES

NPM SESSION SUMMARY LU LIST - APPLICATION

Command ===>Insert DYN to get dynamic (real time) dataHost Name = LOCALApplication = CICS Line = PU =Group = Node = VR/TP =Date/Time: from 9/30/00 15:25:00 to 09/30/00 15:40:00

Transactions <- Average Transit Time -> TotalSession Names Total Response Operator Host Network BytesLU032 / CICS 53 53 56.89 56.67 .22 19594LU033 / CICS 0 0 .00 .00 .00 0LU034 / CICS 83 83 50.36 48.57 1.79 76021LU035 / CICS 40 40 42.92 41.64 1.28 43896LU036 / CICS 50 50 47.00 46.00 1.00 45260LU037 / CICS 0 0 .00 .00 .00 0


Figure 63. NPM Session Summary LU List - Application Panel (FNM04LTN)



Because the host transit times are larger than the network transit times for most of the LUsusing the CICS application, the application is probably at fault. However, you shouldcontinue your analysis using the other scenarios in this chapter to determine if the problemis with CICS or with VTAM.

Stopping Collection for the ApplicationUse the following procedure to stop the collection after you have viewed session data for theapplication:


2. Select option 2 on the Response Times panel to display the Session Status/Stop (Active)Resource panel (FNM03SSA), shown in Figure 64. You can also use fast path =2.2 todisplay the Session Status/Stop (Active) Resource panel.

3. Type P in the Option field �1� next to the name of the application and press ENTER tostop the collection for the application. NPM issues a message indicating it has stoppedcollection for the application.

Example: Examining an Application Using VTAM Statistics DataYou determined that the problem is in the host in the previous scenario. This scenariodescribes how to determine if an application (CICS) is the source of the problem.

Use the following procedure to collect and display application data using NPM’s VTAMstatistics collection management function:

1. Select option 5 on the Primary Options panel (FNM00PRI) to display the VTAMResource Type Selection panel (FNM01VTM).

2. Select option 6 on the VTAM Resource Type Selection panel to display the VTAMApplication Selection panel (FNM02PS1), shown in Figure 65 on page 148. You canalso use fast path =5.6 to display the VTAM Application Selection panel.


SESSION STATUS/STOP (ACTIVE) RESOURCE

Command ===>

Host Name = LOCALEnter Option: S=Detailed Status, P=Stop, Z=Stop All

Option Resource Resource Maximum SessionName Type Collected Collected Logging Data Forwd Monitors

=> A02MPU HOST 250 0 0 0 0=> P�1� CICS APPL 437 1 0 1 0=> A31C52A NCP 437 0 0 0 0=> A99M CDRM 50 0 0 0 0=> B63M CDRM 50 0 0 0 0


Figure 64. Session Status/Stop (Active) Resource Panel (FNM03SSA)



11.Iso

lating

Pro

blem

sin

the

Ho

st

3. Type S in the Option field �1� next to the CICS application name and press ENTER todisplay the VTAM Start panel (FNM03VTD), shown in Figure 66.



5. Verify that CICS is in the Resource Name field.

6. Verify that APL is in the Resource Type field.



All zeros (the default) in this field causes NPM to start collection immediately. Becauseyou want to find the source of the poor response time right away, you need to startcollecting data immediately.

FNM02PS1 NPM V2R7 5655-043VTAM MANAGEMENT

VTAM APPLICATION SELECTION

Command ===>

Host Name = LOCALEnter Command: LOCATE <Appl>, REFRESH, SORT <NAME/STATUS>or Option: S=Start, R=Review, L=List, Z=Stop All

Data CollectionOption Appl Forwd Status=> S �1� CICS 0 INACTIVE

PF 1=HELP 2=REFRESH 3=END 5=RIGHT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 65. VTAM Application Selection Panel (FNM02PS1)

FNM03VTD NPM V2R7 5655-043VTAM MANAGEMENTVTAM START

Command ===>

*---------------*Interval Number ===> 1 �2� <=====| Interval |

| Num Time |Resource Name ===> CICS | 1 00:03:45 |or DESTSA VR TP | 2 00:07:30 |Virtual Route ===> | 3 00:15:00 |

| 4 00:30:00 |Resource Type ===> APL (GBL/BPL/VR/DEV/APL/ADR) | 5 01:00:00 |Dynamic Resource ===> NO �3� (Yes/No) | 6 02:00:00 |

| 7 04:00:00 |*---------------*

Start Time ===> 00 : 00 : 00 �4� (hh:mm:ss)Stop Time ===> 00 : 00 : 00 �5�Daily ===> NO �6� (Yes/No)PF 1=HELP 3=END 12=RETURN 15=NCP 16=ROUTER 17=LINEPF20=APPL 24=TERMINAL

Figure 66. VTAM Start Panel (FNM03VTD)

VTAM Applications



All zeros (the default) in this field causes NPM to collect data until you tell it to stop.



11. Press ENTER to display the second VTAM Start panel (FNM03VT2), shown inFigure 67.

12. Type YES in the Data Destinations Detail VSAM field. �7�

Because you want to review the data online, type YES in the VSAM data destinationfield. In this example, it does not matter whether you send the data to the otherdestinations.

13. Press ENTER to start a collection on the CICS application. The VTAM ApplicationSelection panel (FNM02PS1) is redisplayed.

14. Use the LEFT, RIGHT, and REFRESH commands to display current data for thecollection. The LEFT and RIGHT keys alternately display the VTAM ApplicationSelection panel (FNM02PS1) and the VTAM Application Current Data panel(FNM02PS2), shown in Figure 68 on page 150.

Note: You must wait at least one refresh interval before data is displayed. Use theREFRESH command to display the most current data.

FNM03VT2 NPM V2R7 5655-043VTAM MANAGEMENTVTAM START

Command ===>

Host Name = LOCAL Resource Name = CICS Resource Type = APLDest Subarea = VR = TP =

Data Destinations NPMLOG VSAM SMF ALERT GLOBAL �7�Detail ===> NO YES NO N/A N/A


Figure 67. VTAM Start Panel (FNM03VT2)

VTAM Applications


11.Iso

lating

Pro

blem

sin

the

Ho

st

15. Examine the Receive Any counter field �8� on the VTAM Application Current Datapanel. If the Receive Any field frequently displays zeros between screen refreshes, thismight indicate that the incoming data to the application is being queued. When theReceive Any count is zero, incoming data to the application is queued into the privatestorage area. In this case, you probably need to adjust the MXT and RAPOOL CICSparameters to improve response times (see the CICS Transaction Server for OS/390CICS Resource Definition Guide).

If the Receive Any count does not display any zeros between screen refreshes, continueusing the other scenarios in this chapter to try and isolate the problem.

Stopping VTAM Statistics Collection on an ApplicationUse the following procedure to stop VTAM statistics collection on an application:

1. On the VTAM Application Current Data Panel (FNM02PS2), type L in the Option fieldnext to the application name and press ENTER to display the Command List panel(FNM03VCL), shown in Figure 69 on page 151.

FNM02PS2 NPM V2R7 5655-043VTAM MANAGEMENT More: <

VTAM APPLICATION CURRENT DATA

Command ===>

Host Name = LOCALEnter Command: LOCATE <Appl>, REFRESH, SORT <NAME/STATUS>or Option: S=Start, R=Review, L=List, Z=Stop All

�8�Sampled <--------- Sessions ---------> Inbnd Pacing Receive

Option Appl hh:mm:ss Active Domain PLU APPC Pend Rsp Rsp Any=> CICS 00:00:30 6 6 6 0 0 0 0 1

PF 1=HELP 2=REFRESH 3=END 4=LEFT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 68. VTAM Application Current Data Panel (FNM02PS2)

VTAM Applications


2. Type P in the Option field next to the appropriate collection row and press ENTER tostop the collection. A message indicating the collection has been stopped is displayed.

Example: Examining VTAM for Problems in the HostHigh VTAM CPU utilization has a direct impact on user response time. This examplescenario describes how to collect VTAM statistics to help determine the cause of high CPUutilization.

NPM can collect VTAM statistics data to help determine if VTAM is the cause of high CPUutilization. Table 15 lists some of the common reasons for excessive CPU utilization and thedata that can be analyzed to solve the problem. A ‘Y’ in Table 15 indicates where you canuse NPM’s VTAM statistics data to help determine the cause of high CPU utilization.Procedures describing how to use NPM’s VTAM management function to collect this dataare provided in this scenario.

Table 15. Sample Checklist for Determining High CPU UtilizationGlobal VTAM Data VTAM Buffer Pool Data

Reason for High CPUUtilization

CSA Storage Page-Ins SIO Counts

Y Y Y Y

Y Y Y

Y Y

Y Y Y

Y

Y Y Y

Starting a VTAM Global Data CollectionNPM provides a VTAM global data option which allows you to collect a variety of VTAMinformation, including storage information, CPU utilization, and I/O statistics. Use thefollowing procedure to collect and view global data:

1. Select option 5 on the Primary Options panel (FNM00PRI) to display the VTAMResource Type Selection panel (FNM01VTM).

FNM03VCL NPM V2R7 5655-043VTAM MANAGEMENTCOMMAND LIST

Command ===>

Host Name = LOCAL Resource Name = CICS Resource Type = APLDest Subarea = VR = TP =

Enter Option: A=Alter, P=Stop

Time Collect <- Detail -> <----- Monitor ------>Option Start Stop Status Daily Int LOG VSAM SMF LOG VSAM SMF ALERT GBL=> P 00:00:00 00:00:00 STARTED NO 1 N Y N N N N N N


Figure 69. Command List Panel (FNM03VCL)

VTAM Applications


11.Iso

lating

Pro

blem

sin

the

Ho

st

2. Select option 2 on the VTAM Resource Type Selection panel to display the VTAMGlobal Data Selection panel (FNM02GS1), shown in Figure 70. You can also use fastpath =5.2 to display the VTAM Global Data Selection panel. This panel lists the VTAMresource by its SSCP name.

3. Type S in the Option field �1� and press ENTER to display the first VTAM Start panel(FNM03VTD), shown in Figure 71.



5. Verify that your VTAM SSCP name is in the Resource Name field.

6. Verify that GBL is in the Resource Type field. �3�


FNM02GS1 NPM V2R7 5655-043VTAM MANAGEMENT More: >

VTAM GLOBAL DATA SELECTION

Command ===>

Host Name = LOCALEnter Option: S=Start, R=Review, L=List, Z=Stop All

Data Collection MonitorOption SSCP Forwd Status Status=> S �1� SSCPA1 0 INACTIVE

PF 1=HELP 2=REFRESH 3=END 5=RIGHT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 70. VTAM Global Data Selection Panel (FNM02GS1)

FNM03VTD NPM V2R7 5655-043VTAM MANAGEMENTVTAM START

Command ===>


| Num Time |Resource Name ===> SSCPA1 | 1 00:03:45 |or DESTSA VR TP | 2 00:07:30 |Virtual Route ===> | 3 00:15:00 |

| 4 00:30:00 |Resource Type ===> GBL �3� (GBL/BPL/VR/DEV/APL/ADR) | 5 01:00:00 |Dynamic Resource ===> NO �4� (Yes/No) | 6 02:00:00 |

| 7 04:00:00 |*---------------*



VTAM Problems








You would collect data daily if you wanted to determine trends.

11. Press ENTER to display the second VTAM Start panel (FNM03VTC), shown inFigure 72.



13. Because you are not monitoring the data in this example, verify that all the DataDestinations Monitor fields �9� are NO. Also, verify that the Monitor Criteria Low andHigh fields are set to zero.

14. Press ENTER to start a collection on the selected VTAM resources. The VTAM GlobalData Selection panel (FNM02GS1) is redisplayed.

15. Use the RIGHT command to display the first current VTAM Global Current Data panel(FNM02GS2), shown in Figure 73 on page 154.

You can use the REFRESH command to display the most current data on any of theVTAM Global Current Data panels. You must wait at least one refresh interval beforedata is displayed.

FNM03VTC NPM V2R7 5655-043VTAM MANAGEMENTVTAM START

Command ===>

Host Name = LOCAL Resource Name = SSCPA1 Resource Type = GBLDest Subarea = VR = TP =

Data Destinations NPMLOG VSAM SMF ALERT GLOBAL �8�Detail ===> NO YES NO N/A N/AMonitor ===> NO NO NO NO NO �9�


Monitor Criteria LOW : HIGHVTAM total page-ins (0-2147483646) ===> 0 : 0% of CSA-24 usage (0-100) ===> 0 : 0% of CSA usage (0-100) ===> 0 : 0


Figure 72. VTAM Start Panel (FNM03VTC)

VTAM Problems


11.Iso

lating

Pro

blem

sin

the

Ho

st

Note: You can use the LEFT, RIGHT, and REFRESH commands to display currentVTAM global data on the VTAM Global Current Data panels, shown inFigure 73, Figure 74, and Figure 75 on page 155.

16. Use the RIGHT command to display the second current VTAM Global Current Datapanel (FNM02GS3), shown in Figure 74.

17. Use the RIGHT command to display the third current VTAM Global Current Datapanel (FNM02GS4), shown in Figure 75 on page 155.

FNM02GS2 NPM V2R7 5655-043VTAM MANAGEMENT More: < >

VTAM GLOBAL CURRENT DATA

Command ===>

Host Name = LOCALEnter Command: REFRESH or Option: S=Start, R=Review, L=List, Z=Stop All

�10�Sampled Maximum Used Average Alloc Interval Max

Option SSCP hh:mm:ss CSA24 CSA CSA24 CSA CSA24 CSA=> SSCPA1 00:00:30 17394 969081 15582 832213 15582 832213

PF 1=HELP 3=END 4=LEFT 5=RIGHT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 73. VTAM Global Current Data Panel (FNM02GS2)

FNM02GS3 NPM V2R7 5655-043VTAM MANAGEMENT More: < >


Command ===>


�11� �12�Sampled % VTAM <-------- Page-ins -------->

Option SSCP hh:mm:ss CPU Usage Private Common LPA Total=> SSCPA1 00:00:30 90.91 34 33 27 94

PF 1=HELP 2=REFRESH 3=END 4=LEFT 5=RIGHT 12=RETURNPF15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL


VTAM Problems


18. Examine the VTAM CSA field �10� (on the FNM02GS2 panel) and paging rate data(on the FNM02GS3 panel) to determine if VTAM is using excessive storage. Forexample, if a fragmentation problem exists in the system (VTAM is up for a long time),this could indicate excessive system overhead caused by paging activities.

If the amount of CSA and private storage is normal, but the paging is high, this couldbe an indication that additional real storage is needed.

19. Examine the % VTAM CPU Usage field �11� on the FNM02GS3 panel. A high value(90 to 100 percent) in the % VTAM CPU Usage field can indicate that VTAM’sperformance is reduced due to several factors. Continue examining the VTAM globaldata if a high VTAM CPU usage value is displayed.

20. Examine the Page-ins fields �12� on the FNM02GS3 panel. If allocated control blocksare in different pages of storage, paging can occur to reference these control blocks. Forexample, a long SRT chain (collisions) spread in many different pages can cause pagingto locate an SRT entry.

21. Examine the SIO Counts fields �13� on the FNM02GS4 panel. Excessive I/O to certaindevices can be due to inappropriate tuning parameters for the device. The I/O datadisplayed on the FNM02GS4 panel can provide an indication of which devices needtuning.

22. Although the VTAM CPU utilization is high in this example, none of the otherdisplayed data for the collection indicates a problem. See “Collecting and DisplayingVTAM Buffer Pool Data” on page 156 to continue searching for the cause of theproblem.

If the VTAM CPU utilization had been low (under 40 percent), this would indicate thatVTAM was not the cause of the high host response time. In this case, you might wantto examine the virtual routes to determine if they were the cause of the problem.

A scenario for examining virtual routes is provided in “Example: Determining if Thereis a Blocked Virtual Route” on page 160.

Stopping a Global Data CollectionUse the following procedure to stop a global data collection:

FNM02GS4 NPM V2R7 5655-043VTAM MANAGEMENT More: <


Command ===>


�13�Sampled <----------------- SIO Counts ------------------>

Option SSCP hh:mm:ss NCPs CTCs Local-SNA Non-SNA DASD Misc=> SSCPA1 00:00:30 8 23 12 87 32 437

PF 1=HELP 2=REFRESH 3=END 4=LEFT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL


VTAM Problems


11.Iso

lating

Pro

blem

sin

the

Ho

st

1. From any VTAM global data panel, type L in the Option field next to the SSCP nameand press ENTER to display the Command List panel (FNM03VCL), shown inFigure 76.

2. Type P in the Option field next to the appropriate collection row and press ENTER tostop the collection. A message indicating the collection has been stopped is displayed.

Collecting and Displaying VTAM Buffer Pool DataUse the following procedure to collect and view buffer pool data:

1. Select option 3 from the VTAM Resource Type Selection panel (FNM01VTM) todisplay the VTAM Buffer Pool Selection panel (FNM02BS1), shown in Figure 77. Youcan also use fast path =5.3 to display the VTAM Buffer Pool Selection panel.

Note: The buffer pool names displayed on the VTAM Buffer Pool Selection andCurrent Data panels are VTAM release dependent.

FNM03VCL NPM V2R7 5655-043VTAM MANAGEMENTCOMMAND LIST

Command ===>

Host Name = LOCAL Resource Name = SSCPA1 Resource Type = GBLDest Subarea = VR = TP =

Enter Option: A=Alter, P=Stop

Time Collect <- Detail -> <----- Monitor ------>Option Start Stop Status Daily Int LOG VSAM SMF LOG VSAM SMF ALERT GBL=> P 00:00:00 00:00:00 STARTED NO 1 N Y N N N N N N


Figure 76. Command List Panel (FNM03VCL)

FNM02BS1 NPM V2R7 5655-043VTAM MANAGEMENT More: >

VTAM BUFFER POOL SELECTION

Command ===>

Host Name = LOCALEnter Command: LOCATE <Pool>, REFRESH, SORT <NAME/STATUS>or Option: S=Start, R=Review, L=List, Z=Stop All

Buffer Data Collection MonitorOption Pool Forwd Status Status=> S�1� AP00 0 INACTIVE=> CRPL 0 INACTIVE=> IO00 0 INACTIVE=> LF00 0 INACTIVE=> LP00 0 INACTIVE=> SF00 0 INACTIVE=> SP00 0 INACTIVE=> WP00 0 INACTIVEPF 1=HELP 2=REFRESH 3=END 5=RIGHT 8=FORWARD 11=BOTTOMPF12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 77. VTAM Buffer Pool Selection Panel (FNM02BS1)

VTAM Problems


2. Type S in the Option field �1� next to any buffer pool name and press ENTER todisplay the first VTAM Start panel (FNM03VTD), shown in Figure 78.


The interval number determines how long NPM waits each time it collects data. Yourequest the shortest interval by typing 1 in this field.

4. Type ALLBP in the Resource Name field. �3�

This causes a collection to be started on all VTAM buffer pools defined to NPM.

5. Verify that BPL is displayed in the Resource Type field. �4�

6. Verify that NO is displayed in the Dynamic Resource field. �5�





9. Verify that NO is displayed in the Daily field. �8�



10. Press ENTER to display the second VTAM Start panel (FNM03VTC), shown inFigure 79 on page 158.

FNM03VTD NPM V2R7 5655-043VTAM MANAGEMENT

VTAM START

Command ===>


| Num Time |Resource Name ===> ALLBP �3� | 1 00:03:45 |or DESTSA VR TP | 2 00:07:30 |Virtual Route ===> | 3 00:15:00 |

| 4 00:30:00 |Resource Type ===> BPL �4� (GBL/BPL/VR/DEV/APL/ADR) | 5 01:00:00 |Dynamic Resource ===> NO �5� (Yes/No) | 6 02:00:00 |

| 7 04:00:00 |*---------------*

Start Time ===> 00 : 00 : 00 �6� (hh:mm:ss)Stop Time ===> 00 : 00 : 00 �7�Daily ===> NO �8� (Yes/No)



VTAM Problems


11.Iso

lating

Pro

blem

sin

the

Ho

st



12. Because you are not monitoring the data in this example, verify that all the DataDestinations Monitor fields �9� are NO. Also, verify that the Monitor Criteria Low andHigh fields are set to zero.

13. Press ENTER to start a collection on all buffer pools. The VTAM Buffer Pool Selectionpanel (FNM02BS1) is redisplayed.

You can use the REFRESH command to display the most current data. You must waitat least one refresh interval before data is displayed.

Note: You can use the LEFT and RIGHT keys to alternately display the VTAM BufferPool Selection panel (FNM02BS1) and the VTAM Buffer Pool Current Datapanel (FNM02BS2), shown in Figure 80 on page 159.

14. Use the RIGHT command to display the VTAM Buffer Pool Current Data panel(FNM02BS2).

The VTAM Buffer Pool Current Data panel displays the current data for a buffer pool.This data is only available if the collection status is STARTED.

FNM03VTC NPM V2R7 5655-043VTAM MANAGEMENTVTAM START

Command ===>

Host Name = LOCAL Resource Name = ALLBP Resource Type = BPLDest Subarea = VR = TP =



Monitor Criteria LOW : HIGHThrashing coefficient (20-9999) ===> 0 : 0Expansion rate (0-2147483646) ===> 0 : 0% CRPL usage by highest user (0-100) ===> 0 : 0% IO00 usage by highest user (0-100) ===> 0 : 0% IO00 usage in expansion limit (0-100) ===> 0 : 0


Figure 79. VTAM Start Panel (FNM03VTC)

VTAM Problems


15. Examine the Number Expands column �10� on the VTAM Buffer Pool Current Datapanel. This data can be used to determine if VTAM is experiencing thrashing.Thrashing occurs when dynamic requests for buffers are excessive, causing anabnormally high rate of expansion and contraction in a buffer pool and a subsequentdrain of CPU resources.

Your system programmer can tune the Expansion Point, Expansion Number, andBASENO parameters in the VTAM start list to prevent thrashing.

Stopping a VTAM Buffer Pool CollectionTo stop a VTAM buffer pool collection, type Z in the Option field next to all the buffer poolnames on the VTAM Buffer Pool Current Data panel (FNM02BS2) and press ENTER. SeeFigure 81.

Messages indicating the collections have been stopped are displayed.

FNM02BS2 NPM V2R7 5655-043VTAM MANAGEMENT More: <

VTAM BUFFER POOL CURRENT DATA

Command ===>


�10�Buffer Sampled <- Avg Buffers -> <- Max Buffers -> Req Waiting Number

Option Pool hh:mm:ss Alloc Used Avail Alloc Used Avail Avg Max Expands=> AP00 08:23:29 16 0 16 16 0 16 0 0 100=> CRPL 08:23:29 510 481 30 510 481 30 0 0 1820=> IO00 08:23:29 280 4 277 280 5 278 0 0 6688=> LF00 08:23:29 39 6 33 39 6 33 0 0 33=> LP00 08:23:29 66 4 62 66 4 62 0 0 212=> SF00 08:23:29 42 5 37 42 5 37 0 0 11=> SP00 08:23:29 34 0 34 34 0 34 0 0 123=> WP00 08:23:29 473 462 11 473 462 11 0 0 399PF 1=HELP 2=REFRESH 3=END 4=LEFT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 80. VTAM Buffer Pool Current Data Panel (FNM02BS2)

FNM02BS2 NPM V2R7 5655-043VTAM MANAGEMENT More: <

VTAM BUFFER POOL CURRENT DATA

Command ===>


Buffer Sampled <- Avg Buffers -> <- Max Buffers -> Req Waiting NumberOption Pool hh:mm:ss Alloc Used Avail Alloc Used Avail Avg Max Expands=> Z AP00 08:23:29 16 0 16 16 0 16 0 0 100=> Z CRPL 08:23:29 510 481 30 510 481 30 0 0 1820=> Z IO00 08:23:29 280 4 277 280 5 278 0 0 6688=> Z LF00 08:23:29 39 6 33 39 6 33 0 0 33=> Z LP00 08:23:29 66 4 62 66 4 62 0 0 212=> Z SF00 08:23:29 42 5 37 42 5 37 0 0 11=> Z SP00 08:23:29 34 0 34 34 0 34 0 0 123=> Z WP00 08:23:29 473 462 11 473 462 11 0 0 399PF 1=HELP 2=REFRESH 3=END 4=LEFT 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 81. VTAM Buffer Pool Current Data Panel (FNM02BS2)

VTAM Problems


11.Iso

lating

Pro

blem

sin

the

Ho

st

Example: Determining if There is a Blocked Virtual RouteVTAM throughput is affected when virtual routes are not tuned properly. In the previousscenarios, all users on the same NCP were experiencing poor response time. This might becaused by a virtual route blockage between VTAM and the users connected to the NCP.

Use the following procedure to collect and display virtual route data:

1. Select option 5 on the Primary Options panel (FNM00PRI) to display the VTAMResource Type Selection panel (FNM01VTM). You can also use fast path =5 to displaythe VTAM Resource Type Selection panel.

2. Select option 4 on the VTAM Resource Type Selection panel to display the DestinationSubarea Selection panel (FNM02SS1), shown in Figure 82. You can also use fast path=5.4 to display the Destination Subarea Selection panel.

3. Type X in the Option field �1� next to destination node name NCP01 and press ENTERto display the Virtual Route Selection panel (FNM03VS1), shown in Figure 83 onpage 161.

The Virtual Route Selection panel displays a list of VR/TP pairs for the subarea that wasexpanded from the Destination Subarea Selection panel. You can use this panel to start acollection, list all collections, end all active collections, or review data for a specificVR/TP pair.

FNM02SS1 NPM V2R7 5655-043VTAM MANAGEMENT

DESTINATION SUBAREA SELECTION

Command ===>

Host Name = LOCALEnter Command: LOCATE <Name>, REFRESH, SORT <NAME/NUMBER>or Option: X=Expand

�1� Destination DestinationOption Node Name Subarea=> X NCP01 1=> SSCPA1 161


Figure 82. Destination Subarea Selection Panel (FNM02SS1)

Blocked Virtual Routes


4. Type S in the Option field �2� next to any VR/TP pair and press ENTER to display theVTAM Start panel (FNM03VTD), shown in Figure 84.



6. Type ALLVR in the Resource Name field. �4�

Because you do not know which VR/TP pair might be causing the problem, you shouldspecify ALLVR to collect data on all VR/TP pairs.

7. Verify that the destination subarea of the specified destination node is displayed in theVirtual Route field under DESTSA. �5�

The destination subarea number for node NCP01 is 1 in this example.

8. Verify that the VR and TP fields are blank.

FNM03VS1 NPM V2R7 5655-043VTAM MANAGEMENT More: >

VIRTUAL ROUTE SELECTION

Command ===>

Host Name = LOCAL Dest Subarea = 1 Dest Node Name = NCP01Enter Command: REFRESH, SORT <VR/STATUS/BLOCK/SESSIONS>or Option: S=Start, R=Review, L=List, Z=Stop All

�2� Data Collection MonitorOption VR TP Forwd Status Status=> S 0 0 0 INACTIVE=> 0 1 0 INACTIVE=> 0 2 0 INACTIVE=> 7 0 0 INACTIVE=> 7 1 0 INACTIVE=> 7 2 0 INACTIVE

PF 1=HELP 2=REFRESH 3=END 5=RIGHT 8=FORWARD 11=BOTTOMPF12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 83. Virtual Route Selection Panel (FNM03VS1)

FNM03VTD NPM V2R7 5655-043VTAM MANAGEMENT

VTAM START

Command ===>


| Num Time |Resource Name ===> ALLVR �4� | 1 00:03:45 |or DESTSA VR TP | 2 00:07:30 |Virtual Route ===> 1 �5� | 3 00:15:00 |

| 4 00:30:00 |Resource Type ===> VR �6� (GBL/BPL/VR/DEV/APL/ADR) | 5 01:00:00 |Dynamic Resource ===> NO �7� (Yes/No) | 6 02:00:00 |

| 7 04:00:00 |*---------------*





11.Iso

lating

Pro

blem

sin

the

Ho

st

9. Type VR in the Resource Type field. �6�

10. Verify that NO is displayed in the Dynamic Resource field. �7�




All zeros (the default) in this field causes NPM to collect data until you tell it to stop.If you wanted to stop collection at a specific time, you would specify a stopping time.

13. Verify that NO is displayed in the Daily field. �10�



14. Press ENTER to display the VTAM Data Collection panel (FNM03VTC), shown inFigure 85.



16. Press ENTER to start a collection on all the virtual routes for the specified subarea. TheVirtual Route Selection panel (FNM03VS1) is redisplayed.

17. Use the RIGHT command to display the first Virtual Route Current Data panel(FNM02VS2), shown in Figure 86 on page 163.

FNM03VTC NPM V2R7 5655-043VTAM MANAGEMENT

VTAM DATA COLLECTION

Command ===>

Host Name = LOCAL Resource Name = ALLVR Resource Type = VRDest Subarea = 1 VR = TP =



Monitor Criteria LOW : HIGH% of time blocked (20-999) ===> 0 : 0


Figure 85. VTAM Data Collection Panel (FNM03VTC)



You can use the REFRESH command to display the most current data on any of theVirtual Route Current Data panels. You must wait at least one refresh interval beforedata is displayed.

Note: You can use the LEFT, RIGHT, and REFRESH commands to display currentdata on the Virtual Route Current Data panels, shown in Figure 86 and Figure 87on page 164.

18. The data displayed in the % Time Blocked field �12� indicates that the virtual routepair VR7/TP0 is blocked.

19. Examine the LU-LU Sessions fields. �13�

Note that the number of LU-LU sessions on the VR7/TP0 pair is very high. Also notethat the VR7/TP1 pair shows no blockage and has low session activity.

20. Use the RIGHT command to display the second Virtual Route Current Data panel(FNM03VS3), shown in Figure 87 on page 164.

FNM03VS2 NPM V2R7 5655-043VTAM MANAGEMENT More: < >

VIRTUAL ROUTE CURRENT DATA

Command ===>


�12� �13�Sampled % Time % Time LU-LU Total Queued

Option VR TP hh:mm:ss Blocked Active Sessions Sessions PIUs=> 0 0 13:30:29 0 0 0 0 0=> 0 1 13:30:35 0 0 0 0 0=> 0 2 13:31:37 0 100 0 109 0=> 7 0 13:30:15 70 100 5000 5000 756=> 7 1 13:30:23 0 100 50 50 0=> 7 2 13:30:28 0 0 0 0 0

PF 1=HELP 2=REFRESH 3=END 4=LEFT 5=RIGHT 8=FORWARDPF11=BOTTOM 12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPLPF24=TERMINAL

Figure 86. Virtual Route Current Data Panel (FNM03VS2)



11.Iso

lating

Pro

blem

sin

the

Ho

st

21. Examine the VR blockage pattern using the current data by refreshing the display. Youshould examine the Current Window Size Max field �14� for a virtual route if the %Time Blocked field on the first Virtual Route Current Data panel (FNM03VS2) is over20 percent. When the Interval Window Size Max �15� is the same as the CurrentWindow Size Max parameter, (as displayed for the VR7/TP0 pair in this example) thisis an indication that VR throughput is affected.

There are two actions you can take based on the data displayed in Figure 87:

a. Increase the maximum window size setting in the VTAM path definition statement.

b. Change the class-of-service (COS) table in VTAM to distribute the sessions moreevenly to destination subareas where the virtual routes end.

Note: Because this could be a temporary situation, further analysis should beperformed to understand the general trend for this VR and to avoid future VRblockage. The following scenario describes how to collect VR data to helpanalyze long-term VR trends.

Analyzing Long-Term VR DataBecause the VR blockage in the previous scenario might be a temporary situation, confirmyour diagnosis by analyzing the VR data over a longer period. Let the VTAM data collectionyou started in the previous scenario continue running to provide better data sampling forlong-term trend analysis.

Use the following procedure to examine a long-term trend for a specific virtual route:

1. Select option 5 on the Primary Options panel (FNM00PRI) to display the VTAMResource Type Selection panel (FNM01VTM). You can also use fast path =5 to displaythe VTAM Resource Type Selection panel.

2. Select option 4 on the VTAM Resource Type Selection panel to display the DestinationSubarea Selection panel (FNM02SS1), shown in Figure 88 on page 165. You can alsouse fast path =5.4 to display the Destination Subarea Selection panel.

FNM03VS3 NPM V2R7 5655-043VTAM MANAGEMENT More: <

VIRTUAL ROUTE CURRENT DATA

Command ===>


�14� �15�Current Interval

Sampled Window Size Window Size <--- PIUs --->Option VR TP hh:mm:ss Min Max Min Max Inbound Outbound=> 0 0 00:00:29 0 0 0 0 0 0=> 0 1 00:00:34 0 0 0 0 0 0=> 0 2 00:00:38 1 255 2 2 0 0=> 7 0 00:00:46 3 10 3 10 300 40000=> 7 1 00:00:50 3 10 3 8 40 100=> 7 2 00:00:53 0 0 0 0 0 0

PF 1=HELP 3=END 4=LEFT 8=FORWARD 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 87. Virtual Route Current Data Panel (FNM03VS3)



3. Type X in the Option field �1� next to a destination subarea and press ENTER todisplay the Virtual Route Selection panel (FNM03VS1), shown in Figure 89.

The Virtual Route Selection panel (FNM03VS1) displays a list of VR/TP pairs for thesubarea that was expanded from the Destination Subarea Selection panel (FNM02SS1).You can use this panel to start a collection, list all collections, end all active collections,or review data for a specific VR/TP pair.

4. Type R in the Option field �2� next to the VR/TP pair that is blocked and press ENTERto display the VTAM Data Analysis panel (FNM03VAN), shown in Figure 90 onpage 166.

FNM02SS1 NPM V2R7 5655-043VTAM MANAGEMENT

DESTINATION SUBAREA SELECTION

Command ===>

Host Name = LOCALEnter Command: LOCATE <Node>, REFRESH, SORT <NAME/NUMBER>or Option: X=Expand

�1� Destination DestinationOption Node Name Subarea=> X NCP01 1=> SSCPA1 161


Figure 88. Destination Subarea Selection Panel (FNM02SS1)

FNM03VS1 NPM V2R7 5655-043VTAM MANAGEMENT More:

VIRTUAL ROUTE SELECTION

Command ===>


�2� Data Collection MonitorOption VR TP Forwd Status Status=> 0 0 0 STARTED INACTIVE=> 0 1 0 STARTED INACTIVE=> 0 2 0 STARTED INACTIVE=> R 7 0 0 STARTED INACTIVE=> 7 1 0 STARTED INACTIVE=> 7 2 0 STARTED INACTIVE

PF 1=HELP 2=REFRESH 3=END 5=RIGHT 8=FORWARD 11=BOTTOMPF12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 89. Virtual Route Selection Panel (FNM03VS1)



11.Iso

lating

Pro

blem

sin

the

Ho

st


6. Verify that 1 is in the DESTSA field.

7. Verify that 7 is in the VR field.

8. Verify that 0 is in the TP field.

9. Verify that VR is in the Resource Type field.

10. Press ENTER to display the Virtual Route Detail Data panel (FNM04VD1), shown inFigure 91.

This panel displays a list of records written to the VSAM review file for a particularvirtual route. FNM04VD1 is the first virtual route detail data panel.

11. Examine the LU-LU Sessions fields. �4�

FNM03VAN NPM V2R7 5655-043VTAM MANAGEMENT

VTAM DATA ANALYSIS

Command ===>

Host Name = LOCAL *----------------------*| Resource Type |

Data Type ===> DETAIL �3� (Detail/Monitor) | GBL - VTAM global |Resource Name ===> (Name/All) | BPL - Buffer pool |or DESTSA VR TP | VR - Virtual route |

Virtual Route ===> 1 7 0 | DEV - Device || APL - Application |

Resource Type ===> VR <======| ADR - Address space || ALL - All types |

Search criteria Start Stop *----------------------*Time ===> 00 : 00 : 00 00 : 00 : 00 (hh:mm:ss)Date ===> 09 / 30 / 00 09 / 30 / 00 (mm/dd/yy)


Figure 90. VTAM Data Analysis Panel (FNM03VAN)

FNM04VD1 NPM V2R7 5655-043VTAM MANAGEMENT More: >+

VIRTUAL ROUTE DETAIL DATA

Command ===>

Host Name = LOCAL Destination Subarea = 1 VR = 7 TP =0Date/Time: from 09/30/00 00:00:00 to 09/30/00 00:00:00Enter Command: REFRESH, SORT <BLOCK/TIME/SESSIONS>

�4�Interval % Time % Time LU-LU Total Queued

End Time hh:mm:ss Blocked Active Sessions Sessions PIUs08:41:28 00:00:28 70 100 5000 5000 75608:41:58 00:00:30 72 100 5000 5000 92208:42:28 00:00:30 72 100 5000 5000 91608:42:58 00:00:30 70 100 5000 5000 70608:43:28 00:00:30 70 100 5000 5000 72608:43:58 00:00:30 70 100 5000 5000 74608:44:28 00:00:30 75 100 5000 5000 98808:44:58 00:00:30 74 100 5000 5000 956PF 1=HELP 2=REFRESH 3=END 5=RIGHT 8=FORWARD 11=BOTTOMPF12=RETURN 15=NCP 16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 91. Virtual Route Detail Data Panel (FNM04VD1)



Note that the number of LU-LU sessions on the VR7/TP0 pair is very high. Also notethat the VR7/TP1 pair displays high values in the % Time Blocked field.

12. Use the RIGHT command to display the second virtual route detail data panel(FNM04VD2), shown in Figure 92. This panel displays a list of records written to theVSAM review file for a specific virtual route.

13. Examine the pattern of VR activity and performance over the previous several hours.The data displayed in Figure 92 indicates that the VR throughput is affected, becausethe Current Window Size Max value �5� is usually equal to the Interval Window SizeMax value �6�.

This long-term analysis confirms the suspected VR blockage. See the recommendedactions listed at the end of the previous scenario, “Example: Determining if There is aBlocked Virtual Route” on page 160.

FNM04VD2 NPM V2R7 5655-043VTAM MANAGEMENT More: <+

VIRTUAL ROUTE DETAIL DATA

Command ===>

Host Name = LOCAL Destination Subarea = 1 VR = 7 TP = 0Date/Time: from 09/30/00 00:00:00 to 09/30/00 08:45:00Enter Command: REFRESH, SORT <BLOCK/TIME/SESSIONS>

�5� �6�Current Interval

Interval Window Size Window Size <--- PIUs --->End Time hh:mm:ss Min Max Min Max Inbound Outbound08:41:28 00:00:28 3 10 3 10 300 4000008:41:58 00:00:30 3 10 3 10 330 4120008:42:28 00:00:30 3 10 3 10 334 4130008:42:58 00:00:30 3 10 3 10 301 4010008:43:28 00:00:30 3 10 3 10 312 4022008:43:58 00:00:30 3 10 3 10 320 4023308:44:28 00:00:30 3 10 3 10 367 4210008:44:58 00:00:30 3 10 3 10 340 41980PF 1=HELP 3=END 4=LEFT 8=FORWARD 12=RETURN 15=NCPPF16=ROUTER 17=LINE 20=APPL 24=TERMINAL

Figure 92. Virtual Route Detail Data Panel (FNM04VD2)



11.Iso

lating

Pro

blem

sin

the

Ho

st



Reviewing Network Performance

The performance of your network can be affected as network use increases. You may seepoor response time and other problems. By using NPM to spot these symptoms early, youcan adjust the network before performance deteriorates and avoid user inconvenience.

This chapter explains how to use the NPM network monitors to review network performanceand identify potential problems.

Example: Using a Network MonitorYou can spot potential problems by monitoring individual components of your network.NPM monitors alert you when data has fallen outside thresholds you have specified. Forexample, a monitor can alert you when the error count for a line becomes too high.

The following sections show how to set up a network monitor and view the messages itgenerates. In this scenario, you are concerned about the performance of a particular NTRIphysical link, TIC01. You want NPM to generate monitor event messages when the physicallink’s utilization percentage falls outside a specific range.

Note: This scenario shows the concept for network data provided by NCPs. The concept fornetwork data provided by routers is similar.

Starting a Network CollectionUse the following procedure to start a network monitor on the physical link:

1. Use fast path =1.4 to display the Network Start panel (FNM03STD), shown inFigure 93 on page 170.

12


12.R

eviewin

gN

etwo

rkP

erform

ance

2. Complete the Network Start panel fields as described in this section. Use the Tab key tomove from field to field. Do not press ENTER until you are instructed to do so.



4. Type the name of the NCP in the NCP Name field. �2�



7. Verify that the Start Time field �5�is all zeros.

This is the default for this field, which causes collection to start immediately. Becauseyou want to find the source of the poor response time right away, you need to startcollecting data immediately.

8. Verify that the Stop Time field �6� is all zeros.

This is the default for this field, which causes NPM to collect data until you tell it tostop.




FNM03STD NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK START

Command ===>


| Num Time |NCP Name ===> NCP01 �2� | 1 00:03:45 |Resource Name ===> TIC01 �3� | 2 00:07:30 |Dynamic Resource ===> NO (Yes/No) �4� | 3 00:15:00 |

| 4 00:30:00 || 5 01:00:00 |

Start Time ===> 00 : 00 : 00 �5� (hh:mm:ss) | 6 02:00:00 |Stop Time ===> 00 : 00 : 00 �6� | 7 04:00:00 |Daily ===> NO �7� (Yes/No) *---------------*



Using a Network Monitor


11. Indicate where to send the data in the Detail Data Destination fields. �8�

Because you want to review the data online, type YES in the VSAM monitor fieldcolumn. For the purposes of this example, it does not matter whether you send the datato the other destinations. See the NPM Reference for information about the otherdestinations.

12. Use the FORWARD command to page down the list of monitor criteria to display theTIC utilization monitor field. �9�

13. Type 45 in the TIC utilization LOW field. Type 60 in the TIC utilization HIGH field.

14. Press ENTER to start collection on the specified resource.

Displaying the Monitor Event MessagesYou need to wait at least one collection interval before viewing the data. However, youshould wait for several intervals to give the exception errors a chance to resolve to see bothmonitor and resolution messages.

Use the following procedure to display the data when you believe enough data has beencollected:

1. Use fast path =1.7 to access the Network Review panel (FNM02RVM), shown inFigure 95 on page 172.

FNM03STM NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK START

Command ===>

Host Name = LOCAL NCP Name = NCP01 Resource Name = TIC01

Data Destinations NPMLOG VSAM SMF ALERT GLOBALDetail ===> NO NO NO N/A N/AMonitor ===> NO �8� YES NO NO NO

Resolve Monitors ===> YES (Yes/No)

Monitor Criteria LOW : HIGHBytes received/second (0-2147483646) ====> 0 : 0

�9�TIC utilization (0-100) ====> 45 : 60Congestion count (0-2147483646) ====> 0 : 0% bytes retransmitted (0-100) ====> 0 : 0PDUs transmitted/minute (0-2147483646) ====> 0 : 0PDUs received/minute (0-2147483646) ====> 0 : 0





12.R

eviewin

gN

etwo

rkP

erform

ance

2. Complete the Network Review panel fields as described in this section. Use the Tabkey to move from field to field. Do not press ENTER until you are instructed to do so.



If you were running more than one monitor, you could see the data for all monitors onall resources by typing MONITOR.

5. Type PHYlINK in the Resource Type field. �3�






9. Type MONITOR in the Data Type field. �9�

10. Press ENTER to display the data on the Review Monitor Event Messages panel(FNM03RVE), shown in Figure 96 on page 173.

FNM02RVM NPM V2R7 5655-043NETWORK MANAGEMENT

NETWORK REVIEW

Command ===>

Host Name ===> LOCAL �1�Resource Name ===> TIC01 �2� (Name)Resource Type ===> PHYLINK �3� (Name/ALL only for Data Type=MONITOR)Review File Name ===> REVIEW �4� (REVIEW for active review file)



Data Type ===> MONITOR �9� (Detail/Monitor)





The Review Monitor Event Messages panel (FNM03RVE) displays event messages for thismonitor. For this example, NPM calculated TIC utilization every 15 minutes. If the TICutilization was outside your specified thresholds, NPM issued a message showing the TICutilization. NPM issued a resolution message if the TIC utilization fell back within thethresholds.

Because you had monitor resolution turned on, NPM issued messages only when the datafirst fell outside the thresholds and when it fell back within the thresholds. If you did nothave monitor resolution turned on, NPM would have issued a message at the end of eachdata collection interval during which the utilization remained outside the thresholds.

FNM03RVE NPM V2R7 5655-043NETWORK MANAGEMENT

REVIEW MONITOR EVENT MESSAGES

Command ===>

Host Name = LOCAL Resource Name = TIC01 Data Type = NETWORK RESOURCESDate/Time: from 09/30/00 12:00:00 to 09/30/00 13:30:00

Actual Resource Monitor ActualTime Name Type Value Monitor Event Description Limit12:00:00 TIC01 TICUTIL 20 MONITOR VALUE WAS BELOW THE LIMIT OF 4512:15:09 TIC01 TICUTIL 47 RESOLVED, NO LONGER BELOW THE LIMIT OF 4512:30:00 TIC01 TICUTIL 66 MONITOR VALUE WAS ABOVE THE LIMIT OF 6012:45:00 TIC01 TICUTIL 57 RESOLVED, NO LONGER ABOVE THE LIMIT OF 6013:00:00 TIC01 TICUTIL 7 MONITOR VALUE WAS BELOW THE LIMIT OF 4513:15:09 TIC01 TICUTIL 7 MONITOR VALUE WAS BELOW THE LIMIT OF 45


Figure 96. Review Monitor Event Messages Panel (FNM03RVE)



12.R

eviewin

gN

etwo

rkP

erform

ance



Isolating Problems on a Novell NetWareNetwork

If your network includes NetWare network resources, NPM can help you isolate or preventproblems by gathering performance data for these resources and by monitoring them againstperformance criteria you specify. For key performance data collected by NPM, you can sethigh and low criteria levels and thereby monitor the data continuously to check whether itexceeds the high criterion or falls below the low criterion.

The performance data you collect on NetWare Agent servers, to identify bottlenecks in yournetwork, for tuning and load balancing purposes and to optimize the usage of your networkresources.

To control the collection of this performance data, you can initialize NPM to collectperformance data automatically and then start, stop, and modify the collection using theNetWare commands LWGCOLL, LWGRES, and LWGSTOP.

You can view the performance data that NPM collects by using reporting programs togenerate and print reports from stored data.

Using NetWare Counters and MonitorsNPM provides a NetWare Agent that you install on a NetWare server. In NPM terms, such aserver is called a NetWare Agent server. Your NetWare network can include more than oneAgent server. An Agent server acts as the collection point for NetWare performance data.

The performance data is stored in NetWare counters which are combined into countergroups. Refer to the NPM Reference to obtain more information about the counter groupsand individual counters.

NPM enables you to collect performance data for these counter groups according to the typeof resource as shown in Table 16:

Table 16. NetWare Counter Group and Resource RelationshipsCounter Group Agent Server Server External Router

Server Global U

Server Volume U

Router Global U U U

LAN Board U U U

Communications U U U

13


13.Iso

lating

Pro

blem

so

na

NetW

areN

etwo

rk

You can set monitor criteria for certain counters within these groups and evaluate theperformance of your NetWare network using monitors as shown in Table 17:

Table 17. NetWare Counter Group and Monitor Type RelationshipsCounter Group Counter Group Description Monitor Type Monitor Description

Communications Gives information about specificIPX and SPX protocol-relatedinformation

- You cannot monitor this countergroup

LAN board Gives information aboutcommunications device drivers

PACKRCVD

PACKXMIT

Total number of packets received bythe LAN driversTotal number of packets transmittedby the LAN drivers

Router global Gives routing information aboutthe router services (packetsinformation)

RTRBUFFS

RTRHOPS

Number of packets discarded becauseno receive buffers were availableNumber of packets discarded becauseof too many hops

Server global Gives a general overview of theAgent server activity, includingCPU utilization, connections,disk operation, communications,and other information

CONNUTIL

SRVUTIL

Percentage of connections in useon the serverPercentage utilization of the server’sCPU

Server volume Gives detailed storageinformation about all diskvolumes on the Agent server.

VOLUTIL Percentage of volume space used onthe server for all volumes

Example: Tuning and Load Balancing a NetWare NetworkFor planning purposes, you might need to understand the utilization of some key resourcesin your NetWare network. For example, the number of connections in use and the peaknumber of connections in use on an Agent server. You can determine from this data whetheror not your planning assumptions are valid.

To obtain this information for an Agent server, start a collection for the server global countergroup. This group contains counters NWG06, NWG07, and NWG08, which are used to storeconnections data.

Follow this procedure to collect connections data:

1. Use the LWGRES command to define the NetWare Agent server for which data is to becollected.

2. Use the LWGCOLL command to collect data for this Agent server specifying the serverglobal counter group.

3. Print the data collected periodically to get the connections data from the appropriatecounters.

You can follow a similar procedure to obtain performance data for the other counter groups.For example, use the router global counter group to obtain data about communicationsdevice drivers.

Example: Monitoring a NetWare Network for Potential ProblemsYou can use NPM’s monitoring facility to help you prevent the performance of yournetwork from degrading. For example, you want to be informed if a server is being overutilized so that you can take preventative actions.

Using NetWare Counters and Monitors


NPM enables you to monitor resources by setting monitoring criteria. You can set high andlow criteria levels and thereby monitor the data continuously to check whether it exceeds thehigh criterion or falls below the low criterion. For example, you could be notifiedautomatically if the CPU utilization of a server falls outside the criteria levels you specify.

Follow this procedure to start monitoring critical resources in your NetWare network:

1. Use the LWGRES command to define the critical resources.

2. Use the LWGCOLL command to start monitoring these resources specifying theappropriate monitor types and criteria and counter groups.

For example, use the monitor type SRVUTIL to monitor the CPU utilization of an Agentserver.

3. Take action as appropriate if NPM notifies you that the data collected for a particularresource falls outside the monitoring criteria you specified.

You can follow a similar procedure to use other monitors. For example, use the monitor typePACKRCVD to monitor LAN board device drivers.

Monitoring a NetWare Network


13.Iso

lating

Pro

blem

so

na

NetW

areN

etwo

rk

Monitoring a NetWare Network


Managing NPM Data Files

This chapter provides an overview of NPM data files and describes file managementprocedures. It explains how to view the status of each file used by NPM and describes theactions you can take on those files. Finally, it provides scenarios that show how to performthese actions, using NPM’s online panels or the system console.

You must have data file management authorization specified in your security profile toperform the tasks described in this chapter. You also need console authorization to use thesystem console. See the NPM User’s Guide to determine what authorization you have.

You specify where NPM sends the data when you start data collection. The destination forthe data depends on the data type:

¶ Network data can be written to the review file, the NPM log, and SMF. It can also besent to the terminal or to the NetView program as an alert.

¶ Session data can be written to the session file, the VTAM log, the NPM log, and SMF.It can also be sent to the terminal or to the NetView program as an alert.

¶ LAN data can be written to the review file, the NPM log, and SMF. It can also be sentto the terminal or to the NetView program as an alert.

¶ RTM data can be written to the session file.

¶ VTAM data can be written to the review file, the NPM log, and SMF. It can also be sentto the terminal or to the NetView program as an alert.

¶ Network accounting data can be written to the NPM log or SMF.

¶ NetWare data can be written to the LAN work group file, the NPM log, and SMF. It canalso be sent to the NetView program as an alert.

Where you send the data determines what you can do with it. You can display only datawritten to the review (FNMREVn) and session (FNMSESn) files using NPM’s online panels.Use a reporting facility to view data from the NPM log, the VTAM log, or SMF. See theNetView Performance Monitor Reference for more information.

Your NPM probably has at least two files of each type, and can have as many as 39 files ofeach type. NPM writes data to the current file of each type. A current file is a file that isboth open and active. It is highlighted on the Data File Display and Management panel(FNM02OFL). When the current file becomes full, NPM automatically switches to the nextavailable file of that type. For session, review, and LAN work group files, the next availablefile is a file that is neither full, locked, nor defined as inactive at initialization.

For other types of files, the next available file is a file that is empty and was not defined asinactive at initialization. If there is no available file, NPM stops recording the data, although

14


14.M

anag

ing

NP

MD

ataF

iles

it does continue to collect it. After NPM fills the last file, it wraps around again to the firstavailable file of the same type, if one is available.

If there are no available files, NPM will reset the oldest full file that is defined asWRAP=YES. If one or more files are defined with WRAP=YES, NPM will be able tocontinue writing records indefinitely without requiring operator (manual or automated)intervention.

If you want to ensure that NPM continues to record the data it collects, you should defineone or more files with WRAP=YES. You can create a file management procedure to archivethe data that NPM has written before the file is reused.

Note: You can change or delete data written to the review file, session file, LAN workgroup file, NPM log, or VTAM log. However, data written to SMF or to the alert fileis owned by other programs. NPM cannot change or delete the data.

Example: No Data Found (Error Message)When you start to collect data, you specify whether you want to save the data to a file forviewing at a later time. When you are ready to view the data, you must specify the filewhere the data was saved. Because of NPM’s file management procedures, it is possible thatthe file or data you specified is not available. For example, you might receive the followingerror message when you try to display data:FNM756E NO DATA FOUND FOR THIS REQUEST

If you press the HELP PF key when you receive this message, you discover that the datayou specified for review does not match any data that was collected and saved. There arethree possible reasons for the mismatch:¶ The data was specified incorrectly¶ The data was not collected¶ The data was not saved

The following sections explain how to check systematically for these possibilities.

Checking for Incorrect SpecificationsTo display collected data, you must accurately specify the resource on which data wascollected, the file where the data was stored, and the time and date of the collection. Checkthese specifications on the panel where you tried to display the data. Use the followingprocedure to ensure there are no errors:

1. Verify the Resource Name field.

¶ Verify that you typed the resource name correctly in the Resource Name field.

¶ If you are displaying network or LAN data, ensure that you specify either monitor ordetail data as follows:

v To see monitor event messages for a particular resource, verify that you typed theresource name in the Resource Name field and MONITOR in the Data Type field.

v To see monitor event messages for all resources, verify that you typed MONITOR inthe Resource Name field. You also need to specify both a starting and stoppingdate and time.

v To see detail data, verify that you typed a resource name (not MONITOR) in theResource Name field and DETAIL in the Data Type field.

Managing NPM Data Files


2. Verify the file name.

¶ Verify that file names are typed correctly. NPM uses the current file if you do notenter a file name.

¶ Verify which file contains the data you want.

Use the Data File Display and Management panel (FNM02OFL) to determine theavailable files and the time spans covered by those files. Use fast path =9.5 to accessthe Data File Display and Management panel (FNM02OFL). See Figure 97 onpage 184.

For example, suppose you want to display network data. You specified REVIEW forthe current review file to see data for 07/01/00 from 07:15:00 to 10:10:00. Thecurrent file, which is highlighted on the Data File Display and Management panel(FNM02OFL), contains data for 07/02/00 from 00:00:01 to 24:00:00. However, yousee that another review file, FNMREV1, contains data for 07/01/00 from 00:00:01 to24:00:00. In this case, you must specify the FNMREV1 file to display the data youwant.

¶ If you do not see a file that has data for the period you want, determine if the datawas collected and saved. See “Determining Whether Data Was Collected” and“Determining Whether the Collected Data Has Been Saved” on page 183.

3. Verify the file status.

¶ Use fast path =9.5 to access the Data File Display and Management panel(FNM02OFL). Look at the Status/Remarks column. Ensure that the status of the fileyou want is not LOCKED, EMPTY, or blank. A blank status field indicates the file isclosed.

4. Verify the starting and stopping dates.

¶ If you omit these fields, NPM uses the last entries typed on the panel.

5. Verify the starting and stopping times.

¶ If you omit these fields, NPM uses the last entries typed on the panel.

¶ If you want to display data collected for an entire day, specify both the starting andstopping times as 00:00:00. Do not specify the starting time as 00:00:00 and thestopping time as 24:00:00. Specifying 00:00:00 is the same as specifying24:00:00, so no data is displayed.

See the NPM Reference for more information about specifying data in these fields.

Determining Whether Data Was CollectedIf you accurately specified the data to be displayed, it is possible that the data you want wasnot collected. For example, data might not have been collected for the particular resourceyou want to see. Use the following procedure to determine if the data you specified wasactually collected.

1. Determine whether data collection was automated at NPM initialization.

If NPM was initialized to collect data automatically, ask your system programmer toexamine the configuration report, the FNMILOG, or the SYSPRINT data set to see whattypes of data collection were specified at NPM initialization. Perhaps the data you wantis not collected automatically.

2. Verify that data collection was started from online panels or from the console.

No Data Found


14.M

anag

ing

NP

MD

ataF

iles

There are seven panels that show the data that is currently being collected and thecollections that have been deferred. Access these panels as follows:

¶ To view network data that is currently being collected, use fast path =1.1 to displaythe Resource List panel (FNM02RSL).

Examine the Collection Status field to determine if the collection is active for aparticular resource.

Note: If the specific resource you want to examine is not displayed, use the X optionto expand the displayed resources until you find it.

¶ To view session data that is currently being collected, use fast path =2.2 to displaythe Session Status/Stop (Active) Node Selection panel (FNM03SSA).

For either active or deferred session collections, a list of resources from which datais being collected is displayed. The panel listing active collections gives you theoption of displaying more detail.

¶ To view session data collections that have been deferred, use fast path =2.3 todisplay the Session Status/Stop (Deferred) Resource panel (FNM04SSD).

¶ To view the status of data collections for LAN bridges, use fast path =4.1 to displaythe LAN Bridge Selection panel (FNM02LBS).

NPM lists the bridge name along with its collection status, and the LAN Managerservice point name for each LAN bridge.

¶ To view the status of data collections for LAN segments, use fast path =4.2 todisplay the LAN Segment Selection panel (FNM02LSS).

NPM lists the segment number along with its collection status for each LANsegment.

¶ To view the status of VTAM data collections, use fast path =5.2 to display theVTAM Global Data Selection panel (FNM02GS1).

¶ To view the status of RTM data collections, select option 3 from the PrimaryOptions panel (FNM00PRI) to display the RTM Management panel (FNM01RTM).Select option 3 from this panel to display RTM collection status.

3. Verify that NPM has been bound to the primary NPALU.

NPM must be bound to the primary NPALU to perform network data collection. Use thefollowing procedure to determine whether NPM is bound to the primary NPALU:

a. Use fast path =9.3 to display the NPALU Display and Management panel(FNM02OCC).

b. Type the name of the host where data should have been collected in the Host Namefield and press ENTER.

c. Review the Status/Remarks field for the NCP. The status is CONNECTED if the NPM isbound to the NPALU.

If the status is DISCONNECTED (unbound) and if you are authorized to change it, typeB (for bind) in the Option field next to the NCP name. You can then collect networkdata for the host. If you do not have the proper authority, ask your systemprogrammer to bind NPM and the NPALU.

No Data Found


Determining Whether the Collected Data Has Been SavedEven though NPM has collected the data you want to view, it might not have recorded it.When you specify data to be collected, you have several options for storing the data. If thereview file, the session file, or the LAN work group file was not specified, the data is notavailable for viewing. If these files were specified, they might have been unavailable toreceive data or the data might have been deleted. Use the following procedure to determinewhether the data was saved properly:

1. Verify the files that were specified as the data destinations.

When you start data collection, you must specify a file where data can be saved if youwant to view it. For session data, specify the session file as a destination. For networkand LAN data, specify the review file as a destination. For NetWare data, specify theLAN work group file as the destination.

You can tell if the data has been saved to a review or session file by looking at thestatus of data collection. Follow the directions under Step 2 in “Determining WhetherData Was Collected” on page 181 to display the status.

For network and LAN data, look under the EXCEPTION DEST and DATA DEST columns.You should see an R in the REV column for review. For session data, look under theSESSCOLL column. You should see a value greater than zero if collection is active.

You can tell if the data has been saved to a LAN work group file by checking the statusof the data collection on panel FNM02FL.

2. Determine if NPM has stopped recording data.

The collected data might have been sent to a file at a time when all files of that typewere full or otherwise unavailable. In this case, NPM stops recording the data in the fileand no data is saved. To prevent this problem, you need to reset files when they becomefull, switch to the next available file before the current one becomes full, or define oneor more files with WRAP=YES to automate this process. See the next two scenarios,Example: Resetting a File and “Example: Preparing a File for Backup” on page 185 formore information.

3. Determine if the file was reset.

The data might have been saved in a file that was reset later by an operator. Resetting afile deletes all its data.

Note: If you still are not able to display the collected data, there is one other possiblereason. NPM has buffers for the data written to the VSAM files. If the number ofrecords written is small, the data might still be contained in these buffers.

Example: Resetting a FileAs discussed in the previous scenario, one reason that you might not be able to viewcollected data is that all data files were full when the data was collected. Periodically, youmust reset data collection files so that NPM can record data without interruption. You canuse up to 39 session, 39 review files, and 39 LAN work group files for recording data thatyou can view. When one file is full, NPM switches to the next file and continues to recorddata. NPM stops recording data when all files are full.

You can choose either an automatic or manual way to enable NPM to continue to recorddata when all files are full. Both methods delete the current contents of a file and change itsstatus to EMPTY. This occurs even if the file was previously closed.

No Data Found


14.M

anag

ing

NP

MD

ataF

iles

To do this automatically, define all the files with WRAP=YES in FNMINIT. NPM willautomatically reset and switch to the oldest full file.

To do this manually you must reset the files yourself. This less efficient method is describedbelow.

For example, suppose your NPM has two session files, FNMSES1 and FNMSES2. NPM hasjust filled FNMSES1 and has switched to FNMSES2, where it is currently writing data. Youmust reset FNMSES1 so it is ready to receive data when FNMSES2 becomes full. Use thefollowing procedure to reset FNMSES1:

1. Use fast path =9.5 to display the Data File Display and Management panel(FNM02OFL), shown in Figure 97

This panel shows the status of all data files known to NPM.

If FNMSES1 is not on your local host, use fast path =9 to display the Control Functionspanel (FNM01OMN) and enter the host name before selecting option 5.

2. If you want to save the data, dump the file to tape using your installation’s proceduresand tools.

3. Type R in the Option field next to FNMSES1 �1� and press ENTER.

Option R resets the file, deleting its contents and changing the status to EMPTY so that thefile can receive data again. NPM issues a message indicating that your request is beingprocessed.

NPM starts writing data to FNMSES1 when FNMSES2 becomes full.

Note: You can also use the procedure described in this scenario to reset review, LAN workgroup, NPM log, and NPM VTAM log files.

FNM02OFL NPM V2R7 5655-043CONTROL FUNCTIONS

DATA FILE DISPLAY AND MANAGEMENTCommand ===>

Host Name = LOCALSelect Option: O=Open, C=Close, R=Reset, S=Switch, L=Lock, U=Unlock

Option Filename Beginning and Ending Date/Time Status/Remarks=> �1� FNMSES1 04/19/00 14:32 04/19/00 14:58 FULL=> FNMSES2 04/21/00 09:03 04/22/00 09:37 ACTIVE=> FNMREV1 04/19/00 16:56 04/19/00 16:58 ACTIVE=> FNMREV2 EMPTY=> FNMLWG1 11/25/99 16:56 11/25/99 16:58 ACTIVE=> FNMLWG2 EMPTY=> FNMLOG1 04/20/00 09:03 04/21/00 09:37=> FNMSMF STOP EMPTY=> FNMALERT 04/20/00 09:06 04/20/00 09:12 ACTIVE=> FNMVLOG1 EMPTY=> FNMVLOG2


Figure 97. Data File Display and Management Panel (FNM02OFL)

Resetting a File


Example: Preparing a File for BackupYou might not want to wait to save collected data until a file is full. You can back up a fileat any time. However, you must ensure that NPM can continue recording data to another filebefore you back up the file.

For example, suppose that your NPM has two review files, FNMREV1 and FNMREV2. Youwant to back up FNMREV1, the file where NPM is currently writing data. You must firstswitch from FNMREV1 to FNMREV2, so that NPM continues to record data. Then, youneed to prevent NPM from writing to FNMREV1 while you perform your backupprocedures. Use the following procedure to accomplish these tasks:

1. Use fast path =9.5 to access the Data File Display and Management panel (FNM02OFL).

2. Ensure that EMPTY appears in the Status/Remarks field next to FNMREV2.

If the status does not say EMPTY, reset the file as explained in “Example: Resetting aFile” on page 183.

3. Type S in the Option field next to FNMREV1 and press ENTER.

Option S switches NPM to the next available file, FNMREV2.

4. Type C in the Option field next to FNMREV1 and press ENTER.

NPM temporarily closes FNMREV1 so that no data can be written to it. You can nowback up the file. Note, however, that the close is only temporary: if you perform a switchon FNMREV2, or if FNMREV2 becomes full, NPM will switch back to FNMREV1. IfFNMREV1 has been defined with WRAP=YES, even if the file is full and closed, NPMwill reopen and reset the file, overriding the close option. After you have backed up thefile, reset the file so that it is available for collection. See the previous scenario forinstructions.

Note: You can use the procedures described in this scenario to back up session, LAN workgroup, NPM log, and VTAM log files as well.

Example: Managing Data Files with the System ConsoleYou might not want to log on to NPM just to reset or switch files. You can enter commandsfrom the system console to perform these and other tasks. NPM’s console support enablesyou to enter general, data collection, and special console control commands from the systemconsole. See the NPM User’s Guide for descriptions of all NPM commands.

There are three ways to issue commands to NPM from the system console. They aredescribed in detail in the NPM User’s Guide.

You must know the name of the procedure used to start NPM before you enter commands atthe system console. Type =9.4;down on the Select Option or Command field of any onlinepanel to display the Summary Display panel (FNM02OPS). The name of the procedure usedto start NPM is shown in the Job Name field on this panel.

Use the following procedure to perform the file management procedures described in theearlier scenario on resetting files:

1. Enter the following command to close the file FNMSES1:F FNMSNPM,VARY INACT,ID=FNMSES1

Preparing a File for Back Up


14.M

anag

ing

NP

MD

ataF

iles

FNMSNPM is the sample name of the procedure used to start NPM, substitute the nameof your procedure in its place.

2. If you want to save the data, dump the file to tape using your installation’s proceduresand tools.

3. Enter the following command to reset FNMSES1:F FNMSNPM,VARY RESET,ID=FNMSES1

FNMSNPM is the sample name of the procedure used to start NPM, substitute the nameof your procedure in its place.

This command deletes the contents of the file so it can receive data from NPM again.

See the NPM User’s Guide for more information about VARY and other commands that youcan issue from the system console.

Note: You can also use the commands described in this scenario to reset review, LAN workgroup, NPM log, and NPM VTAM log files.

Example: Available Actions Based on File StatusThis section describes the different actions you can take with NPM files when you workwith the Data File Display and Management panel (FNM02OFL), shown in Figure 98.

Table 18 on page 187 describes some of the common conditions displayed on the Data FileDisplay and Management panel and lists the actions you can perform. The exampleconditions used in Table 18 on page 187 are based on the displayed values for the Beginningand Ending Date/Time and Status/Remarks field. This table is not a comprehensive list.

FNM02OFL NPM V2R6 5655-043CONTROL FUNCTIONS

DATA FILE DISPLAY AND MANAGEMENTCommand ===>

Host Name = LOCALEnter Option: O=Open, C=Close, R=Reset, S=Switch, L=Lock, U=Unlock

Option File Name Beginning and Ending Date/Time Status/Remarks=> FNMSES1 EMPTY=> FNMSES2 EMPTY=> FNMREV1 09/30/00 10:02 09/30/00 11:08 ACTIVE=> FNMREV2 OPEN EMPTY=> FNMLWG1 11/25/99 10:02 11/25/99 11:08 ACTIVE=> FNMLWG2 OPEN EMPTY=> FNMLOG1 EMPTY=> FNMLOG2 EMPTY=> FNMSMF ACTIVE EMPTY=> FNMVLOG1 EMPTY=> FNMVLOG2 EMPTY


Figure 98. Data File Display and Management Panel (FNM02OFL)

Managing Data Files with the System Console


Table 18. Examples of File Management SituationsFNM02OFL Panel Fields

Explanation Available ActionsDate/ Time

Status/Remarks

Not Displayed Active/Empty¶ data set is immediately

available to record

¶ No data recorded duringcurrent NPM execution

S/C If available1, makes the next data set active;otherwise, stops recording.

L Stops recording.

Prevents the data set from being activated.2

Prevents the SWITCH command from affectingthe data set.

U Releases a locked data set.

Displayed Active¶ data set is immediately

available to record

¶ Some data alreadyrecorded

S/C If available1, makes the next data set active;otherwise, stops recording.

L Stops recording.


U Releases a locked data set.

Displayed Not displayed¶ data set is immediately

available to record (itneeds to be switched)


O Opens the data set.

S Makes this data set active.2

L Prevents the data set from being active.


R Deletes all recorded data.

Not displayed Not displayed¶ Specific to the NPM log

data set

¶ data set is immediatelyavailable to record (itneeds to be reset)


O Opens the data set.

L Prevents NPM from using the data set. Forexample, you cannot display the contents of thedata set using NPM panels.


Displayed Full¶ data set is immediately

available to record (itneeds to be reset)

¶ All data sets recorded

L Prevents NPM from using the data set. Forexample, you cannot display the contents of thedata set using NPM panels.


S=SWITCH C=CLOSE L=LOCK U=UNLOCK R=RESET O=OPEN

Note:

1. For session, review, or LAN work group data sets, the next available data set is one that is not full, locked, or defined asinactive at initialization. For NPM log data sets, the next available data set is one that is empty and was not defined asinactive at initialization.

2. A data set can become active when a SWITCH or CLOSE command is issued on the previous data set. The lock preventsthe data set from being activated.

File Status Actions


14.M

anag

ing

NP

MD

ataF

iles


Part V. Appendixes



Glossary

A

ACB(1) In VTAM programs, access method control block. (2) In NCP, adapter control block. (3) Application controlblock.

access method control block (ACB)(1) A control block that links an application program to VSAM or VTAM. (2) In VTAM statistics collection, thecontrol block passed to VTAM when an application is establishing itself as able to send and receive data.

access method services (AMS)The facility used to define and reproduce VSAM key-sequenced data sets (KSDS).

ACFAdvanced Communications Function.

ACF/NCPAdvanced Communications Function for the Network Control Program. Synonym for NCP.

ACF/SSPAdvanced Communications Function for the System Support Programs. Synonym for SSP.

ACF/TCAMAdvanced Communications Function for the Telecommunications Access Method. Synonym for TCAM.

ACF/VTAMAdvanced Communications Function for the Virtual Telecommunications Access Method. Synonym for VTAM.

active collectionIn NPM, the process of collecting data at the current time about a resource.

adapter control block (ACB)In NCP, a control block that contains line control information and the states of I/O operations for BSC lines, SSlines, or SDLC links.

address spaceA set of addresses used to uniquely identify network accessible units, sessions, adjacent link stations, and links ina node for each network in which the node participates. A type 2.1 node has one address space for intranoderouting and one for each transmission group on which it can send message units.

address space identifier (ASID)A unique, system-assigned identifier for an address space.

adjacent link station (ALS)(1) In SNA, a link station directly connected to a given node by a link connection over which network traffic canbe carried.

Note: Several secondary link stations that share a link connection do not exchange data with each other andtherefore are not adjacent to each other.

(2) With respect to a specific node, a link station partner in an adjacent node.

adjacent nodesTwo nodes connected together by at least one path that connects no other node.

ADPAutomatic data processing.

Advanced Communications Function (ACF)A group of IBM-licensed programs, principally VTAM, TCAM, NCP, and SSP, that use the concepts of SystemsNetwork Architecture (SNA), including distribution of function and resource sharing.


Glo

ssary

advanced peer-to-peer networking (APPN)An extension to SNA featuring (a) greater distributed network control that avoids critical hierarchicaldependencies, thereby isolating the effects of single points of failure, (b) dynamic exchange of network topologyinformation to foster ease of connection and reconfiguration, adaptive route selections, and simplified networkdefinition, and (c) automated resource registration and directory lookup. APPN extends the LU 6.2 peerorientation for end-user services to network control; APPN also uses LU 6.2 protocols on its own control pointsessions that provide the network control.

advanced program-to-program communication (APPC)An implementation of the SNA/SDLC LU6.2 protocol that allows interconnected systems to communicate andshare the processing of programs.

agentReports to the managing process, such as a network control station, on the status of managed network elementsand performs actions on these elements as directed by the managing process. Examples of network elements aredevices such as hosts, routers, and terminal servers.

alert(1) A message sent to a management services focal point in a network to identify a problem or an impendingproblem. (2) In the NetView program, a high priority event that warrants immediate attention. A database recordis generated for certain event types that are defined by user-constructed filters.

alert conditionA problem or impending problem for which some or all of problem determination, diagnosis, or resolution isexpected at a collection point or a system problem determination focal point.

alias addressAn address used by a gateway NCP and a gateway system services control point (SSCP) in one network torepresent a logical unit (LU) or SSCP in another network.

alias nameA name unique within one of two or more interconnected networks that is assigned by a gateway SSCP and isused in that subnetwork to represent an NAU that resides in another subnetwork. Alias names must be predefinedwithin a gateway SSCP; if an alias is not provided, it is assumed to be the same as the real name.

allocateA logical unit (LU) 6.2 application program interface (API) verb used to assign a session to a conversation forthe conversation’s use. Contrast with deallocate.

alternate applicationThe subsystem that is prepared to take over a particular active application’s extended recovery facility (XRF)sessions with terminal users in case the application fails.

AMSAccess method services.

APARAuthorized program analysis report. A report of a problem caused by a suspected defect in a current unalteredrelease of a program.

APIApplication program interface.

APPCAdvanced program-to-program communication.

APPLApplication program.

application control block (ACB)The control blocks created from the output of DBDGEN and PSBGEN and placed in the ACB library for useduring online and DBB region type execution of IMS/VS.


application identifier (APPLID)The name of an application as defined to VTAM.

application program interface (API)(1) A functional interface supplied by the operating system or by a separately orderable licensed program thatallows an application program written in a high-level language to use specific data or functions of the operatingsystem or the licensed program. (2) The interface through which an application program interacts with an accessmethod. In VTAM, it is the language structure used in control blocks so that application programs can referencethem and be identified to VTAM.

APPLIDApplication ID.

APPNAdvanced peer-to-peer networking.

APPN intermediate routingThe capability of an APPN network node to accept traffic from one adjacent node and pass it on to another, withawareness of session affinities in controlling traffic flow and outage notifications.

APPN intermediate routing networkThe portion of an APPN network consisting of the network nodes and their interconnections.

ASIDAddress space identifier.

authorized program analysis report (APAR)A request for correction of a problem caused by a defect in a current unaltered release of a program.

availableIn VTAM, pertaining to a logical unit that is active, connected, enabled, and not at its session limit.

B

base collection intervalThe primary unit, in seconds or minutes, which NPM uses to calculate the span of time in which data iscollected.

basic sequential access method (BSAM)In NPM, the method by which all PIUs collected for selected LUs can be logged into a sequential data set asthey pass through VTAM.

basic transmission unit (BTU)In SNA, the unit of data and control information passed between path control components. A BTU can consist ofone or more path information units (PIUs). See also blocking of PIUs.

binary synchronous communication (BSC)A form of telecommunication line control that uses a standard set of transmission control characters and controlcharacter sequences, for binary synchronous transmission of binary-coded data between stations. Contrast withSynchronous Data Link Control (SDLC).

binary synchronous transmissionData transmission in which synchronization of characters is controlled by timing signals generated at the sendingand receiving stations. See also start-stop transmission and Synchronous Data Link Control (SDLC).

blocking of PIUsIn SNA, an optional function of path control that combines multiple path information units (PIUs) in a singlebasic transmission unit (BTU).

Note: When blocking is not done, a BTU consists of one PIU.


Glo

ssary

bracketIn SNA, one or more chains of request units and their responses that are exchanged between two session partnersand that represent a transaction between them. A bracket must be completed before another bracket can bestarted. Examples of brackets are database inquiries/replies, update transactions, and remote job entry outputsequences to workstations.

bracket protocolIn SNA, a data flow control protocol in which exchanges between two session partners are achieved through theuse of brackets, with one partner designated at session activation as the first speaker and the other as the bidder.The bracket protocol involves bracket initiation and termination rules.

BSAMBasic sequential access method.

BSCBinary synchronous communication.

BTUBasic transmission unit.

buffer pool(1) An area of storage in which all buffers of a program are kept. (2) In ACF/TCAM, a group of buffers havingthe same size. A buffer pool is established at initialization time in the message control program. The buffers arebuilt in extents chained together.

C

CCU(1) Communication control unit. (2) Central control unit.

CDRMCross-domain resource manager.

CDRSCCross-domain resource.

central control unit (CCU)The communication controller hardware unit that contains the circuits and data flow paths needed to executeinstructions and to control controller storage and the attached adapters.

chain(1) A group of logically linked user data records processed by LU 6.2. (2) A group of request units delimited bybegin-chain and end-chain. Responses are always single-unit chains. See RU chain.

channel-attached(1) Pertaining to the attachment of devices directly by input/output channels to a host processor. (2) Pertaining todevices attached to a controlling unit by cables, rather than by telecommunication lines. Contrast withlink-attached. Synonymous with local.

CICSCustomer Information Control System.

CIPChannel Interface Processor.

class of service (COS)A designation of the transport network characteristics, such as route security, transmission priority, andbandwidth, needed for a particular session. The class of service is derived from a mode name specified by theinitiator of a session.


cluster(1) A station that consists of a control unit (a cluster controller) and the terminals attached to it. (2) In systemswith VSAM, a named structure consisting of a group of related components, for example, a data component withits index component.

cluster controllerA device that can control the input/output operations of more than one device connected to it. A cluster controllermay be controlled by a program stored and executed in the unit; for example, the IBM 3601 FinanceCommunication Controller. Or, it may be entirely controlled by hardware; for example, the IBM 3272 ControlUnit.

CMSCommunications storage manager.

collection intervalIn NPM, a user-specified value that controls the time at which performance data is transmitted.

collection point block (CPB)In NPM, a control block used to coordinate the collection of network and session data.

common storage area (CSA)An area of storage common to all address spaces.

communication control unit (CCU)A communication device that controls transmission of data over lines in a network. Communication control unitsinclude transmission control units (such as the 2702 transmission control unit) and communication controllers(such as the 3720 or 3725).

communication controllerA type of communication control unit whose operations are controlled by one or more programs stored andexecuted in the unit. It manages the details of line control and the routing of data through a network.

Communications storage manager (CMS).A component of VTAM that enables host applications to share data with VTAM and other CSM users withouthaving to physically copy the data.

Configuration Control Program (CCP)An IBM-licensed program used interactively to define, display, and alter configurations that contain networkcontrollers.

connectedIn VTAM, the state of a physical unit (PU) or a logical unit (LU) that has an active physical path to the hostprocessor containing the system services control point (SSCP) that controls the respective PU or LU.

connectionIn VTAM, synonym for physical connection.

connection networkA representation within an APPN network of a shared-access transport facility, such as a token ring, that reducesthe system-definition burden on each APPN end node attached to the facility. Each such node may represent itsconnectivity to the other, real nodes on the facility generically, by a single, virtual routing node, which eachreports to its network node server in the APPN network. The report includes local signaling information neededby any partner wanting to contact it over the facility. The transport facility represented this way, and theassemblage of nodes using the same virtual routing node representation, are collectively referred to as aconnection network. By matching references to the same virtual routing node during its route selection, thenetwork node server passes the required DLC signaling information in the search reply to the node originating asession over the connection network.

control point (CP)A collection of tasks that provide directory and route selection functions for advanced peer-to-peer networking(APPN). An end node control point provides its own configuration, session, and management services withassistance from the control point in its serving network node. A network node control point provides session androuting services.


Glo

ssary

conversationA logical connection between two transaction programs using an LU 6.2 session. Conversations are delimited bybrackets to gain exclusive use of a session.

COSClass of service.

CPControl point.

CP nameA network-qualified name of a control point (CP), consisting of a network ID qualifier identifying the network(or name space) to which the CP’s node belongs, and a unique name within the scope of that network IDidentifying the CP. Each type 2.1 node has one CP name, assigned to it at system-definition time. Within anAPPN network, all network nodes share a common network ID. End nodes may have distinct network IDs; thisallows them to connect into separate APPN networks and to manage their own name spaces independently of therest of the network.

CP-CP sessionsThe parallel sessions between two control points, using LU 6.2 protocols and a mode name of CPSVCMG, onwhich network services requests and replies are exchanged. Each CP of a given pair has one contention-winnersession and one contention-loser session with the other.

CPBCollection point block.

cross-domainIn SNA, pertaining to control or resources involving more than one domain.

cross-domain resource manager (CDRM)(1) In VTAM, the function in the system services control point (SSCP) that controls initiation and termination ofcross-domain sessions. (2) In SNA, a CDRM is a host with VTAM running on it that manages a portion of anSNA network.

cross-domain resource (CDRSC)In VTAM, synonym for other-domain resource.

CRPLCopied request parameter list control block.

CSACommon storage area.

CSMCommunications storage manager.

Customer Information Control System (CICS)An IBM-licensed program that enables transactions entered at remote terminals to be processed concurrently byuser-written application programs. It includes facilities for building, using, and maintaining databases.

D

DASDDirect access storage device.

data communication equipment (DCE)In a data station, the equipment that provides the signal conversion and coding between the data terminalequipment (DTE) and the line.

Notes:

1. The DCE may be separate equipment or an integral part of the DTE or of the intermediate equipment.

2. A DCE may perform other functions that are usually performed at the network end of the line.


data flow control (DFC)In SNA, a request/response unit (RU) category used for requests and responses exchanged between the data flowcontrol layer in one half-session and the data flow control layer in the session partner.

data flow control (DFC) protocolIn SNA, the sequencing rules for requests and responses by which network addressable units (NAUs) in a sessioncoordinate and control data transfer and other operations; for example, bracket protocol. See also data linkcontrol protocol.

data forwardingThe transmission of data from the NPM host to a workstation.The number of data forwarding requests indicates the number of workstations requesting real-time data from theNPM host about a particular resource.

data linkIn SNA, synonym for link.

data link control (DLC)A set of rules used by nodes on a data link (such as an SDLC link or a token ring) to accompany an orderlyexchange of information.

data link control (DLC) protocolIn SNA, a set of rules used by two nodes on a data link to accomplish an orderly exchange of information.Synonymous with line control.

data setThe major unit of data storage and retrieval, consisting of a collection of data in one of several prescribedarrangements and described by control information to which the system has access.

data set membersMembers of partitioned data sets that are individually named elements of a larger file that can be retrieved byname.

data terminal equipment (DTE)That part of a data station that serves as a data source, data sink, or both.

data typesIn the NetView program, a description of the organization of panels. Data types are alerts, events, and statistics.Data types are combined with resource types and display types to describe the NetView program’s displayorganization. See also display types and resource types.

DCEData communication equipment.

DCSDynamic configuration support.

DDData definition.

DDRDynamic definite response.

deallocateA logical unit (LU) 6.2 application program interface (API) verb that terminates a conversation, thereby freeingthe session for a future conversation. Contrast with allocate.

deferred collectionIn NPM, the process of collecting data at a later time about a resource.

definite response (DR)In SNA, a protocol requested in the form-of-response-requested field of the request header that directs thereceiver of the request to return a response unconditionally, whether positive or negative, to that request chain.Contrast with exception response and no response. See also negative response and positive response.


Glo

ssary

definition statement(1) In VTAM, the statement that describes an element of the network. (2) In NCP, a type of instruction thatdefines a resource to the NCP.

definition statement identifierA specific character string that identifies the purpose of a definition statement.

destination subareaIn SNA, the location to which information is to be sent.

direct access storage device (DASD)A device in which access time is effectively independent of the location of the data.

directoryA database in an APPN node that lists names of resources (in particular, logical units) and records the CP nameof the node where each resource is located. See distributed directory database and local directory database.

directory services (DS)A control point component of an APPN node that maintains a directory of the location of network resources andmanages searches of that directory.

discarded packetA packet that is intentionally destroyed.

display levelsSynonym for display types.

display typesIn the NetView program, a concept to describe the organization of panels. Display types are defined as total,most recent, user action, and detail. Display types are combined with resource types and data types to describeNetView’s panel organization. See also data types and resource types. Synonymous with display levels.

distributed directory databaseThe complete listing of all the resources in the network as maintained in the individual directories scatteredthroughout an APPN network. Each node has a piece of the complete directory, but it is not necessary for anyone node to have the entire list. Entries are created, modified, and deleted through system definition, operatoraction, automatic registration, and ongoing network search procedures. Synonymous with distributed networkdirectory and network directory database.

distributed network directorySynonym for distributed directory database.

DLCData link control.

DNCDynamic network collection.

domainThat part of a computer network in which the data processing resources are under common control.

DSDirectory services.

DSADestination subarea field.

DTEData terminal equipment.

dynamic configuration support (DCS)In NPM, a function which allows users to change NCP definitions.


dynamic data displayIndicates that the REAL-TIME DataView window is refreshed automatically as soon as new data arrives.

dynamic definite response (DDR)A facility that allows a demountable volume to be moved and repositioned if necessary without abnormallyterminating the job or repeating the initial program load procedure.

dynamic network collection (DNC)The NPM subsystem that collects, monitors, and displays data from within the network control program and hasan automatic start and stop.

E

ECSA(1) Extended common storage area. (2) Extended common service area.

element(1) A field in the network address. (2) In SNA, the particular resource within a subarea that is identified by anelement address. See also subarea.

Enterprise System Connection (ESCON)A set of IBM products and services that provides a dynamically connected environment within an enterprise.

entry pointIn SNA, a type 2.0, type 2.1, type 4, or type 5 node that provides distributed network management support. Itsends network management data about itself and the resources it controls to a focal point for centralizedprocessing, and it receives and executes focal-point initiated commands to manage and control its resources.

ER(1) Explicit route. (2) Exception response.

ESCONEnterprise Systems Connection.

ESS(1) Ethernet transmission subsystem. (2) Ethernet subsystem.

EthernetA 10-megabit baseband local area network that allows multiple stations to access the transmission medium at willwithout prior coordination, avoids contention by using carrier sense and deference, and resolves contention byusing collision detection and transmission. Ethernet uses carrier sense multiple access with collision detection(CSMA/CD).

eventIn the NetView program, a record indicating irregularities of operation in physical elements of a network.

event messageA message created in response to an event.

exception response (ER)In SNA, a protocol requested in the form-of-response-requested field of a request header that directs the receiverto return a response only if the request is unacceptable as received or cannot be processed; that is, a negativeresponse, but not a positive response, may be returned. Contrast with definite response and no response. See alsonegative response and positive response.

EXEC(1) In a VM operating system, a user-written command file that contains CMS commands, other user-writtencommands, and execution control statements, such as branches. (2) In NPM, a user-written command file thatcontains NPM commands that can be run at NPM startup, online, or through the console. Also called NPMEXEC.

exit programSynonym for exit routine.


Glo

ssary

exit routineEither of two types of routines: installation exit routines or user exit routines. Synonymous with exit program.See installation exit routine and user exit routine.

explicit route (ER)In SNA, a series of one or more transmission groups that connect two subarea nodes. An explicit route isidentified by an origin subarea address, a destination subarea address, an explicit route number, and a reverseexplicit route number. Contrast with virtual route (VR).

F

fast pathIn SAA Basic Common User Access architecture, a method of doing something more directly and quickly thanthe usual way; for example, pressing a function key is faster than typing a command.

FICFirst-in-chain.

FIDFormat identification.

filterIn the NetView program, a function that limits the data that is to be recorded on the database and displayed atthe terminal. See recording filter and viewing filter.

first-in-chain (FIC)A request unit (RU) whose request header (RH) begin chain indicator is on and whose RH end chain indicator isoff. See also RU chain.

flow controlIn SNA, the process of managing the rate at which data traffic passes between components of the network. Thepurpose of flow control is to optimize the rate of flow of message units with minimum congestion in thenetwork; that is, to neither overflow the buffers at the receiver or at intermediate routing nodes, nor leave thereceiver waiting for more message units. See also pacing.

FMDFunction management data.

FMHFunction management header.

focal pointIn the NetView program, the focal point domain is the central host domain. It is the central control point for anymanagement services element containing control of the network management data.

format identification (FID) fieldIn SNA, a field in each transmission header (TH) that indicates the format of the TH; that is, the presence orabsence of certain fields. TH formats differ in accordance with the types of nodes between which they pass.There are six FID types:

1. FID0, used for traffic involving non-SNA devices between adjacent subarea nodes when either or both nodesdo not support explicit route and virtual route protocols

2. FID1, used for traffic involving SNA devices between adjacent subarea nodes when either or both nodes donot support explicit route and virtual route protocols

3. FID2, used for traffic between a subarea node and an adjacent type 2 peripheral node

4. FID3, used for traffic between a subarea node and an adjacent type 1 peripheral node

5. FID4, used for traffic between adjacent subarea nodes when both nodes support explicit route and virtualroute protocols

6. FIDF, used for certain commands (for example, for transmission group control) sent between adjacent subareanodes when both nodes support explicit route and virtual route protocols.


formatted system servicesA portion of VTAM that provides certain system services as a result of receiving a field-formatted command,such as an Initiate or Terminate command.

frame(1) The unit of transmission in some local area networks, including the IBM Token-Ring Network. It includesdelimiters, control characters, information, and checking characters. (2) In SDLC, the vehicle for every command,every response, and all information that is transmitted using SDLC procedures.

function management data (FMD)An RU category used for end-user data exchanged between logical units (LUs) and for requests and responsesexchanged between network services components of LUs, PUs, and control points.

function management header (FMH)One or more headers, optionally present in the leading request units (RUs) of an RU chain, that allow one LU to:(a) select a transaction program or device at the session partner and control the way in which the end-user data itsends is handled at the destination, (b) change the destination or the characteristics of the data during the session,and (c) transmit between session partners status or user information about the destination (for example, a programor device). Function management headers can be used with LU type 1, 4, and 6.2 protocols.

G

gateway(1) A functional unit that interconnects two computer networks with different network architectures. A gatewayconnects networks or systems of different architectures. A bridge interconnects networks or systems with thesame or similar architectures. (2) In the AIX operating system, an entity that operates above the link layer andtranslates, when required, the interface and protocol used by one network into those used by another distinctnetwork. (3) In TCP/IP, a device used to connect two systems that use either the same or differentcommunications protocols. (4) The combination of machines and programs that provide address translation, nametranslation, and system services control point (SSCP) rerouting between independent SNA networks to allowthose networks to communicate. A gateway consists of one gateway NCP and at least one gateway VTAM. (5) Inthe IBM Token-Ring Network, a device and its associated software that connect a local area network to anotherlocal area network or a host that uses different logical link protocols.

gateway NCPAn NCP that performs address translation to allow cross-network session traffic. The gateway NCP connects twoor more independent SNA networks. Synonymous with gateway node.

gateway nodeSynonym for gateway NCP.

gateway SSCPSynonym for gateway VTAM.

gateway VTAMAn SSCP that is capable of cross-network session initiation, termination, takedown, and session outagenotification. A gateway VTAM is in session with the gateway NCP; it provides network name translation andassists the gateway NCP in setting up alias network addresses for cross-network sessions. Synonymous withgateway SSCP.

generationThe process of assembling and link editing definition statements so that resources can be identified to all thenecessary programs in a network.

generation definitionThe definition statement of a resource used in generating a program.

H

hexHexadecimal.


Glo

ssary

HIPERHigh-impact or pervasive APAR.

historical dataIndicates that the data displayed in the HISTORICAL DataView window was requested within a specified timespan in the past from the NPM host VSAM data files. The performance data collection is not currently active. Nodata forwarding is required.

hopIn APPN, a portion of a route that has no intermediate nodes. It consists of only a single transmission groupconnecting adjacent nodes.

host NPMA host to which a user is connected that is running NPM.

host transit timeIn the NetView Performance Monitor (NPM), the average time (in seconds) that all transactions spend in thehost. It includes both VTAM and application time. It is also reported as an average for the transactionsoriginating at the logical unit for which data collection is occurring. See operator transit time and network transittime.

I

I frameInformation frame.

installation exitThe means specifically described in an IBM software product’s documentation by which an IBM softwareproduct may be modified by a customer’s system programmers to change or extend the functions of the IBMsoftware product. Such modifications consist of exit routines written to replace one or more existing modules ofan IBM software product, or to add one or more modules or subroutines to an IBM software product, for thepurpose of modifying or extending the functions of the IBM software product. Synonymous withinstallation-wide exit. See user exit.

installation exit routineA routine written by a user to take control at an installation exit of an IBM software product.

installation-wide exitSynonym for installation exit.

interconnected networksSNA networks connected by gateways.

intermediate routing networkSee APPN intermediate routing network.

Internet Protocol (IP)A protocol used to route data from its source to its destination in an Internet environment.

intranode routingThe capability of path control to route PIUs for sessions between NAUs that reside in the same node.

IPInternet Protocol.

J

JCLJob control language.

JESJob entry subsystem (MVS).


job control language (JCL)A control language used to identify a job to an operating system and to describe the job’s requirements.

K

key-sequenced data set (KSDS)A VSAM file or data set whose records are loaded in key sequence and controlled by an index. The NetViewPerformance Monitor (NPM) uses this type of file for the session statistics file and the network review file.

keyword(1) A name or symbol that identifies a parameter. (2) The part of a command operand that consists of a specificcharacter string (such as DSNAME=). See also definition statement.

keyword parameterA parameter that consists of a keyword followed by one or more values.

KSDSKey-sequenced data set.

L

LANLocal area network.

LAN network managerAn IBM program that manages LAN networks.

last-in-chain (LIC)A request unit (RU) whose request header (RH) end chain indicator is on and whose RH begin chain indicator isoff. See also RU chain.

layerIn SNA, a grouping of related functions that are logically separate from the functions in other groups.Implementation of the functions in one layer can be changed without affecting functions in other layers.

LENLow-entry networking.

LIC(1) Last-in-chain. (2) In NCP, line interface coupler.

line controlSynonym for data link control protocol.

line speedThe number of binary digits that can be sent over a telecommunication line in one second, expressed in bits persecond (bps).

linkIn SNA, the combination of the link connection and the link stations joining network nodes, for example aSystem/370 channel and its associated protocols or a serial-by-bit connection under the control of SynchronousData Link Control (SDLC). A link connection is the physical medium of transmission. A link, however, is bothlogical and physical. Synonymous with data link.

link connectionThe physical equipment providing two-way communication between one link station and one or more other linkstations; for example, a telecommunication line and data communication equipment (DCE).

link protocol(1) The rules for sending and receiving data at the link level. (2) See protocol.


Glo

ssary

link station(1) The hardware and software components within a node representing a connection to an adjacent node over aspecific link. For example, if node A is the primary end of a multipoint line that connects to three adjacent nodes,node A will have three link stations representing the connections to the adjacent nodes. See also adjacent linkstation. (2) In VTAM, a named resource within a subarea node that represents another subarea node that isattached by a subarea link. In the resource hierarchy, the link station is subordinate to the subarea link.

link-attachedPertaining to devices that are connected to a controlling unit by a data link. Contrast with channel-attached.Synonymous with remote.

LMILocal management interface.

localPertaining to a device accessed directly without use of a telecommunication line. Synonym for channel-attached.

local area network (LAN)(1) A computer network located on a user’s premises within a limited geographical area. Communication within alocal area network is not subject to external regulations; however, communication across the LAN boundary maybe subject to some form of regulation. (2) A network in which a set of devices are connected to one another forcommunication and that can be connected to a larger network. See also token ring.

local directory databaseThat set of resources (LUs) in the network known at a particular node. The resources included are all those in thenode’s domain as well as any cache entries.

logical unit (LU)(1) A type of network accessible unit that enables end users to gain access to network resources andcommunicate with each other. (2) In SNA, a port through which an end user accesses the SNA network and thefunctions provided by system services control points (SSCPs). An LU can support at least two sessions-one withan SSCP and one with another LU-and may be capable of supporting many sessions with other LUs. See alsonetwork addressable unit (NAU), physical unit (PU), system services control point (SSCP), primary logical unit(PLU), and secondary logical unit (SLU).

logical unit (LU) 6.2A type of logical unit that supports general communication between programs in a distributed processingenvironment. LU 6.2 is characterized by (a) a peer relationship between session partners, (b) efficient utilizationof a session for multiple transactions, (c) comprehensive end-to-end error processing, and (d) a genericapplication program interface (API) consisting of structured verbs that are mapped into a product implementation.

low-entry networking (LEN)A capability in type 2.1 nodes allowing them to directly attach to one another using peer-to-peer protocols andallowing them to support multiple and parallel sessions between logical units.

LULogical unit.

LU groupIn the NetView Performance Monitor (NPM), a file containing a list of related or unrelated logical units. The LUgroup is used to help simplify data collection and analysis.

LU typeThe classification of an LU in terms of the specific subset of SNA protocols and options it supports for a givensession, namely:

¶ The mandatory and optional values allowed in the session activation request

¶ The usage of data stream controls, function management headers (FMHs), request unit parameters, and sensedata values

¶ Presentation services protocols such as those associated with FMH usage

LU types 0, 1, 2, 3, 4, 6.1, 6.2, and 7 are defined.


LU type 6.2 (LU 6.2)A type of logical unit that supports general communication between programs in a distributed processingenvironment. LU 6.2 is characterized by (a) a peer relationship between session partners, (b) efficient utilizationof a session for multiple transactions, (c) comprehensive end-to-end error processing, and (d) a genericapplication program interface consisting of structured verbs that are mapped into a product implementation.

LU 6.2Logical unit 6.2.

LU 6.2 sessionA session that is initiated by VTAM on behalf of a logical unit (LU) 6.2 application program, or a sessioninitiated by a remote LU in which the application program specifies that VTAM is to control the session by usingthe APPCCMD macroinstruction.

LU-LU session typeDeprecated term for LU type.

LU-LU sessionA session between two logical units (LUs) in an SNA network. It provides communication between two endusers, or between an end user and an LU services component.

M

MIBManagement information base.

migrationThe installation of a new version or release of a program to replace an earlier version or release.

MNPSMultinode persistent sessions.

mode nameThe name used by the initiator of a session to designate the characteristics desired for the session, such as trafficpacing values, message-length limits, sync point and cryptography options, and the class of service within thetransport network.

monitorIn the IBM Token-Ring Network, the function required to initiate the transmission of a token on the ring and toprovide soft-error recovery in case of lost tokens, circulating frames, or other difficulties. The capability ispresent in all ring stations.

monitor event messageA message created in response to a value that has exceeded a user-defined threshold.

monitor resolution messageA message created when a value that has exceeded a user-defined threshold falls into normal range.

multinode persistent sessions (MNPS)MNPS provides for the recovery of hardware, VTAM, MVS, or other software failures with minimal impact tothe users.

Multiple Virtual Storage (MVS)See MVS.

MVS(1) Multiple virtual storage. Implies MVS/370, the MVS/XA product, and the MVS/ESA product. (2) MultipleVirtual Storage, consisting of MVS/System Product Version 1 and the MVS/370 Data Facility Product operatingon a System/370 processor. See also MVS/XA product.


Glo

ssary

N

name translationIn SNA network interconnection, the conversion of logical unit names, logon mode table names, andclass-of-service names used in one network to equivalent names for use in another network. This function can beprovided through the NetView program and invoked by a gateway system services control point (SSCP) whennecessary. See also alias name.

NAU(1) Network accessible unit. (2) Network addressable unit.

NCNetwork control.

NCPNetwork Control Program.

NCP/Token Ring interconnect (NTRI)An NCP function that allows a communication controller to attach to the IBM Token-Ring Network and thatprovides both subarea and peripheral node data link control (DLC) services in the SNA network.

negative pollA negative response to polling in a binary synchronous terminal.

negative response (NR)In SNA, a response indicating that a request did not arrive successfully or was not processed successfully by thereceiver. Contrast with positive response.

NEONetwork extension option.

NetView Performance Monitor (NPM)An IBM-licensed program that collects, monitors, analyzes, and displays data relevant to the performance of aVTAM telecommunication network. It runs as an online VTAM application program.

NetView Synergy Interface (NSI)An interface for collecting data from VTAM in the host or from other session managers. NSI is only availablefor MVS.

networkA group of nodes and the links interconnecting them.

network accessible unit (NAU)A logical unit (LU), physical unit (PU), control point (CP), or system services control point (SSCP). It is theorigin or the destination of information transmitted by the path control network. Synonymous with networkaddressable unit.

network addressable unit (NAU)Synonym for network accessible unit.

network control (NC)In SNA, a request/response unit (RU) category used for requests and responses exchanged between physical units(PUs) for such purposes as activating and deactivating explicit and virtual routes and sending load modules toadjust peripheral nodes. See also data flow control and function management data.

Network Control Program (NCP)An IBM-licensed program that provides communication controller support for single-domain, multiple-domain,and interconnected network capability.

network directory databaseSynonym for distributed directory database.

network extension option (NEO)A function provided by NCP that allows the user to define user line control resources and programmed resources.


network gateway accounting (NGA)The NetView Performance Monitor (NPM) subsystem that receives traffic information from the gateway NCP forsessions that flow throughout a network.

network node (NN)Synonym for APPN network node. A node that offers full SNA end-user services and that can provide thefollowing to its local LUs and client end nodes:¶ Distributed directory services¶ Intermediate routing services within an APPN network¶ Network services

The APPN network node cooperates with other network nodes to maintain a network topology database, which isused to select optimal routes for LU-LU sessions based on requested classes of service. An APPN network nodecan also attach to a subarea network as a peripheral node or to other end nodes.

network node serverAn APPN network node that provides network services for its local LUs and client end nodes.

Network Performance Analysis Logical Unit (NPALU)In NPM, the virtual logical unit generated in an NCP with which the network subsystem communicates.

network performance analyzer (NPA)A function of NCP that collects performance data about devices. The data is recorded by NPM.

network services(1) The services within network accessible units that control network operation through SSCP-SSCP, SSCP-PU,SSCP-LU, and CP-CP sessions. (2) The session services (directory and route-selection functions) andmanagement services provided by an APPN network-node control point to its domain.

network session accounting (NSA)The NetView Performance Monitor (NPM) subsystem that receives session accounting information from the NCPfor sessions that flow throughout a network.

network transit timeIn the NetView Performance Monitor (NPM), the average time (in seconds) that all transactions spend in thenetwork. See operator transit time and host transit time.

NGANetwork gateway accounting.

no responseIn SNA, a protocol requested in the form-of-response-requested field of the request header that directs thereceiver of the request not to return any response, regardless of whether or not the request is received andprocessed successfully. Contrast with definite response and exception response.

node nameIn VTAM, the symbolic name assigned to a specific major or minor node during network definition.

node typeA designation of a node according to the protocols it supports and the network accessible units that it cancontain. Five types are defined: 1, 2.0, 2.1, 4, and 5. Within a subarea network, type 1, type 2.0, and type 2.1nodes are peripheral nodes, while type 4 and type 5 nodes are subarea nodes.

NPANetwork performance analyzer.

NPALUNetwork performance analysis logical unit.

NPMNetView Performance Monitor.

NPM logIn NPM, a data set in which NPM data can be stored.


Glo

ssary

NPSIX.25 NCP Packet Switching Interface.

NSANetwork session accounting.

NSINetView Synergy Interface.

NTRINCP/Token Ring interconnect.

NVASNetView access services.

O

ODLCOutboard data link control.

OpenEditionPertaining to the elements of OS/390 that incorporate the UNIX interfaces standardized in POSIX.

operator transit timeIn the NetView Performance Monitor (NPM), the sum of host and network transit times. See host transit timeand network transit time.

OS/390 operating systemAn IBM licensed program that not only includes and integrates functions previously provided by many IBMsoftware products (including the MVS operating system) but also (a) is an open, secure operating system for theIBM S/390 family of enterprise servers, (b) complies with industry standards, (c) is enabled for networkcomputing and e-business, and (d) supports technology advances in networking server capability, parallelprocessing, and object-oriented programming.

other-domain resourceA representation for a logical unit that is owned by another domain and is referenced by a symbolic name, whichcan be qualified by a network identifier.

outboard data link control (ODLC) resourcesSDLC and serial optical channel resources that are connected to the 3746 Model 900 (expansion unit of the 3745CCU).

P

pacingA technique by which a receiving component controls the rate of transmission of a sending component to preventoverrun or congestion. See also flow control.

packetIn data communication, a sequence of binary digits, including data and control signals, that is transmitted andswitched as a composite whole. The data, control signals, and, possibly, error control information are arranged ina specific format.

packet mode operationSynonym for packet switching.

packet switching(1) The process of routing and transferring data by means of addressed packets so that a channel is occupied onlyduring transmission of a packet. On completion of the transmission, the channel is made available for transfer ofother packets. (2) Synonymous with packet mode operation.

parameterA variable used in conjunction with a command. See also keyword.


partitioned data set (PDS)A data set in direct access storage that is divided into partitions, called members, each of which can contain aprogram, part of a program, or data.

path information unit (PIU)A message unit consisting of a transmission header (TH) alone, or a TH followed by a basic information unit(BIU) or a BIU segment. See also transmission header.

PDSPartitioned data set.

PDUProtocol data unit.

physical levelIn X.25, the mechanical, electrical, functional, and procedural media used to activate, maintain, and deactivate thephysical link between the data terminal equipment (DTE) and the data communication equipment (DCE).

physical unit (PU)The component that manages and monitors the resources (such as attached links and adjacent link stations)associated with a node, as requested by an SSCP via an SSCP-PU session. An SSCP activates a session with thephysical unit in order to indirectly manage, through the PU, resources of the node such as attached links. Thisterm applies to type 2.0, type 4, and type 5 nodes only.

PIUPath information unit.

PLUPrimary logical unit.

poll(1) To determine whether any remote device on a telecommunication line is ready to transmit data. (2) Toexecute a polling sequence. See also positive poll and negative poll.

polling(1) On a multipoint connection or a point-to-point connection, the process whereby data stations are invited, oneat a time, to transmit. (2) Interrogation of devices for such purposes as to avoid contention, to determineoperational status, or to determine readiness to send or receive data.

positive pollA positive response to polling in a binary synchronous terminal.

positive responseIn SNA, a response indicating that a request was received and processed. Contrast with negative response.

POSIXPortable Operating System System Interface For Computer Environments. An IEEE standard for computeroperating systems.

primary logical unit (PLU)In SNA, the logical unit (LU) that sends the BIND to activate a session with its partner LU. Contrast withsecondary logical unit.

program temporary fix (PTF)A temporary solution or bypass of a problem diagnosed by IBM in a current unaltered release of the program.

protocol(1) A set of semantic and syntactic rules that determine the behavior of functional units in achievingcommunication. (2) In Open Systems Interconnection architecture, a set of semantic and syntactic rules thatdetermine the behavior of entities in the same layer in performing communication functions. (3) In SNA, themeanings of, and the sequencing rules for, requests and responses used for managing the network, transferringdata, and synchronizing the states of network components. See link protocol.


Glo

ssary

protocol data unit (PDU)A unit of data in a network. For SDLC protocols, a PDU is a path information unit. For token-ring protocols, aPDU is an I-frame.

PTFProgram temporary fix.

PUPhysical unit.

R

RACFResource Access Control Facility.

rapid transit protocol (RTP)An efficient mechanism used by High Performance Routing (HPR) to perform end-to-end error recoveries(selective retries) and flow control.

RCReturn code.

real nameThe name by which a logical unit (LU), logon mode table, or class-of-service (COS) table is known within theSNA network in which it resides.

real time(1) In Open Systems Interconnection architecture, pertaining to the processing of data by a computer inconnection with another process outside the computer according to time requirements imposed by the outsideprocess. This term is also used to describe systems operating in conversational mode and processes that can beinfluenced by human intervention while they are in progress. (2) In Open Systems Interconnection architecture,pertaining to an application such as a process control system or a computer-assisted instruction system in whichresponse to input is fast enough to affect subsequent input.

real-time dataIndicates an active data forwarding collection. The performance information is current, and the data is displayedonline in a REAL-TIME DataView window.Real-time performance data is collected at regular intervals and the DataView is refreshed automatically, as soonas the data arrives.

record(1) In programming languages, an aggregate that consists of data objects, possibly with different attributes, thatusually have identifiers attached to them. In some programming languages, records are called structures. (2) Aset of data treated as a unit. (3) A set of one or more related data items grouped for processing. (4) In VTAM,the unit of data transmission for record mode. A record represents whatever amount of data the transmitting nodechooses to send.

recording filterIn the NetView program, the function that determines which events, statistics, and alerts are stored on a database.

refresh intervalThe interval at which NPM displays the most recent data collected from VTAM. See sampling interval.

releaseIn VTAM, to relinquish control of resources (communication controllers or physical units).

request header (RH)The control information that precedes a request unit (RU). See also request/response header (RH).

request unit (RU)A message unit that contains control information, end-user data, or both.


request/response unit (RU)A generic term for a request unit or a response unit. See request unit (RU) and response unit (RU).

request/response header (RH)Control information associated with a particular RU. The RH precedes the request/response unit (RU) andspecifies the type of RU (request unit or response unit).

resolution messageA message created when a value that has exceeded a user-defined threshold falls into normal range.

resource(1) Any facility of a computing system or operating system required by a job or task, and including main storage,input/output devices, the processing unit, data sets, and control or processing programs. (2) In the NetViewprogram, any hardware or software that provides function to the network.

Resource Access Control Facility (RACF)An IBM-licensed program that provides for access control by identifying and verifying the users of the system,by authorizing access to protected resources, by logging the detected unauthorized attempts to enter the system,and by logging the detected accesses to protected resources.

resource resolution table (RRT)In NPM, this table contains the names of network resources for which data is to be collected. The NPM RRTcorresponds with an NCP and is built by NPMGEN from an NCP Stage I and an NCP RRT.

resource typesIn the NetView program, a concept to describe the organization of panels. Resource types are defined as centralprocessing unit, channel, control unit, and I/O device for one category; and communication controller, adapter,link, cluster controller, and terminal for another category. Resource types are combined with data types anddisplay types to describe display organization. See also data types and display types.

response header (RH)A header, optionally followed by a response unit (RU), that indicates whether the response is positive or negativeand that may contain a pacing response. See also negative response, and positive response.

response time(1) The elapsed time between the end of an inquiry or demand on a computer system and the beginning of theresponse; for example, the length of time between an indication of the end of an inquiry and the display of thefirst character of the response at a user terminal. (2) For response time monitoring, the time from the activationof a transaction until a response is received, according to the response time definition coded in the performanceclass.

response time monitor (RTM)A feature available with certain hardware devices to allow measurement of response times, which may becollected and displayed by the NetView program.

response unit (RU)A message unit that acknowledges a request unit. It may contain prefix information received in a request unit. Ifpositive, the response unit may contain additional information (such as session parameters in response to BINDSESSION). If negative, the response unit contains sense data defining the exception condition.

return code (RC)(1) A code used to influence the execution of succeeding instructions. (2) A value returned to a program toindicate the results of an operation requested by that program. (3) In NPM, a VSAM key-sequenced data set(KSDS) containing data collected and recorded as a result of a network start display command or start monitorcommand.

RHRequest/response header.

RNRReceive not ready.


Glo

ssary

routeAn ordered sequence of nodes and transmission groups (TGs) that represent a path from an origin node to adestination node traversed by the traffic exchanged between them.

router(1) A computer that determines the path of network traffic flow. The path selection is made from several pathsbased on information obtained from specific protocols, algorithms that attempt to identify the shortest or bestpath, and other criteria such as metrics or protocol-specific destination addresses. (2) An attaching device thatconnects two LAN segments, which use similar or different architectures, at the reference model network layer.(3) In OSI terminology, a function that determines a path by which an entity can be reached.

routing(1) The process of determining the path to be used for transmission of a message over a network. (2) Theassignment of the path by which a message will reach its destination.

RRTResource resolution table.

RTMResponse time monitor.

RTPRapid transport protocol.

RURequest/response unit.

RU chainIn SNA, a set of related request/response units (RUs) that are consecutively transmitted on a particular normal orexpedited data flow. The request RU chain is the unit of recovery: if one of the RUs in the chain cannot beprocessed, the entire chain is discarded. Each RU belongs to only one chain, which has a beginning and an endindicated by means of control bits in request/response headers within the RU chain. Each RU can be designatedas first-in-chain (FIC), last-in-chain (LIC), middle-in-chain (MIC), or only-in-chain (OIC). Response units andexpedited-flow request units are always sent as only-in-chain.

S

SAASystems Application Architecture.

SAFSystem Authorization Facility.

same-domainPertaining to communication between entities in the same SNA domain. Contrast with cross-domain. See alsosingle-domain network.

sampling intervalThe interval at which NPM updates its own counters. This updated data is not displayed until the next refreshinterval. If a sampling interval is set higher than a refresh interval, the sampling interval is automatically reset tothe refresh interval. See refresh interval.

SDLCSynchronous Data Link Control.

secondary logical unit (SLU)In SNA, the logical unit (LU) that contains the secondary half-session for a particular LU-LU session. An LUmay contain secondary and primary half-sessions for different active LU-LU sessions. Contrast with primarylogical unit (PLU).


segmentIn the IBM Token-Ring Network, a section of cable between components or devices. A segment may consist of asingle patch cable, several patch cables that are connected, or a combination of building cable and patch cablesthat are connected.

service point (SP)An entry point that supports applications that provide network management for resources not under the directcontrol of itself as an entry point. Each resource is either under the direct control of another entry point or notunder the direct control of any entry point. A service point accessing these resources is not required to use SNAsessions (unlike a focal point). A service point is needed when entry point support is not yet available for somenetwork management function.

session(1) In network architecture, for the purpose of data communication between functional units, all the activities thattake place during the establishment, maintenance, and release of the connection. (2) In SNA, a logical connectionbetween two network accessible units (NAUs) that can be activated, tailored to provide various protocols, anddeactivated, as requested. Each session is uniquely identified in a transmission header (TH) accompanying anytransmissions exchanged during the session.

session collectionThe NPM subsystem that collects, monitors, and displays data collected in the host for analysis.

session dataData about sessions collected by NPM.

session limit(1) The maximum number of concurrently active LU-LU sessions that a particular logical unit (LU) can support.(2) In NCP, the maximum number of concurrent line-scheduling sessions on a non-SDLC, multipoint line.

session managerA product, such as NetView Access Services, that allows a user at a terminal to log on to multiple applicationsconcurrently.

session monitorThe component of the NetView program that collects and correlates session-related data and provides onlineaccess to this information.

session partnerIn SNA, one of the two network accessible units (NAUs) having an active session.

session statistics fileIn NPM, an online VSAM key-sequenced data set (KSDS) used for storing session data.

sharedPertaining to the availability of a resource for more than one use at the same time.

shared-access transport facility (SATF)A transmission facility, such as a multipoint link connection, a public switched network, or a token ring, onwhich multiple pairs of nodes can form concurrently active links.

Simple Network Management Protocol (SNMP)In the Internet suite of protocols, a network management protocol that is used to monitor routers and attachednetworks. SNMP is an application layer protocol. Information on devices managed is defined and stored in theapplication’s Management Information Base (MIB).

single-domain networkIn SNA, a network with one system services control point (SSCP).

SIOStart I/O.

SLUSecondary logical unit.


Glo

ssary

SMFSystem management facility.

SNASystems Network Architecture.

SNA networkThe part of a user-application network that conforms to the formats and protocols of Systems NetworkArchitecture. It enables reliable transfer of data among end users and provides protocols for controlling theresources of various network configurations. The SNA network consists of network accessible units (NAUs),boundary function, gateway function, and intermediate session routing function components; and the transportnetwork.

SNMPSimple Network Management Protocol.

SPService point.

spanIn the NetView program, a user-defined group of network resources within a single domain. Each major or minornode is defined as belonging to one or more spans.

SPXSequenced packet exchange.

SRTSystem reference table.

SSSession services.

SSCPSystem services control point.

SSCP reroutingIn SNA network interconnection, the technique used by the gateway system services control point (SSCP) to sendsession-initiation request units (RUs), by way of a series of SSCP-SSCP sessions, from one SSCP to another,until the owning SSCP is reached.

SSCP-LU sessionIn SNA, a session between a system services control point (SSCP) and a logical unit (LU). The session enablesthe LU to request the SSCP to help initiate LU-LU sessions.

SSCP-PU sessionIn SNA, a session between a system services control point (SSCP) and a physical unit (PU); SSCP-PU sessionsallow SSCPs to send requests to and receive status information from individual nodes in order to control thenetwork configuration.

SSCP-SSCP sessionIn SNA, a session between the system services control point (SSCP) in one domain and the SSCP in anotherdomain. An SSCP-SSCP session is used to initiate and terminate cross-domain LU-LU sessions.

SSPSystem Support Program product.

start optionIn VTAM, a user-specified or IBM-supplied option that determines certain conditions that are to exist during thetime a VTAM system is operating. Start options can be predefined or specified when VTAM is started.

start-stop (SS) transmission(1) Asynchronous transmission such that each group of signals representing a character is preceded by a startsignal and is followed by a stop signal. (2) Asynchronous transmission in which a group of bits is (a) precededby a start bit that prepares the receiving mechanism for the reception and registration of a character, and (b)


followed by at least one stop bit that enables the receiving mechanism to come to an idle condition pendingreception of the next character. See also binary synchronous transmission and synchronous data link control.

statement identifierThe lexical entity in a language statement that indicates the purpose of the statement, such as the action to beperformed or the resource being defined. See also definition statement and definition statement identifier.

stationAn input or output point of a system that uses telecommunication facilities; for example, one or more systems,computers, terminals, devices, and associated programs at a particular location that can send or receive data overa telecommunication line.

subareaA portion of the SNA network consisting of a subarea node, attached peripheral nodes, and associated resources.Within a subarea node, all network accessible units (NAUs), links, and adjacent link stations (in attachedperipheral or subarea nodes) that are addressable within the subarea share a common subarea address and havedistinct element addresses.

subnetwork(1) Any group of nodes that have a set of common characteristics, such as the same network ID. (2) In the AIXoperating system, one of a group of multiple logical network divisions of another network, such as can be createdby the Transmission Control Protocol/Internet Protocol (TCP/IP) interface program.

Synchronous Data Link Control (SDLC)A discipline conforming to subsets of the Advanced Data Communication Control Procedures (ADCCP) of theAmerican National Standards Institute (ANSI) and High-level Data Link Control (HDLC) of the InternationalOrganization for Standardization, for managing synchronous, code-transparent, serial-by-bit information transferover a link connection. Transmission exchanges may be duplex or half-duplex over switched or nonswitchedlinks. The configuration of the link connection may be point-to-point, multipoint, or loop. See also binarysynchronous communications.

system definitionThe process, completed before a system is put into use, by which desired functions and operations of the systemare selected from various available options. Synonymous with system generation.

system generationSynonym for system definition.

System Management Facility (SMF)A standard feature of MVS that collects and records a variety of system and job-related information.

system services control point (SSCP)A component within a subarea network for managing the configuration, coordinating network operator andproblem determination requests, and providing directory services and other session services for end users of thenetwork. Multiple SSCPs, cooperating as peers with one another, can divide the network into domains of control,with each SSCP having a hierarchical control relationship to the physical units and logical units within its owndomain.

System Support Program (SSP) productA group of IBM-licensed programs that manage the running of other programs and the operation of associateddevices, such as the display station and printer. The SSP also contains utility programs that perform commontasks, such as copying information from diskette to disk. See Advanced Communication Function (ACF).

Systems Network Architecture (SNA)The description of the logical structure, formats, protocols, and operational sequences for transmitting informationunits through, and controlling the configuration and operation of, networks.

T

TCAMTelecommunications Access Method. Synonymous with ACF/TCAM.


Glo

ssary

TCPTransmission Control Protocol.

telecommunication line(1) The portion of a data circuit external to a data communication equipment (DCE) that connects the DCE to adata-switching exchange (DSE), that connects a DCE to one or more other DCEs, or that connects a DSE toanother DSE. (2) Any physical medium, such as a wire or microwave beam, that is used to transmit data.Synonymous with transmission line.

Telecommunications Access Method (TCAM)An access method used to transfer data between main storage and remote or local terminals.

teleprocessing network simulator (TPNS)A testing package that enables a user to test and evaluate teleprocessing systems before actual terminalinstallation.

TGTransmission group.

THTransmission header.

threshold(1) In the NetView program, a percentage value, set for a resource and compared to a calculated error-to-trafficratio. (2) In NPM, high or low values supplied by the user to monitor data and statistics being collected.

TICToken-ring interface coupler.

Time Sharing Option (TSO)An operating system option; for the System/370 system, the option provides interactive time sharing from remoteterminals.

token(1) In a local area network, the symbol of authority passed successively from one data station to another toindicate the station temporarily in control of the transmission medium. Each data station has an opportunity toacquire and use the token to control the medium. A token is a particular message or bit pattern that signifiespermission to transmit. (2) A sequence of bits passed from one device to another along the token ring. When thetoken has data appended to it, it becomes a frame.

token ringA network with a ring topology that passes tokens from one attaching device to another; for example, the IBMToken-Ring Network.

token-ring interface coupler (TIC)An adapter that can connect a 3720, 3725, or 3745 Communication Controller to an IBM Token-Ring Network.

TPTransmission priority.

TPNSTeleprocessing network simulator.

TPXTerminal Productivity Executive. A session manager interface.

TRToken ring.

transit timeIn NPM, transit time is the same as response time. See response time, host transit time, network transit time, andoperator transit time.


Transmission Control Protocol (TCP)A communications protocol used in Internet and in any network that follows the U.S. Department of Defensestandards for inter-network protocol. TCP provides a reliable host-to-host protocol between hosts inpacket-switched communications networks and in interconnected systems of such networks. It assumes that theInternet protocol is the underlying protocol.

transmission control unit (TCU)A communication control unit whose operations are controlled solely by programmed instructions from thecomputing system to which the unit is attached. No program is stored or executed in the unit. Examples are theIBM 2702 and 2703 Transmission Controls. Contrast with communication controller.

transmission group (TG)A group of links between adjacent subarea nodes, appearing as a single logical link for routing of messages. Atransmission group may consist of one or more SDLC links (parallel links) or of a single System/370 channel. InAPPN, transmission group is synonymous with link.

transmission header (TH)Control information, optionally followed by a basic information unit (BIU) or a BIU segment, that is created andused by path control to route message units and to control their flow within the network. See also pathinformation unit.

transmission lineSynonym for telecommunication line.

transmission priorityIn SNA, a rank assigned to a path information unit (PIU) that determines its precedence for being selected by thetransmission group control component of path control for forwarding to the next subarea along the routetraversed by the PIU.

TSOTime Sharing Option.

type 2.1 nodeAn SNA node that can be configured as an endpoint or intermediate routing node in a type 2.1 network, or as aperipheral node attached to a subarea network.

type 4 nodeA subarea node that contains a PUCP rather than an SSCP and that is controlled by one or more type 5 nodes.

type 5 nodeA subarea node that contains an SSCP and that has hierarchical control of peripheral nodes and type 4 subareanodes.

U

user exit(1) A point in an IBM-supplied program at which a user exit routine may be given control. (2) A programmingservice provided by an IBM software product that may be requested during the execution of an applicationprogram for the service of transferring control back to the application program upon the later occurrence of auser-specified event.

user exit routineA user-written routine that receives control at predefined user exit points. User exit routines can be written inassembler or a high-level language.

V

VCVirtual circuit.


Glo

ssary

viewing filterIn the NetView program, the function that allows a user to select the alert data to be displayed on a terminal. Allother stored data is blocked.

virtual circuit (VC)(1) In packet switching, the facilities provided by a network that give the appearance to the user of an actualconnection. (2) A logical connection established between two DTEs.

virtual route (VR)In SNA, either of the following:

¶ A logical connection between two subarea nodes that is physically realized as a particular explicit route

¶ A logical connection that is contained wholly within a subarea node for intranode sessions.

A virtual route between distinct subarea nodes imposes a transmission priority on the underlying explicit route,provides flow control through virtual route pacing, and provides data integrity through sequence numbering ofpath information units (PIUs). See also explicit route (ER).

virtual routing nodeA representation of a node’s connectivity to a connection network defined on a shared-access transport facility,such a token ring. Synonymous with connection network.

virtual storage (VS)The storage space that may be regarded as addressable main storage by the user of a computer system in whichvirtual addresses are mapped into real addresses. The size of virtual storage is limited by the addressing schemeof the computer system and by the amount of auxiliary storage available, not by the actual number of mainstorage locations.

Virtual Storage Access Method (VSAM)An access method for direct or sequential processing of fixed and variable-length records on direct accessdevices. The records in a VSAM data set or file can be organized in logical sequence by a key field (keysequence), in the physical sequence in which they are written on the data set or file (entry-sequence), or byrelative-record number.

Virtual Telecommunications Access Method (VTAM)An IBM-licensed program that controls communication and the flow of data in an SNA network. It providessingle-domain, multiple-domain, and interconnected network capability.

VRVirtual route.

VSVirtual storage.

VSAMVirtual Storage Access Method.

VSRBVirtual storage request block.

VTAMVirtual Telecommunications Access Method. Synonymous with ACF/VTAM.

VTAM application programA program that has opened an access method control block (ACB) to identify itself to VTAM and that cantherefore issue VTAM macroinstructions.

W

windowIn data communication, the number of data packets a data terminal equipment (DTE) or data communicationequipment (DCE) can send across a logical channel before waiting for authorization to send another data packet.The window is the main mechanism of pacing, or flow control, of packets.


X

X.25An International Telegraph and Telephone Consultative Committee (CCITT) recommendation for the interfacebetween data terminal equipment and packet-switched data networks. See also packet switching.

X.25 NCP Packet Switching Interface (NPSI)An IBM-licensed program that allows SNA users to communicate over packet switching data networks that haveinterfaces complying with CCITT Recommendation X.25. It allows SNA programs to communicate with SNA ornon-SNA equipment over such networks.

X.3An International Telegraph and Telephone Consultative Committee (CCITT) recommendation for packetassembly/disassembly (PAD) in a public data network.

XIX.25 SNA interconnection.


Glo

ssary


Bibliography

NPM PublicationsThe following paragraphs briefly describe the publications for this release of NPM:

NetView Performance Monitor Concepts and Planning (GH19-6961)

This book is written for system programmers and administrators who are responsiblefor understanding the capabilities of NPM and planning for its installation.

NetView Performance Monitor Diagnosis (LY19-6381)

This licensed book is intended to help system programmers service and debug NPMprogram problems. It contains procedures useful in reporting problems to IBM andinformation on traps, traces, and the problem determination function.

NetView Performance Monitor Console User’s Guide (SH19-4522)

This book is designed as a primer and reference manual for operators who use theNPM console on a daily basis.

NetView Performance Monitor Installation and Customization (SH19-6964)

This book is designed to aid system programmers who are responsible for installingand customizing NPM. It includes installation procedures as well as customization, filemanagement, and tuning information.

NetView Performance Monitor Messages and Codes (SH19-6966)

This manual lists messages and codes issued by NPM. It contains information to helpoperators and system programmers understand, interpret, and respond to error messagesand codes.

NetView Performance Monitor Reference (SH19-6965)

This book provides the information you need to produce reports using data collected byNPM. It describes the record formats that NPM uses and provides information neededto create applications that use these records. It also contains all the referenceinformation for users of the NPM product.

NetView Performance Monitor User’s Guide (SH19-6962)

This book is designed as a primer and reference manual for operators who use NPM ona daily basis.

NetView Performance Monitor Marketing Brochure for Version 2. (GC27-9215)

This brochure introduces customers to the benefits of purchasing Version 2 of NPM.

See “NPM Publications on CD” on page 224 for additional information.


Bib

liog

raph

y

Other Network Program Products PublicationsThe following list shows the “umbrella” publications for the NetView program, VTAM,NCP, and related products. Detailed listings of the specific product publications appear insubsequent sections in this bibliography.

Network Program Products Planning (SC30-3351)

Network Program Products Samples (SC30-3352)

Bibliography and Master Index for NetView, NCP, and VTAM (GC31-6430)

SMP/E User’s Guide (SC28-1740)

Planning and Reference for NetView, NCP, and VTAM (SC31-6092)

NetView PublicationsThe following list shows the publications for the NetView program.

NetView Automation Planning (SC31-7082)

NetView Administration Reference (SC31-7080)

NetView Application Programming Guide (SC31-7091)

NetView Bridge Implementation (SC31-6131)

NetView Customization Guide (SC31-7091)

NetView Customization: Using Assembler (SC31-7094)

NetView Customization: Using PL/I and C (SC31-7093)

NetView Customization: Writing Command Lists (SC31-7092)

NetView Installation and Administration Guide (SC31-7084)

NetView Messages (SC31-7096)

NetView Operation (SC31-7066)

NetView Resource Alerts Reference (SC31-7097)

NetView Tuning Guide (SC31-7079)

VTAM PublicationsThe following list shows the publications for VTAM. You should use the appropriate bookfor the version you are running.

VTAM Codes (GC31-8369)

VTAM Messages (GC31-8368)

VTAM Network Implementation Guide (SC31-8370)


VTAM Operation (SC31-8372)

VTAM Programming (SC31-8373)

VTAM Programming Guide for LU 6.2 (SC31-8374)

VTAM Programming Reference for LU 6.2 (SC31-8375)

VTAM Resource Definition Reference (SC31-8377)

NCP, SSP, and EP PublicationsThe following list shows the publications for NCP, SSP, and EP.

NCP, SSP, and EP Generation and Loading Guide (SC31-6221)

NCP, SSP, and EP Messages and Codes (SC31-6222)

NCP, SSP, and EP Resource Definition Guide (SC31-6223)

NCP, SSP, and EP Resource Definition Reference (SC31-6224)

Operating System PublicationsYou should use the appropriate book for your operating system type and version. This list isnot comprehensive.

z/OS MVS System Commands (GC28-1781)

z/OS Application Enabling Technology: Administration and Programming (GC28-1993)

z/OS Application Enabling Technology: Customization Guide (GC28-1994)

z/OS MVS System Codes (GC28-1780)

z/OS MVS Diagnosis Tools and Service Aids (SY28-1085)

z/OS MVS Initialization and Tuning Guide (SC28-1751)

z/OS MVS Initialization and Tuning Reference (SC28-1752)

z/OS MVS Extended Addressability Guide (GC28-1769)

z/OS MVS System Management Facilities (GC28-1783) Reference (GC26-4152)

z/OS TSO/E REXX Reference (SC28-1975)

OS/VS VSAM Programmer’s Guide (GC26-3838)


Bib

liog

raph

y

Related PublicationsYou should use the appropriate book for your operating system type and version. This list isnot comprehensive.

IBM Dictionary of Computing (SC20-1699)

Local Area Network Administrator’s Guide (GA27-3748)

X.25 Planning and Installation NCP and X.25 NPSI (SC30-3470)

Systems Network Architecture Formats (GA27-3136)

Systems Network Architecture Technical Overview (GC30-3073)

Service Level Reporter User’s Guide: Reporting (SH19-6530)

Service Level Reporter User’s Guide: Performance Management (SH19-6442)

z/OS Security Server (RACF): System Programming Guide (SC28-1913)

z/OS Security Server (RACF).: Security Administrator’s Guide (SC28-1915)

VSAM Administration: Macro Instruction Reference (GC26-4016)

VSAM Data Management Programming (SR21-2689)

System Programming Library: Initialization and Tuning (SC23-0041)

You and the IBM Support Center (GA21-9824)

NPM Publications on CDSoftcopy versions of the NPM manuals for this release of the product, which can be readonline using BookManager, are available on the following CD:

¶ IBM Online Library Omnibus Edition OS/390 Collection Kit (SK2T-6700)

¶ IBM Online Library z/OS Software Products Collection Kit (SK3T-4270)


Index

Numerics3270 panels, dynamic data display and PF keys 123270 panels, rename cryptic labeled items 13

Aaccess to NPM, controlling 86accounting data

collecting 63recording 67viewing 67

accounting data collection 4agent, NetWare 18, 61agent server 61allocating NPM data sets 81application definition xvarchiving session files 80authorization 179

Bbacking up a file 185backup NPALUs 64base interval 24, 39batch reporting facility, FNMREPRT 69books

feedback xiionline xiiordering xii

bridgeconfiguration information 56data 18defined 53traffic 55

broadcast frames threshold field 122

Ccalculating transit times 40CCU data 26Cisco Channel Interface Processor support 14Cisco router support 22collecting

accounting data 4, 63data from the VTAM Session Manager 66from session managers 47LAN data 53LAN Data 53

collecting (continued)NetWare resources data 61network accounting data 63network data 23performance data 17RTM data 57transit time data 40utilization data 54volume statistics 44VTAM statistics 59

collecting dataactive collection 182deferred collection 182for LAN bridge 120for LAN segment 123for network 105for NTRI 134for session 96status of collection 182

collection interval 23Command List panel (FNM03NCL) 111Command List panel (FNM03VCL) 150, 156configuration, dynamic 80configuration information

bridge 56segment 56

console security 85Console user interface, installation requirements for 13control functions

access to NPM 86LAN collection 55LAN monitoring 55NetWare resources collection 62network accounting collection 65network collection 35network monitoring 35performance data collection 19RTM collection 59session collection 45session monitoring 45VTAM statistics collection 60VTAM statistics monitoring 60

control session 47control session data 49controlling NPM functions

authorization 179conventions used in this book xvcounters for 3746 NNP support 8creating reports with FNMREPRT 69criteria, monitoring 17cross-domain applications, supporting 52Customer Support xiv


Ind

ex

DDaily field 170data, types of

of NetWare resources data 61of ODLC LAN data 29of RTM data 58of session data 39

Data File Display and Management panel (FNM02OFL)file status 186resetting files 184

data filesbacking up 185managing 179, 185resetting 183status of 184switching 183types of 179

Data flow control 43data not found message 180data sets

allocating 81protecting 86review 82session 82user profile 82

DataView support, NMC-NPM Console 10DDR 43defining LAN managers 54definite response 42, 43definite response time 42Destination Subarea Selection panel (FNM02SS1)

virtual route datadetermining blocked route 160long-term analysis 164

destinations of performance data 19determining if there is a blocked virtual route 160DFC 43displaying data

by application 144by line 108by LU 146for an NCP 114for LAN bridge collection 126for LAN segment collection 129for network collection 108, 115for NTRI collection 136for session collection 99, 144in summary 101specifying the data 180

DNC 63, 67dynamic

configuration 80definite response 43network collection 63network data 67network data, collecting 67

Dynamic NPM Configuration discovery using RODM 8

Ee-mail contact xiverrors 28Errors field

checking for incorrect specifications 180determining if collected data was saved 183determining if data was collected 181in data entry 180in data transmission 128no data found 180

Ethernet data 29, 30examining an application using VTAM statistics data 147examining VTAM for problems in the host 151examples

collection interval 24network monitor with exception 34network monitor with resolution 35

examples of network data 25exceptions 34EXECs 35, 45exit

NPM installation-wide 79PIU analysis 80

exits, installation-wide 79expanding the network 69expected data support per network element 22external router 61

Ffeedback about publications xivfile management 80File Name field

on LU Detail Analysis Panel (FNM02DNM) 100on Session Analysis Panel (FNM02SAN) 145

FNM756E, error message 180FNMARCHV sample 80FNMEXEC 81FNMILOG 181FNMINIT 81FNMLOG 38, 46, 57, 59FNMLUGRP 81FNMOPER 81FNMPROF 81FNMPROFS 82FNMREPRT

batch reporting facility 69creating reports with 69report definitions 69

FNMREV 57FNMREV data sets 38FNMSES 46, 59FNMSMF 81FNMSTRT 81FNMUEXIT 80FNMVARCH sample 80FNMVLOG 46FNMxxxxx panel IDs

FNM02BS1 156


FNMxxxxx panel IDs (continued)FNM02BS2 158, 159FNM02DNM 100FNM02GS1 152FNM02GS2 154FNM02GS3 154FNM02GS4 154FNM02LBB 120FNM02LBM 127, 130FNM02LBS 121, 133FNM02LSB 123FNM02LSS 125, 133FNM02OCC 182FNM02OFL 184, 186FNM02PS1 147FNM02PS2 149FNM02RSL 105, 106FNM02RVM 109, 114, 137, 171FNM02SAM 102FNM02SAN 145FNM02SCL 97, 142FNM02SS1 160, 164FNM03LB2 128FNM03LBC 122FNM03LBR 128FNM03LSC 125FNM03LSR 131, 132FNM03NCL 111FNM03RVE 172FNM03RVL 110FNM03RVN 138FNM03RVP 116FNM03SAE 102FNM03SAS 98, 143FNM03SMN 101, 146FNM03SSA 104, 147FNM03STD 112, 134, 138, 169FNM03STM 107, 113, 135, 170FNM03VAN 165FNM03VS1 160, 165FNM03VS2 163FNM03VS3 163FNM03VT2 149FNM03VTC 153, 157, 162FNM03VTD 148, 152, 157, 161FNM04LTN 146FNM04SSA 104FNM04VD1 166FNM04VD2 167

frame relaydata 31, 32DCE 31DTE 31LMI PU 31physical station 31

frames lost threshold field 122Free Buffer High field 116function management data 44functional security 85

Ggroup IDs, specifying 51growth, planning for 169GTF trace field 97, 142GUI, counters and code for Cisco CIP 13GUI, installation requirements for 13GUI interface connection, recovery on TCP/IP failure 13

Hhost

transit time 95, 146host transit time 40, 41

Iidentifier field 145installation process, overview 14Installation requirements, GUI (NPM Console) 13installation-wide exits 79interval

base 24LAN collection 55refresh 59sampling 59session collection 39specifying 24

introduction to planning 3IP network, problems in an 116IP performance data collection 20ISDN resources, description 33

LLAN

bridge 53bridge data 18bridge data, collection 53managers, defining 54monitoring, controlling 55resources network data 29segment 53segment collection 53segment data 18segment utilization 55

LAN Bridge Collection Control panel (FNM03LBC) 122LAN Bridge Control panel (FNM02LBB) 120LAN bridge data collection,

broadcast frames 122data destination 120, 179displaying data

examining data 120, 126Interval Length 121Interval Synch 121


Ind

ex

LAN bridge data collection, (continued)lost frames 122monitor event messages 120non-broadcast frames 122setting parameters 120setting thresholds 122starting collection 121stopping collection 132

LAN Bridge Detail panel (FNM03LBR) 128LAN Bridge Lost Frames Detail panel (FNM03LB2) 128LAN Bridge Selection panel (FNM02LBS)

starting LAN bridge data collection 121stopping LAN bridge data collection 133

LAN collectioncontrolling 55

LAN collection interval 55LAN data

collecting 53definition 53monitoring 53, 55recording 57types 55viewing 57

LAN Resource Name field 127, 130LAN Review panel (FNM02LBM) 127, 130LAN Segment Collection Control panel (FNM03LSC) 125LAN Segment Control panel (FNM02LSB) 123LAN segment data collection

data destination 124examining data 124, 129Interval Length 124Interval Synch 124monitor event messages 124segment utilization 126setting parameters 123setting thresholds 126starting collection 124stopping collection 133

LAN Segment Detail panel (FNM03LSR) 131, 132LAN Segment Selection panel (FNM02LSS) 125, 133line data 26line utilization 28lines 97, 143

collecting data on 105displaying data on 108, 110problems with 105, 110

link data 26logging on to NPM 83LU data 27LU definition xvLU Detail Analysis panel (FNM02DNM) 100LU6.2 session collection 43

Mmanuals


messages,for monitor event 103, 172

destination of 120, 124for monitor resolution 120, 124No Data Found 180

messages, statistics for 27MIB data, description 17migration information 89minimal security 84Minimum PIU Trace field 97, 142monitor

criteria 45exceptions 34, 45, 55resolution 34, 45, 55resolution tracking. 34

Monitor Messages Destination field 120, 123monitor type and NetWare counter groups 176monitoring

criteria 17ISDN resources 33LAN data 53, 55NetWare resources 61network data 33network resources 3session data 38, 45VTAM statistics 59

monitoring network data,displaying messages 171, 173event messages 120, 124, 173, 180resolution messages 120, 124, 173starting a monitor 169

monitoring session datadisplaying messages 101event messages 101, 180monitor types 98, 143starting a monitor 98, 143

MPC devices, collection 9multiple terminals, supporting 52MVS samples 81

NNCP (network control program)

displaying data for 114monitoring 169problems with 111starting collection on 112, 114utilization 169, 173utilization of 116

NCP activation, starting collection at 66NCP Name field 107, 112, 135, 139, 170NEO data 11, 13, 32NEO resources 32NETCOLL command 7, 34NetView

alerts 34PPI 34, 53program-to-program interface 34, 53synergy interface 47


NetWare agent 18, 61NetWare resources data

collecting 61controlling collection 62controlling monitoring 62description 7, 18displaying 62monitoring 61recording 62viewing 62

networkaccounting collection, controlling 65accounting data, collecting 63collection, controlling 35collection interval 23gateway accounting 63growth, planning for 5monitoring, controlling 35performance analysis logical unit 23resources 25resources, monitoring 3session accounting 63transit time 40, 41tuning and expanding the 69tuning the 5

network datacollecting 23definition 23examples of 25ISDN resources 33monitoring 33recording 37viewing 37

network data collection,by line 105by NCP 112, 114data destinations 179starting 112, 114, 134stopping 110

Network Review Data for NTRI Resources panel(FNM03RVS) 138

Network Review Data panel (FNM03RVL) 110Network Review Data panel (FNM03RVP) 116Network Review panel (FNM02RVM) 109, 114, 137, 171Network Start panel (FNM03STD) 106, 112, 134, 169Network Start panel (FNM03STM) 107, 113, 135, 170Network Stop panel (FNM03STD) 138network transit time field 95, 146new functions 5NGA 63NMC-NPM console

DataView support 10NMC-NPM Console

profiling support 10Start, Stop, Alter collection 10

node 39node name field 97, 142non-broadcast frames threshold field 122normal security 84NPALU 23NPALU, binding to NPM 182

NPALU Display and Management panel (FNM02OCC) 182NPALU takeovers 64NPALUs, backup 64NPM

-to-NPM security 85EXECs 35, 45installation-wide exit 79log 46, 57, 59log file 38logging on to 83security 83support functions 79user profile data sets 82

NPM (NetView Performance Monitor)binding to NPALU 182

NPM and other productsNetWare resources 62session managers 47

NPM ConsoleStart, Stop, Alter collection 9

NPM Console user interface 13NPM data sets

allocating 81definition 81protecting 86

NPM installation process, overview 14NPM log field 179NPM Session Analysis Summary - Application panel

(FNM03SMN) 146NPM Session Analysis Summary - Logical Unit panel

(FNM03SMN) 101NPM Session Summary LU List - Application panel

(FNM04LTN) 146NSA 63NSI 47NTRI (network token ring interconnect) data collection

displaying data 136starting collection 134stopping collection 138

NTRI data 29

OODLC LAN data 29, 30ODLC LAN data, types of 29online publications xiiiOpenEdition, description 4operator

data 44profile 83transit time 40

operator transit time 95ordering publications xiii

Ppacket-switching resources network data 30


Ind

ex

performance datacollecting 17collection, controlling 19destinations of 19sources of 19viewing 19

performing problem determination 5PIU analysis exit 80planning, introduction to 3planning for network growth 5polling 28PPI 34problem determination

examining a CCU 111, 116examining a LAN 119, 128examining a line 110examining an application 141, 146examining the TIC 134examining VTAM 151no data found 180starting a monitor 169

problem determination, performing 5problems in an IP network 116profiles

operator 83remote 85security 83

profiling support, NMC-NPM Console 10protecting NPM data sets 86publications


RRACF security 84rebuilding session files 80recording

accounting data 67LAN data 57NetWare resources data 62network data 37RTM data 59session data 46VTAM data 60

refresh interval 59relay session 47

data 47release 6 new functions 5remote profiles 85report definitions, FNMREPRT 69report generation 80resetting a file 183resolution 34Resolution field 120, 124Resource List panel (FNM02RSL) 105, 106Resource Name field 170, 180response option, for TN3270E 41

response timefor host 105, 141on a LAN 119on a NetWare network 175on network 95, 110

response time monitor data 18review data sets 82review file 38, 57Review File,

backing up 185list of 183resetting 184, 186switching 183

Review Monitor Event Messages panel (FNM03RVE) 172router data 17RTM (response time monitor)

data destination 179RTM collection, controlling 59RTM data

collecting 57definition 57recording 59types of 58viewing 59

Ssamples, MVS 81sampling interval 59scenarios

data not found 180, 183determining if there is a blocked virtual route 160examining a CCU for potential problems 111, 116examining a LAN for potential problems 119, 133, 134examining a line for potential problems 105, 111examining a TIC for potential problems 134examining an application for potential problems 141, 147examining an application using VTAM statistics data 147examining VTAM for problems in the host 151isolating poor response time to host or network 95managing data files with the system console 185, 186preparing a file for back up 185resetting a file 183, 184, 186using a network monitor 169, 173

securityconsole 85functional 85minimal 84normal 84NPM 83NPM-to-NPM 85profile 83RACF 84user-defined 84

segment 53segment configuration information 56segment data 18server 61SESSAPPL command 8


Session Analysis panel (FNM02SAN) 145session collection

controlling 45interval 39

session datacollecting 38definition 38monitoring 38, 45recording 46sets 82types of 39viewing 46

session data collectionby LU 96displaying,

LU detail data 99starting 96stopping 103, 104summary 101

session file,backing up 185list of 183managing 179resetting 183switching 183

session files 46, 59archiving 80rebuilding 80

session managercollecting session data from 47defined 47transit time thresholds 51transit times 50volume statistics 51

Session Monitor Event Messages panel (FNM03SAE) 102Session Monitor Review Menu panel (FNM02SAM) 102Session Monitor Selection panel (FNM03SAS) 98, 143session monitoring, controlling 45session statistics field 97, 142Session Status/Stop (Active) Details panel (FNM04SSA) 104,

147session volume data 44SMF (system management facility) 179SNMP router alerts 10SNMP router collection, recovery on TCP/IP failure 13SNMP routers, APPN support 12sources of performance data 19specifying group IDs 51specifying interval 24Start, Stop, Alter collection

NMC-NPM Console 10NPM Console 9

Start Date field 100, 102, 109, 115, 127, 130, 137, 145, 181Start Session panel (FNM02SCL) 97, 142Start Time field 170, 181starting collection at NCP activation 66statistics for messages 27Stop Time field 170, 181storing data,

in Review File 183in Session file 183

storing data, (continued)managing 179

support functions 79supporting cross-domain applications 52supporting multiple terminals 52switching a file 185SYSPRINT data set 181system console,

entering commands 185managing files with 185

system data 44

Ttakeovers, NPALU 64TELNET transit time 41terminal data 27TIC (token ring-interface coupler) 134

utilization 138Time field

for starting and stopping 170, 181Tivoli Business Systems Manager and NPM GUI,

integration 9Tivoli Customer Support xivTN3270 transit time 41token ring 119, 128, 130, 134transaction 41transit time

data, collecting 40definition 39host 40network 40operator 40thresholds, session manager 51

Transit Time 95transit times

calculating 40session manager 50

transmission priority 29trend analysis 69tuning the network 5

Uuser-defined security 84user profile data sets 82

Vviewing

accounting data 67LAN data 57NetWare resources data 62network data 37performance data 19


Ind

ex

viewing (continued)RTM data 59session data 46VTAM data 60

Virtual Route Current Data panel (FNM03VS2) 163Virtual Route Current Data panel (FNM03VS3) 163Virtual Route Detail Data panel (FNM04VD1) 166Virtual Route Detail Data panel (FNM04VD2) 167Virtual Route Selection panel (FNM03VS1) 160, 165volume statistics

collecting 44definition 39session manager 51

VTAMlog file 46session manager, collecting data 66

VTAM Application Current Data panel (FNM02PS2) 149VTAM Application Selection panel (FNM02PS1) 147VTAM Buffer Pool Current Data panel (FNM02BS2) 158,

159VTAM Buffer Pool Selection panel (FNM02BS1) 156VTAM Data Analysis panel (FNM03VAN) 165VTAM Data Collection panel (FNM03VTC) 153, 157, 162VTAM Global Current Data panel (FNM02GS2) 154VTAM Global Current Data panel (FNM02GS3) 154VTAM Global Current Data panel (FNM02GS4) 154VTAM Global Data Selection panel (FNM02GS1) 152VTAM log 179VTAM Start panel (FNM03VT2) 149VTAM Start panel (FNM03VTD) 148, 152, 157, 161VTAM statistics data

collecting 59controlling collection 60controlling monitoring 60description 5, 18environment 59monitoring 59recording 60viewing 60

XX.25 data 30, 31


Program Number: 5655-043

Printed in Denmark by IBM Danmark A/S

GH19-6961-06

Documents

NPM Concepts and Planning - IBMpublib.boulder.ibm.com/tividd/td/perfmon/SH19-6961... · Contents Figures..... vii Tables..... ix