IBMTivoli OMEGAMON XE for Mainframe Networks Version 5.1 · IBMTivoli OMEGAMON XE for Mainframe...

IBM Tivoli OMEGAMON XE for Mainframe NetworksVersion 5.1.1

Planning and Configuration Guide

SC27-4447-01

��

IBM Tivoli OMEGAMON XE for Mainframe NetworksVersion 5.1.1

Planning and Configuration Guide

SC27-4447-01

��

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

This edition applies to version 5.1.1 of IBM Tivoli OMEGAMON XE for Mainframe Networks (product number5698-T03) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2006, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

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

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

Chapter 1. Introducing IBM TivoliOMEGAMON XE for Mainframe Networks 1Enhanced 3270 user interface . . . . . . . . . 2Tivoli Management Services . . . . . . . . . 3

OMEGAMON XE common components . . . . 4Interoperability and integration . . . . . . . 5

Software and hardware prerequisites . . . . . . 5Required software . . . . . . . . . . . 6Supported hardware . . . . . . . . . . . 8

New in this release . . . . . . . . . . . . 9New in Version 5.1.1 . . . . . . . . . . 10New common features of all OMEGAMONversion 5.1.0 monitoring agents on z/OS . . . 20New function added since Version 4.2.0 Fix Pack3 . . . . . . . . . . . . . . . . . 23

IPv6 considerations . . . . . . . . . . . . 36Abbreviations used by the Configuration Tool . . . 36

Chapter 2. Planning for configuration 39CPU usage for monitoring networks on z/OSsystems. . . . . . . . . . . . . . . . 39Understanding how real-time data is collected. . . 39Determining which systems and TCP/IP addressspaces to monitor . . . . . . . . . . . . 40Determining which types of real-time data to collect 41Defining data collection intervals . . . . . . . 46Defining display intervals . . . . . . . . . 47Defining and running situations . . . . . . . 47Understanding how historical data is collected . . 48Determining which types of historical data to collect 50Designing workspaces . . . . . . . . . . . 51Tuning OMEGAMON XE components . . . . . 53Planning security . . . . . . . . . . . . 55Planning for OMEGAMON II for MainframeNetworks . . . . . . . . . . . . . . . 56

Chapter 3. Preparing your z/OSenvironment . . . . . . . . . . . . 59Enabling the z/OS Communications Server networkmanagement interface . . . . . . . . . . . 59Enabling SNMP manager functions . . . . . . 60Starting the OSA adapter SNMP subagent . . . . 61Verifying the z/OS environment setup . . . . . 62Defining monitoring agent access to the NMI andcommands. . . . . . . . . . . . . . . 65

Chapter 4. Upgrading to the newrelease. . . . . . . . . . . . . . . 67Upgrade overview . . . . . . . . . . . . 67Upgrading to the new release . . . . . . . . 68

Configuring a high availability hub andconverting a static hub to a remote . . . . . 68Enabling new features . . . . . . . . . . 68Performing a staged upgrade . . . . . . . 70

Upgrade considerations for the OMEGAMON XEfor Mainframe Networks monitoring agent . . . . 71

Upgrading a persistent data store . . . . . . 71Migrating historical data in the Tivoli DataWarehouse for Tivoli Enterprise Portal . . . . 71Upgrade issues related to SNMP configuration 71Upgrade issues related to running differentproduct versions. . . . . . . . . . . . 72

Upgrading an existing OMEGAMON II forMainframe Networks environment . . . . . . 72

Chapter 5. Configuration . . . . . . . 75

Chapter 6. Configuring OMEGAMON XEfor Mainframe Networks using thePARMGEN method . . . . . . . . . 77Configuring the enhanced 3270 user interface usingthe PARMGEN method . . . . . . . . . . 78Mainframe Networks configuration parameters . . 79Configuring security for Take Action commands . . 84Finding previous PARMGEN configuration sessions 84Ensuring that your runtime environment supportsthe NetView for z/OS packet trace usingPARMGEN . . . . . . . . . . . . . . 85

Chapter 7. Configuring the monitoringagent using the Configuration Tool . . 87Configuring the enhanced 3270 user interface usingthe Configuration Tool. . . . . . . . . . . 87Summary of the OMEGAMON XE configurationsteps . . . . . . . . . . . . . . . . 89

Running the JCL Jobs . . . . . . . . . . 90Accessing OMEGAMON XE configuration steps inthe Configuration Tool. . . . . . . . . . . 91Step 1: Registering with local TEMS . . . . . . 92Step 2: Specifying configuration parameters . . . 92

Adding, changing, or updating a monitoredsystem definition . . . . . . . . . . . 100

Step 3: Specifying agent address space parameters 105Step 4: Specifying dynamic terminal integrationparameters . . . . . . . . . . . . . . 117Step 5: Creating runtime members . . . . . . 118Step 6: Configuring the persistent datastore (in theagent) . . . . . . . . . . . . . . . . 118Step 7: Loading the runtime libraries . . . . . 123

Considerations when performing the RTE loadfunction . . . . . . . . . . . . . . 124

Step 8: Completing the configuration . . . . . 124Updating your runtime environment to support theNetView for z/OS packet trace . . . . . . . 124

© Copyright IBM Corp. 2006, 2012 iii

Chapter 8. Completing theconfiguration . . . . . . . . . . . 127Perform agent-specific security configuration . . . 128

Define monitoring agent access to the networkmanagement interfaces and commands . . . . 128Give users authorization and resource access torun the VARY TCPIP DROP command . . . . 130

Add support for the SYSTCPD DDNAME in thestarted tasks . . . . . . . . . . . . . . 131Copy the started task procedures to yourprocedure library . . . . . . . . . . . . 132Vary the VTAM major node active and copy it toyour VTAMLST library . . . . . . . . . . 133APF authorize your libraries . . . . . . . . 133Enable historical data store maintenance . . . . 134Run the ITMSUPER Tools (optional). . . . . . 135Making the performance monitor interface (PMI)exit available to VTAM . . . . . . . . . . 135Enabling CSA tracking to display TCP/IP CSAusage . . . . . . . . . . . . . . . . 136Configuring the OMEGAMON XE for MainframeNetworks SNMP manager functions . . . . . . 136Authorize the OMEGAMON XE for MainframeNetworks started tasks for TCP/IP privileges . . 137Configure historical data collection . . . . . . 137Enable Warehouse agents on a z/OS hubmonitoring server . . . . . . . . . . . . 138Install application and language support . . . . 139Verify the configuration . . . . . . . . . . 139Enable security . . . . . . . . . . . . . 140

Enabling security at Tivoli Enterprise Portal . . 140Enabling SNMP V3 passwords for autonomousagents . . . . . . . . . . . . . . . 140Authorizing users to access OMEGAMON XEfor Mainframe Networks managed systems onthe enhanced 3270 user interface . . . . . . 141Authorizing users to issue Take Actioncommands . . . . . . . . . . . . . 141

Deploy the configuration . . . . . . . . . 146Relink the runtime environments . . . . . . . 147

Chapter 9. Verifying the configuration 149Verifying configuration if you configured bothTivoli Enterprise Portal and the enhanced 3270user interface . . . . . . . . . . . . . 149Verifying configuration if you configured only theenhanced 3270 user interface . . . . . . . . 151

Appendix A. Configuring theOMEGAMON II for MainframeNetworks component . . . . . . . . 155Components of OMEGAMON II for MainframeNetworks that you configure . . . . . . . . 155Configuring OMEGAMON II for MainframeNetworks using the PARMGEN method . . . . 159Configuring OMEGAMON II for MainframeNetworks using the Configuration Tool. . . . . 159

Accessing OMEGAMON II configuration stepsin the Configuration Tool . . . . . . . . 160Step 1: Specify configuration values . . . . . 162

Step 2: Allocate additional runtime data sets . . 168Step 3: Create runtime members . . . . . . 169Step 4: Run migration utility . . . . . . . 169Step 5: Loading the runtime libraries and exitingthe Configuration Tool . . . . . . . . . 170Step 6: Completing the configuration . . . . 171Step 7: Configuring SAS Historical Reportingand complete SAS configuration . . . . . . 179

Changing the parameters after you exit theConfiguration Tool . . . . . . . . . . . 183Next steps . . . . . . . . . . . . . . 183

Appendix B. Customizing theOMEGAMON II components andverifying installation . . . . . . . . 185Customizing NCP . . . . . . . . . . . . 185

Specifying required NCP generation parameters 186Displaying performance statistics using X.25NCP generation . . . . . . . . . . . 186Using the NPALU definition to connect to theNCP collector . . . . . . . . . . . . 187Enabling NCP data collection . . . . . . . 188Disabling NCP data collection . . . . . . . 188

Customizing ETE . . . . . . . . . . . . 189Enabling ETE . . . . . . . . . . . . 189Disabling ETE . . . . . . . . . . . . 190

Configuring security . . . . . . . . . . . 190Using the NAM facility for security . . . . . 190Using RACF. . . . . . . . . . . . . 192Implementing external function-level security 192

Running in dedicated mode . . . . . . . . 194Activating a dedicated terminal . . . . . . 194Deactivating a dedicated terminal . . . . . 195Setting the polling interval . . . . . . . . 195

SMF record considerations . . . . . . . . . 195Enabling SMF recording . . . . . . . . . 195

Verifying the configuration . . . . . . . . . 196Starting End-to-End V620 . . . . . . . . 196Activating the OMEGAMON II major node . . 198Starting OMEGAMON II . . . . . . . . 198Initializing the NAM database. . . . . . . 199Logging onto OMEGAMON II . . . . . . 199Enabling TCP/IP data collection . . . . . . 200Enabling OMEGAMON II console support . . 201Setting thresholds and exceptions . . . . . 201

Appendix C. KN3FCCMD andKONFCCMD command reference . . . 203Introduction to the KN3FCCMD commands . . . 203

KN3FCCMD HELP . . . . . . . . . . 204KN3FCCMD INSTALL FPCT . . . . . . . 206KN3FCCMD INSTALL FPON . . . . . . . 206KN3FCCMD INSTALL SEMV . . . . . . . 207KN3FCCMD INSTALL SEVT . . . . . . . 207KN3FCCMD INSTALL TCPC . . . . . . . 207KN3FCCMD START CONN . . . . . . . 208KN3FCCMD START CSM . . . . . . . . 210KN3FCCMD START DBUG. . . . . . . . 211KN3FCCMD START EEHPR . . . . . . . 214KN3FCCMD START FTP . . . . . . . . 215

iv IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

KN3FCCMD START GLBS . . . . . . . . 216KN3FCCMD START INTE . . . . . . . . 217KN3FCCMD START INTS . . . . . . . . 218KN3FCCMD START IPSEC . . . . . . . . 219KN3FCCMD START OSA . . . . . . . . 221KN3FCCMD START ROUTE . . . . . . . 222KN3FCCMD START SNAC. . . . . . . . 223KN3FCCMD START TCPC . . . . . . . . 225KN3FCCMD START TN3270 . . . . . . . 229KN3FCCMD STATUS DBUG . . . . . . . 231KN3FCCMD STATUS FCPT . . . . . . . 231KN3FCCMD STATUS FPON . . . . . . . 232KN3FCCMD STATUS SEMV . . . . . . . 232KN3FCCMD STATUS SEVT . . . . . . . 232KN3FCCMD STATUS SNAC . . . . . . . 233KN3FCCMD STATUS TCPC . . . . . . . 233KN3FCCMD STOP CONN . . . . . . . . 234KN3FCCMD STOP CSM . . . . . . . . 236KN3FCCMD STOP DBUG . . . . . . . . 237KN3FCCMD STOP EEHPR . . . . . . . . 238KN3FCCMD STOP FTP . . . . . . . . . 239KN3FCCMD STOP GLBS . . . . . . . . 240KN3FCCMD STOP INTE . . . . . . . . 241KN3FCCMD STOP INTS . . . . . . . . 242KN3FCCMD STOP IPSEC . . . . . . . . 243KN3FCCMD STOP OSA. . . . . . . . . 245KN3FCCMD STOP ROUTE. . . . . . . . 246KN3FCCMD STOP TCPC . . . . . . . . 247KN3FCCMD STOP TN3270. . . . . . . . 251

Introduction to the KONFCCMD commands . . . 253Using the KONFCCMD command . . . . . 253KONFCCMD examples . . . . . . . . . 255

Appendix D. Disk space requirementsfor historical data tables . . . . . . 257Alternative methods of determining storagerequirements . . . . . . . . . . . . . 257

Trial and error approach. . . . . . . . . 258Estimating approach . . . . . . . . . . 258

Allocating additional storage and data sets . . . 258Estimating the space requirements . . . . . . 260

Historical data tables . . . . . . . . . . . 261Tools for estimating data storage requirements . . 263

Agent historical data storage . . . . . . . 263TCP/IP historical data storage. . . . . . . 265VTAM historical data storage . . . . . . . 277FTP historical data storage . . . . . . . . 281TN3270 historical data storage. . . . . . . 283

OMEGAMON XE for Mainframe Networks diskspace summary worksheet . . . . . . . . . 284

Estimating the storage required per LPAR . . . 286

Appendix E. Format of the SNMPconfiguration file . . . . . . . . . . 289When to create the SNMP configuration file . . . 289Format of the SNMP manager configuration file 289Sample configuration file . . . . . . . . . 290

Documentation library . . . . . . . 293IBM Tivoli OMEGAMON XE for MainframeNetworks publications . . . . . . . . . . 293OMEGAMON XE and Tivoli Management Serviceson z/OS common library . . . . . . . . . 294IBM Tivoli Monitoring library . . . . . . . . 294

Documentation for the base agents . . . . . 296Related publications . . . . . . . . . . . 296Other sources of documentation . . . . . . . 296

Support information . . . . . . . . 299

Index . . . . . . . . . . . . . . . 301

Accessibility . . . . . . . . . . . . 311

Notices . . . . . . . . . . . . . . 313Privacy policy considerations . . . . . . . . 315Privacy policy considerations . . . . . . . . 315Trademarks . . . . . . . . . . . . . . 316

Index . . . . . . . . . . . . . . . 317

Contents v

vi IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

Figures

1. Tivoli Management Services architecture . . . 42. The Enterprise Networks view in the

OMEGAMON XE for Mainframe NetworksTivoli Enterprise Portal Navigator . . . . . 10

3. Enterprise Networks Navigation view. . . . 124. Typical configuration for deployment of the

OMEGAMON XE for Mainframe Networksmonitoring agent. . . . . . . . . . . 75

5. PARMGEN Workflow Welcome panel on entry 856. Product component selection menu panel 887. The Configure OMEGAMON Enhanced 3270

UI / RTE: rte panel . . . . . . . . . . 888. The Specify Configuration Values panel 899. Product component selection menu panel 91

10. Configure OMEGAMON XE for MainframeNetworks panel . . . . . . . . . . . 92

11. Specify configuration parameters panel 9312. Specify component configuration panel 9313. Specify component configuration (page 2)

panel. . . . . . . . . . . . . . . 9514. Specify component configuration (page 3)

panel. . . . . . . . . . . . . . . 9615. Specify component configuration (page 4)

panel. . . . . . . . . . . . . . . 9716. Specify VTAM applid values / RTE (Page 5)

panel. . . . . . . . . . . . . . . 9817. Specify TCP/IP monitored system information

panel. . . . . . . . . . . . . . . 9918. Add TCP/IP monitored systems information

panel . . . . . . . . . . . . . . 10119. Add TCP/IP monitored systems info2 panel 10320. Add TCP/IP monitored systems info3 panel 10421. Specify agent address space parameters panel 10522. Specify IP.PIPE communication protocol panel 10923. Specify Agent IP.UDP Configuration Values

panel . . . . . . . . . . . . . . 11124. Specify Agent SNA Configuration Values

panel . . . . . . . . . . . . . . 11125. Specify Advanced Agent Configuration

Values panel . . . . . . . . . . . . 11326. Specify Dynamic Terminal Integration

Parameters panel . . . . . . . . . . 11727. Specify persistent data store values for the

monitoring agent . . . . . . . . . . 11928. Allocate persistent data store menu for the

monitoring agent . . . . . . . . . . 12029. Persistent data store specifications panel for

the monitoring agent . . . . . . . . . 120

30. Allocate persistent data store menu for themonitoring agent . . . . . . . . . . 122

31. Runtime Environments panel . . . . . . 12532. Update Runtime Environment (3 of 3) panel 12533. Command and Response Log workspace

(KN3CRTS) . . . . . . . . . . . . 14434. NCP Collector within the OMEGAMON II

address space . . . . . . . . . . . 15835. NCP Collector in another OMEGAMON II

address space . . . . . . . . . . . 15836. Runtime environments (RTEs) panel . . . . 16137. Product component selection menu panel 16138. Configure OMEGAMON II for Mainframe

Networks/RTE: rtename panel . . . . . . 16139. Specify configuration values/RTE:rtename

panel . . . . . . . . . . . . . . 16240. Local NCP data collection/RTE: rtename

panel . . . . . . . . . . . . . . 16641. Remote NCP data collection/RTE: rtename

panel . . . . . . . . . . . . . . 16742. Specify TCP/IP component configuration

panel . . . . . . . . . . . . . . 16743. Configure OMEGAMON II for Mainframe

Networks /RTE:rtename panel . . . . . . 17044. Configure SAS Historical Reporting / RTE:

rtename panel: Panel 1 . . . . . . . . 17945. SAS Historical Components / RTE: rtename

panel: Panel 2 . . . . . . . . . . . 18046. Define SAS Historical Components/ RTE:

rtename panel: Panel 3 . . . . . . . . 18047. SAS Historical Components / RTE: rtename

panel: Panel 4 . . . . . . . . . . . 18148. NCP NPALU Definitions panel . . . . . 18849. Formula for calculating DASD . . . . . . 25950. Formula for Agent historical collection data

storage. . . . . . . . . . . . . . 26451. Formula for TCP/IP historical collection data

storage. . . . . . . . . . . . . . 26652. Formula for VTAM historical collection data

storage. . . . . . . . . . . . . . 27853. Formula for FTP historical collection data

storage. . . . . . . . . . . . . . 28254. Formula for TN3270 historical collection data

storage. . . . . . . . . . . . . . 28355. KB formula for total storage required per

LPAR for cylinders of 3390 DASD. . . . . 28656. Cylinder formula for total storage required

per LPAR in cylinders of 3390 DASD . . . 287

© Copyright IBM Corp. 2006, 2012 vii

viii IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

Tables

1. z/OS common components . . . . . . . 52. New workspaces displayed in Tivoli Enterprise

Portal . . . . . . . . . . . . . . 113. New workspaces displayed in the enhanced

3270 user interface . . . . . . . . . . 134. New attributes and attribute values . . . . 155. New attributes and attribute values . . . . 246. Configuration Tool abbreviations . . . . . 367. Names and sizes for data spaces used during

data collection . . . . . . . . . . . 408. Data collected every time the Agent or TCP/IP

subnode workspaces are displayed orrefreshed . . . . . . . . . . . . . 42

9. Data collected once every collection interval 4210. Data collected for each monitored LPAR 4411. FTP data collected . . . . . . . . . . 4512. TN3270 data collected . . . . . . . . . 4613. Preconfiguration tasks . . . . . . . . . 7514. Tasks to complete before configuring

OMEGAMON XE for Mainframe Networks . . 7715. OMEGAMON XE for Mainframe Networks

parameters divided into the groups found inthe configuration profile . . . . . . . . 80

16. Parameters and explanations for the UpdateRuntime Environment (3 of 3) panel . . . . 86

17. Parameters and explanations for the SpecifyConfiguration Parameters panel . . . . . . 93

18. Parameters and explanations for the SpecifyComponent Configuration panel . . . . . 94

19. Parameters and explanations for the SpecifyComponent Configuration (Page 2) panel . . 95



22. Parameters and explanations for the SpecifyVTAM APPLID Values (Page 5) panel . . . . 99

23. Parameters and explanations for the SpecifyTCP/IP Monitored Systems Information panel 100

24. Parameters and explanations for the AddTCP/IP Monitored Systems Info panel . . . 101

25. Parameters and explanations for the AddTCP/IP Monitored Systems Info2 panel . . . 103

26. Parameters and explanations for the AddTCP/IP Monitored Systems Info3 panel . . . 104

27. Parameters and explanations for the SpecifyAgent Address Space Parameters panel . . . 105

28. Parameters and explanations for the SpecifyAgent IP.PIPE Communication Protocol andSpecify Agent IP.UDP Configuration Valuespanels . . . . . . . . . . . . . . 109

29. Parameters and explanations for the SpecifyAgent SNA Configuration Values panel . . . 112

30. Parameters and explanations for theAdvanced agent configuration values panel . 114

31. Parameters and explanations for the Specifydynamic terminal integration parameterspanel . . . . . . . . . . . . . . 118

32. Parameters and explanations for the SpecifyPersistent Datastore Values panel . . . . . 119

33. Parameters and explanations for thePersistent Datastore Specifications panel . . 121

34. Parameters and explanations for the UpdateRuntime Environment (3 of 3) panel . . . . 126

35. Product components for OMEGAMON II forMainframe Networks . . . . . . . . . 155

36. Parameters and explanations for the SpecifyConfiguration Values panel . . . . . . . 162

37. Parameters and explanations for the LocalNCP Data Collection panel . . . . . . . 166

38. Parameters and explanations for the RemoteNCP Data Collection panel . . . . . . . 167

39. Parameters and explanations for the SpecifyTCP/IP Component Configuration panel . . 168

40. Parameters and explanations for theConfigure SAS Historical Reporting / RTE:rtename panel . . . . . . . . . . . 179

41. Parameters and explanations for the DefineSAS Historical Component / RTE: rtenamepanel . . . . . . . . . . . . . . 181

42. Parameters and explanations for the SASHistorical Components / RTE: rtename panel . 182

43. Operating requirements for NCP . . . . . 18544. Attribute groups and workspaces affected by

the KN3FCCMD START CONN command . . 20945. Attribute groups and workspaces affected by

the KN3FCCMD START CSM command . . 21046. Components available from subset trace

records. . . . . . . . . . . . . . 21147. Attribute groups and workspaces affected by

the KN3FCCMD START EEHPR command . 21448. Attribute groups and workspaces affected by

the KN3FCCMD START FTP command . . . 21549. Attribute groups and workspaces affected by

the KN3FCCMD START GLBS command . . 21750. Attribute groups and workspaces affected by

the KN3FCCMD START INTE command . . 21851. Attribute groups and workspaces affected by

the KN3FCCMD START INTS command . . 21952. Attribute groups and workspaces affected by

the KN3FCCMD START IPSEC command . . 22053. Attribute groups and workspaces affected by

the KN3FCCMD START OSA command . . 22154. Attribute groups and workspaces affected by

the KN3FCCMD START ROUTE command . 22355. Attribute groups and workspaces affected by

the KN3FCCMD START SNAC command . . 22456. Attribute groups and workspaces affected by

the KN3FCCMD START TCPC command . . 22557. Attribute groups and workspaces affected by

the KN3FCCMD START TN3270 command . 230

© Copyright IBM Corp. 2006, 2012 ix

58. Attribute groups and workspaces affected bythe KN3FCCMD STOP CONN command . . 235

59. Attribute groups and workspaces affected bythe KN3FCCMD STOP CSM command . . . 236

60. Components available from subset tracerecords. . . . . . . . . . . . . . 237

61. Attribute groups and workspaces affected bythe KN3FCCMD STOP EEHPR command . . 239

62. Attribute groups and workspaces affected bythe KN3FCCMD STOP FTP command . . . 240

63. Attribute groups and workspaces affected bythe KN3FCCMD STOP GLBS command. . . 241

64. Attribute groups and workspaces affected bythe KN3FCCMD STOP INTE command . . . 242

65. Attribute groups and workspaces affected bythe KN3FCCMD STOP INTS command . . . 243

66. Attribute groups and workspaces affected bythe KN3FCCMD STOP IPSEC command . . 244

67. Attribute groups and workspaces affected bythe KN3FCCMD STOP OSA command . . . 245

68. Attribute groups and workspaces affected bythe KN3FCCMD STOP ROUTE command . . 247

69. Attribute groups and workspaces affected bythe KN3FCCMD STOP TCPC command . . 247

70. Attribute groups and workspaces affected bythe KN3FCCMD STOP TN3270 command . . 252

71. Definition and default values for cylindersand group count parameters . . . . . . 259

72. Sample group count and cylinders to allocateto enable viewing of 24 hours of data . . . 260

73. Historical data tables . . . . . . . . . 26174. Agent data collected . . . . . . . . . 26475. KN3 Agent Status (KN3AGS) worksheet 26576. TCP Collector Status (KN3TCS) worksheet 26577. SNA Collector Status (KN3SCS) worksheet 26578. Data collected once every collection interval 26679. Current IP Filters (KN3IFC) worksheet 26880. Dynamic IP Tunnels (KN3ITD) worksheet 26881. Interfaces (KN3TIF) worksheet . . . . . . 26882. IKE Tunnels (KN3ITI) worksheet . . . . . 26983. IPSec Status (KN3ISS) worksheet . . . . . 26984. KN3 ICMP Global Counters (KN3GCG)

worksheet. . . . . . . . . . . . . 26985. KN3 ICMP Type Counters (KN3GCT)

worksheet. . . . . . . . . . . . . 26986. KN3 Interface Address (KN3IFA) worksheet 27087. KN3 Interface Read Queue (KN3IFR)

worksheet. . . . . . . . . . . . . 27088. KN3 Interface Statistics (KN3IFS) worksheet 27089. KN3 Interface Status (KN3IFE) worksheet 27090. KN3 Interface Write Queue (KN3IFW)

worksheet. . . . . . . . . . . . . 27191. KN3 IP Counter Statistics (KN3GIC)

worksheet. . . . . . . . . . . . . 27192. IP General Statistics (KN3GIG) worksheet 27193. KN3 TCP Counter Statistics (KN3GTC)

worksheet. . . . . . . . . . . . . 27194. KN3 UDP Counter Statistics (KN3GUC)

worksheet. . . . . . . . . . . . . 272

95. Manual IP Tunnels (KN3ITM) worksheet 27296. OSA-Express Channels (KN3TCH) worksheet 27297. OSA-Express LPARS (KN3TLP) worksheet 27298. OSA-Express Ports (KN3TPO) worksheet 27399. OSA 10 Gigabit Ports Control (KN3TTC)

worksheet. . . . . . . . . . . . . 273100. OSA 10 Gigabit Ports Errors (KN3TTE)

worksheet. . . . . . . . . . . . . 273101. OSA 10 Gigabit Ports Summary (KN3TTS)

worksheet. . . . . . . . . . . . . 273102. OSA 10 Gigabit Ports Throughput (KN3TTT)

worksheet. . . . . . . . . . . . . 274103. OSA-Express3 Ports Control (KN3THC)

worksheet. . . . . . . . . . . . . 274104. OSA-Express3 Ports Errors (KN3THE)

worksheet. . . . . . . . . . . . . 274105. OSA-Express3 Ports Summary (KN3THS)

worksheet. . . . . . . . . . . . . 274106. OSA-Express3 Ports Throughput (KN3THT)

worksheet. . . . . . . . . . . . . 275107. TCP Listener (KN3TCL) worksheet . . . . 275108. TCPIP Address Space (KN3TAS) worksheet 275109. TCPIP Applications (KN3TAP) worksheet 275110. TCPIP Connections (KN3TCN) worksheet 276111. TCPIP Details (KN3TCP) worksheet . . . . 276112. TCPIP Devices (KN3TDV) worksheet 276113. TCPIP Gateways (KN3TGA) worksheet 276114. TCPIP Memory Statistics (KN3TPV)

worksheet. . . . . . . . . . . . . 277115. TCPIP Stack Layer (KN3TSL) worksheet 277116. UDP Connections (KN3UDP) worksheet 277117. Data collected once every collection interval 278118. CSM Storage (KN3CSM) worksheet . . . . 279119. EE Connection Details (KN3EED) worksheet 279120. EE Connections (KN3EEC) worksheet 279121. HPR RTP Connections (KN3HPR) worksheet 279122. KN3 CSM Storage by Owner (KN3CSO)

worksheet. . . . . . . . . . . . . 280123. VTAM Summary Statistics (KN3VAS)

worksheet. . . . . . . . . . . . . 280124. VTAM Buffer Pool Extents (KN3BPE)

worksheet. . . . . . . . . . . . . 280125. VTAM Buffer Pools (KN3BPD) worksheet 280126. VTAM Buffer Usage by Address Space

(KN3BPS) worksheet . . . . . . . . . 280127. VTAM Buffer Usage by Application for

Address Space (KN3BPA) worksheet . . . . 281128. VTAM Buffer Usage by Category (KN3BPG)

worksheet. . . . . . . . . . . . . 281129. VTAM I/O (KN3VIO) worksheet . . . . . 281130. VTAM Summary Statistics (KN3SNA)

worksheet. . . . . . . . . . . . . 281131. FTP data collected . . . . . . . . . . 282132. FTP Sessions (KN3FSE) worksheet . . . . 282133. TCPIP FTP (KN3FTP) worksheet . . . . . 283134. TN3270 data collected. . . . . . . . . 284135. TN3270 Server Sess Avail (KN3TNA)

worksheet. . . . . . . . . . . . . 284136. Disk space summary . . . . . . . . . 284

x IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

Chapter 1. Introducing IBM Tivoli OMEGAMON XE forMainframe Networks

IBM® Tivoli® OMEGAMON® XE for Mainframe Networks is a monitoring agent that is located on eachz/OS® image you want to monitor.

This monitoring agent assists you in anticipating network performance problems and warns you whencritical events take place on your systems.

OMEGAMON XE for Mainframe Networks Version 5.1.1 is equivalent to Version 5.1.0 with APARsOA42339 and OA42422 applied. You can upgrade from OMEGAMON XE for Mainframe Networks V5.1.0by installing the PTFs and fix pack that are associated with APARs OA42339 and OA42422, or you canupgrade from V4.1.0 or later by ordering and installing OMEGAMON XE for Mainframe Networks V5.1.1PID: 5698-T03. If you have enabled the self-describing agent feature, and you do not use the TivoliEnterprise Portal desktop client, you do not need to install the distributed fix pack that goes with theAPARs. Refer to the Version 5.1.1 Program Directory for pre-requisites and installation instructions.

With OMEGAMON XE for Mainframe Networks, you can monitor and manage the health of TCP/IP andVTAM® resources (in addition to NCP performance monitoring, which is provided by the OMEGAMONII for Mainframe Networks component) within your IBM z/OS environments. OMEGAMON XE forMainframe Networks is designed to analyze TCP/IP performance among CICS®, DB2®, IMS™, and otherkey applications to identify resource loss and unstable connections. The power to monitor the userexperience lets you fine-tune TCP/IP performance and resolve problems before customers complain.

OMEGAMON XE for Mainframe Networks has the following features:v Monitors TCP/IP and VTAMv Monitors file transfer protocol (FTP) and TN3270 sessionsv Monitors High-Performance Routing (HPR) links and Enterprise Extender (EE) connectionsv Monitors performance of OSA adaptersv Provides information about application connections, ports, packet size, and volumev Measures IP discards, reassemblies, and fragmentationv Provides detailed analysis of TCP/IP connections that are slow, unstable, or downv Displays information for each TCP/IP connection such as application name and IP addressesv Measures transaction round-trip time using the OMEGAMON II for Mainframe Networks ETE

componentv Resolves common problem scenarios using the OMEGAMON enhanced 3270 user interface set of

predefined workspaces

The OMEGAMON XE for Mainframe Networks monitoring agent is included with Tivoli ManagementServices, which provides a common architecture for all products that use the Tivoli Enterprise Portal.

The data that is collected by the monitoring agents and alerts that are triggered by monitored conditionsare displayed in one of the three interfaces supported by this monitoring agent:v The new OMEGAMON enhanced 3270 user interface, the latest generation of 3270 interfaces for the

OMEGAMON family of monitoring products, which provides specially designed workspaces, thatpromote intelligent navigation to expedite problem diagnosis that span multiple products. See“Enhanced 3270 user interface” on page 2.

v Tivoli Enterprise Portal, a graphical, Java™-based interface, shared with other OMEGAMON XE andIBM Tivoli Monitoring products.

© Copyright IBM Corp. 2006, 2012 1

v OMEGAMON II for Mainframe Networks product, sometimes called the CUA interface.

This configuration and planning guide covers not just the OMEGAMON XE product but also theOMEGAMON II component. See Appendix A, “Configuring the OMEGAMON II for MainframeNetworks component,” on page 155 and Appendix B, “Customizing the OMEGAMON II components andverifying installation,” on page 185 for information about OMEGAMON II. The configuration informationfor the enhanced 3270 user interface is found in the IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide.

This information assumes you are ready to configure the OMEGAMON XE for Mainframe Networksmonitoring agent and (optionally) the OMEGAMON II for Mainframe Networks component. Before youbegin configuring this agent, be sure to consult the following resources and complete the following tasks:v Gather the OMEGAMON XE for Mainframe Networks monitoring agent information described in the

Preinstallation Requirements and Instructions found at http://www-01.ibm.com/support/docview.wss?uid=swg21318692. Additional planning information for the OMEGAMON XE forMainframe Networks monitoring agent is also found in Chapter 2, “Planning for configuration,” onpage 39.

v Set up your z/OS environment using the information found in Chapter 3, “Preparing your z/OSenvironment,” on page 59.

v Study and review the progression of tasks defined in the IBM Tivoli OMEGAMON XE MonitoringAgents on z/OS: Quick Start Guide if you are installing an OMEGAMON monitoring agent for the firsttime. Review the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guideand Chapter 4, “Upgrading to the new release,” on page 67 if you are upgrading from a previousversion.

v Set up or upgrade your Tivoli Management Services environment to match the versions described inthe IBM Tivoli Monitoring: Installation and Setup Guide under “Software and hardware prerequisites” onpage 5.

v Use the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference toconfigure this monitoring agent and the z/OS components of your environment using the PARMGENmethod. Choose the scenario that best matches your requirements, and use the IBM TivoliOMEGAMON XE and Tivoli Management Services on z/OS: Common Parameter Reference to understandconfiguration parameters common to the Tivoli Management Services environment, and the IBM TivoliOMEGAMON XE for Mainframe Networks: Parameter Reference to understand configuration parametersassociated with this monitoring agent. See Chapter 6, “Configuring OMEGAMON XE for MainframeNetworks using the PARMGEN method,” on page 77.

v Optionally, you can use the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:Common Planning and Configuration Guide and the Configuration Tool to install and configure the z/OScomponents of your environment. The preferred method is PARMGEN. See Chapter 7, “Configuringthe monitoring agent using the Configuration Tool,” on page 87.

v Configure your Tivoli Enterprise Monitoring Server on z/OS using the information in IBM TivoliMonitoring: Configuring the Tivoli Enterprise Monitoring Server on z/OS.

v Perform the steps to complete your configuration found in Chapter 8, “Completing the configuration,”on page 127.

v Perform the verification steps found in “Verifying configuration if you configured both TivoliEnterprise Portal and the enhanced 3270 user interface” on page 149.

Enhanced 3270 user interfaceThe OMEGAMON enhanced 3270 user interface is a component within the OMEGAMON XE forMainframe Networks base product.

The OMEGAMON enhanced 3270 user interface component is the latest generation of 3270 interfaces forthe OMEGAMON family of monitoring products. The new interface preserves many of the valued

2 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

http://www-01.ibm.com/support/docview.wss?uid=swg21318692


features of the earlier OMEGAMON II (CUA) interface, but extends the functionality to include manynew features, including cross-system and cross-product reporting.

You can use the OMEGAMON enhanced 3270 user interface component to monitor the performance ofyour z/OS systems, applications, and devices in your environment and helps you identify andtroubleshoot problems with those monitored resources. The OMEGAMON enhanced 3270 user interface isdeveloped using the common OMNIMON base component. In the interface, data is presented inworkspaces and subpanels in which thecollected data and relevant information are displayed. You canuse the predefined workspaces in OMEGAMON XE for Mainframe Networks to quickly and easilydiagnose problems with monitored resources and take action to correct them.

For more information about this interface, see the IBM Tivoli OMEGAMON XE and IBM Tivoli ManagementServices on z/OS: OMEGAMON Enhanced 3270 User Interface Reference and the IBM Tivoli OMEGAMON XEfor Mainframe Networks: Enhanced 3270 User Interface Guide.

Tivoli Management ServicesOMEGAMON XE for Mainframe Networks takes advantage of the Tivoli Management Servicesinfrastructure.

Tivoli Management Services provides security, data transfer and storage, notification mechanisms, userinterface presentation, and communication services for a number of products, including IBM TivoliMonitoring and OMEGAMON XE monitoring agents, in an agent-server-client implementation. This setof relationships is shown in Figure 1 on page 4.

Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 3

Some components of Tivoli Management Services, such as Tivoli Enterprise Portal and the WarehouseProxy and Summarization and Pruning agents, run only on distributed systems (Windows, AIX®, andLinux). The Tivoli Enterprise Monitoring Server and the Tivoli Data Warehouse can run on eitherdistributed or mainframe systems. The Tivoli Management Services: Engine (TMS: Engine) runs only onmainframe systems. The components of Tivoli Management Services are described in detail in the IBMTivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and Configuration Guide.For detailed information about installing, configuring, and using Tivoli Management Services, see theIBM Tivoli Monitoring and OMEGAMON Information Center.

Note: The shared components of the IBM Tivoli Management Services on z/OS product are notautomatically included in the product package for a monitoring agent on z/OS systems. Be sure toinclude IBM Tivoli Management Services on z/OS in your order. If you have not ordered any monitoringagents on a z/OS system but you want to install a monitoring server on a z/OS system, you can orderIBM Tivoli Management Services on z/OS by itself. The IBM Tivoli Management Services on z/OSproduct includes both mainframe and distributed components of Tivoli Management Services (IBM TivoliMonitoring).

OMEGAMON XE common componentsOMEGAMON XE monitoring agents on z/OS share several components (referred to as commoncomponents: see Table 1). These common components, along with the monitoring agent software areincluded on the OMEGAMON XE for Mainframe Networks V5.1.0 product tape.

Figure 1. Tivoli Management Services architecture


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/

Table 1. z/OS common components

Component Function

End-to-End Response Timecollector V6.2.0

Provides response time data for several OMEGAMON XE products.

OMNIMON base V7.0.0 Provides a set of common code that is used by OMEGAMON Classic (realtimecollectors) components and the OMEGAMON enhanced 3270 user interface tocontrol initialization, security, and I/O for all sessions. OMNIMON Base has twocomponents:

v OMEGAMON Subsystem (formerly Candle Subsystem):

A z/OS subsystem, running in its own address space, that enablesOMEGAMON IIs running in other address spaces to monitor dynamic deviceactivity. A single OMEGAMON Subsystem can support multiple copies ofOMEGAMON II and multiple OMEGAMON II products on a single z/OSimage. Some OMEGAMON XE monitoring products, including OMEGAMONXE for Mainframe Networks, do not use the OMEGAMON Subsystem.

v Enhanced 3270 User Interface

An enhanced 3270-based user interface that collects and displays data from theTivoli Enterprise Monitoring Server and the supporting OMEGAMON XE onz/OS monitoring agents. One instance of the interface must be installed in eachSysplex for use by all supporting agents.

Note: If you install OMEGAMON XE for Mainframe Networks into an existing environment, in whichthe components are already at the required level, for example, if you have already installed anotherOMEGAMON XE agent, you might need to delete the FMIDs for these components from the SMP/Einstall jobs to avoid errors because they are already installed. See the IBM Tivoli OMEGAMON XE forMainframe Networks: Program Directory for more information.

Interoperability and integrationOMEGAMON XE for Mainframe Networks is designed to integrate with all products that use TivoliManagement Services.

These products exploit the ability of the Tivoli Enterprise Portal to integrate and correlate performanceand availability information from a variety of sources. For example, with OMEGAMON DE, you cancreate custom workspaces composed of data from a range of Tivoli monitoring solutions (IBM TivoliMonitoring, IBM Tivoli Composite Application Manager, and IBM Tivoli NetView® for z/OS, andOMEGAMON XE monitoring agents). You can also create context-sensitive links between productworkspaces to obtain additional information about systems, subsystems, resources, or networkcomponents that are being monitored by other monitoring agents, or links that access related screens inTN3270-based applications.

OMEGAMON XE products are being integrated with an increasing number of other Tivoli and IBMproducts. Situation events reported by OMEGAMON XE for Mainframe Networks can be forwarded toTivoli Event Console or Tivoli Netcool/OMNIbus for event correlation and management. From the TivoliEnterprise Portal you can "launch in context" into other Web-based or Web-enabled Tivoli applicationswithout having to re-enter user credentials, and you can "launch in context" into Tivoli Enterprise Portalworkspaces from applications such as IBM Tivoli Business Services Manager.

Software and hardware prerequisitesTivoli Management Services must already be installed. Versions of all the required products forMainframe Networks are provided in the product package.

However, if you already installed V5.1.0 of another OMEGAMON XE monitoring agent on z/OS in yourenterprise, you can use the currently installed Tivoli Management Service components. A complete list of


the product components is found in the IBM Tivoli OMEGAMON XE Monitoring Agents on z/OS: QuickStart Guide, and the z/OS prerequisites are found in the IBM Tivoli OMEGAMON XE for MainframeNetworks: Program Directory. Information about z/OS and distributed prerequisites are found in thesections that follow.

Required softwareThe required levels of software for the Configuration Tool, Tivoli Management Services components,PARMGEN configuration, SAF product, z/OS, IBM Tivoli NetView for z/OS, and other software areexplained in the section that follows.

Software product and levels

The following software products and levels are required for running the Tivoli Management Servicescomponents and the OMEGAMON XE for Mainframe Networks monitoring agent.

PARMGEN configuration requirements

OMEGAMON XE for Mainframe Networks and OMEGAMON II for Mainframe Networks are configuredby using the PARMGEN method. Configuration using the PARMGEN method requires a minimum ofIBM Tivoli Management Services v6.2.3 Fix Pack 1 with APAR OA39890 or later or PTFs UA66332 andUA69076 (for LIMIT support) applied.

If the hub monitoring server and the remote monitoring server reside on z/OS, they must also bemodified to use LIMIT(24,X). Follow the process outlined in the Configuring the Tivoli Enterprise MonitoringServer on z/OS book and ensure that the Maximum storage request size (Extended) value is set to greaterthan or equal to 24.

Also, you cannot migrate or configure an OMEGAMON monitoring agent on z/OS earlier than v4.2.0 byusing the PARMGEN method. See the PARMGEN Technote found at http://www.ibm.com/support/docview.wss?uid=swg21417935 for additional requirements. See also the IBM Tivoli OMEGAMON XE andTivoli Management Services on z/OS: PARMGEN Reference.

Configuration Tool requirements

If you install this monitoring agent using the Configuration Tool, use v310.25 or later of the ConfigurationTool, which is included in the product package. If you have an earlier version of the Configuration Toolon your z/OS system in the same consolidated software inventory (CSI), it is automatically replaced byv310.25 or later of the Configuration Tool during installation.

The preferred method of configuration is PARMGEN.

Software requirements for Tivoli Enterprise Monitoring Server, Tivoli EnterprisePortal, Tivoli Enterprise Portal Server, and Tivoli Data Warehouse on distributedoperating systems

Before you install the OMEGAMON XE for Mainframe Networks monitoring agent into an existing TivoliManagement Services environment, ensure that you have upgraded this environment to version 6.2.3 FixPack 1 or later.

Best practice: Version 6.2.3 Fix Pack 3 or later. If you are already running v6.3.0 of IBM Tivoli Monitoringcomponents, then v6.3.0 Fix Pack 1 is the best practice recommendation.

Detailed software requirements for all distributed components of the Tivoli Management Services (TivoliEnterprise Monitoring Server, Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Tivoli Data


http://www.ibm.com/support/docview.wss?uid=swg21417935

http://www.ibm.com/support/docview.wss?uid=swg21417935

Warehouse running on any of the supported operating systems) are found in IBM Tivoli Monitoring:Installation and Setup Guide.

Software requirements for the enhanced 3270 user interface

To use the functionality provided by the enhanced 3270 user interface, you should install PTF UA66193or later.

Best practice: PTF UA69205.

Software requirements for the Tivoli Enterprise Monitoring Server on z/OS

Detailed software requirements for a Tivoli Enterprise Monitoring Server running on z/OS are found inIBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide. Other environment planning decisions about the Tivoli Enterprise Monitoring Server on z/OS arealso found in this book.

Software requirements for historical data collection and the Tivoli Data Warehouse

Software requirements for storing and retrieving historical data in the Tivoli Data Warehouse are found inIBM Tivoli Monitoring: Installation and Setup Guide.

Historical collection is currently a function of the Tivoli Enterprise Portal interface.

Supported system authorization facility (SAF) products for a Tivoli EnterpriseMonitoring Server on z/OS

Security on Tivoli Enterprise Monitoring Server on z/OS is based on password validation that uses thelocal operating system. You can use the Resource Access Control Facility (RACF®), which is part of thez/OS operating system, or another SAF product to provide user authentication.

In V5.1.0 and later of this monitoring agent, you can use the SAF security class that is defined for theruntime environment to control access to the OMEGAMON XE for Mainframe Networks commands, oryou can use a separate security class. Unlike previous releases, these commands fail RACF authorizationunless SAF security is configured. See “Authorizing users to issue Take Action commands” on page 141for information about configuring SAF security for Take Action commands.

Supported versions of z/OS for the OMEGAMON XE for Mainframe Networksmonitoring agent

z/OS systems on which zSeries® monitoring agents such as OMEGAMON XE for Mainframe Networksare installed must be running z/OS V1.12 or later. For information about APARs required, see the IBMTivoli OMEGAMON XE for Mainframe Networks: Program Directory. For late-breaking information, see thePreventive Service Planning (PSP) bucket for this monitoring agent.

If you recently migrated to z/OS v2.1, you might find OMVS errors in the system log when you launchthe OMEGAMON XE for Mainframe Networks monitoring agent. Be aware that as of z/OS V2R1, theability to use default OMVS segments has been removed. All z/OS UNIX users or groups must now haveOMVS segments defined for user and group profiles with unique user IDs (UIDs) and group IDs (GIDs).For more information about this error and workarounds, see "OMVS and SNAMGMT errors found insystem log on z/OS v2.1 systems" in the IBM Tivoli OMEGAMON XE for Mainframe Networks:Troubleshooting Guide.


Supported versions of Tivoli NetView for z/OS

If you want to use the Tivoli NetView dynamic workspace links (DWL) feature or launch the NetViewpacket trace feature from the OMEGAMON XE for Mainframe Networks monitoring agent, ensure thatyou are running IBM Tivoli NetView for z/OS. Versions 5.4 or 6.1 are supported with APAR OA32192.

For more information about DWL links between NetView for z/OS and the OMEGAMON XE forMainframe Networks monitoring agent, refer to the overview of product-provided workspaces section ofthe IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide. For moreinformation about running the NetView packet trace feature from the OMEGAMON XE for MainframeNetworks monitoring agent, see the section on accessing NetView for z/OS packet trace by usingdynamic links to 3270 applications in the IBM Tivoli OMEGAMON XE for Mainframe Networks: TivoliEnterprise Portal User's Guide.

Optional software

Tivoli NetView Performance Monitor V2R7 is provided as an optionally orderable, no-cost feature tosupport customers using SNA or moving from SNA to IP. Tivoli NetView Performance Monitor runs as az/OS Communications Server application program. You can use Tivoli NetView Performance Monitor tocollect and monitor performance data, collect accounting data, and determine problems in the networkfor SNA networks. NetView Performance Monitor is provided as part of the IBM Tivoli OMEGAMON XEfor Mainframe Networks product package.

For more information about Tivoli NetView Performance Monitor, see http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.perfmon.doc_2.7/toc.xml.

Supported hardwareMost of the hardware that is required to run OMEGAMON XE for Mainframe Networks is determinedby operating system considerations.

For example, the requirements for the UNIX systems where parts of the IBM Tivoli Monitoring platformare running are determined by the operating system. For most hardware prerequisites, see the IBM TivoliMonitoring: Installation and Setup Guide.

The following remaining prerequisites apply to OMEGAMON XE for Mainframe Networks product.

Requirements for z/OS systems where monitoring agents are deployed

OMEGAMON XE for Mainframe Networks monitoring agents can be deployed on any z/OS system thatcan run z/OS V1.12 or higher.

You must also ensure that you have adequate direct access storage device (DASD) space to accommodatethe products you are installing. Before you install your OMEGAMON products, you must review thespace requirements and considerations for an SMP/E installed environment to make sure that sufficientDASD storage is available.

Note: Program directories cover DASD requirements for SMP/E target and distribution data sets. Youcan also use the Job Generator (JOBGEN) Reallocation Facility to analyze your DASD requirements andcompute your persistent data store requirements. Remember that you also have DASD requirements forruntime libraries and short-term history. Ensure that you define enough DASD for short-term historicaldata storage. See Appendix D, “Disk space requirements for historical data tables,” on page 257 for moreinformation about sizing your persistent data store. See http://www-01.ibm.com/support/docview.wss?uid=swg21417935 and http://www-01.ibm.com/support/docview.wss?uid=swg21338430 forinformation about the JOBGEN tool.


http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=%2Fcom.ibm.perfmon.doc_2.7%2Fwelcome.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=%2Fcom.ibm.perfmon.doc_2.7%2Fwelcome.htm




The Tivoli OMEGAMON XE for Mainframe Networks: Program Directory contains the approximate DASDspace requirements for the OMEGAMON II for Mainframe Networks and OMEGAMON XE forMainframe Networks products. Be aware that this estimate presupposes that these products are installedas standalone applications. When multiple OMEGAMON products are installed into a shared CSIenvironment, DASD requirements can be less.

The Tivoli OMEGAMON XE for Mainframe Networks: Program Directory provides the basic spacerequirements for the Tivoli Enterprise Monitoring Server, the Tivoli Enterprise Portal, the Tivoli EnterprisePortal Server, and for the monitoring agents. These basic space requirements do not include additionalspace that is required for maintaining historical data files.

Because of the variations in design characteristics such as client distributed systems, system size, andnumber of managed systems, providing specific disk space requirements for historical data collection isdifficult. You might want to experiment to determine how much space you need. Start out by using thedefault disk space requirements to configure the data store. Then observe how quickly space is used.Eventually you might want to allocate enough space so that maintenance procedures only need to runonce a day. Use the information in Appendix D, “Disk space requirements for historical data tables,” onpage 257 to help determine how much space to allocate.

Requirements for OSA-Express adapters

You can use OMEGAMON XE for Mainframe Networks to monitor the performance of the OSA adaptersin your environment. OSA-Express and OSA-Express2 (except OSA-Express2 10 Gigabit) adapters aresupported by both OSA/SF and OSA-Express Direct SNMP.

For more information, see the following resources:v The section on configuring the Open System Adapter in Open System Adapter-Express Customer's Guide

and Reference (SA22-7476)v zEnterprise 196, System z10, System z9, and eServer zSeries Open Systems Adapter-Express Customer's Guide

and Reference (SA22-7935)v “Starting the OSA adapter SNMP subagent” on page 61 and “Verifying the z/OS environment setup”

on page 62 in this book

To support the latest version of the OSA-Express MIB, the Licensed Internal Code (LIC) levels of theOSA-Express adapters must meet the following criteria:v If you are running the OSA module on an IBM eServer™ zSeries 900 or 800 system, you must have a

licensed internal code (LIC) V3.33 or higher installed.v If you are running the OSA module on an IBM eServer zSeries 990 processor or higher, all LIC levels

are supported.v Monitoring OSA-Express3 adapters requires the use of the OSA-Express Direct SNMP subagent

(IOBSNMP).

The OSA-Express LIC level requirements are outlined at the following Web site: https://www-01.ibm.com/servers/resourcelink/lib03010.nsf/pages/osaLibrary?OpenDocument&pathID=&Start=1 -.

New in this releaseThe following updates were made to the Tivoli OMEGAMON XE for Mainframe Networks monitoringagent for Version 5.1.0.v “New in Version 5.1.1” on page 10v “New function added since Version 4.2.0 Fix Pack 3” on page 23v “New common features of all OMEGAMON version 5.1.0 monitoring agents on z/OS” on page 20


https://www-01.ibm.com/servers/resourcelink/lib03010.nsf/pages/osaLibrary?OpenDocument&pathID=&Start=1 -

https://www-01.ibm.com/servers/resourcelink/lib03010.nsf/pages/osaLibrary?OpenDocument&pathID=&Start=1 -

New in Version 5.1.1The following changes were introduced to OMEGAMON XE for Mainframe Networks in Version 5.1.1.

Changes to the Navigator in Tivoli Enterprise Portal

A new logical view that contains a set of Enterprise Networks workspaces is available from theOMEGAMON XE for Mainframe Networks Navigator in Tivoli Enterprise Portal, an addition to theexisting Navigator view. These Enterprise Networks workspaces are accessed by right-clicking theEnterprise_Networks folder of the Enterprise Networks physical Navigator view, as shown in Figure 2.

The Enterprise Networks workspaces require that an administrator has assigned the Tivoli EnterprisePortal user access to the Enterprise Networks navigator view from the Navigator Views tab of theAdminister Users dialog for Tivoli Enterprise Portal.

New Enterprise Networks view and new Tivoli Enterprise Portal workspaces

In version 5.1.0, enterprise views were introduced to IBM Tivoli OMEGAMON XE for MainframeNetworks users in the new enhanced 3270 user interface. In version 5.1.1, these enterprise views aremade available to users who prefer Tivoli Enterprise Portal using the new set of Enterprise Networksworkspaces, an addition to the existing Navigator physical view.

The Enterprise_Networks Navigator View was created to simplify the monitoring of z/OS networks.Many of these workspaces were created from user experiences to identify and resolve specific networkissues. This view provides a cross-LPAR, real-time view of the z/OS Communications Server networkfocused on specific application and networking issues. This set of workspaces moves away fromLPAR-scope views to enterprise-wide views. These new workspaces eliminate many of the mouse clickspreviously required to get to key issues, dramatically improving system availability with faster problemresolution through built-in problem solving scenarios. They also facilitate new enterprise-wide searchesbased on characteristics such as System ID, application name, IP address, FTP user ID, or data set name.These new workspaces and the views that they include are summarized in Table 2 on page 11.

Figure 2. The Enterprise Networks view in the OMEGAMON XE for Mainframe Networks Tivoli Enterprise PortalNavigator


Table 2. New workspaces displayed in Tivoli Enterprise Portal

Workspace name Description

Enterprise Applications Health workspace Displays a summary of applications, applications with percentout-of-order segments >=5% or total out-of-order segments>=15%, applications with connections in backlog >= 10 ORtotal backlog connections rejected > 10, and applications withpercent segments retransmitted > 3% OR total segmentsretransmitted > 10 for applications throughout yourenterprise. This workspace also displays 3 Top 5 applicationbar charts for total backlog connections rejected, totalsegments retransmitted, and total out-of-order segments.

Enterprise Connections Find workspace Displays performance metrics for connections matchingsearch criteria specified by the end user.

Enterprise Connections Health workspace Displays connections with time since last activity greater than10 minutes, connections with connection state not equal to theestablished state, and connections with inbound or outboundbytes buffered throughout your enterprise.

Enterprise EE Connections Overview workspace Displays performance data for Enterprise Extender (EE) linksacross the enterprise when the IP address for one end of anEE link is located on a monitored z/OS system image.

Enterprise FTP Sessions Find workspace Displays performance metrics for all FTP sessions matchingsearch criteria specified by the end user. All active orcomplete FTP sessions captured within the configured FTPdisplay interval that match the search criteria are displayed

Enterprise FTP Sessions Overview workspace Displays all FTP sessions that were completed or becameactive within the display interval across the enterprise. Activesessions that were established or closed prior to the displayinterval are not displayed.

Enterprise FTP Transfers Find Displays performance metrics for all FTP transfers matchingsearch criteria specified by the end user. All active orcompleted FTP transfers captured within the configured FTPdisplay interval that match the search criteria are displayed.

Enterprise HiperSockets Interfaces Overview Displays errors, statistics, configuration and status data for allHiperSockets™ interfaces across the enterprise

Enterprise HPR Connections Overview Displays performance data for High-Performance Routing(HPR) Rapid Transfer Protocol (RTP) connections (pipes)when one endpoint of an HPR connection is located on amonitored z/OS system image.

Enterprise Interfaces Overview Displays errors, statistics, configuration and status data for allinterfaces across the enterprise.

Enterprise OMEGAMON for Mainframe NetworksHealth

Displays configuration and status information forOMEGAMON XE for Mainframe Networks monitoring agentsacross the enterprise.

Enterprise OSA Express Channels Displays a channel summary for all OSA channels in yourenterprise.

Enterprise OSA Express Ports workspace Displays summary information for all OSA-Express3 ports,OSA-Express2 10 Gigabit ports, OSA-Express 4s, andOSA-Express ports across your enterprise

Enterprise OSA Interfaces Overview workspace Displays errors, statistics, configuration and status data for allOSA interfaces across the enterprise.


Table 2. New workspaces displayed in Tivoli Enterprise Portal (continued)


Enterprise TN3270 Find Displays performance metrics for all TN3270 serverconnections matching search criteria specified by the enduser. All TN3270 server connections captured within theconfigured TN3270 display interval that match the searchcriteria display regardless of the status of the session (Active,Completed or None).

Enterprise TN3270 Server Overview Displays the current status of all TN3270 Server ports acrossthe enterprise.

You can also access these new workspaces using the Enterprise Networks Navigation view found inevery Enterprise_Networks workspace.

The Enterprise Networks Navigation view is a scrollable list of workspaces available from theEnterprise_Networks view. This view also includes Enterprise-level Find workspaces used to locategroups of like resources. The Enterprise Networks Navigation view is found in every Enterpriseworkspace immediately adjacent to the Navigator. This view is shown in Figure 3:

To access one of the Enterprise Networks workspaces from the Enterprise Networks Navigation view, dothe following:1. Select the Link icon in the row adjacent to the name of the workspace you want to access.2. Select the workspace.

If you select a Find workspace, the link filter dialog associated with the target workspace is displayedthat allows you to create an enterprise-wide search based on characteristics such as System ID,application name, IP address, FTP user ID, or data set name.

Other new Tivoli Enterprise Portal workspaces

The following physical workspaces were added to the TCP/IP and VTAM workspaces in TivoliEnterprise Portal, accessed through the Enterprise Networks workspaces:v Under the Applications Navigator item:


Application Details Displays connection data, throughput data, and datagram data forthe selected application.

v Under the Connections Navigator item:

Figure 3. Enterprise Networks Navigation view



TCP Connection Details Displays status and response time, retransmissions andout-of-order segments, statistics, window size, configuration,security, and TN3270 information for the selected connection.

v Under the EE Navigator item:


EE Connection Summary Displays performance data for a selected Enterprise Extender (EE)connection.

v Under the HPR Navigator item:


HPR Connection Details Displays performance data for a selected High-PerformanceRouting (HPR) Rapid Transfer Protocol (RTP) connection (pipe).

v Under the FTP Navigator item:


FTP Session Details Displays IP addresses and ports, application name, user IDs, andsessions for the selected FTP session.

FTP Transfer Details Displays detailed information for the selected FTP transferincluding IP addresses, ports, transmission details, user IDs,commands, dataset, security, and connection attributes

FTP Transfers for Session Displays all FTP transfers that were completed or became activewithin the display interval for a selected FTP session

v Under the TN3270 Navigator item:


Active TN3270 Server Connections for SelectedPort

Displays the current status of all active TN3270 Serverconnections on a given system, TCP/IP stack name and port. Theworkspace displays both active TN3270 server sessions and activeTN3270 server sessionless connections (V5101)

New enhanced 3270 user interface workspaces

The following workspaces were added to the enhanced 3270 user interface.

Table 3. New workspaces displayed in the enhanced 3270 user interface

Workspace Panel ID Description

CSM Storage by Owner Summaryworkspace

KN3CSOS Displays the following for a selected system:v Communications Storage Manager (CSM) storage by ownerv CSM storage allocated by poolv CSM storage

EE Connection Summary forEE_PU_NAME workspace

KN3EEDS Displays the following performance data for the selectedEnterprise Extender (EE) link:v Enterprise Extender Connection Detailsv HPR Connections Summary

Enterprise Active FTP TransfersOverview workspace

KN3FTPO Displays all FTP transfers that became active within the displayinterval across the enterprise. Active transfers that were initiatedbefore the display interval are not displayed.


Table 3. New workspaces displayed in the enhanced 3270 user interface (continued)


Enterprise EE and HPRConnections Health workspace

KN3EECO2 Displays Enterprise Extender (EE) and High PerformanceRouting (HPR) connections throughout your enterprise that meetthe following criteria:v EE connections with high percent packets retransmittedv HPR connections with ARB mode = yellow or redv HPR connections experiencing path switchesv HPR connections with high unacknowledged buffersv HPR connections with high out of sequence buffersv HPR connections with long routesv HPR connections with actual < initial throughput rate

Enterprise EE and HPRConnections Health workspace

KN3EECO Displays performance data for EE connections throughout yourenterprise.

Enterprise FTP SessionsOverview workspace

KN3FSEO Displays the following for all FTP Sessions that were completedor became active within the display interval across the enterprise.Active sessions that were established prior to the display intervalare not displayed.v FTP sessions summaryv FTP login failures summaryv FTP session failures summary

Enterprise HiperSocket InterfacesOverview workspace

KN3IFSO2 Displays the following information for HiperSocket interfacesthroughout your enterprise:v HiperSocket interface statisticsv HiperSocket interface statusv HiperSocket interface write queue statisticsv HiperSocket interface read queue statistics

Enterprise HPR ConnectionsOverview workspace

KN3HPRO Displays performance data for High-Performance Routing (HPR)Rapid Transfer Protocol (RTP) connections (pipes) when oneendpoint of an HPR connection is located on a monitored z/OSsystem image.

FTP Session Details workspace KN3FSED Displays the following data for the selected FTP session:v IP Addresses and portsv Application name and user IDv Sessionv Securityv TCP connections

FTP Transfers by Session forApplication_Name workspace

KN3FTPS Displays all FTP transfers that were completed or became activewithin the display interval for a selected FTP session. Activetransfers that were initiated before the display interval are notincluded.

FTP Transfer Details workspace KN3FTPD Displays the following for the selected FTP transfer:v IP Addresses and Portsv Transmissionv User ID and Commandv Datasetv Securityv Transfer TCP Connectionv Session TCP Connection


Table 3. New workspaces displayed in the enhanced 3270 user interface (continued)


HPR Connection Detailsworkspace

KN3HPRD Displays the following detailed statistics about the HPRconnections in your enterprise:v ARB, Throughput, and Response Timev Retransmissions, Out of Sequence, and Unacknowledgedv Path Switches, Sessions, and Linksv SNA Linksv Bytes and Packets Statisticsv Configuration

The name of the KN3START workspace has been changed from Enterprise Applications Health toEnterprise Network Health.

New attributes and attributes groups

Table 4. New attributes and attribute values

Attributegroup Table prefix New or changed information

EEConnections

KN3EEC The following attributes were added.v Bytes Received. The old version of this attribute was deprecated.v Bytes Sent. The old version of this attribute was deprecated.v VTAM STC Name

Additionally, the following attributes are now deprecated:v Bytes Received (in GB)v Bytes Sent (in GB)

EEConnectionsDetails

KN3EED The following attributes were added.

v Bytes Received. The old version of this attribute was deprecated.

v Bytes Sent. The old version of this attribute was deprecated.


FTP Sessions KN3FSE The following attributes were added.v Cipher Specificationv Local Port. The old version of this attribute was deprecated.v Login Methodv Remote Port. The old version of this attribute was deprecated.v Security Mechanismv Security Protocol Levelv Session Protection Levelv Total Bytes Transferredv Total Files Transferredv Transfer Protection Level

Enumerated values 9 (Certificate not valid) and 10 (Client name does not match username) were also added to the Login Failure Reason Description , and enumeratedvalue 0 (Normal session end) was added to Session End Reason Description.


Table 4. New attributes and attribute values (continued)


HPRConnections

KN3HPR The following new attribute was added:v VTAM STC Name

The following attributes were updated from 32-bit integers to 64-bit integers (longlong integers).

v Bytes Received. The old version of this attribute was deprecated.

v Bytes Sent. The old version of this attribute was deprecated.


KN3 CSMStorage byOwner

KN3CSO This is a new attribute group. Use the CSM Storage by Owner attributes to createsituations that monitor applications that are using Communications Storage Manager(CSM) buffer pools shared between VTAM and TCP/IP. This attribute group containsthe following attributes:v Application Name.v ASIDv Average Storage in Use Across DSP Poolsv Average Storage in Use Across ECSA Poolsv Average Storage in Use Across Poolsv Collection Timev DSP4K Pool Storage In Usev DSP16K Pool Storage In Usev DSP32K Pool Storage In Usev DSP60K Pool Storage In Usev DSP180K Pool Storage In Usev ECSA4K Pool Storage In Usev ECSA16K Pool Storage In Usev ECSA32K Pool Storage In Usev ECSA60K Pool Storage In Usev ECSA180K Pool Storage In Usev Origin Nodev Percent DSP Storage In Usev Percent ECSA Storage In Usev Storage In Use Across Poolsv Storage In Use Across DSP Poolsv Storage In Use Across ECSA Poolsv System IDv VTAM STC Name

OSAExpress®

Ports

KN3TPO The zOS Release attribute has been designated IBM internal use only.

OSA-Express3PortsSummary

KN3THS The zOS Release attribute has been designated IBM internal use only.

OSA 10Gigabit PortsSummary

KN3TTS The zOS Release attribute has been designated IBM internal use only.

TCP Listener KN3TCL The following attribute was updated from a two-byte integers to four-byte integer.

v Local Port. The old version of this attribute was deprecated.




TCPIPAddressSpace

KN3TAS The following attributes were added:

v Input Packets. This attribute replaces the earlier attributes representing the samevalue, Input Packet Count, which are now deprecated.

v Output Packets. This attribute replaces the earlier attributes representing the samevalue, Output Packet Count, which are now deprecated.

v TCP Input Segments. This attribute replaces the earlier attribute representing thesame value, TCP Input Segment Count, which are now deprecated.

v TCP Output Segments. This attribute replaces the earlier attributes representing thesame value, TCP Output Segment Count, which are now deprecated.

v UDP Input Datagrams. This attribute replaces the earlier attributes representing thesame value, UDP Input Datagram Count, which are now deprecated.

v UDP Output Datagrams. This attribute replaces the earlier attributes representingthe same value, UDP Output Datagram Count, which are now deprecated.

The following additional attributes are now deprecated:v Input Packet Countv Input Packet Count (in G)v Output Packet Countv Output Packet Count (in G)v TCP Input Segment Countv TCP Input Segment Count (in G)v TCP Output Segment Countv TCP Output Segment Count (in G)v UDP Input Datagram Count,v UDP Input Datagram Count (in G)v UDP Output Datagram Count,v UDP Output Datagram Count (in G)v UDP Total Datagrams Received (in G)

The zOS Release attribute has been designated IBM internal use only.

TCPIPApplications

KN3TAP The following attributes were updated from 32-bit integers to 64-bit integers (longlong integers).

v Total Bytes. The old version of this attribute was deprecated.

v Total Bytes Received. The old version of this attribute was deprecated.

v Total Bytes Sent. The old version of this attribute was deprecated.

Additionally, the following attributes are now deprecated:v Total Bytes (in GB)v Total Bytes Received (in GB)v Total Bytes Sent (in GB)

TCPIPDetails

KN3TCP The following attribute was added:v Agent STC Name

The following attribute was updated from a two-byte integer to four-byte integer.

v Local Port. The old version of this attribute was deprecated.

v Remote Port. The old version of this attribute was deprecated.




TCPIP FTP KN3FTP The following attributes were added.

v Application Name

v Bytes Transferred. This attribute replaces the earlier attributes representing thesame value, Bytes Transmitted and Bytes Transmitted (in GB), which are nowdeprecated.

v Cipher Specification

v Local Port. This attribute replaces the earlier attribute representing the same value,Local IP Port, a two-byte integer, which is now deprecated.

v Login Method

v Remote Port. This attribute replaces the earlier attribute representing the samevalue, Remote IP Port, a two-byte integer, which is now deprecated.

v Security Mechanism

v Security Protocol Level

v Session Protection Level

v Transfer Protection Level

The following attributes were updated to enable the advanced situation option,Display Item, on FTP transfers:v Application Namev Client User IDv Last Reply to Client Descriptionv User ID on Server Extended

Additionally, the following attributes are now deprecated:v Bytes Transmittedv Bytes Transmitted (in GB)v Local IP Portv Remote IP Port

TN3270Server SessAvail

KN3TNA The following attributes were updated from 32-bit integers to 64-bit integers (longlong integers).

v Total Bytes. The old version of this attribute was deprecated.

v Total Bytes Received. The old version of this attribute was deprecated.

v Total Bytes Sent. The old version of this attribute was deprecated.

Additionally, the following attributes are now deprecated:v Total Bytes (in GB)v Total Bytes Received (in GB)v Total Bytes Sent (in GB)




TCPIP StackLayer

KN3TSL The following attributes were updated from 32-bit integers to 64-bit integers (longlong integers).

v Input Packet Count. The old version of this attribute was deprecated.

v Output Packet Count. The old version of this attribute was deprecated.

v TCP Input Segment Count. The old version of this attribute was deprecated.

v TCP Output Segment Count. The old version of this attribute was deprecated.

v UDP Input Datagram Count. The old version of this attribute was deprecated.

v UDP Output Datagram Count. The old version of this attribute was deprecated.

v UDP Total Datagrams Received. The old version of this attribute was deprecated.

Additionally, the following attributes are now deprecated:v Input Packet Count (in G)v Output Packet Count (in G)v TCP Input Segment Count (in G)v TCP Output Segment Count (in G)v UDP Input Datagram Count (in G)v UDP Output Datagram Count (in G)v UDP Total Datagrams Received (in G)

Interface Status is now the default for the Interfaces Navigator item

The Interfaces workspace is no longer the default when you select the Interfaces Navigator item. The newdefault workspace is Interface Status. This change was made because beginning at z/OSV1.12, z/OSCommunications Server implemented callable network management interfaces (NMIs) that provideadditional metrics for Interfaces, metrics not available in earlier releases of z/OS. The Interfaces Statusworkspace and the workspaces that it links to were designed to exploit the new data available in theNMI.

New location for launching Tivoli NetView for z/OS packet trace

In addition to the workspaces from which NetView packet trace could previously be launched(Connections and Application Connections), you can now launch a packet trace from the newEnterprise_Networks Enterprise Connections Find workspace. The advantage of this new access point isthat the Enterprise Connections Find workspace allows you to specify search criteria to quickly identifythe connection whose packets you are about to trace.

Configuration changes

In Version 5.1.0 and earlier, the default value for the LIMIT extended (X) parameter in the sampleKN3SYSIN and KONSYSIN files was 23. That default value has been increased to 24. You see this changereflected in the default values for the KN3_X_AGENT_STORAGE_LIMIT_EXTEND parameter and in the updateddefaults for the sample KN3SYSIN file.

If you are monitoring a large number of a resources, such as TN3270 sessions, you might want to increasethe value for LIMIT to a number greater than 24.

Tivoli Enterprise Monitoring Server also has a parameter for setting the LIMIT value(KDS_TEMS_STORAGE_LIMIT_EXTEND). If the monitoring agent is configured in the TEMS addressspace, the TEMS value applies to both the TEMS and the monitoring agent, and the monitoring agentdoes not have its own value. If the monitoring agent is configured stand-alone, then the monitoring agentvalue for each parameter overrides the TME:Engine value, and the TEMS value has no effect on the


monitoring agent. If the TEMS value can override the monitoring agent value in your environment, youwill need to increase the LIMIT value for KDS_TEMS_STORAGE_LIMIT_EXTEND parameter as well.

New serviceability message and troubleshooting added

A new serviceability message, KN3CT059, and a new troubleshooting scenario related to this messagewere added. New messages KN3CT040 and KONCT040 were also added

Leading zeros problem in PARMGEN-generated KN3SNMP

PARMGEN discovers the IP address for a TCP/IP image and puts this address in the member pointed toby the PARMGEN profile parameter KN3_SNMP_CONFIG_FILE. When PARMGEN adds the IP address, theaddress is padded with leading zeros. This may prevent the SNMP Manager from connecting properly tothe SNMP Agent.

To address this problem, if leading zeros are present, remove them from the IP address that PARMGENplaces in the member pointed to by KN3_SNMP_CONFIG_FILE. For example, if PARMGEN adds this IPaddress:009.042.057.114

Change it to the following:9.42.57.114

Or you can apply APAR OA42212, which enables the SNMP Manager to tolerate the leading zeroes.

This fix has been applied to Version 5.1.1, so neither workaround is necessary.

New common features of all OMEGAMON version 5.1.0 monitoringagents on z/OSThe following sections describe new features of the framework, the Configuration Tool, or the productitself that affect deployment and configuration of the monitoring agent. If you are already using TivoliManagement Services components at V6.2.3 or later, you might already be familiar with some of thechanges described here. The following topics are covered:v “Configuration methods,” including PARMGEN and the Configuration Toolv “Tivoli Management Services” on page 21 enhancements, including the self-describing agent feature,

the high availability hub, autonomous agents, and automatic registration of products with the localmonitoring server

v “New shared publications” on page 23v “New OMEGAMON XE for Mainframe Networks publication” on page 23

Configuration methods

The following configuration methods affect deployment and configuration:v PARMGEN configuration method

The PARMGEN configuration method uses a runtime-environment-based approach to configuration.With PARMGEN, you edit a comprehensive list of parameters to configure all the installed productsand components in a runtime environment. You then submit a series of jobs to create a completeruntime environment with the parameter values that you specified. A workflow "wrapper" leads youthrough the configuration process.The PARMGEN configuration method is the preferred configuration method and is intended to replacethe Configuration Tool (ICAT).The PARMGEN method is particularly suitable for the following types of customers:


– Existing OMEGAMON XE customers in environments in which one person is responsible forconfiguring all OMEGAMON XE products and components

– New OMEGAMON XE customers who are already accustomed to supplying z/OS parameter valuesdirectly in the SYS1.PARMLIB data set and do not want to learn a new tool.

For more information, see the following information sources:– "Configuring products with the PARMLIB method" in the IBM Tivoli OMEGAMON XE and Tivoli

Management Services on z/OS: Common Planning and Configuration Guide

– IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Parameter Reference

– IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference

– IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference

– The PARMGEN Technote at http://www.ibm.com/ support/docview.wss?uid=swg21417935.If you have been using the PARMGEN (formerly PARMLIB) configuration method previously, be awareof the following new addition. The KN3_SECURITY_ACTION_CLASS parameter was added to override theRTE_SECURITY_CLASS value specified for the runtime environment, allowing the use of a separatesecurity class to control command-level security for OMEGAMON XE for Mainframe Networksmonitoring agent Take Action commands.

v Configuration Tool

OMEGAMON XE for Mainframe Networks requires version 3 release 1 modification level 24 (version310.24) or higher of the Installation and Configuration Assistance tool, which is included in the productpackage. If you have an earlier version of the Configuration Tool on your z/OS operating system inthe same consolidated software inventory (CSI), it is automatically replaced by version 310.24 of theConfiguration Tool during installation. The IBM Tivoli OMEGAMON XE and Tivoli Management Serviceson z/OS: Common Planning and Configuration Guide extensively documents the new features of theConfiguration Tool.

Tivoli Management Services

OMEGAMON XE for Mainframe Networks supports Tivoli Management Services V6.2.3 Fix Pack 1. Thefollowing topics introduce new features that can affect deployment and configuration. If you are alreadyusing Tivoli Management Services components at V6.2.3 or later, you might already be familiar withsome of the features. For detailed descriptions of all the new features in Tivoli Management ServicesV6.2.3 Fix Pack 1, see IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide.

The following new features might affect deployment and configuration:v High-availability hub

You can now configure a high-availability hub monitoring server in any sysplex environment withdynamic virtual IP addressing (DVIPA) and shared DASD. A high-availability hub is configured in itsown runtime environment, without any monitoring agents, and can be configured on the same LPARwith a remote monitoring server. This configuration enables the hub monitoring server to be relocatedto any suitable LPAR in the sysplex with no changes, and with minimal disruption to the componentsconnecting to the hub.For information about configuring a high-availability hub on the z/OS operating system, andconversion from a static hub to a high-availability hub, see IBM Tivoli Management Services on z/OS:Configuring the Tivoli Enterprise Monitoring Server on z/OS. For an example scenario on configuring thehigh availability hub, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:PARMGEN Reference.

v Self-describing agent

Monitoring agents have been enhanced with a self-description capability that automatically distributeseach agent's operating configuration directly to the local monitoring server. The server then distributesthose agent configuration files first to the hub monitoring server (if necessary) and then to the variousIBM Tivoli Monitoring components that require it.


Before IBM Tivoli Monitoring V6.2.3, before an agent could connect to a Tivoli Enterprise MonitoringServer, you were required to manually update the monitoring server, as well as other TivoliManagement Services components such as the Tivoli Enterprise Portal Server and the Tivoli DataWarehouse, with information necessary for it to recognize and process data that is sent by that agent.As of V6.2.3, this "seeding" step (as it was once known) becomes unnecessary.By default, the self-describing capability is disabled on hub monitoring servers. Enabling theself-describing capability of monitoring agents ensures that the proper level of application data isinstalled on monitoring servers and the Tivoli Enterprise Portal. If the self description feature isactivated, runtime verification checks for updated application data. If inconsistent conditions aredetected, application data is propagated from the agent to the various monitoring servers, which areautomatically updated without the hub monitoring server having to be recycled.If you intend to enable the self describing features and a z/OS hub monitoring server, you shouldconfigure a high availability hub. For more information, see IBM Tivoli Monitoring: Configuring the TivoliEnterprise Monitoring Server on z/OS.When you run your hub server on a distributed platform before connecting your OMEGAMON XE forMainframe Networks agent and before you install your OMEGAMON XE for Mainframe Networksagent, you must ensure you have installed IBM Tivoli Monitoring V6.2.3 Fix Pack 1.The OMEGAMON XE for Mainframe Networks agent is installed with self-describing support enabled.Once self-description is enabled at the hub Tivoli Enterprise Monitoring Server that the agent isreporting to, the application support file updates are automatically synchronized, and, if relevant, theupdates are deployed to the Tivoli Enterprise Monitoring Server and the connected Tivoli EnterprisePortal Server.The following OMEGAMON XE for Mainframe Networks agent TMS:Engine parameter valuesincreased in order to support self-describing processing:LIMIT(23,X)MINIMUM(768000,X)

These parameters are generated in the RKANPARU library of the KN3SYSIN member.v Autonomous agents

You can choose to configure stand-alone monitoring agents to run in autonomous mode (withoutcommunicating directly with a monitoring server). When running autonomously, a monitoring agentcan retain event information when communications with its monitoring server are interrupted. Theagent can run private situations that generate events that can be sent to a Netcool/OMNIbusObjectServer as EIF events or as SNMP alerts, and can collect private history in local short-term storageof the monitoring agent for private situations.An autonomous agent requires the DSEVT DDNAME in the monitoring agent started task in the&rhilev.&rte.RKANSAMU data set. This DDNAME points to the &rhilev.&rte.RKDSEVT data set.The IBM Tivoli Monitoring: Installation and Setup Guide provides instructions for configuringNetcool/OMNIbus ObjectServers to receive the events. For information on specifying which situationevents to forward, see the Tivoli Enterprise Portal online help and the IBM Tivoli Monitoring: TivoliEnterprise Portal User's Guide. For information about parameters to set for an autonomous agent, andabout defining private situations, private history, and SNMP alerts for private situations, see the "Agentautonomy" chapter of the IBM Tivoli Monitoring: Administrator's Guide.You can add these parameters for an autonomous agent on a z/OS system by editing the Kpp$PENVmember of the PARMGEN WCONFIG library or by using the Specify Nonstandard Parameters panelin the Configuration Tool. See the “Adding, changing, or deleting a parameter in a runtime member”in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning andConfiguration Guide for more information. For instructions on enabling SNMP V3 passwords forautonomous agents, see the “Enabling SNMP V3 passwords for autonomous agents” topic in the IBMTivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.

v Automatic registration of products with the local monitoring server


The runtime environment load processing option now automatically copies the product attribute andcatalog members from the &thilev.TKANDATV target data set that was installed by SMP/E to theruntime environment &rhilev.&rte.RKANDATV library. If you apply maintenance that updates theproduct attribute and catalog members only, you do not have to regenerate and rerun the "Registerwith local TEMS" job for each product in the runtime environment. Instead, you can just reload theruntime environment to refresh the members.

New shared publications

The following new publications have been added to the OMEGAMON XE for Mainframe Networkslibrary, available in the Shared documents part of the information center:v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Enhanced 3270 Interface User’s

Guide: provides a brief overview of the new 3270 workspaces and scenarios provided under the new3270 interface.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference: describes theuse of the PARMGEN tool for the initial deployment and configuration of Tivoli Management Serviceson z/OS components such as the Tivoli Enterprise Monitoring Server and the Tivoli Enterprisemonitoring agents on z/OS.

New OMEGAMON XE for Mainframe Networks publication

The following new publication for this monitoring agent has been added to the OMEGAMON XE forMainframe Networks library:v IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User Interface Guide: provides a brief

overview of the new 3270 workspaces and scenarios provided under the new 3270 interface.

New function added since Version 4.2.0 Fix Pack 3The following changes were introduced to OMEGAMON XE for Mainframe Networks after Version 4.2.0Fix Pack 3.

OMEGAMON XE for Mainframe Networks data available from the enhanced 3270user interface

OMEGAMON XE for Mainframe Networks now supports the IBM Tivoli OMEGAMON enhanced 3270user interface.

The enhanced 3270 user interface is the latest generation of 3270-based user interfaces for theOMEGAMON monitoring products. When you use the enhanced 3270 user interface in conjunction withOMEGAMON XE monitoring agents and the Tivoli Enterprise Monitoring Server, you can monitor theperformance of the z/OS systems, applications, and devices in your environment and helps you identifyand troubleshoot problems with those monitored resources.

The enhanced interface offers the following features:v Enterprise-wide and single-system views of datav Autodiscovery of and autoconnection to data sourcesv Customizable workspacesv Support for screen sizes up to 62 x 160v Dynamic behavior and operationv Take Action commandsv SAF-based security for logon, data access, and Take Action commands

New attributes and attribute values

This section lists new and changed attributes since OMEGAMON XE for Mainframe Networks v4.2.0 FixPack 3.


Table 5. New attributes and attribute values

Attribute group Table prefix New or changed information

FTP Sessions KN3FSE The following attribute, which expresses time spans as the seconds, centiseconds,or milliseconds since an event took place, was updated to report time spans in amore consumable format. The unit for expressing this value is now dynamic,meaning that it is reported in the most appropriate format (milliseconds, seconds,minutes, hours, or even days) depending on how long the operation takes.

Session DurationThe duration of the session.

KN3 InterfaceStatistics

KN3IFS The following attributes were added:

Bytes Received or TransmittedThe number of bytes sent and received during the most recent samplinginterval. The format is an unsigned long long integer.

Total Bytes Received or TransmittedThe number of bytes sent and received during the most recent samplinginterval. The format is an unsigned long long integer.

These attributes are not currently in the product-provided Tivoli Enterprise Portalworkspaces. They can be added to any user-customizable workspace.

OSA 10 GigabitPorts Errors

KN3TTE The following attribute was added:

Interface IndexThe interface index associated with this port. The format is a four-byteinteger.

This attribute is not currently in the product-provided Tivoli Enterprise Portalworkspaces. It can be added to any user-customizable workspace.

OSA ExpressChannels

KN3TCH The following attributes were updated with new valid values, as indicated in bold.

Channel Hardware LevelThe hardware model of the channel. This value is stored as an integer butdisplayed as a string. The possible values are:v 0 = unavailable: This value indicates that the hardware level of the

channel is unavailable.v 1 = unknown: This value indicates that the hardware level is unknown.v 2 = osaExp150: This value indicates a hardware level of 1.50, which

defines this feature as OSA-Express.v 3= osaExp175: This value indicates a hardware level of 1.75, which

defines this feature as OSA-Express.v 4 = osaExp300: This value indicates a hardware level of 3.00, which

defines this feature as OSA-Express2.v 5 = osaExp400: This value indicates a hardware level of 4.00, which

defines this feature as OSA-Express3.v 6 = osaExp500: This value indicates a hardware level of 5.00, which

defines this feature as OSA-Express4S.

Channel TypeThe type of channel for this interface. This value is stored as an integerbut displayed as a string. The possible values are:v 16 = OSAExpressv 17 = OSADirectExpressv 48 = osaIntraensembleDatav 49 = osaIntraensembleManage




OSA Express3Ports Errors

KN3THE The following attribute was added:

Interface IndexThe interface index associated with this port. The format is a four-byteinteger.


TCP Listener KN3TCL The following attribute was added. This attribute is in addition to the a two-byteinteger version of the same attribute.

Local PortThe local port for this connection. The format is a four-byte integer.


The following new attribute was added:

Listener TypeIndicates whether this listener is for a TN3270 server. A value of x’01’indicates that the listener is for a TN3270 Server. The format is anunsigned integer. The following are valid values:

v 0 = Unknown

v 1 = TN3270_ServerThis attribute is not currently in the product-provided Tivoli Enterprise Portalworkspaces. It can be added to any user-customizable workspace.

The following attribute, which expresses time spans as the seconds, centiseconds,or milliseconds since an event took place, was updated to report time spans in amore consumable format. The unit for expressing this value is now dynamic,meaning that it is reported in the most appropriate format (milliseconds, seconds,minutes, hours, or even days) depending on how long the operation takes.

Idle TimeThe amount of time that the server has been idle since the most recentconnection was accepted.





TCPIP AddressSpace

KN3TAS The following new attribute was added:

Telnet Session CountThe number of Telnet connections that are currently in session with anapplication. The format is an integer.

This attribute is displayed in the Address Space workspace, the TN3270workspaces, and the TCP/IP Summary and Summary History workspaces.

The zOS Release attribute was updated to accommodate the latest version of z/OS,as indicated in bold.

zOS ReleaseThe version and release level of z/OS on which this monitoring agent isrunning. This value is stored as an integer and displayed as a string. Thefollowing values are valid:v 0 = blankv 1 = zOS_1.8v 2 = zOS_1.9v 3 = zOS_1.10v 4 = zOS_1.11v 5 = zOS_1.12v 6 = zOS_1.13




TCPIPApplications

KN3TAP The following attributes were updated from 32-bit integers to 64-bit integers (longlong integers).

Byte RateThe number of bytes per minute transmitted to or sent from thisapplication during the most recent time interval. The format is a long longinteger.

The old version of this attribute was deprecated and has "_32" appendedto its name.

Bytes ReceivedThe number of bytes received on all connections for this application thatexisted at the end of the most recent time interval. The format is a longlong integer.


Bytes SentThe number of bytes sent on all connections for this application thatexisted at the end of the most recent time interval. The format is a longlong integer.


Bytes Sent or ReceivedThe number of bytes sent or received on all connections for thisapplication that existed at the end of the most recent time interval. Theformat is a long long integer.


Receive Byte RateThe number of bytes that was received, per minute, during the mostrecent time interval. The format is a long long integer.


Transmit Byte RateThe number of bytes that was transmitted, per minute, during the mostrecent time interval. The format is a long long integer.





TCPIPApplications(continued)

KN3TAP The following attributes were added. The existing versions of these attributes weredisplayed as bytes in Tivoli Enterprise Portal. The new versions are displayed sinthe most significant unit to better accommodate the column width in the enhanced3270 user interface.

Total BytesThe total number of bytes sent or received on all connections for thisapplication that existed at the end of the most recent time interval. Theformat is a long long integer.

Total Bytes ReceivedThe total number of bytes received on all connections for this applicationthat existed at the end of the most recent time interval. The format is aninteger.

Total Bytes SentThe total number of bytes sent on all connections for this application thatexisted at the end of the most recent time interval. The format is aninteger.


The following new attribute was added:

Application TypeIndicates whether this application is a TN3270 server. A value of x’01’indicates that the application is acting as a TN3270 Server. The format isan unsigned integer. The following are valid values:v 0 = Unknownv 1 = TN3270_Server

The following attribute, which expresses time spans as the seconds, centiseconds,or milliseconds since an event took place, was updated to report time spans in amore consumable format. The unit for expressing this value is now dynamic,meaning that it is reported in the most appropriate format (milliseconds, seconds,minutes, hours, or even days), depending on how long the operation takes.

Time Since Last ActivityThe average time since the most recent activity on all connections for thisapplication that existed at the end of the most recent time interval.

TCPIPConnections

KN3TCN The following attribute that expresses time spans as the seconds, centiseconds, ormilliseconds since an event took place was updated to report time spans in a moreconsumable format. The unit for expressing these values is now dynamic, meaningthat it is reported in the most appropriate format (milliseconds, seconds, minutes,hours, or even days) depending on how long the operation takes.

Time Since Last ActivityThe time since the most recent activity on this connection.




TCPIP Details KN3TCP The following attributes, which express time spans as the seconds, centiseconds, ormilliseconds since an event took place, were updated to report time spans in amore consumable format. The unit for expressing these values is now dynamic,meaning that the values are reported in the most appropriate format (milliseconds,seconds, minutes, hours, or even days) depending on how long the operationtakes.

Connection DurationThe amount of time since this connection was created.

Time Since Last ActivityThe time since the most recent activity on this connection.

The following attribute was added. This is in addition to the a two-byte integerversion of the same attribute.

Local PortThe local port for this connection. The format is a four-byte integer.


The zOS Release attribute was updated to accommodate the latest version of z/OS,as indicated in bold.

zOS ReleaseThe version and release level of z/OS on which this monitoring agent isrunning. This value is stored as an integer and displayed as a string. Thefollowing values are valid:

v 0 = blank

v 1 = zOS_1.8

v 2 = zOS_1.9

v 3 = zOS_1.10

v 4 = zOS_1.11

v 5 = zOS_1.12

v 6 = zOS_1.13

TCPIP FTP KN3FTP The following attribute, which expresses time spans as the seconds, centiseconds,or milliseconds since an event took place, was updated to report time spans in amore consumable format. The unit for expressing these values is now dynamic,meaning that it is reported in the most appropriate format (milliseconds, seconds,minutes, hours, or even days) depending on how long the operation takes.

File Transmission DurationThe amount of time required for the transfer or command to becompleted.




TCPIPGateways

KN3TGA The following attribute was updated to add a new valid value, as indicated inbold:

Route TypeThe type of route used by this gateway. This value is stored as an integerand displayed as a string. Valid values are:v 0 = (blank)v 1 = Otherv 2 = Staticv 4 = ICMPv 8 = RIPv 13 = OSPFv 129 = Router Advertisementv 130 = Replaceable Static

TCPIP StackLayer

KN3TSL The following attributes were added. The existing versions of these attributes weredisplayed as bytes in Tivoli Enterprise Portal. The new versions are displayed as inthe most significant unit to better accommodate the column width in the enhanced3270 user interface.

Input Packet CountThe number of IP segments that this TCP/IP address space received fromthe network since TCP/IP initialization. The format is a long long integer.

Output Packet CountThe number of IP segments that this TCP/IP address space sent to thenetwork since TCP/IP initialization. The format is a long long integer.

TCP Input Segment CountThe count of TCP segments that this TCP/IP address space received fromthe network since TCP/IP initialization. The format is a long long integer.

TCP Output Segment CountThe count of TCP segments that this TCP/IP address space delivered tothe network since TCP/IP initialization. The format is a long long integer.

UDP Input Datagram CountThe number of UDP datagrams received since TCP/IP initialization. Theformat is a long long integer.

UDP Output Datagram CountThe number of datagrams this host sent since TCP/IP initialization. Theformat is a long long integer.


The following new attribute was added.

UDP Total Datagram CountThe total number of UDP datagrams received, including those with errors,since TCP/IP initialization. The format is a long long integer.





TCPIPSummary

KN3TCP The zOS Release attribute was updated to accommodate the latest version of z/OS,as indicated in bold.

zOS ReleaseThe version and release level of z/OS on which this monitoring agent isrunning. This value is stored as an integer and displayed as a string. Thefollowing values are valid:v 0 = blankv 1 = zOS_1.8v 2 = zOS_1.9v 3 = zOS_1.10v 4 = zOS_1.11v 5 = zOS_1.12v 6 = zOS_1.13




TN3270 ServerSess Avail

KN3TNA The following attributes were updated to add the information shown in bold.

Session TypeThe session type. While a TN3270 session is active, the Session Typeattribute always displays as Unknown if the session is not monitored bymeans of a MONITORGROUP definition. At session termination, moregranular descriptions of the SSL status are available and the SECUREsession's status will be updated to reflect the session's status. This valueis stored as an integer and displayed as a string. Valid values are:v 0 = Unknownv 1 = TN3270v 2 = TN3270Ev 3 = Linemodev 4 = DBCSTransformv 5 = Binary

SSL StatusThe Secure Sockets Layer (SSL) status for the session. This value is storedas an integer and displayed as a string. While a TN3270 session is active,the SSL status will show as either SECURE, NON_SSL, or Unknown. TheSECURE and NON_SSL statuses are only available if the session ismonitored by means of a MONITORGROUP definition. At sessiontermination, more granular descriptions of the SSL status are available andthe SECURE session's status will be updated to reflect the session's status.The valid values are:v 0 = NON_SSLv 1 = SERVER_AUTHv 2 = NO_SAFv 3 = SAFv 9 = Unknownv 128 = SECURE. This is an interim state that can be displayed while a

session or connection is active. The session termination recordupdates the row with more granular security information when thesession or connection ends.

The following attributes were added. The existing versions of these attributes weredisplayed as bytes in Tivoli Enterprise Portal. The new versions are displayed as inthe most significant unit to better accommodate the column width in the enhanced3270 user interface.

Total BytesThe number of bytes sent or received by the server for this session. Theformat is a long long integer.

Total Bytes ReceivedThe number of bytes received by the server for this session. The format isa long long integer.

Total Bytes SentThe number of bytes sent by the server for this session. The format is along long integer.





TN3270 ServerSess Avail(continued)

KN3TNA The following attributes, which express time spans as the seconds, centiseconds, ormilliseconds since an event took place, were updated to report time spans in amore consumable format. The unit for expressing these values is now dynamic,meaning that it is reported in the most appropriate format (milliseconds, seconds,minutes, hours, or even days) depending on how long the operation takes.

Average IP Response TimeThe average IP response time over the last Response Times CollectionInterval.

Average SNA Response TimeThe average SNA response time over the last Response Times CollectionInterval.

Average Total Response TimeThe average total response time over the last Response Times CollectionInterval.

Updates to workspacesv The TCP/IP Address Space workspace was updated as follows:

– The existing Telnet Session Count in the Address Space Summary Table view was renamed to TelnetConnection Count.

– In the Telnet Pool Usage view, Telnet Session Count in the legend was changed to Telnet ConnectionCount.

v The TCP/IP Summary workspace was updated as follows:– In the Resource Summary view, Telnet Session Count in the legend was renamed to Telnet

Connection Count.– The existing Telnet Session Count in the TCP/IP Summary Table view was renamed to Telnet

Connection Count.v The TCP/IP Summary History workspace was updated as follows:

– The title of the Telnet Session Count view was changed to Telnet Connection Count.– The legend on the graph for the Telnet Connection Count view was changed from Telnet Session

Count to Telnet Connection Count.– The label on the Y-axis of the graph for the Telnet Connection Count view was changed from

Sessions to Connections.– The existing Telnet Session Count in the TCP/IP Summary History Table view was renamed to

Telnet Connection Count.v The TN3270 Server Sessions workspace was updated as follows:

– The existing Telnet Session Count attribute in the Active TN3270 Sessions Table view was renamedto Telnet Connection Count to reflect its actual meaning, which is all connections, including thosethat are in session with an application and those that are not in session with an application.

– A new attribute Telnet Session Count was added to the Active TN3270 Sessions Table view. Thefollowing existing links continue to be available from this table view:- TN3270 Server Session Pair- TN3270 Server Sessions for Remote IP- TN3270 Server Sessions for SNA Name

– The Active TN3270 Server Session graph view was changed to plot both the existing TelnetConnection Count and the new Telnet Session Count.


– The existing TN3270 Server Session Summary Table now displays only Telnet connections that are insession with an application, as well as completed TN3270 Server Sessions that meet the TN3270display interval criteria. The following existing links continue to be available from this table view:- TN3270 Server Session Pair- TN3270 Server Session Details- TN3270 Server Sessions for Remote IP- TN3270 Server Sessions for SNA Name- System CPU Utilization- TCP Connections

– A new table, the TN3270 Server Sessionless Connection Summary table, was added below theTN3270 Server Session Summary Table to display Telnet connections that are not in session with anapplication, and sessionless Telnet connections that completed within the TN3270 display interval.The following links are available from this table view:- TN3270 Server Sessions for Remote IP (the default link)- TN3270 Server Session Details- TCP Connections Link

v The TN3270 Server Sessions for Remote IP workspace was updated as follows:– The existing Telnet Session Count in the Active TN3270 Sessions Table view was renamed to Telnet

Connection Count.– The new attribute (Telnet Session Count) was added to the Active TN3270 Sessions Table view. The

following existing links continue to be available from this summary table:- TN3270 Server Session Pair- TN3270 Server Sessions for Remote IP- TN3270 Server Sessions for SNA Name

– The Active TN3270 Server Session graph view was changed to plot both Telnet Connection Countand the new Telnet Session Count.

v The TN3270 Server Sessions for SNA Name workspace was updated as follows:– The existing Telnet Session Count in the Active TN3270 Sessions Table view was renamed to Telnet

Connection Count and the meaning of the Telnet Session Count attribute was changed to mean "thetotal number of Telnet connections."

– The new attribute (Telnet Session Count) was added to the Active TN3270 Sessions Table view. Thefollowing existing links continue to be available:- TN3270 Server Session Pair- TN3270 Server Sessions for Remote IP- TN3270 Server Sessions for SNA Name

– The Active TN3270 Server Session graph view was changed to plot Telnet Connection Count, as wellas the new Telnet Session Count.

Take Action commands issued from the enhanced 3270 interface with SAF security

In version 4, the OMEGAMON XE for Mainframe Networks produce function was enhanced to add a setof Take Action commands. These commands were available from Tivoli Enterprise Portal and wereexecuted with the prefix N3. In V5.1.0. you can now issue these commands from the enhanced 3270interface with improved security. These commands are:v Dropv Pingv Nslookupv Tracerte


In V5.1.0, the new 3270 and existing Tivoli Enterprise Portal Take Action commands fail unless explicitsecurity definitions are configured that enable these commands to be issued. Security for this monitoringagent Take Action commands is implemented through direct System Authorization Facility (SAF) callsand is based on resource profiles. Both user ID and command are validated. These information sourcesexplain this change in behavior:v You must enable security for the enhanced 3270 user interface and implement a resource profile. See

the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning andConfiguration Guide for more information

v You can configure a common SAF security class name for OMEGAMON enhanced 3270 user interfacesecurity controls. See the IBM Tivoli OMEGAMON XE and Tivoli Management Services: Common ParameterReference for information about the RTE_SECURITY_CLASS parameter.

v You can configure the KN3_SECURITY_ACTION_CLASS to override the RTE_SECURITY_CLASS value that isspecified for the runtime environment, allowing the use of a separate security class to controlcommand-level security for OMEGAMON XE for Mainframe Networks monitoring agent Take Actioncommands. See the IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference forinformation about the KN3_SECURITY_ACTION_CLASS parameter.

v See the completing the configuration section of the IBM Tivoli OMEGAMON XE for Mainframe Networks:Planning and Configuration Guide for information about restricting access to the 3270 Command Log andResponse workspace.

v See the section on Take Action commands in the IBM Tivoli OMEGAMON XE for Mainframe Networks:Enhanced 3270 User Interface Guide for more information about the parameters associated with thesecommands when run in the enhanced 3270 user interface.

v See the appendix on product-specific Take Action commands in the IBM Tivoli OMEGAMON XE forMainframe Networks: Tivoli Enterprise Portal User’s Guide for more information about the parametersassociated with these commands when run in Tivoli Enterprise Portal.

You can use the SAF security class that is defined for the runtime environment to control access to theOMEGAMON XE for Mainframe Networks commands, or you can use a separate security class. Thesecommands will fail RACF authorization unless SAF security is configured. See the completing theconfiguration information in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning andConfiguration Guide for information about configuring SAF security for Take Action commands.

For a summary of the issues associated with configuring security on the enhanced 3270 user interface, seehttp://www.ibm.com/software/brandcatalog/ismlibrary/

Updates to attribute definitions to address the requirements of the enhanced 3270user interface

Definitions of some attributes were updated to meet the requirements of the enhanced 3270 userinterface.v Some attributes displayed in the enhanced 3270 interface are expressed by using the unit that best

meets 3270 display requirements. This characteristic also makes the value easier to understand. A longnumber that was previously displayed in bytes, for example, might now be expressed as gigabytes. Theunit is displayed with the attribute in the enhanced 3270 interface.

v Some attributes that were hidden in Tivoli Enterprise Portal are available for display in the enhanced3270 interface.

v Sometimes the date and time, usually displayed as a single value, are displayed in two separatecolumns: date and time.

v Dates are displayed differently. In Tivoli Enterprise Portal, the format is mm/dd/yy hh:mm:ss. In theenhanced 3270 interface, it is yy/mm/dd hh:mm:ss.



v Some attributes use abbreviated names in the enhanced 3270 interface to conserve space. Attributesnames are always correct in the help for the environment in which the help appears. Both the longname and the abbreviated names, when used, are shown together in the IBM Tivoli OMEGAMON XEfor Mainframe Networks: Enhanced 3270 User Guide.

v Attributes with restrictions that are imposed by versions of z/OS earlier than v1.11 have had theserestrictions removed.

v Attributes that described actions that are performed using the Configuration Tool method now also listthe PARMGEN method.

Supported versions of IBM Tivoli NetView for z/OS

If you want to use the Tivoli NetView for z/OS dynamic workspace links (DWL) feature or launch theNetView packet trace feature from the OMEGAMON XE for Mainframe Networks monitoring agent,ensure that you are running IBM Tivoli NetView for z/OS. Versions 5.4 or 6.1 are supported with APAROA32192.

New serviceability messages

Two serviceability messages were added that make it easy for you to provide build level and dates of thedata collection servers when you talk with IBM Software Support. These messages are KN3N015I for theKN3ANMON data collector and KN3CT051 for the KN3ACTCS data collector. See IBM TivoliOMEGAMON XE for Mainframe Networks: Troubleshooting for explanations of these messages.

IPv6 considerationsThese factors should be considered if you are using IPv6.

The following IPv6 changes are included in this release of the OMEGAMON XE for Mainframe Networksprogram:v When using the Configuration Tool to configure your agent, host names and IP addresses are limited

to 32 bytes.v The following OMEGAMON XE for Mainframe Networks workspaces display IPv4 addresses in place

of IPv4-mapped IPv6 addresses (for example, 129.144.52.38 will be displayed in place of::FFFF:129.144.52.38):– Connections workspaces– FTP workspaces– TN3270 workspaces– Enterprise Extender workspaces

v All other OMEGAMON XE for Mainframe Networks workspaces that display IP addresses can showIP addresses in IPv4 or IPv6 format.

Abbreviations used by the Configuration ToolIn the books that discuss configuration and in the Configuration Tool, the abbreviations shown in thefollowing table are used.

Table 6. Configuration Tool abbreviations

Abbreviation Meaning

&rtename The name of the runtime environment (RTE)

&midlev The mid-level qualifier. Used with &rhilev

&rhilev Runtime high-level qualifier (non-VSAM)

&rvhilev Runtime high-level qualifier (VSAM)


Table 6. Configuration Tool abbreviations (continued)

Abbreviation Meaning

&shilev Installation high-level qualifier of the INST* libraries

&thilev SMP/E target high-level qualifier



Chapter 2. Planning for configuration

Several variables that affect planning decisions contribute to the amount of CPU, memory, and disk spaceused by OMEGAMON XE for Mainframe Networks and the Tivoli Management Services components.

Collecting, processing, and storing data consumes system and network resources. Several variablescontribute to the amount of CPU, memory, and disk space used by OMEGAMON XE for MainframeNetworks and the OMEGAMON XE platform components. The amount of CPU, memory, and disk spaceused on each monitored system is dependent on the number of resources being monitored, how oftenperformance data is collected and whether you choose to store historical data.

This section identifies options to consider while planning the configuration and deployment of thisproduct to meet the needs of your enterprise. This chapter also provides information to consider whencreating and modifying situations and workspaces.

Additional performance information for OMEGAMON products is available at http://www-306.ibm.com/software/tivoli/features/ccr2/info.html. Additional deployment and environment designrecommendations are found in the IBM Tivoli Monitoring: Deployment Guide.

This section also provides a high-level description of planning information about security issues and theOMEGAMON II component, if you decide to configure this component. The OMEGAMON II FMID hasbeen merged with the OMEGAMON XE FMID in this release.

Additional support for planning decisions can be found in the task-oriented OMEGAMON IntegratedInformation Center, found at http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/index.jsp.

CPU usage for monitoring networks on z/OS systemsTotal CPU usage attributed to running the OMEGAMON XE for Mainframe Networks monitoring agentincludes the percentage of CPU used by the agent and the additional CPU usage associated with thefollowing activities:v Using the z/OS Communications Server network management interfaces (NMI). As a result, you will

notice a slight increase in the amount of CPU used by the TCP/IP address space.v Querying SNMP MIBs. This activity is represented by processing incurred by OSNMPD. You must start

an instance of the OSNMPD address space for each TCP/IP address spaces where OSA channels,LPARs and ports data is to be collected.

v Querying the IOASNMP or IOBSNMP subagent. The IOASNMP subagent OR the IOBSNMP subagentis required on systems where OSA channels, LPARs and ports data is to be collected. OSA-Express3and OSA-Express4s adaptors are supported only with the OSA Direct Express SNMP subagent(IOBSNMP).

v The z/OS Communication Server external I/O control (IOCTL) function calls are used to retrieveroute information when the monitoring is running in an address space on z/OS 1.10 or later. SNMPwas previously used to obtain this data. The change in data retrieval methods was made to reduceCPU utilization when a large number of routes are defined.

Note: Remember that the OMEGAMON XE for Mainframe Networks monitoring agent might not be theonly application or user querying SNMP.

Understanding how real-time data is collectedReal-time data collection allows you to monitor performance of your network and system resources in aneffort to resolve potential problems before they affect the user.


http://www-306.ibm.com/software/tivoli/features/ccr2/info.html

http://www-306.ibm.com/software/tivoli/features/ccr2/info.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v42r1/index.jsp

The OMEGAMON XE for Mainframe Networks monitoring agent is designed to collect z/OS TCP/IPand VTAM performance data. You must run the monitoring agent on each LPAR being monitored. Theagent monitors all of the TCP/IP address spaces running on the LPAR.

The monitoring agent can be used to collect several types of performance data, allowing you to monitorTCP/IP address spaces, TN3270 server sessions, High Performance Routing connections, EnterpriseExtender connections, FTP sessions and transfers, OSA adapters, TCP/IP connections, interfaces,gateways, Communication Storage Manager, VTAM buffer pools, and VTAM environment. Performancedata is collected using the z/OS Communications Server network management interface (NMI), byquerying SNMP MIBs and using the VTAM Performance Monitor Interface. The OMEGAMON XE forMainframe Networks monitoring agent is designed with performance in mind, providing an efficientmechanism for collecting large amounts of network performance data.

Total storage associated with real-time data collection, as shown in Table 7, includes the storage used inthe monitoring agent address space as well as the following dataspaces used during data collection:

Table 7. Names and sizes for data spaces used during data collection

Dataspace name Size Description

KN3ACTCS 928 MB This data space is used to store data that has been collected using SNMP,Performance Monitor Interface data, data collected using the z/OS CommunicationsServer network management interface (NMI), the z/OS Communication Serverexternal I/O control (IOCTL) function data, and Take Action command data. Thestorage area is reused each time the monitoring agent performs a collection. Theactual amount of storage used is determined by the number of resources beingmonitored.

N3TCPIP 2 GB This data space is used to store data collected using the z/OS CommunicationsServer network management interface (NMI). A maximum of 225 MB is used forVTAM data. A maximum of 225 MB for each TCP/IP address space is used forTCP/IP data. The storage area is reused each time the monitoring agent performs acollection. The actual amount of storage used is determined by the number ofresources that are being monitored.

N3FTP 2 GB This data space is used to store data collected for FTP sessions and transfers. Amaximum of 256 MB is used for each TCP/IP address space. Over time, all 256 MBis used because each new row of data is added to the existing data. When all 256MB has been used, the data space wraps and new data is written to the beginning ofthe storage area.

N3TN3270 2 GB This data space is used to store data collected for TN3270 server sessions. Amaximum of 256 MB is used for each TCP/IP address space. The actual amount ofstorage used is determined by the number of resources being monitored. One recordfor each active session and one record for each session that closed in the last 24hours is stored in the data space.

The data spaces are created when the monitoring agent initializes and are deleted when the monitoringagent is stopped. The sizes are not configurable. However, the amount of storage used is determined bythe number of TCP/IP address spaces and the types of data you configure the monitoring agent tocollect.

Determining which systems and TCP/IP address spaces to monitorAll production LPARS and TCP/IP address spaces should be monitored because they represent the coreof your business enterprise.

You might choose to collect data less frequently on some systems, especially non-production LPARs, tominimize the cost of monitoring your networks.


Since V4.2.0 and later, you can decide whether to monitor a TCP/IP address space on a per-address-spacebasis. To learn about this new feature and how to select not to monitor some TCP/IP address spaces, seeFigure 18 on page 101 in section about “Adding, changing, or updating a monitored system definition”on page 100.

Determining which types of real-time data to collectThe OMEGAMON XE for Mainframe Networks monitoring agent includes two data collectorcomponents:v The TCPC component that includes these data types:

– TCP/IP Connection and Application Performance statistics collection– Routing Table statistics collection– TN3270 server statistics collection– IPSec security collection (if configured)– FTP data collection– Enterprise Extender and High Performance Routing statistics collection– Communications Storage Manager (CSM) buffer pools– OSA statistics– Interface statistics– Data Link Control (DLC) statistics– TCP/IP Stack layer statistics

v The SNAC component (if configured), including Buffer Pool and VTAM Environment data collection

By default, both of these components start automatically at startup and run for the life of the monitoringagent. Data collection for these components or any of the individual data types they include can bestopped and started between recycles using the KN3FCCMD commands. See Appendix C, “KN3FCCMDand KONFCCMD command reference,” on page 203 for more information about stopping and startingcollections of various types of data.

By default, the OMEGAMON XE for Mainframe Networks monitoring agent is configured to monitor allresources. The monitoring agent always collects a required minimum amount of real-time data. You maychoose to disable one or more of these data types. The following tables show the storage costs formonitoring the required and optional types of resources. These tables are provided to inform you of therelative size of attribute tables and the frequency in which data is collected. You might use thisinformation to determine what to monitor: which types of resources, which systems and at whatcollection interval.

The monitoring agent monitors itself. Configuration and status information for the agent is displayed inthe Agent Status workspace. This workspace is part of a special group of workspaces known as the Agentand TCP/IP Subnode workspaces. These workspaces include high-level views accessed from the Agent nodein the Navigation tree that display configuration, status, and command execution information about theinstance of the OMEGAMON XE for Mainframe Networks monitoring agent represented by the specifiednode. Data for these workspaces is stored in internal control blocks maintained by the agent. The data isgathered from the control blocks whenever a user navigates to one of these workspaces or refreshes theview for that workspace. There is no collection interval for this data. There is also no memory in a dataspace for this data. Status data for these workspaces is always available and cannot be disabled throughconfiguration of any kind. Table 8 on page 42 shows the data gathered every time you display or refreshAgent and TCP/IP Subnode workspaces.

Chapter 2. Planning for configuration 41

Table 8. Data collected every time the Agent or TCP/IP subnode workspaces are displayed or refreshed

LPAR name

Type of dataReal-time data attributesgroup

Row size inbytes Frequency per display/refresh

Agent Subnode KN3 Agent Status 224 1 row

KN3 SNA Collector Status 104 1 row

KN3 TCP Collector Status 756 1 row per monitored TCP/IP stack

KN3 Take Action Command 596 A maximum of 33130 rows of data

KN3 Take Action CommandResponse

312

Multiplerows ofcommandresponsescan beassociatedwith agiven TakeActioncommand..

A maximum of 390427 rows of data.

The data shown in Table 9 is collected once every collection interval and stored in memory (in a dataspace). The memory is reused each collection interval. When a user navigates to a workspace, a querywill result in the monitoring agent retrieving the appropriate data from a data space. Use this table tocalculate the memory usage by multiplying the row size by the number of resources. Add the numbers inthe memory usage column to obtain the total memory used to hold data collected in an interval for aTCP/IP address space. Perform these calculations for each TCP/IP address space you are monitoring.

Table 9. Data collected once every collection interval

LPAR name

TCP/IP addressspace name

Type of dataReal-time data attributestable

Row sizein bytes Frequency per interval

Memoryusage

TCP/IP Stack Layerstatistics

TCPIP Address Space 624 1 row per TCPIP address space

KN3 ICMP GlobalCounters

100 Up to 2 rows per TCPIP address space

KN3 ICMP Type Counters 80 Up to 2 rows per TCPIP address space

KN3 IP Counter Statistics 232 Up to 2 rows per TCP/IP address space

KN3 IP General Statistics 84 1 row per TCP/IP address space

KN3 TCP CounterStatistics

280 1 row per TCP/IP address space

KN3 UDP CounterStatistics

128 1 row per TCPIP Address Space

TCPIP Stack Layer 608 1 row per TCP/IP address space


Table 9. Data collected once every collection interval (continued)

LPAR name




Memoryusage

Interface statisticscollection

TCPIP Devices 432 1 row per device

Interfaces 472 1 row per TCP/IP interface

KN3 Interface Address 132 1 row per TCP/IP interface address

KN3 Interface Statistics 304 1 row per active strategic TCP/IPinterface (max 256)

KN3 Interface Status 344 1 row per TCP/IP interface

Data Link Controlstatistics collection

KN3 Interface ReadQueue

312 1 row per read queue per active OSAQueued Direction I/O (QDIO) orHiperSockets interface

KN3 Interface WriteQueue

200 1 row per configured queue priority perOSA-Express Queued Direct I/O (QDIO)or HiperSockets interface

OSA statisticscollection

OSA Channels 416 1 row per OSA Channel

OSA-Express LPARS 106 16 rows per OSA Channel per LPAR perlocal channel subsystem

OSA-Express Ports 768 1 row per OSA channel of channelsubtype: gigabitEthernet,fastEthernet oroneThousandBaseTEthernet per port

OSA 10 Gigabit PortsControl

390 1 row per OSA channel of channelsubtype: tenGigabitEthernet per port

OSA 10 Gigabit PortsErrors


OSA 10 Gigabit PortsSummary


OSA 10 Gigabit PortsThroughput


OSA-Express3 PortsControl

390 1 row per OSA channel of channelsubtype: osaexp3gigabitEthernet,osaexp3oneThousandBaseTEthernet orosaexp3tenGigabitEthernet per port

OSA-Express3 PortsErrors


OSA-Express3 PortsSummary


OSA-Express3 PortsThroughput


TCP/IP and VTAM(required collection)”

TCPIP Memory Statistics 472 1 row per TCP/IP address space



LPAR name




Memoryusage

TCP/IP Connectionand ApplicationPerformance statisticscollection

TCPIP Applications 656 1 row per TCP/IP application

TCPIP Connections 632 1 row per TCPIP connection

TCPIP Details 616 1 row per TCP connection

TCP Listener 268 1 row per TCP listener

UDP Connections 360 1 row per UDP endpoint

Routing Tablestatistics collection

TCPIP Gateways 600 1 row per TCP/IP gateway collected onRouting Table Collection Frequency

IPSec SecurityCollection

IPSec Status 360 1 row per TCP/IP address space

Current® IP Filters 812 1 row per IP filter

Dynamic IP Tunnels 1024 1 row per dynamic IP tunnel

IKE Tunnels 664 1 row per IKE tunnel

Manual IP Tunnels 364 1 row per manual IP tunnel

The data shown in Table 10 is collected once every collection interval and stored in memory. This data iscollected for each LPAR you monitor. The memory is each collection interval. Use this table to calculatethe memory usage by multiplying the row size by the number of resources. Total the memory usagecolumn to obtain the total memory used to hold data collected in an interval for these resources.

Table 10. Data collected for each monitored LPAR

LPAR name

Type of dataReal-time data attributegroup


Memoryusage

TCP/IP and VTAM(required collection)

VTAM SummaryStatistics

72 1 row

Enterprise Extender (EE)and High PerformanceRouting (HPR) statisticscollection

EE Connections 248 1 row per EE connection

EE Connections Details 240 5 rows per EE connection

HPR RTP Connections 568 1 row per HPR RTP connection

Communications StorageManager (CSM) bufferreporting

CSM Storage 176 1 row

KN3CSM Storage byOwner

168 1 row per address space that ownsCSM storage


Table 10. Data collected for each monitored LPAR (continued)

LPAR name



Memoryusage

Buffer Pool and VTAMEnvironment datacollection

VTAM Address Space 244 1 row

VTAM I/O 72 1 row for each of 6 resources

VTAM Buffer Pools 154 1 row for each of 14 resources

VTAM Buffer PoolExtents

96 1 row per buffer pool extent

VTAM Buffer Usage byAddress Space

72 1 row per address space usingIO00 or CRPL buffers

VTAM Buffer Usage byApplication

80 1 row per application per addressspace using IO00 buffers

VTAM Buffer Usage byCategory

68 1 row for each of 12 resources

The FTP data shown in Table 11 is collected when a new session or transfer is opened or when anexisting session or transfer is closed. This data is collected when z/OS Communications Server notifiesthe monitoring agent that data is available and therefore does not adhere to a collection interval. Asexplained previously, new records are appended to the previously collected data until the table in thedata space is full, at which time the table wraps. Therefore, over time 256 MB per TCP/IP address spacewill be used to hold FTP data.

This data is collected for each TCP/IP stack where FTP is running.

Table 11. FTP data collected

LPAR name

TCP/IP address spacename


Row sizein bytes Frequency

Maximumrows stored

FTP Data Collection FTP Sessions 384 2 rows per FTP session 25,000

TCPIP FTP 2464 2 rows per FTP transfer 100,000

The TN3270 session workspaces display information about open, closed and active TN3270 sessions for aTCP/IP address space. Data for open and closed sessions is provided when z/OS CommunicationsServer notifies the monitoring agent that data is available and therefore is not driven by a collectioninterval. Data for active sessions is collected once per collection interval.

Memory used to store data for one session is reused for the same session each collection interval and forthe data collected when the session is closed. Approximately 24 hours after a session is closed, thememory used to hold that session’s data will be made available for a new session.

Use Table 12 on page 46 to calculate the memory usage by multiplying the row size by the number ofresources. Total the memory usage column to obtain the total memory used to hold TN3270 datacollected for a TCP/IP address space. Perform these calculations for each TCP/IP address space you aremonitoring.

Note: The TN3270 Response Time Buckets table is not collected or stored as a separate table. Instead, it isa different view into the TN3270 Server Sess Avail table. When a query is issued to retrieve TN3270


Response Time Buckets data, the appropriate TN3270 Response Time Buckets rows (one row for each ofthe five response time buckets) are created from the corresponding row in the TN3270 Server Sess Availtable.

Table 12. TN3270 data collected

LPAR name

TCP/IP address spacename

Type of dataReal-time data attributetable


Maximumrows stored

TN3270 Server StatisticsCollection

TN3270 Server SessAvail

432 1 row per TN3270 server sessionthat is active or was closed in thelast 24 hours

TN3270 Response TimeBuckets

204 0 rows 0

Use the Configuration Tool or the z/OS MODIFY command to enable or disable data collection for specifictypes of data. See Appendix C, “KN3FCCMD and KONFCCMD command reference,” on page 203 formore information about these commands.

Note: OMEGAMON II for Mainframe Networks can be used to collect TCP/IP performance data.However, this option is disabled by default. OMEGAMON XE for Mainframe Networks provides moreextensive coverage of TCP/IP and its resources and provides a more efficient monitoring solution. Beaware that enabling both OMEGAMON II for Mainframe Networks and OMEGAMON XE for MainframeNetworks to monitor TCP/IP generates unnecessary processing activities. To enable the best performanceof your system, use only OMEGAMON XE for Mainframe Networks to monitor TCP/IP resources inyour enterprise.

Defining data collection intervalsThe collection intervals control how often real-time data is collected. Each time you collect data, themonitoring agent incurs a certain amount of CPU usage. How much processing is incurred depends onthe number and type of resources you monitor.

Collection intervals are specified in minutes and have a valid range of 1 to 60. The default value for acollection interval is 5 minutes. This default value satisfies the monitoring needs of many customers whorequire near 'real time' access to data.

The collection intervals are specified in the Configuration Tool or the PARMGEN method, or you canmodify a collection interval by executing a MODIFY procname,KN3FCCMD command (see Appendix C,“KN3FCCMD and KONFCCMD command reference,” on page 203 for more information about theMODIFY commands). Specify values for the following collection intervals:v TCP/IP sample interval (for the TCPC component): the collection interval used to control most of the

data collection, with the exceptions that follow.v SNA data collection interval (for the SNAC component): controls the Buffer Pool and VTAM

Environment data collection. This option is available only if you enter Y for Buffer Pool/VTAMEnvironment Data Collection when you configure the monitoring agent in the Configuration Tool.

The z/OS Communications Server network management interface (NMI) and Performance MonitoringInterfaces maintain performance information between collection intervals. For example, spikes areidentified in such attributes as “Maximum Authorized Private Storage Allocated.” Over- andunder-utilization values are identified in such attributes as “Total Bytes Sent.”


The network performance data displayed in the Tivoli Enterprise Portal is the latest collection interval; auser request to view data does not initiate a new data collection. Therefore, increasing the frequency ofdata collection (that is, decreasing the collection interval) by the monitoring agent generally results inyour network operators viewing more recent data but results in higher CPU consumption by themonitoring agent. By decreasing the frequency of data collection (for example, from 5 to 15 minutes), youreduce the number of times per hour that the monitoring agent collects data (from 12 to 4 times perhour), thus reducing the total CPU consumption (by a factor of approximately 3).

You can further reduce the CPU consumption by changing the Routing Table Collection Frequency in theConfiguration Tool or on a KN3FCCMD START ROUTE command. See Appendix C, “KN3FCCMD andKONFCCMD command reference,” on page 203 for information about this command. The Routing TableCollection Frequency controls how often the Routing Table Statistics (Gateway table) are collected. Bydefault, this data is collected once every 10 collection intervals (once every 50 minutes when the defaultcollection interval is used). The frequency does not affect the amount of storage used; it affects only CPUconsumption.

Set the collection intervals and routing table frequency to meet your monitoring needs, ensuring that youare promptly alerted to problems so they can be resolved quickly. But, also be aware that each datacollection comes with a cost in CPU usage.

Run OMEGAMON XE for Mainframe Networks and use Tivoli OMEGAMON XE on z/OS or theResource Measurement Facility™ (RMF™) to measure CPU usage. Adjust the collection intervals until youhave achieved the desired balance between currency of data and CPU usage.

Defining display intervalsA display interval determines how long a session or transfer will be available for display at the TivoliEnterprise Portal.

During configuration of the monitoring agent, specify values for FTP and TN3270 display intervals. Thevalue is specified as a number of hours (1 to 24 are valid values). FTP and TN3270 workspaces displaysession and transfer information that was collected during the specified display interval. Note that someworkspaces also have default query filters that will determine which data or how much data to display.

Setting a display interval to a lesser value might reduce the amount of CPU used by the monitoringagent when retrieving data for display at the Tivoli Enterprise Portal. Similarly, setting a display intervalto a higher value might increase the amount of CPU usage. Balance your need to view data for sessionsor transfers that occurred up to 24 hours ago with the CPU usage.

An alternative to increasing the display interval is to enable historical collection for the data table andviewing historical data instead of real-time data in the Tivoli Enterprise Portal. See the TivoliOMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide for more information aboutthe display intervals used for FTP and TN3270 workspaces.

Defining and running situationsSituations are used to identify monitored resources that meet certain performance criteria, raising an alertwhen the criteria is met.

A situation definition includes a sampling frequency, a set of conditions, and a list of monitored systems.Each of these situations has implications on CPU and storage consumption. Also, the cumulative effect ofall the active situations has implications on performance.

OMEGAMON XE for Mainframe Networks provides 100 predefined situations (none of which areautostarted) to detect some of the most common mainframe network problems. Autostarted situationsrun automatically when the OMEGAMON XE for Mainframe Networks monitoring agent is started. See


the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide for a list anddescription of the product-provided situations. If you are upgrading from a previous version of thismonitoring agent, then whatever customization and autostart settings you have on current situations areretained after upgrading.

A situation can include a Take Action command that runs when the situation is triggered. By using aTake Action command, you can automate a response to a specific system condition. In addition, eachsituation can include text describing the probable cause and expert advice that helps you to address andresolve problems quickly.

Any triggered situation raised by IBM Tivoli Monitoring or any of the OMEGAMON XE V4.2 or latermonitoring agents can be forwarded to the Netcool® OMNIbus Event List or IBM Tivoli Event Console.IBM Tivoli Monitoring and the OMEGAMON agents monitor systems and can proactively alert you towarnings or detect critical situations when they occur. Those alerts or situation events can be forwardedby means of the Event Integration Facility, (EIF). The Netcool OMNIbus Event List and the Tivoli EventConsole show details like the severity of the event, (Warning, Critical, informational) and the status,(open, closed, acknowledged). The capability to drill down into the event to determine what thresholdswere exceeded or which parts of the network are affected is available with Event Integration. If theNetcool OMNIbus user determines that the problem is being addressed, the user can acknowledge it,attach a journal entry, or close the event. The user can also escalate events or suppress escalation.

When planning for configuration and deployment of OMEGAMON XE for Mainframe Networks,evaluate all situations provided by the product. Determine which situations to autostart. If necessary,modify existing situations and create new situations to meet the needs of your enterprise.

For each situation that you choose to run, determine the importance and therefore the desired samplingfrequency. All situations that query a specific attribute table should be defined with the same samplingfrequency to enable the OMEGAMON XE platform to group situations and thereby optimizeperformance.

For situations to be grouped, they must be active when the hub Tivoli Enterprise Monitoring Server starts(autostarted), have the same sampling frequency, and test conditions on attributes in the same attributetable.

Verify that the conditions evaluated by each situation are appropriate for your environment. Check boththe set of conditions and individual conditions. The predefined situations attempt to use the mostefficient means to identify problems. There might be alternative conditions that identify the sameproblems but are less expensive to evaluate in your environment. Ensure that the values being checkedare correct for your environment.

After you modify situations that are auto-started, stop and start the hub Tivoli Enterprise MonitoringServer. The process of combining situations occurs only during initialization of the hub Tivoli EnterpriseMonitoring Server.

Understanding how historical data is collectedBefore you can configuration historical data collection, understand the difference between short-term andlong-term historical data and how both are collected.

Historical data collection is an optional feature that is enabled using the Tivoli Enterprise Portal. TheOMEGAMON platform provides the following types of historical data collection:v Short-term historical data is stored in the persistent data store on z/OS systems or in files on

distributed systems. To optimize performance, configure the persistent data store at the monitoringagent, meaning that you will have a persistent data store on each z/OS system you are monitoring.


Short-term historical data typically refers to data that is stored for 24 hours or less. However, theamount and age of the short-term data that is retained depends on the number of resources beingmonitored and the amount of disk space configured for use by the persistent data store.

v Long-term historical data is stored in the Tivoli Data Warehouse. The long-term history database canretain data collected by OMEGAMON XE for Mainframe Networks monitoring agents for as long asyou like (days, weeks, months or years).

Short-term historical data is best used for analysis during problem determination. Additional prerequisitesoftware is not required for short-term historical data collection, however the data sets used by thepersistent data store must be configured using the Configuration Tool or PARMGEN.

Long-term historical data is better used for trend analysis and to determine workload balance. See thechapter about configuring the warehouse proxy for Tivoli Data Warehouse in the IBM Tivoli Monitoring:Installation and Setup Guide for the list of supported databases, releases and operating system platforms.Long-term history also requires installation of the warehouse proxy software (provided) andconfiguration of an Open Database Connectivity (ODBC) connection. Use the warehouse proxyinstallation default support for defining database tablespaces and creating the ODB connection.Short-term historical data collection must be enabled and configured if you want to perform long-termhistorical data collection.

After historical data collection is enabled, an icon is displayed in qualifying views in Tivoli EnterprisePortal workspaces. Allow time for historical data to be stored, to produce meaningful reports. You canclick this icon to extend any existing Tivoli Enterprise Portal view (also called a report) to includehistorical data. Tivoli Enterprise Portal reports automatically pull data from short-term and long-termhistory, based upon the time period you specify for the report.

The collection interval for historical data can be configured to be different from the collection interval forreal-time data. To avoid excessive processing activities and decrease storage consumption, historical datacollection is typically performed less frequently than real-time data collection. You can configure ashort-term historical data collection interval of 1, 5, 15, 30 or 60 minutes or 1 day.

Writing the data to long-term history can be configured for 15 or 30 minutes or 1, 12, or 24 hours. If youconfigure long-term history, use a warehousing interval of 1 hour to avoid transferring 24 hours worth ofhistorical data at one time. This shorter interval reduces the duration of CPU usage associated withwriting data to the warehouse by spreading the writing across 24 periods.

The following example illustrates the rate of accumulation of historical records, assuming the followingintervals have been specified:v Real-time data collection interval: 5 minutesv Short-term historical data collection interval: 15 minutesv Long-term warehousing interval: 1 hour1. At 1:57, data collection is initiated for 1 TCP/IP Address Space.2. One row of data (512 bytes) is collected at 1:57, another row at 2:02, another at 2:07, 2:12, 2:17, and so

on. Only the current row of data is stored because the old row is discarded when a new row arrives.Because the real-time data collection interval is 5 minutes, 12 collections are made per hour.

3. At 1:58, collection of historical data is initiated for 1 TCP/IP Address Space.4. One row of data (540 bytes) is stored in short-term history at 2:00, the second row is collected at 2:15,

the third at 2:30, 2:45, 3:00, and so on. Short-term history uses the most recent collection and thereforedoes not initiate another data collection. The row stored at 2:00 would use the 1:57 collection. The rowstored at 2:15 would use the 2:12 collection.

5. Because the short-term historical data collection interval is 15 minutes, 4 collections are made perhour. All measurements are stored for future use.


6. After one hour, all (4) rows of short-term historical data are transferred by the warehouse proxy to thelong-term history SQL database.

7. After 24 hours, 96 (24 x 4) rows of data will be stored in the Tivoli Data Warehouse.

Determining which types of historical data to collectWhen deciding which types of data to store in short-term and long-term history and how long to store it,you must recognize that data collection consumes CPU cycles and disk space.

Note: Long-term history is not displayed for the Enterprise_Networks workspaces and the followingadditional workspaces:v Active TN3270 Server Sessions for Selected Portv EE Connection Summaryv FTP Transfers for Session

The queries for these workspaces contain clauses that are not supported by Tivoli Data Warehouse. Youcan view long-term history for the same attribute groups from workspaces accessed from the physicalnavigator.

Writing data to short-term history is cost effective and typically much less costly than writing tolong-term history. Retrieving short-term history data to display historical reports increases CPU usage atthe hub Tivoli Enterprise Monitoring Server (monitoring server) and at the monitoring agent, whenshort-term history data is stored at the monitoring agent.

Short-term historical data is written to disk, typically performed at the monitoring agent, consuming CPUcycles on the z/OS monitoring agent system. Additional CPU cycles are used when the Warehouse Proxyextracts data from short-term history and transfers it to the Data Warehouse. If you have collected a largeamount of data in short-term history, the extraction process will significantly increase the monitoringagent’s CPU usage. Similarly, when a table contains thousands of rows, the retrieval process for a TivoliEnterprise Portal display of historical data will significantly increase the monitoring agent's CPU usage.

Depending on your needs, you may configure historical data collection for only a subset of attributetables. Using only a subset of attribute tables is an effective means for limiting storage and CPUconsumption, particularly if you choose not to perform historical data collection for high volume attributetables such as TCP connections or attribute tables with many bytes per row (many attributes), such asFTP transfers. Collect only data that you will use in historical reports. Collect those tables only asfrequently as your enterprise needs. Selecting a less frequent historical collection interval (30 minutesinstead of 15 minutes) will reduce both storage and CPU consumption.

The tables in the “Determining which types of real-time data to collect” on page 41 section allow you tocalculate storage consumption based on real-time data collection. The information you gather for thesetables also provide the basis for calculating the storage requirements for historical collection.

The additional storage cost for short-term historical data collection equals the number of bytes ofreal-time data storage, per row of data, plus 28 bytes. The additional storage cost for long-term historicaldata collection, in the Tivoli Data Warehouse, is the same number of bytes. To calculate storage associatedwith historical data, add 28 bytes to each row of real-time data. See Appendix D, “Disk spacerequirements for historical data tables,” on page 257 for detailed calculations.

You can use this information as a basis for choosing which attribute tables to enable for historicalcollection. You can select individual attribute tables for historical collection, including specifying differenthistorical collection intervals and warehouse intervals. Here is a list of attribute tables that are likely tohave a large number of resources and therefore require higher amounts of storage and CPU consumptionwhen enabled for historical collectionv TCPIP Connections


v TCPIP Detailsv TN3270 Server Sess Availv TCPIP Devicesv Interfacesv EE Connectionsv EE Connections Detailsv HPR Connectionsv VTAM Buffer Pool Extents

If you choose to not collect all attribute tables, TCPIP Connections is a logical choice to omit. All of thedata in TCPIP Connections is also available in TCPIP Details, TCP Listener and UDP Connections. Thischoice affects which workspaces can draw historical reports, but the data is there if needed for reporting.

By default historical reports retrieve up to 24 hours of data from short-term history. If your persistentdata store is not allocated with sufficient space, you will not have 24 hours of short-term data to retrieve.Allocate your persistent data store to hold a full 24 hours of data or change the default of 24 hours. Youmay also want to change the default in order to retrieve less data from short-term history and more datafrom long-term history in order to reduce the CPU consumed by the monitoring agent to process queriesfor historical data. See “Tuning OMEGAMON XE components” on page 53 for information about how tochange the default of 24 hours.

Because historical data accumulates, you must also determine how long you want to keep the data.Short-term history data in the persistent data store automatically wraps, and thus does not need to bemaintained. You can also run a KPDXTRA job to write short-term history to flat files, for backup, or foranalysis in a statistical or graphing package. See the IBM Tivoli Monitoring: Administrator's Guide fordetails on KPDXTRA.

Long-term history, in the Tivoli Data Warehouse, does not automatically prune old records. You mustdetermine how much data to retain, and either use the database manager tools to manually delete oldrecords or configure the IBM Tivoli Monitoring Summarization and Pruning agent to run automatically todelete old records.

For detailed instruction about setting up historical data collection, see the section on configuring yoursystem for Tivoli Enterprise Portal in the IBM Tivoli Monitoring: Installation and Setup Guide book.Additional agent configuration information about the warehouse proxy is found in the IBM TivoliMonitoring: Administrator's Guide. For information about reporting, see IBM Tivoli Monitoring: User's Guide.

Designing workspacesWhen a user navigates to a workspace, one or more queries are processed by the OMEGAMON XEcomponents in order to display the requested workspace. Those same queries are processed again whenthe user requests a refresh or periodically in the cases where the workspace is configured to refreshautomatically.

The workspaces and queries provided in the OMEGAMON XE for Mainframe Networks product havebeen designed with performance in mind. However, your environment and the resources you monitormight require customization of the product-provided workspaces and queries.

The following are tips to improve the performance for users viewing workspaces. See IBM TivoliOMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide to see the default filtersprovided for each workspace.

The query assigned to a chart or table view requests data from a particular attribute table. It runs whenyou open or refresh the workspace. The Tivoli Enterprise Portal Server sends the query to the hub Tivoli


Enterprise Monitoring Server. The hub Tivoli Enterprise Monitoring Server distributes the query to theappropriate monitoring agent or agents and aggregates the resulting rows. The Tivoli Enterprise PortalServer retrieves the results and holds the entire result set in memory. The Tivoli Enterprise Portalretrieves one page of the results to display and holds both the current and previous page in memory.

You can dramatically reduce the amount of data retrieved by doing the following:v Reducing the number of rows or attributes retrievedv Applying the same query to multiple views in a workspacev Adjusting the auto-refresh ratev Reducing the number of rows retrieved

One of the best ways to improve the performance of queries is to reduce the number of rows retrieved.The Query Editor allows you to add filters that reduce the number of rows that are returned. Youmight want to change the existing filter values of a query or add filters to the query. For example, theApplications workspace contains a table view that displays all applications that have TCP/IPconnections. You might be interested in only those applications that have active connections. You couldcustomize the query by adding a filter in the Query Editor for “Active Connections” greater than 0. SeeIBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide to see thedefault filters provided for each workspace.Do not confuse custom queries with view filters, which can also be invoked from the TEP propertiesdialog. View filters have no effect on reducing the CPU and storage consumption by the monitoringagent and actually increase the Tivoli Enterprise Portal client CPU consumption.View filters are applied by the client and affect only the current page. If more than one page isreturned by the query, only a subset of the data is viewed on each page. Increasing the page size is anoption available in Tivoli Enterprise Portal. Increasing the page size typically provides more filtereddata on each page, but increases the client’s memory requirements because now the two pages perquery stored at the client are larger. It is more efficient to filter in the queries.

v Reducing the number of attributes retrieved

Most product-provided queries return all attributes. There might be 50 attributes in an attribute table,yet you might want to view only 25 of them. Creating a custom query to retrieve only those 25attributes reduces Tivoli Enterprise Portal Server and client processing and memory requirements.For example, the OMEGAMON XE for Mainframe Networks applications attribute table contains 54attributes. If you are creating a workspace that displays information about TCP applications, you arenot required to select the 14 UDP attributes of the attribute table.Historical workspaces retrieve much more data than real-time workspaces. Accordingly, all of thequeries used for predefined historical workspaces request only the most valuable subset of attributeson the source table. The queries used by predefined historical workspaces are good starting places forbuilding better performing workspace views. See the IBM Tivoli OMEGAMON XE for MainframeNetworks: Tivoli Enterprise Portal User's Guide for more information about modifying or creating queries.

v Applying the same query to multiple views in a workspace

Having multiple views in a workspace that retrieve data from different attribute tables is fine. But ifyou have a graph containing “Total Retransmissions” and a table containing “Transmit Segment Rate”(both available from the same attribute table), create one custom query for both views. By creating asingle custom query, Tivoli Enterprise Portal will retrieve the data once for both views.The objective is to use only one query for each attribute table used in a workspace. When a workspaceis displayed, the entire results set for each query is stored on the Tivoli Enterprise Portal Server. The100 rows (default page size) from each query currently being viewed and the previous page of anypane viewed are stored on the Tivoli Enterprise Portal client.

v Adjusting the auto-refresh rate

The operator can choose an automatic refresh rate from every 30 seconds to once per hour. Each timethe workspace is refreshed, the data is retrieved from the data spaces that reside on the system wherethe monitoring agent is running. The happens only for the currently displayed workspace. Retrieving


data from the agent consumes CPU so it is important to specify a refresh rate that meets yourmonitoring needs while avoiding unnecessary performance activities by the monitoring agent.When an operator clicks the Time Span button to display historical data, the auto-refresh rate definedfor the workspace will continue to be used. The current auto-refresh rate can result in significant CPUconsumption by the monitoring agent because the workspace is automatically refreshed (as frequentlyas once every 30 seconds). Consider changing the default auto-refresh rate to "On Demand" forworkspaces that your users frequently use to display historical data.

For the enhanced 3270 user interface, you can edit the product-provided workspaces by copying anexisting workspace and updating the attributes and the queries associated with it. See the "Customizingworkspaces" topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:OMEGAMON Enhanced 3270 User Interface Guide to understand how to create workspaces for theenhanced 3270 user interface. You will also need to know COLUMN value for the attribute you want tocode. This is found by locating the Object Definition Interchange (ODI) file for this monitoring agent. TheKANDATV DD card points to the location of the KN3DOC file in your installation or you can look in theCandle_Home\TEPS directory for the dockn3 file. You need to search first on the name of the attributegroup. See the mapping appendix of the IBM Tivoli OMEGAMON XE for Mainframe Networks: TivoliEnterprise Portal User’s Guide for the names of attribute groups. The same design principles discussed inthis section apply to the design of 3270 workspaces.

Tuning OMEGAMON XE componentsOnce configuration is complete, you can tune some components to make them operate more efficiently.You can change data collection options, change the default value for short-term history, and tune TivoliData Warehouse.

This section includes some tuning information about the components of the OMEGAMON XE forMainframe Networks monitoring agent that you might want to implement once the monitoring agent isinstalled.v Changing data collection options

While an OMEGAMON XE for Mainframe Networks monitoring agent is running, you can change thedata that is being collected by using z/OS MODIFY commands to temporarily change how often datacollection is performed.Using z/OS MODIFY commands, you can reduce the z/OS system resources used to monitor yournetworks while a larger than normal workload is being performed. You can also monitor more of yournetwork resources while you are investigating a problem.Changes made using the z/OS MODIFY command are temporary. The next time that the monitoringagent is started, the agent reverts to the definitions made in the Configuration Tool. In other words, thechanges made using the z/OS MODIFY command are not retained when the monitoring agent isstopped.Changes associated with the tolerate TCP/IP recycle option reimplement the configured monitoringoptions whenever the state of a network monitoring interface (NMI) AF-UNIX socket changes, whichmay further reduce the effects of changing the monitoring options using the command line interface.Monitoring options that require permanency should be made through the Configuration Tool.The following z/OS operator command causes the monitoring agent to stop collecting applications andconnections data from the TCP/IP address space named TCPIPB.MODIFY proc_name,KN3FCCMD STOP CONN TCPNAME(TCPIPB)

The output from this command is:KLVOP191 ’KN3FCCMD STOP CONN TCPNAME(TCPIP)’ KN3C115I STOP FOR

COMPONENT CONN ACCEPTED.TCPNAME: TCPIP KN3FC000 KN3FCCMD PROCESSING COMPLETE


Note: After you have issued this command, you might experience a delay (the default is up to 30minutes) before this output is written to RKLVLOG. To see the output immediately, enter the followingz/OS operator command:MODIFY proc_name,FLUSH

To reset to the data collection you specified during configuration of the monitoring agent, you caneither stop and start the started task procedure or issue the following z/OS operator commands to stopall data collection and start the data collection as configured in the Configuration Tool:MODIFY proc_name,KN3FCCMD STOP TCPCMODIFY proc_name KN3FCCMD START TCPC

See Appendix C, “KN3FCCMD and KONFCCMD command reference,” on page 203 for detailedinformation on the z/OS MODIFY command support.

v Tuning the TMS:Engine LIMIT value

IBM Tivoli Management Services: Engine (TMS:Engine) is a common component for both the TivoliEnterprise Monitoring Server and for OMEGAMON XE for Mainframe Networks Monitoring. It hasstartup parameters that are defined with appropriate defaults for many customer environments, andthese parameters are defined in the data set pointed to by the RKLVIN DD statement in the startedtask procedure.If you see this message:KN3I008E CALL TO ADDDATA FUNCTION FAILED, RETURN CODE=retcode, FOR TABLE=table

An error has occurred when the monitoring agent tried to return data for the table specified by thetable variable and failed. The most common cause of this error is a query that returns a large numberof rows of data, causing an out-of-memory condition.Options are to either modify the query so that it returns fewer rows of data or change the LIMIT andMINIMUM values in &rhilev..&midlev.RKANPARU.The current recommendation for the OMEGAMON XE for Mainframe Networks Agent isMINIMUM(768000,X) and LIMIT(24,X) as specified in member (KN3SYSIN). The currentrecommendation for the Tivoli Enterprise Monitoring Server in (KDSSYSIN) is MINIMUM(768000,X)and a LIMIT value of 24 or greater.The LIMIT parameter can be used to specify the largest block of primary storage or extended storagethat can be allocated. The syntax for setting the largest block of extended storage is shown in theexample (note that setting the limit for primary storage is not recommended): LIMIT(n,X)This value is specified in bytes, as a power of 2. For example, if n is 22, the largest block that can beallocated is 4 MB. If the LIMIT value is too small and a process in ITMS:Engine attempts to allocate ablock of storage larger allowed by LIMIT, a program interruption U0100 or U0200 results Whenmanaging a large number of connections or TN3270 sessions, use a value of LIMIT (25,X) or greater.

v Changing the default value for short-term history from 24 hours

By default, historical data from the last 24 hours is retrieved from the persistent data store for displayat the Tivoli Enterprise Portal. Historical data from earlier time periods is retrieved from the TivoliData Warehouse.You can alter this default by modifying the KFW_REPORT_TERM_BREAK_POINT environmentvariable in the kfwenv file on the Tivoli Enterprise Portal Server. Information about the environmentvariable is found in IBM Tivoli Monitoring: Administrator's Guide. This variable is specified in seconds.The default is 86400 (= 60 seconds * 60 minutes * 24 hours). Increasing this value will result inhistorical data being retrieved from the persistent data store for time periods farther in the past.Decreasing this value will result in historical data being retrieved from the Tivoli Data Warehouse formore recent time periods.You might want to increase the value of this environment variable if you have not implemented TivoliData Warehouse. By increasing the value, you can view more historical data, assuming the persistentdata stores are allocated large enough to contain more than 24 hours of data.


You might want to decrease the value of this environment variable if you configured the warehouseinterval to be one hour. By decreasing the value, you can view all historical data with smallerpersistent data stores.

v Tuning considerations for the Tivoli Data Warehouse

The default database manager settings provided by DB2 may not be sufficient to support warehousingof large amounts of monitor data from OMEGAMON XE for Mainframe Networks. Review theappendix “Relational database design and performance tuning for DB2 database servers” appendix inthe IBM Tivoli Monitoring: Administrator's Guide to learn about DB2 tuning considerations.

Planning securityAs you plan the configuration of this monitoring agent, understand how security is provided.

Security for monitoring agents, such as OMEGAMON XE for Mainframe Networks, is provided by TivoliManagement Services through the local system registry or an external, LDAP-enabled registry.

Access to the Tivoli Enterprise Portal is controlled by user accounts (user IDs) defined to the portalserver. In addition to defining the user IDs that are authorized to log on to the Tivoli Enterprise Portal,these accounts define the permissions that determine the Tivoli Enterprise Portal Server features a user isauthorized to see and use, the monitored applications the user is authorized to see, and the Navigatorviews (and the highest level within a view) the user can access. An initial sysadmin user ID with fulladministrator authority is provided at installation so you can log in to the Tivoli Enterprise Portal andadd more user accounts. No password is required to log on to the Tivoli Enterprise Portal unless userauthentication is enabled.

Authentication of user IDs can be enabled through the hub Tivoli Enterprise Monitoring Server orthrough the Tivoli Enterprise Portal Server. User IDs authenticated through the hub monitoring servercan be authenticated by either the local system registry or an external LDAP-enabled central registry.User IDs authenticated through the Tivoli Enterprise Portal Server can be authenticated only by anexternal LDAP-enabled registry. User IDs that are required to make SOAP Server requests (including userIDs that issue CLI commands that invoke SOAP server methods) must be authenticated through the hubmonitoring server. User IDs that require single sign-on (SSO) capability for launching into other IBMproducts must be authenticated through the portal server. LDAP authentication must be enabled throughthe portal server before SSO can be configured.

See the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning andConfiguration Guide for an overview of the security options. See IBM Tivoli Management Services on z/OS:Configuring the Tivoli Enterprise Monitoring Server on z/OS and the IBM Tivoli Monitoring: Administrator'sGuide for instructions on setting various types of security.

In V5.1.0, the new 3270 and existing Tivoli Enterprise Portal Take Action commands fail unless explicitsecurity definitions are configured that enable these commands to be issued. Security for this monitoringagent’s Take Action commands is implemented through direct SAF (System Authorization Facility) callsand is based on resource profiles. Both user ID and command are validated. See the "Take Actioncommands issued from the enhanced 3270 interface with SAF security" topic in “New function addedsince Version 4.2.0 Fix Pack 3” on page 23 for help locating the SAF configuration information for thismonitoring agent.

At the end of the configuration process for the OMEGAMON XE for Mainframe Networks monitoringagent, two additional agent-specific security tasks must be performed:v “Define monitoring agent access to the network management interfaces and commands” on page 128v “Give users authorization and resource access to run the VARY TCPIP DROP command” on page 130


Planning for OMEGAMON II for Mainframe NetworksStarting with V4.2, delivery and installation of the OMEGAMON II monitoring agent (sometimes calledthe CUA interface) for this OMEGAMON XE product has changed.

The OMEGAMON II FMID has been merged with the OMEGAMON XE FMID. The OMEGAMON IIFMID has been eliminated. This change should shorten the required installation time and simplifyconfiguration. The configuration guide for OMEGAMON II has been merged into the planning andconfiguration guide for OMEGAMON XE. The remaining OMEGAMON II manuals continue to beprovided with the current version of Tivoli OMEGAMON XE for Mainframe Networks. No enhancementshave been made to these documents since version 5.2.0 of the OMEGAMON II interface. See theOMEGAMON II for Mainframe Networks Version 520 User's Guide for information about the performanceattributes displayed in the OMEGAMON II for Mainframe Networks component.

The OMEGAMON II for Mainframe Networks component provides a 3270 CUA interface for monitoringSNA, NCP, VTAM, and TCP/IP performance. NetView Performance Monitor (NPM) providesperformance monitoring similar to that provided by OMEGAMON II for Mainframe Networks and isincluded in the OMEGAMON XE for Mainframe Networks packaging for use by existing NPMcustomers. The OMEGAMON XE for Mainframe Networks component provides a graphical interface formonitoring VTAM, High Performance Routing, Enterprise Extender, FTP, TN3270, OSA, IPSEC andTCP/IP performance data. The OMEGAMON XE graphical interface (Tivoli Enterprise Portal) can run indesktop mode and is also accessible from your internet browser.

OMEGAMON II and NPM are considered older technologies. For optimum performance, use theOMEGAMON XE for Mainframe Networks monitoring agent and Tivoli Enterprise Portal instead ofOMEGAMON II for Mainframe Networks or NPM.

If your primary goal is to monitor TCP/IP and VTAM resources, you should install and configure theOMEGAMON XE for Mainframe Networks monitoring agent. The OMEGAMON XE for MainframeNetworks monitoring agent provides a richer set of capabilities for monitoring TCP/IP and VTAM andtheir associated resources and it uses a much more efficient method of collecting TCP/IP data. TheOMEGAMON XE for Mainframe Networks monitoring agent uses the z/OS Communications Servernetwork monitoring interfaces (NMIs) to collect most of the TCP/IP data. The OMEGAMON II forMainframe Networks monitoring agent uses SNMP as it primary means of data collection, which is lessefficient and generates more CPU use than the NMIs. Additionally, OMEGAMON II does NOT support%INCLUDE statements as part of the TCP/IP profile. For example, if you created a TCP/IP profile thatincluded %INCLUDE statements, the OMEGAMON II agent will not process those statements, so it ispossible that OMEGAMON II might fail to calculate metrics correctly.

Collecting TCP/IP data using both OMEGAMON II for Mainframe Networks and OMEGAMON XE forMainframe Networks is not recommended. Using both products to collect TCP/IP data causes redundantdata, an increase CPU overhead, and ultimately has a negative impact on performance. If you arecurrently monitoring your TCP/IP environment with the OMEGAMON II monitoring agent, considerusing the OMEGAMON XE for Mainframe Networks monitoring agent instead. If you must run bothmonitoring agents, you should disable TCP/IP monitoring in the OMEGAMON II monitoring agent toavoid additional resource use. See Figure 39 on page 162 for information about the field in theConfiguration Tool where you set this value. See the KON_TCP_CONFIGURE_FLAG parameter used to set thisvalue in PARMGEN in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference.

However, in some cases, you may find it necessary to use OMEGAMON II or NPM:v If you want to monitor and analyze SNA response times, you should install the OMEGAMON II

component. OMEGAMON II for Mainframe Networks uses the End to End response time monitor(ETE) to collect response time data. The OMEGAMON XE for Mainframe Networks monitoring agentdoes not use the ETE facility and does not collect SNA response time data.


v If you want to monitor channel data for older VTAM transport protocols and virtual routes, this data isprovided by the OMEGAMON II monitoring agent or NPM. Additionally, the VTAM trace facility inOMEGAMON II enables you not just to start, run and view traces. If you have a need to browse MIBsOMEGAMON II provides this function. The OMEGAMON XE for Mainframe Networks monitoringagent provides support to monitor VTAM address space, I/O, Storage, Buffer Pools, HPR and EE butdoes not provide support for monitoring older VTAM transport protocols and virtual routes and doesnot provide access to the VTAM trace facility.

v If you want to monitor NCP performance, you may use the OMEGAMON II for Mainframe Networksagent or NPM. The OMEGAMON XE for Mainframe Networks monitoring agent does not provide afunction for monitoring NCP.

v If your enterprise requires SMF records to generate historical reports, OMEGAMON II and NPMgenerate SMF records to produce reports and graphs. OMEGAMON XE stores historical data in theTivoli Data Warehouse and uses Tivoli Enterprise Portal or Tivoli Common Reporting to producereports.

Appendix A, “Configuring the OMEGAMON II for Mainframe Networks component,” on page 155provides information about the components of OMEGAMON II for Mainframe Networks and the tasksfor configuring this component. To understand the parts of the OMEGAMON II for Mainframe Networks,see “Components of OMEGAMON II for Mainframe Networks that you configure” on page 155. Formore information about using OMEGAMON II for Mainframe Networks, see OMEGAMON II forMainframe Networks: User's Guide, OMEGAMON II for Mainframe Networks: Historical Reporting Guide, andOMEGAMON II for Mainframe Networks: NCP Monitoring Guide in the IBM Tivoli Monitoring andOMEGAMON Information Center.

If you are upgrading from a previous version of OMEGAMON II for Mainframe Networks within thesame runtime environment, the same profile and screen space data sets will be used.

If you are installing OMEGAMON II for Mainframe Networks in a new runtime environment, you canuse the migration utility provided by the Configuration Tool to migrate tables and data sets. See “Step 4:Run migration utility” on page 169 for more information.



Chapter 3. Preparing your z/OS environment

These z/OS environment setup tasks must be completed on z/OS system or LPAR where this monitoringagent is running.

To make the OMEGAMON XE for Mainframe Networks environment fully operational, you mustperform some z/OS environment setup. The following setup operations must be performed on eachz/OS system on which the OMEGAMON XE for Mainframe Networks monitoring agent will run.

Enabling the z/OS Communications Server network managementinterfaceOne of the configuration steps you must perform on every z/OS system where the monitoring agent willbe running is to enabled the z/OS Communication Server network management interface, for FTP, 3270,SNA, and IPSec.

z/OS Communication Server provides a set of network management interface (NMI) APIs that allownetwork management applications to programmatically obtain data in real time. To enable these interfacesto collect specific data types, you must update your TCP/IP profile and your VTAM start list.

Enabling FTP and TN3270 monitoring

Update your TCP/IP profile to include the following statement to activate the profile configurationoptions for FTP and TN3270 monitoring:NETMONitor SMFService

See the IBM z/OS Communications Server: IP Configuration Reference (SC31-8776) for more informationabout this statement.

If you modify the TCP/IP profile, you must stop and start TCP/IP for the changes to take effect.

Note: You can also use the VARY TCPIP,,OBEYFILE command to dynamically enable the real-time SMFinformation service. See the IBM z/OS Communications Server: IP System Administrator's Commands(SC31-8781) for information on how to use this command.

If you wish to collect TN3270 response time data, ensure that the BEGINVTAM block of your Telnetprofile, which is part of the BEGINVTAM block, includes a MONITORGROUP statement that applies themonitoring characteristics required by the OMEGAMON XE for Mainframe Networks monitoring agentto the set of resources in your organization that requires Telnet support. The MONITORGROUPstatement defines the parameters for monitoring the performance of connections mapped to this group.At a minimum, this statement must include these parameters: AVERAGE (indicates whether slidingaverages should be calculated) and BUCKETS (indicates whether time buckets are being used), as in thisexample:MONITORGROUP MONGRP1

AVERAGEBUCKETS

ENDMONITORGROUPMONITORMAP MONGRP1 Client_Identifier

where Client_Identifier is one of the client identifier types supported by z/OS Communications Server. Formore information about supported client identifiers, see the "Client identifier types and definitions" topicin the IBM z/OS Communications Server: IP Configuration Reference ( SC31-8776).


Note: Ensure that you specify Client_Identifier in a way that enables you to collect TN3270 response timedata for the desired sessions. See also the "No data in FTP and TN3270 workspaces" topic in the IBMTivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide.

To retrieve data for all TN3270 sessions, you can use the IPGROUP parameter, as shown in this example:IPGROUP IPALL 0.0.0.0:0.0.0.0 ENDIPGROUPMONITORGROUP MONGRP1AVERAGEBUCKETSENDMONITORGROUPMONITORMAP MONGRP1 IPALL

Enabling SNA monitoring

Update your VTAM start list (ATCSTRxx, if LIST=xx entered) to activate Communications StorageManager (CSM), Enterprise Extender (EE), and High Performance Routing (HPR) monitoring. Include thefollowing statement to activate the SNA NMI:SNAMGMT=YES

If you modify the VTAM start list, you must stop and start VTAM for the changes to take effect.

Note: You can also activate the SNA NMI dynamically using the following MODIFY command:F <vtam_procname>,VTAMOPTS,SNAMGMT=YES

where <vtam_procname> is the name of your VTAM procedure where the SNA NMI is to be activated.The response should look similar to the following example, indicating that the MODIFY statement wasaccepted:IST097I MODIFY ACCEPTEDIST223I MODIFY COMMAND COMPLETEDIST1925I SOCKET OPENED BY SNAMGMT SERVER SUBTASK

The MODIFY statement is in effect until you either restart VTAM or issue another MODIFY command tochange this setting.

Enabling IPSec monitoring

IPSec is enabled in the TCP profile data set. If your organization is using IP Security, then this update tothe TCP/IP profile data set should already have been made.

On each z/OS system where you will monitor IP filters and IPSec tunnels, the IKE daemon and PolicyAgent daemon must be started. The NMI for IP filters and IPSec tunnels is available for monitoringagents without updating the TCP/IP profile.

Enabling SNMP manager functionsThe SNMP manager agent and subagent must be active on every system where the monitoring agent isrunning.

The OMEGAMON XE for Mainframe Networks monitoring agent uses the Simple Network ManagementProtocol (SNMP) Management Information Base (MIB) to obtain TCPIP performance data. Both theOMEGAMON XE for Mainframe Networks monitoring agents and its OMEGAMON II componentrequire that the SNMP manager agent and subagent be active. The chapter about SNMP in the IBM z/OSCommunications Server: Configuration Guide (SC31-8775) explains the configuration procedure for runningthe TCP/IP SNMP agent and subagent. The chapter also explains how to automatically start the SNMPagent when TCP/IP starts.


The SNMP subagent, a task in the TCP/IP address space, is a z/OS UNIX system services applicationthat communicates with the SNMP agent using an AF_UNIX socket. Consequently, the AF_UNIX domainmust be configured in your BPXPRMxx member of SYS1.PARMLIB. Consult the BPXPRMxx chapter inthe IBM MVS Initialization and Tuning Reference for details about activating the AF_UNIX domain.

If your SNMP agent and subagent are not already configured and running, use the information in theIBM z/OS Communications Server: Configuration Guide to configure them. Steps 3 and 4 under “Verifyingthe z/OS environment setup” on page 62 tell you how to verify that this setup was performed correctly.

This setup is only part of the SNMP configuration task. The second part is performed after themonitoring agent is installed. The Configuration Tool creates sample SNMP system definition files andstores them in &hilev.&midlev.&rtename.RKANSAMU. These sample files are named KN3SNMP (forOMEGAMON XE for Mainframe Networks) and KONSNMP (for the OMEGAMON II for MainframeNetworks component), though you can use the same file for both agents by modifying the OMEGAMONII PROC to point to the KN3SNMP file. Edit the SNMP system definition file or files to add aconfiguration statement for each SNMP agent from which data will be collected (one per TCP/IP stack).You must create this configuration file and save it to the correct location before you can monitor andcollect TCP/IP data using the SNMP agent and subagent.v See Appendix E, “Format of the SNMP configuration file,” on page 289 for more information about the

format of the KN3SNMP (OMEGAMON XE) or KONSNMP (OMEGAMON II) SNMP configurationfile.

v See “Configuring the OMEGAMON XE for Mainframe Networks SNMP manager functions” on page136 for more information about SNMP validation in the "Complete the configuration" process for theOMEGAMON XE for Mainframe Networks monitoring agent.

v See “Authorize the OMEGAMON XE for Mainframe Networks started tasks for TCP/IP privileges” onpage 137 for more information about SNMP validation in the "Complete the configuration" process forthe OMEGAMON II for Mainframe Networks component.

Starting the OSA adapter SNMP subagentFollow these steps to start the OSA adatper SNMP subagent.

About this task

You can use OMEGAMON XE for Mainframe Networks to monitor the performance of the OSA adaptersin your environment. The OSA data is obtained from z/OS Communications Server SNMP subagents.Before you can collect OSA data, either the OSA-Express Direct SNMP subagent, or the TCP/IP SNMPsubagent and the OSA/SF application, must be configured and running. You should use the OSA-ExpressDirect SNMP subagent because it provides additional attributes not available from the TCP/IP SNMPsubagent, and does not require the OSA/SF applications.

To enable the OSA data support, perform the following steps:

Procedure1. Verify that the Licensed Internal Code of the OSA adapters meet the requirements listed in the

OMEGAMON XE for Mainframe Networks Program Directory.2. Configure and start the SNMP subagent.

v OSA-Express Direct SNMP subagent

The SNMP subagent for OSA-Express Direct SNMP subagent is started by using the catalogedprocedure, IOBSNMP. A sample IOBSNMP procedure can be found in z/OS CommunicationsServer target data set hlq.SEZAINST.

v TCP/IP SNMP subagent

To obtain the OSA data from the TCP/IP SNMP subagent, perform the following steps:

Chapter 3. Preparing your z/OS environment 61

a. Configure the subagent TCP/IP profile statement, SACONFIG.b. Configure and start the OSA/SF application (IOAOSASF) and the TCP/IP SNMP subagent

(IOASNMP). Sample cataloged procedures for these applications can be found in the OSA/SFtarget data set IOA.SIOASAMP.

3. Configure your TCP/IP profile to match your OSA configuration.v If you are using the TCP/IP SNMP subagent for OSA adapter data, specify OSAENABLED and

OSASF on the SACONFIG statement in your TCP/IP profile. Reserve a port on the PORTstatement. For example:SACONFIG OSAENABLED OSASF 721 COMMUNITY public

v Define the OSA adapter to TCP/IP using DEVICE and LINK or INTERFACE statements.4. If you are using the OSA-Express Direct SNMP subagent for OSA adapter data, install the OSA MIB

in the MIBS.DATA data set.

Results

For more information about configuring and starting the OSA subagent, see the following:v The section on configuring the Open System Adapter in z/OS Communications Server: IP Configuration

Guide Open Systems Adapter-Express Customer's Guide and Reference (SA22-7476).v Open Systems Adapter-Express Customer's Guide and Reference (SA22-7935).v OSA-Express MIB support is described at http://www.ibm.com/servers/resourcelink. After logging in,

select Library. Under Library shortcuts, select Open System Adapter (OSA) Library.v The OSA Redbook OSA-Express Implementation Guide (SG24-5948) is available at http://publib-

b.boulder.ibm.com/abstracts/sg245948.html?Open.

Verifying the z/OS environment setupSeveral short commands can verify that you have your environment set up correctly.

About this task

Issue the following commands to confirm the environment setup:

Procedure1. Verify that TCP/IP is configured correctly by issuing this command:

D TCPIP,<tcpip_procname>,NETSTAT,CONFIG

where <tcpip_procname> is the name of the TCP/IP stack that you want to monitor.These two lines should be included in the response that you receive:NETWORK MONITOR CONFIGURATION INFORMATION:PKTTRCSRV: YES TCPCNNSRV: NO SMFSRV: YES

The correct value for SMFSRV is critical for OMEGAMON XE for Mainframe Networks. If you receivethe response shown in the preceding example, then TCP/IP was configured successfully for thenetwork management interfaces (NMIs) used by OMEGAMON XE for Mainframe Networks. If youplan to use NetView for z/OS packet trace feature, then the values for the PKTTRCSRV TCP/IPparameters should be YES.

2. Confirm that the SNA NMI is enabled by issuing this command:D NET,VTAMOPTS,OPTION=SNAMGMT

SNA management is enabled if the following message is displayed:IST1189I SNAMGMT = YES

3. Confirm that the z/OS Communications Server SNMP Agent, OSNMPD, is configured correctly.


Note: If you have specified that OSA data should be collected using the Configuration Tool or thePARMGEN method, then perform this step. Ifyou have specified that OSA data should not becollected, then skip to Step 6 on page 64.Issue the z/OS UNIX snmp command from the UNIX System Services command line with thefollowing syntax:snmp —c <community_name> —h <host_name_name> -v get sysUpTime.0

where <community_name> and <host_name_name> are the SNMP community name and host name forthe z/OS system where you will be running the OMEGAMON XE for Mainframe Networksmonitoring agent. If OSNMPD is configured correctly, the sysUpTime value is displayed. This value isthe time in seconds that OSNMPD has been active. If the command times out, OSNMPD is notconfigured correctly.For the TCP/IP SNMP subagent, issue the z/OS UNIX snmp command from the UNIX SystemServices command line with the following syntax:snmp —c <community_name> —h <host_name_name> -v get ibmMvsTcpipProcname.0

where <community_name> and <host_name_name> are the SNMP community name and host name forthe z/OS system where you will be running the OMEGAMON XE for Mainframe Networksmonitoring agent. If the TCP/IP subagent is configured correctly, the name of the TCP/IP stack underwhich the subagent is running is displayed. If the command times out, or you receive a value ofnoSuchName or noSuchObject, then either OSNMPD is not configured correctly or the TCP/IP subagentis not active. Verify that the TCP/IP profile statement SACONFIG has been specified correctly.

Note: Only one SNMP Agent should be started per monitored TCP/IP stack.4. Verify that the SNMP subagent for OSA is started for each TCP/IP stack:

v OSA-Express Direct SNMP subagent

Issue the z/OS D A,L console command and verify that IOBSNMP is started. If the subagent is notstarted, start it. You can also look for this message on the console or in the JES log:IOB021I timestamp OSA SNMP subagent initialization complete.

To determine which TCP/IP stack the message applies to, look for this message in the JES log:IOB028I timestamp Using stack name TCP_procname

where timestamp is the time that the command was issued and TCP_procname is the name of theTCP/IP procedure used to start the stack.

v TCP/IP SNMP subagent and OSA/SF application

Issue the z/OS D A,L console command and verify that IOAOSASF and IOASNMP are started. Ifthey are not started, start them.

5. Confirm that the SNMP subagent for OSA is correctly configured.v OSA-Express Direct SNMP subagent

Issue the z/OS UNIX snmp command from the UNIX System Services command line with thefollowing syntax:snmp —c <community_name> —h <host_name_name> -v walk 1.3.6.1.4.1.2.6.188.1.1.1.1

If you receive a “No valid PDUs returned ” message, then the OSA-Express Direct SNMP subagentis not configured correctly.

v TCP/IP SNMP subagent

Issue the z/OS UNIX snmp command from the UNIX System Services command line with thefollowing syntax:snmp —c <community_name> —h <host_name_name> -v walk ibmMvsOsaExpChannelNumber


If you receive a “No valid PDUs returned ” message, then the TCP/IP SNMP subagent is notconfigured correctly.

6. On each z/OS system where you plan to monitor IP filters and IPSec tunnels, confirm that the IKEdaemon and Policy Agent daemon have started. For each stack that you plan to monitor IP filters andIPSec tunnels, also confirm that IP security is enabled.a. Verify that the IKE daemon and PAGENT daemon have started by issuing this command:

D A,L

This command displays what is running on your system. Look at the output of this command andvalidate that the procedure names for the IKE daemon (IKED) and the Policy Agent (PAGENT) arelisted. The output of this command will be similar to this:IEE114I 16.42.25 2009.119 ACTIVITY 312

JOBS M/S TS USERS SYSAS INITS ACTIVE/MAX VTAM OAS00005 00019 00001 00029 00010 00001/00300 00021LLA LLA LLA NSW S VLF VLF VLF NSW SJES2 JES2 IEFPROC NSW S VTAM VTAM VTAM NSW SORACF RACF RACF NSW S TSO TSO STEP OWT STCPIP TCPIP TCPIP NSW SO TN3270 TN3270 TN3270 NSW SOINETD4 STEP1 OMVSKERN OWT AO SYSLOGD8 STEP1 OMVSKERN NSW AORXSERVE RXSERVE RXSERVE OWT SO OSNMPD OSNMPD OSNMPD OWT SOFTPD1 STEP1 OMVSKERN OWT AO TCPCS2 TCPCS2 TCPCS2 NSW SOOSNMPD2 OSNMPD2 OSNMPD OWT SO TCPCS4 TCPCS4 TCPCS4 NSW SOTRMD1 STEP1 TRMD IN AO OSNMPD4 OSNMPD4 OSNMPD OWT SOTRMD1 STEP1 TRMD OWT AO IKED IKED IKED NSW SOPAGENT PAGENT PAGENT OWT SO IOBSNMP IOBSNMP IOBSNMP OWT SOCANSN3 CANSN3 AGENT NSW SO CANSDSST CANSDSST TEMS NSW SO

Note the highlighted lines. You can also search the log for the following messagesHASP373 PAGENT STARTEDIEF403I PAGENT - STARTED - TIME=15.09.32EZZ8431I PAGENT STARTINGEZZ8432I PAGENT INITIALIZATION COMPLETEEZZ8771I PAGENT CONFIG POLICY PROCESSING COMPLETE FOR image : typeEZD1059I IKE CONNECTED TO PAGENTEZD1058I IKE STATUS FOR STACK stack_name IS UPEZD1068I IKE POLICY UPDATED FOR STACK stack_nameEZD1133I IKE STATUS FOR STACK stack_name IS ACTIVE WITHOUT IPSECURITYSUPPORTEZD1128I IKE STATUS FOR STACK stack_name IS ACTIVE WITHOUT POLICYEZZ8771I PAGENT CONFIG POLICY PROCESSING COMPLETE FOR stack_name : IPSECEZD1046I IKE INITIALIZATION COMPLETEEZD1058I IKE STATUS FOR STACK stack_name IS UPEZD1068I IKE POLICY UPDATED FOR STACK stack_name

If the daemons have not started, start them. See the IBM z/OS Communications Server: IPConfiguration Guide (SC31-8775) for more information about the IKE daemon and Policy Agentdaemon. If the stack is up but does not have security enabled, you would see the followingmessage:EZD1133I IKE STATUS FOR STACK stack_name IS ACTIVE WITHOUT IPSECURITY

b. Verify that IP security is enabled for a stack by issuing this commandD TCPIP,<tcpip_procname>,NETSTAT,CONFIG

The response from this command includes information about the IP configuration table and theIPv6 configuration table. Search for IPSECURITY in these sections. A value of YES indicates thatIP security is enabled for IPv4, IPv6, or both. Here, for example, is an excerpt from a response thatindicates IP security is enabled for IPv4 and not for IPv6:IP CONFIGURATION TABLE:FORWARDING: YES TIMETOLIVE: 00064 RSMTIMEOUT: 00060IPSECURITY: YES


...

IPV6 CONFIGURATION TABLE:FORWARDING: YES HOPLIMIT: 00255 IGREDIRECT: NOSOURCEVIPA: NO MULTIPATH: NO ICMPERRLIM: 00003IGRTRHOPLIMIT: NOIPSECURITY: NO

Defining monitoring agent access to the NMI and commandsEdit and run the KN3UAUTH job to give the monitoring agent access to the commands used to collectdata and the commands issued on behalf of Tivoli Enterprise Portal user.

Some security configuration is required to grant the OMEGAMON XE for Mainframe Networksmonitoring agent access to the z/OS Communications Server network manager interface (NMI)application programming interfaces and to commands. The monitoring agent must have access to one ormore of these management interfaces depending on the data you want collected:v SNA network monitoringv Local IPSecv Real-time SMF data

The monitoring agent must also be given access to commands used to collect data and commands issuedon behalf of Tivoli Enterprise Portal users. Give access to the monitoring agent by editing and runningthe KN3UAUTH job created in “Define monitoring agent access to the network management interfacesand commands” on page 128.



Chapter 4. Upgrading to the new release

Consider these topics as you plan to upgrade an existing monitoring agent.

The IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guide covers upgraderequirements and instructions common to all the OMEGAMON XE products, including:v Required versions of Tivoli Monitoring Server componentsv Requirements for staged upgradesv Instructions for upgrading in-place and in a new CSIv An example scenario for using batch mode to roll out an upgrade

This section contains topics to consider if you currently have one or more OMEGAMON monitoringagents in your environment. It includes an overview of the upgrade process and information specific toOMEGAMON XE for Mainframe Network upgrades.

Upgrade overviewUpgrade scenarios include upgrades from versions 4.1.0 and 4.2.0, and 5.1.0, all fix pack levels

The OMEGAMON XE for Mainframe Networks V5.1.1 monitoring agent is equivalent to Version 5.1.0with APARs OA42339 and OA42422 applied. You can upgrade from OMEGAMON XE for MainframeNetworks V5.1.0 by installing the PTFs and fix pack that are associated with APARs OA42339 andOA42422, or you can upgrade from V4.1.0 or later by ordering and installing OMEGAMON XE forMainframe Networks V5.1.1 PID: 5698-T03. If you have enabled the self-describing agent feature, and youdo not use the Tivoli Enterprise Portal desktop client, you do not need to install the distributed fix packthat goes with the APARs. Refer to the Version 5.1.1 Program Directory for pre-requisites and installationinstructions.

The OMEGAMON XE for Mainframe Networks V5.1.0 monitoring agent requires Tivoli ManagementServices V6.2.3 Fix Pack 1 with APAR OA39890 or later applied. If you are not currently running at therequired level, you must, at a minimum, upgrade the Tivoli Enterprise Portal desktop client, the TivoliEnterprise Portal Server, and the hub Tivoli Enterprise Monitoring Server to V6.2.3 Fix Pack 1 before youinstall your first OMEGAMON XE V5.1.0 monitoring agent. Upgrade your monitoring agents and anyTivoli Enterprise Monitoring Server the agents report to. In addition, upgrade the Tivoli Data Warehousecomponents at the same time you upgrade the Tivoli Enterprise Portal Server. All OMEGAMON XEV5.1.0 monitoring agents support a staged migration.

This means that as you are migrating from OMEGAMON XE V4.1 or V4.2 products (running TivoliManagement Services V6.2.3 Fix Pack 1 or higher) to OMEGAMON XE V5.1 products, you can have acombination of V4.1 and V5.1 monitoring agents installed in your environment. For example, you mighthave an OMEGAMON XE for Mainframe Networks V5.1 monitoring agent on one z/OS system (orLPAR) and an OMEGAMON XE for Mainframe Networks V4.1 or V4.2 monitoring agent on anothersystem. You might also have an OMEGAMON XE for Mainframe Networks V5.1 monitoring agent andan OMEGAMON XE for Mainframe Networks V4.1 or V4.2 monitoring agent on the same z/OS system.Note that you should install the application support files for the highest-level OMEGAMON XEmonitoring agent at the Tivoli Enterprise Portal Server and at the hub Tivoli Enterprise MonitoringServer.

These Tivoli Management Services environment upgrade scenarios are documented:v Path A: Upgrading from Tivoli Management Services V6.2.x and OMEGAMON XE with self-describing

agent feature enabled


Note: You cannot upgrade from V4.1 to V5. Upgrade from V4.1 to V4.2 first, and then upgrade fromV4.2 to V5.1.

v Path A1: Integrating self-describing OMEGAMON XE agents into an existing Tivoli Monitoring V6.2.3FP1 (or later) environment

v Path B: Upgrading from Tivoli Management Services V6.2.x to OMEGAMON XE withoutself-describing agent capability

These scenarios are covered in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS:Upgrade Guide.

Upgrading to the new releaseIn addition to the common upgrade requirements documented in the OMEGAMON XE and TivoliManagement Services on z/OS: Upgrade Guide, these technology updates might affect your upgrade plans.v “Configuring a high availability hub and converting a static hub to a remote”v “Enabling new features”v “Performing a staged upgrade” on page 70

Configuring a high availability hub and converting a static hub to aremoteIf you intend to enable the self-describing agent (SDA) feature, and you have an agent configured to runin the hub monitoring server address space, configure a high availability (HA) hub on the LPAR andconvert the static hub to a static remote monitoring server that connects to the new HA hub. In addition,you must reconfigure all the remote monitoring servers that connected to the previous hub to connect tothe new HA hub.

For instructions on configuring an HA hub, see the IBM Tivoli Monitoring: Configuring Tivoli EnterpriseMonitoring Server on z/OS.

To convert a static hub to a remote, you must make the following changes:v Change TCP communication values for the monitoring server:

– The name or IP address of the hub– The port of the HA hub

v Change the type of the local monitoring server type from hub to remote.v Change the hub type that the remote connects to HA Hub.v If the static hub was excluded from proxy eligibility, change it to proxy eligible.v Set the virtual IP address type for connecting to the hub.v Add TEMS network interface list support.

Complete the steps appropriate to the configuration method you are using. If you are using thePARMGEN configuration method, see scenario 4 in the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: PARMGEN Reference.

Enabling new featuresIf you are upgrading from OMEGAMON XE for Mainframe Networks V4.2.0.x to V5.1.0 or later, you donot need to reconfigure the Tivoli Enterprise Monitoring Server or the OMEGAMON XE on z/OSmonitoring agents. You can simply accept the defaults and build and load the runtime libraries for theruntime environment.

However, if you want to use the self describing agent (SDA) feature, you must do the following tasks:v Enable SDA on the hub monitoring server


v If your monitoring server is running on z/OS, specify the UNIX System Services directory from whichthe SDA packages are to be copied for each runtime environment in which an OMEGAMON XE onz/OS monitoring agent is running.

v If your monitoring server is running on a distributed platform, see the "Maintaining monitoringagents" topic in the IBM Tivoli Monitoring: Administrators Guide and https://www.ibm.com/developerworks/community/wikis/home?lang=en#%21/wiki/Tivoli+Monitoring/page/Best+practice+for+ITM+6.2.3+SDA+on+Linux+and+Unix for more information.

If you want to control access to OMEGAMON XE for Mainframe Networks managed systems from theOMEGAMON enhanced 3270 user interface or use the new product-provided Take Action commands,you must create resource profiles for the security class that controls them.

Enabling SDA

By default, support for self describing agents is disabled on the hub monitoring server. To use thisfeature, you must enable it on the hub monitoring server and configure each runtime environment inwhich an OMEGAMON XE for Mainframe Networks monitoring agent is running to support it. Toenable SDA on the hub monitoring server, see IBM Tivoli Monitoring: Configuring the Tivoli EnterpriseMonitoring Server on z/OS.

The new Tivoli Enterprise Portal workspaces created during the v5.1.1 release caused the size of theTivoli Enterprise Portal Server bundle file to grow. SDA fails because the FTP facility cannot process thebundle file unless the value for the ITMS:Engine LIMIT parameter is increased.

If you used the Configuration Tool to configure the monitoring agent, use the SPECIFY NONSTANDARDPARAMETERS dialog to specify this update.

If you reconfigured after you applied this APAR using PARMGEN, this problem was addressedautomatically but you must run the PARMGEN KCIJPCFG job to set up the PARMGEN workenvironment for the RTE and pick up the new LIMIT value.

See the "Self-describing agent function fails after application of APARs OA42339 and OA42422"troubleshooting item in IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide formore information.

To understand other changes to SDA behavior in v5.1.1 that might affect your upgrade, see the"Self-describing agent installation of the OMEGAMON for Mainframe Networks application support filesfails in an IBM Tivoli Monitoring v6.3.0 environment" troubleshooting item.

Securing the OMEGAMON XE for Mainframe Networks managed systems and TakeAction commands

The SAF security class specified for the runtime environment (RTE_SECURITY_CLASS) controls logon accessto the OMEGAMON enhanced 3270 user interface. It also controls authorization to view data frommanaged systems and attribute groups in the interface, and the authority to execute OMEGAMON XE forMainframe Network Take Action commands from either the OMEGAMON enhanced 3270 user interfaceor the Tivoli Enterprise Portal interface.

For security to be enforced, resource profiles must be defined to the class. If a matching SAF profile doesnot exist to protect queries (data collection) from a particular OMEGAMON XE for Mainframe Networksmanaged system or attribute group, all user IDs are allowed to issue the queries. Before you can createresource profiles that restrict access to OMEGAMON XE for Mainframe Networks managed systems, youmust be familiar with the form of OMEGAMON XE for Mainframe Networks managed system names.

If a matching SAF profile does not exist to protect a given agent Take Action command, the request totransmit an action to the managed system is denied. To create resource profiles to control OMEGAMON

Chapter 4. Upgrading to the new release 69

https://www.ibm.com/developerworks/community/wikis/home?lang=en#%21/wiki/Tivoli+Monitoring/page/Best+practice+for+ITM+6.2.3+SDA+on+Linux+and+Unix



XE for Mainframe Networks Take Action commands, you need to know the resource names of thecommands. In addition, if you are using the SAF class name override parameterKN3_SECURITY_ACTION_CLASS to override the SAF security class name for Take Action commands, youmust also create resource profiles for the override class.

OMEGAMON XE for Mainframe Networks product-provided Take Action commands are not affected bythis issue.

For more information, see “Authorizing users to access OMEGAMON XE for Mainframe Networksmanaged systems on the enhanced 3270 user interface” on page 141 and “Prefixed Take Actioncommands” on page 141.

New security compatibility mode for encrypted facilities

Tivoli Management Services V6.3.0 introduced command security restrictions. V6.3.0 Fix Pack 1 providesremediation measures to help migrate to the enhanced command security. The security compatibilitymode has been enhanced to allow commands to execute even if cryptographic facilities are not available.

Starting with V6.3.0, command requests (Take Action commands, situation actions, workflow policyactions, and so forth) are required to include an encrypted security token. To assist in migration, asecurity compatibility mode was provided to allow components that do not yet support tokens to issuecommands without a token. If compatibility mode is enabled, the monitoring server generates a defaultsecurity token. Because security tokens are encrypted to prevent tampering as they are passed betweencomponents, the enhanced command security feature requires access to local cryptographic functions.

In V6.3.0, if encryption facilities were not enabled, the command failed even if compatibility mode wasenabled. However, starting with Fix Pack 1, if compatibility mode is enabled, commands are allowed toexecute even if cryptographic facilities are not available. Now, if compatibility mode is enabled(KMS_SECURITY_COMPATIBILITY_MODE=Y), checking for encrypted command tokens is automatically disabled.

Compatibility mode still requires that the encryption keys be synchronized across all infrastructure andagents for commands to execute properly. If your RTE contains a monitoring server, the synchronizationof encryption keys is handled using the value specified for RTE_SECURITY_KAES256_KEY. The commonagent configuration has been enhanced to allow an agent-only RTE to customize the TMS:Enginepassword encryption key (RKANPARU(KAES256)) and provides a standalone KAES256 encryption job(RKANSAMU(KDSDKAES)) for an agent-only RTE. For more information about this securitycompatibility mode and its implementation in PARMGEN, see the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS Version 6.3.0 FP1 Common Planning and Configuration Guide.

Performing a staged upgradeTo make product upgrades easier, OMEGAMON XE for Mainframe Networks supports upgrading agentsgradually, by allowing a mixture of monitoring agents of the current version and the previous version inthe same environment.

You can deploy new monitoring agents to your z/OS systems along with older monitoring agents of thesame product, during an upgrade transition period. If you are upgrading from a release prior to V4.1.0,you must upgrade to V4.2.0 or higher before upgrading to V5.1.0.

Important: To operate in a mixed environment, monitoring agents must have the correct maintenanceapplied. Check the OMEGAMON XE for Mainframe Networks V5.1.0 Preventative Services Planning(PSP) bucket for the required PTFs.


Upgrade considerations for the OMEGAMON XE for MainframeNetworks monitoring agentAs you upgrade your OMEGAMON XE for Mainframe Networks monitoring agents from an earlierversion to V5.1.0, use the following guidelines:v “Upgrading a persistent data store”v “Migrating historical data in the Tivoli Data Warehouse for Tivoli Enterprise Portal”v “Upgrade issues related to SNMP configuration”v “Upgrade issues related to running different product versions” on page 72

Upgrading a persistent data storeWhen you upgrade your Tivoli Enterprise Monitoring Server, the data set allocation values that weredefined in a previous release will likely need to be changed.

Determine your persistent data store allocation values by using the information in Appendix D, “Diskspace requirements for historical data tables,” on page 257. If persistent data store allocation values needto be modified, delete any existing OMEGAMON XE for Mainframe Networks persistent data store datasets so that these data sets can be reallocated with the correct size during configuration of the product.

History situations that use the persistent data store operate correctly without change. The persistent datastore automatically adds columns to short-term historical record when CATs, ATRs, and PDICTs areupdated. No reformatting of the persistent data store data sets is required.

Migrating historical data in the Tivoli Data Warehouse for TivoliEnterprise PortalWhen you enable long-term historical collection for a table, the warehouse proxy creates tables in theTivoli Data Warehouse.

The tables are created when long-term historical collection is first enabled for a table. When you upgradeto a new release of OMEGAMON XE for Mainframe Networks, the tables that were created in Tivoli DataWarehouse must be updated to contain columns for all the current attributes or the tables must bedropped from the Tivoli Data Warehouse.

Data in the Tivoli Data Warehouse is migrated automatically. No action on your part is required.

Upgrade issues related to SNMP configurationThe way you configure SNMP has changed recently. You need to set up a configuration file that can beshared by OMEGAMON XE and OMEGAMON II.

The Simple Network Management Protocol (SNMP) engine used to collect data was modified in theOMEGAMON XE V4.1 and OMEGAMON II V560 products. An updated sample started task procedurefor both of these products will be generated during configuration using the Configuration Tool orPARMGEN.

Starting in V4.1 and OMEGAMON II V560, a sample SNMP configuration file is generated during theinitial configuration of the monitoring agent. This file must be customized for your environment. TheKN3SNMP DD card of your OMEGAMON XE for Mainframe Networks or the KONSNMP DD card ofyour OMEGAMON II for Mainframe Networks started task procedure must point to the SNMPconfiguration file. Failure to copy these updated started task procedures to your PROCLIB data set willresult in the monitoring agent not collecting any SNMP data.

Note: You can share the same SNMP configuration file between OMEGAMON II for MainframeNetworks and OMEGAMON XE for Mainframe Networks. Sharing the same SNMP configuration file


could make it easier for an administrator to maintain the list of TCP/IP stacks that each application isconfigured to monitor. A shared configuration can be achieved by altering either the KN3SNMP DD cardOMEGAMON XE for Mainframe Networks start procedure or the KONSNMP DD card in theOMEGAMON II for Mainframe Networks start procedure to use the same SNMP configuration file. Notethat OMEGAMON II for Mainframe Networks has no IPv6 support, so entries with IPv6 addresses areonly read and checked for syntax, not used by OMEGAMON II for Mainframe Networks to obtain SNMPagent information.

For more information about the format of the SNMP configuration file, see Appendix E, “Format of theSNMP configuration file,” on page 289.

Upgrade issues related to running different product versionsBe prepared for some unanticipated behaviors in a mixed environment (not all components at the samelevel) that might be found during an upgrade.

Tivoli Management Services supports running a mixture of V4.1, V4.2, and V5.1 monitoring agents inyour environment during an upgrade period. The expectation is that a single Tivoli Enterprise Portalclient can be used to monitor all systems, independent of the version of the monitoring agent. At startup,the monitoring agents identify their versions with the Tivoli Enterprise Monitoring Server, TivoliEnterprise Portal Server, and Tivoli Enterprise Portal. The version determines the attributes that themonitoring agent can provide. This version identification enables the Tivoli Enterprise Portal toconditionally select version-specific objects for Managed System Lists, Situations, Queries, Policies, andWorkspaces.

When users of the enhanced 3270 user interface run multiple versions of OMEGAMON agents during astaged upgrade period, they might experience operational limitations. The common upgrade guidesummarizes related operational considerations by product. See the "Running the products in a mixedenvironment" topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: UpgradeGuide for more information.

Upgrading an existing OMEGAMON II for Mainframe NetworksenvironmentMigrating OMEGAMON II for Mainframe Networks is aided by a configuration utility. If you aremonitoring TCP/IP, consider having TCP/IP collection performed by the OMEGAMON XE forMainframe Networks monitoring agent.

OMEGAMON II for Mainframe Networks can be used to collect TCP/IP, VTAM, SNA and NCP data.OMEGAMON XE for Mainframe Networks V4.1 or later collects TCP/IP performance data in a moreefficient manner. If you are monitoring TCP/IP, consider having TCP/IP collection performed by theOMEGAMON XE for Mainframe Networks monitoring agent.

Likewise, V4.1 or later of OMEGAMON XE for Mainframe Networks collects performance metrics forSNA and VTAM that were previously available only in the OMEGAMON II for Mainframe Networkscomponent. For an overview of all the metrics monitored by OMEGAMON XE for Mainframe Networks,see the Attributes appendix in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli EnterprisePortal User's Guide. If these metrics address your SNA and VTAM performance monitoring needs,consider having VTAM and SNA collection performed by the OMEGAMON XE for Mainframe Networksmonitoring agent.

OMEGAMON II for Mainframe Networks thresholds can be created as OMEGAMON XE for MainframeNetworks situations, which are more powerful and flexible.


"Prepare User Libraries" configuration utility (migration consideration only)

Since V560 of OMEGAMON II for Mainframe Networks, the Configuration Tool supports the allocationof new user libraries required for product operation.

To access the new libraries using the Configuration Tool, from the Main Menu, select Configure products> Services and utilities > Prepare User Libraries. The Prepare User Libraries utility displays the"Runtime Environments (RTEs) for Conversion" (KCIPSP01) panel that lists all the RTEs in thisinstallation environment with exception of Base RTEs. You can prepare user libraries for the default RTElisting (all RTEs) or delete RTEs you want to exclude from the conversion process.

When you are done, press Enter to generate the INSTJOBS(KCIJSP01) job. This job allocates the applicablenew user libraries for each RTE listed. See the Configuration Services and Utilities online help for moreinformation. See also “Step 4: Run migration utility” on page 169.

To access the new libraries using PARMGEN, migrate to V4.2.0 using the Configuration Tool first, andthen use your newly updated V4.2.0 RTE and migrate to PARMGEN. See "Scenario PGN06: clone anexisting environment to run on a different LPAR" in the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: PARMGEN Reference for information about performing this task.



Chapter 5. Configuration

Use this information to understand the flow of task for configuring the OMEGAMON XE for MainframeNetworks monitoring agent.

If you are deploying and configuring the components of the Tivoli Management Services environment forthe first time, or if you are using previous versions of OMEGAMON II for Mainframe Networks orOMEGAMON XE for Mainframe Networks, you will find these sections very useful. The sections thatfollow walk you through the process of setting up the OMEGAMON XE for Mainframe Networksmonitoring agent in the best configuration for running these monitoring agents: in an environment wherethe monitoring server is running on z/OS in a separate address space from the monitoring agent, asshown in Figure 4.

Before you begin to configure OMEGAMON XE for Mainframe Networks, ensure that you havecompleted the tasks listed in Table 13.

Table 13. Preconfiguration tasks

Task Location of information

v Complete any preinstallation requirements. IBM Tivoli OMEGAMON XE Products: PreinstallationRequirements and Instructions

v Verify that you have the required software and DASD.v Install the product.

IBM Tivoli OMEGAMON XE for Mainframe Networks:Program Directory

Figure 4. Typical configuration for deployment of the OMEGAMON XE for Mainframe Networks monitoring agent




Table 13. Preconfiguration tasks (continued)

Task Location of information

v Read the planning information and make anynecessary planning decisions.

v Review information on batch processing and systemsymbolics, so your first runtime environment isappropriate for replication.

v Set up the runtime environment and allocate theruntime libraries.

IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide

v Configure the Tivoli Enterprise Monitoring Server inthe runtime environment.

IBM Tivoli Management Services on z/OS: Configuring theTivoli Enterprise Monitoring Server on z/OS

v Configure your Tivoli Management Servicesenvironment and this monitoring agent using thePARMGEN configuration method.

v IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: PARMGEN Reference to understandPARMGEN scenarios

v IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and ConfigurationGuide for the PARMGEN procedure

v IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Parameter Reference for explanations forcommon parameters

v IBM Tivoli OMEGAMON XE for Mainframe Networks:Parameter Reference for explanations of configurationparameters for this monitoring agent

v Configure the enhanced 3270 user interface. IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration Guide

v Configure SAF security for Take Action commands. IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and Configuration Guidefor general tasks and “Authorizing users to issue TakeAction commands” on page 141 for OMEGAMON XE forMainframe Networks tasks

After completing these tasks, you are ready to configure this monitoring agent. You can configure theOMEGAMON II for Mainframe Networks component (optionally) and OMEGAMON XE for MainframeNetworks (required) using these chapters:v Chapter 6, “Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method,” on

page 77 has information about configuring the OMEGAMON XE for Mainframe networks monitoringagent using the PARMGEN method (the preferred method).

v Chapter 7, “Configuring the monitoring agent using the Configuration Tool,” on page 87 hasinstructions for configuring the OMEGAMON XE for Mainframe networks monitoring agent using theConfiguration Tool.

v Chapter 8, “Completing the configuration,” on page 127 describes the tasks you must perform outsidethe Configuration Tool to complete the configuration of OMEGAMON XE for Mainframe Networks.You can delay performing these tasks until you have finished configuring all additional monitoringagents on z/OS in the Configuration Tool.

v “Verifying configuration if you configured both Tivoli Enterprise Portal and the enhanced 3270 userinterface” on page 149 contains instructions for validating the configuration of OMEGAMON XE forMainframe Networks.


Chapter 6. Configuring OMEGAMON XE for MainframeNetworks using the PARMGEN method

You configure OMEGAMON XE for Mainframe Networks by accepting or customizing the values ofparameters that begin with KON ( OMEGAMON II components) and KN3 (OMEGAMON XE component).

You configure the OMEGAMON XE component of the monitoring product to define enterprise-levelentities, install product-specific data on the Tivoli Enterprise Monitoring Server, and register theOMEGAMON XE for Mainframe Networks monitoring agent to the Tivoli Enterprise Monitoring Serveraddress space. You also configure the persistent data store for the product historical data and allocate thedata sets to store enterprise data. These parameters are specified in the KN3 section of the PARMGENconfiguration profile.

Default values are provided for all required parameters and some optional ones. If you do not want tocustomize these parameters, and you do not want to enable optional features, you can complete theconfiguration by accepting these defaults. Alternatively, you can specify custom values. You can alsospecify custom values for optional parameters that have no defaults. You must specify values for theseparameters in order to activate those features.

If you are migrating from OMEGAMON XE for Mainframe Networks version 4.2.0 or later, you can usethe PARMGEN configuration method. To use PARMGEN with older versions of OMEGAMON XE forMainframe Networks, you must first use the Configuration Tool to migrate to version 4.2.0 or later.

For guidance on setting parameter values, see the following sources of information:v Comments in the configuration profilesv Online help for the configuration profile

If the supplied KCIRPLBS macro has been copied to your SYSPROC concatenation, you can enter TSOKCIRPLBS at the ISPF command line to run the help macro. Place the cursor anywhere on the line thatcontains the parameter for which you want help text displayed, and press PF14.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: PARMGEN Reference

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Parameter Reference

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference.

After you configure the OMEGAMON XE for Mainframe Networks agent using the PARMGEN method,complete the tasks listed in Chapter 8, “Completing the configuration,” on page 127.

Table 14. Tasks to complete before configuring OMEGAMON XE for Mainframe Networks

Configuration task Location of instructions

Set up PARMGEN work libraries for the runtimeenvironment.

IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: Common Planning and ConfigurationGuide

Set up the PARMGEN configuration profile for theruntime environment.


Configure a Tivoli Enterprise Monitoring Server onz/OS.

IBM Tivoli Management Services on z/OS: Configuring theTivoli Enterprise Monitoring Server on z/OS and IBM TivoliOMEGAMON XE and Tivoli Management Services on z/OS:Common Parameter Reference


Table 14. Tasks to complete before configuring OMEGAMON XE for Mainframe Networks (continued)

Configuration task Location of instructions

(Optional) Configure the End-to-End Response Timecollector.

IBM Tivoli Management Services on z/OS: Configuring theTivoli Enterprise Monitoring Server on z/OS and IBM TivoliOMEGAMON XE and Tivoli Management Services on z/OS:Common Parameter Reference

The End-to-End Response Time collector is required foruser response time data.

(Optional) Configure the OMEGAMON enhanced 3270user interface address space.


Note: You only need to configure one OMEGAMONenhanced 3270 user interface address space. If you havealready configured this address space for another version5.1.0 OMEGAMON monitoring agent on z/OS, you donot need to repeat this configuration step.

Tip: If you are enabling self describing agents, configure a stand-alone high-availability hub monitoringserver. Installing a high-availability hub lets you apply maintenance or upgrades without recycling thehub. If you have an existing static hub to which agents report, convert the hub to a remote and configureall the remotes to report to the new high-availability hub.

After you have configured OMEGAMON XE for Mainframe Networks (and any other agents you want toconfigure) using the runtime environment profile, you must complete several configuration tasks outsideof the profile. See Chapter 8, “Completing the configuration,” on page 127.

Configuring the enhanced 3270 user interface using the PARMGENmethodYou configure the Enhanced 3270 User Interface using the rtename configuration profile for the runtimeenvironment.

To configure the interface, you can accept the defaults or specify site-specific values for the started taskname, the VTAM node definition, and the VTAM applid in the following section:* ******************************************************************KOB$ BEGIN *---- Tivoli OMEGAMON Enhanced 3270 User Interface ----*** ============================ ================================** PARMLIB CONFIG Parameter PARMLIB CONFIG Value** ============================ ================================

** Tivoli OMEGAMON Manager (TOM) started task options:KOB_TOM_STC CANSTOM * STC nameKOB_TOM_VTAM_NODE CTDOBN * VTAM nodeKOB_TOM_VTAM_APPL_LOGON CTDOBAP * VTAM logon applid

KOB$ END *---- Tivoli OMEGAMON Enhanced 3270 User Interface ----*

where:

KOB_TOM_STCIs the name of the interface started task.

KOB_TOM_VTAM_NODEIs the name of the VTAM major node used by the Enhanced 3270 User Interface.


KOB_TOM_VTAM_APPL_LOGONIs the VTAM logon applid used by the interface.

After configuring all the components and agents in the runtime environment, you complete theconfiguration by submitting the PARMGEN jobs and completing the required "Complete theconfiguration" steps. If you are configuring other products in this runtime environment, you can performthese steps after you completed all configuration. These steps include:v Copy the OMEGAMON Enhanced 3270 User Interface started task from WKANSAMU to PROCLIB.v Copy the VTAM major node from WKANSAMU to VTAMLST.v Vary the VTAM major node active.v APF-authorize the following load libraries (if this is a full runtime environment):

– &hilev.&rte.RKANMODU– &hilev.&rte.RKANMOD– &hilev.&rte.RKANMODP

See Chapter 8, “Completing the configuration,” on page 127 for more information about these tasks.

Note that if you run the WKANSAMU(KCIJcSYS) job (where c = P if SYSV is not enabled; V if SYSV isenabled), all the STCs and VTAM major nodes are copied to the system libraries that are specified for theGBL_DSN_SYS1_* parameter in the configuration profile. If you are using the global VTAM node(RTE_VTAM_GBL_MAJOR_NODE parameter), you can use the WKANSAMU(ccccAPF) imbed member toVARY the node and APF authorize the load libraries. To use ccccAPF, uncomment the placeholder INAPFINCLUDE statement in each started task://******************************************************************//* Uncomment out the INAPF statement if are using this composite//* member to APF-authorize the libraries concatenated in the//* STEPLIB and RKANMODL DDNAMEs.//*INAPF INCLUDE MEMBER=CANSAPF

If you are using a local node, you must VARY the node active and authorize the libraries yourself.

Mainframe Networks configuration parametersThe parameters used by this monitoring agent for the PARMGEN configuration method are groupedlogically in the configuration profile.

With the PARMGEN configuration method, you edit a comprehensive list of parameters for configuringall installed products and components. You then submit a series of jobs to create a complete runtimeenvironment with the parameter values that you specified.

If you are an existing Configuration Tool user and already have a runtime environment, you can convertit to PARMGEN. See the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGENReference for information about migrating to PARMGEN.

These parameters are found in the configuration profile, which can be generated from an existing RTE. Ifyou installation is new or if you do not want to base the configuration profile on an existing RTE, adefault configuration profile is provided and can be edited. Refer to the IBM Tivoli OMEGAMON XE andTivoli Management Services on z/OS: PARMGEN Reference to understand the other scenarios for usingPARMGEN.

In the configuration profile, the OMEGAMON XE parameters are organized into the groups found inTable 15 on page 80. The most important two groups of parameters for configuring this monitoring agentare the Agent Parameters that set the global values for all configurable parameters that are unique to thismonitoring agent and the Define TCP monitoring systems member parameters that set the stack-specific

Chapter 6. Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method 79

values that override the global parameters. For comprehensive information about these parameters, seethe IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference.

Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configurationprofile

PARMGENclassification Parameters in this group Explanation

AdditionalOMEGAMON XEfor MainframeNetworks Agentsettings

v KN3_X_AGT_CONFIRM_SHUTDOWNv KN3_X_AGT_KDC_DEBUGv KN3_X_AGT_DEBUG_TRACEv KN3_X_AGT_LGSA_VERIFYv KN3_X_AGT_LSRPOOL_BUFFER_NUMv KN3_X_AGT_LSRPOOL_BUFSIZEv KN3_X_AGT_SDUMP_SVC_SYS1_DUMPv KN3_X_AGT_STORAGE_LIMIT_EXTENDv KN3_X_AGT_STORAGE_LIMIT_PRIMARYv KN3_X_AGT_STORAGE_RESERVE_EXTv KN3_X_AGT_STORAGE_RESERVE_PRIv KN3_X_AGT_STORAGE_STGDEBUGv KN3_X_AGT_TASKS_ATTACHED_NUMv KN3_X_SECURITY_USER_EXITv KN3_X_SECURITY_RESOURCE_CLASS

Specifies settings for initializing TivoliMonitoring: Services (TMS: Engine).These values are usually found in theKN3SYSIN member in therhilev.midlev.rtename. RKANPARU libraryand are usually updated only with theassistance of IBM Software Support.

Advanced Agentconfigurationvalues

v KN3_AGT_FLUSH_LSR_BUFR_INT_HRv KN3_AGT_FLUSH_LSR_BUFR_INT_MINv KN3_AGT_ICU_LANGUAGE_LOCALEv KN3_AGT_KGL_WTOv KN3_AGT_KLX_TCP_TOLERATERECYCLEv KN3_AGT_STORAGE_DETAIL_INT_HRv KN3_AGT_STORAGE_DETAIL_INT_MINv KN3_AGT_STORAGE_MINIMUM_EXTENDv KN3_AGT_VIRTUAL_IP_ADDRESSv KN3_AGT_VTAM_APPL_NCSv KN3_AGT_WTO_MSG

Specifies a wide range of essential agentconfiguration parameters, includingparameters that define where consolemessages are displayed, whether TCP/IPcan be recycled, language of the interface,virtual addresses, and storage-relatedvalues.

Agentnonstandardparameters

v KN3_AGT_NSNEWn_VALUEv KN3_AGT_NONSTDn_DSNv KN3_AGT_NONSTDn_MBRv KN3_AGT_NONSTDn_PARMv KN3_AGT_NSOLDn_VALUE

Nonstandard parameters arecustomer-defined or hidden options thatdo not correspond to fields in theConfiguration Tool interactive panels.This set of parameters defines the valuesrequired to establish a nonstandardparameter. Create these parameters underthe guidance of IBM Software Support.


Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configurationprofile (continued)


Agent parameters:TCP/IPinformation

v KN3_SNA_VTAM_COLLECT_DATAv KN3_SNA_VTAM_SNAC_SNACINTVv KN3_SNMP_CONFIG_FILEv KN3_TCP_ALLHPRv KN3_TCP_COLLECT_STACKv KN3_TCP_CONNv KN3_TCP_CSMv KN3_TCP_EEHPRv KN3_TCP_FTPv KN3_TCP_FTP_DSPINTVv KN3_TCP_GLBSv KN3_TCP_INTEv KN3_TCP_INTv KN3_TCP_IPSECv KN3_TCP_OSAv KN3_TCP_ROUTE_TBLv KN3_TCP_ROUTE_TBL_FREQv KN3_TCP_SAMPLE_INTERVALv KN3_TCP_TN3270v KN3_TCP_TN3270_DSPINTVv KN3_TCP_VIO_UNIT

Sets the global values for all configurableparameters that are unique to theOMEGAMON XE for MainframeNetworks monitoring agent.

Agent's Applids v KN3_AGT_VTAM_APPL_AAv KN3_AGT_VTAM_APPL_KN3INVPOv KN3_AGT_VTAM_APPL_NCSv KN3_AGT_VTAM_APPL_OPERATORv KN3_AGT_VTAM_APPL_CNM_SPO

Specifies the VTAM application IDs(applids) that the agent uses to definecommunication with the Tivoli EnterpriseMonitoring Server. Applids are used forcommunication with the monitoringserver, except for KN3_AGT_VTAM_APPL_CNM_SPO, which is used tocollect CNM data. These parameters arenot used unless you are using SNA(instead of TCP/IP) to communicate withthe monitoring server.

Agent's localTCP/IPinformation

v KN3_AGT_TCP_HOSTv KN3_AGT_TCP_STCv KN3_AGT_TCP_KDEB_INTERFACELIST (If the

Agent requires network interface list support)v KN3_AGT_PARTITION_NAME (If the Agent

requires address translation support–optional)

Provides the TCP/IP information that theTivoli Enterprise Monitoring Server usesto communicate with the monitoringagent.

Agent's localVTAM and logoninformation

v KN3_AGT_VTAM_APPL_PREFIXv KN3_AGT_VTAM_NODE

Specifies the values that are used by theagent for creating VTAM definitionsspecific to the monitoring agent.

Agent's primaryTEMS TCP/IPinformation

v KN3_TEMS_TCP_HOST

Note: KN3_TEMS_TCP_HOST andKN3_AGT_TCP_HOST must be the same value ifKN3_TEMS_LOCAL _CONNECT_FLAG=Y (Agentconnects to local TEMS).

Specifies the host name of the TivoliEnterprise Monitoring Server that isspecific to this monitoring agent. Thisfield is required if this server is tocommunicate with agents using TCP/IP.

Agent's PrimaryTEMS VTAMinformation:

v KN3_TEMS_VTAM_LU62_DLOGMODv KN3_TEMS_VTAM_LU62_MODETABv KN3_TEMS_VTAM_NETIDv KN3_TEMS_VTAM_APPL_LLB_BROKER

Specifies the VTAM information that isused by the Tivoli Enterprise MonitoringServer to communicate with themonitoring agent.




Audit parameters v KN3_AGT_AUDIT_ITM_DOMAINv KN3_AGT_AUDIT_MAX_HISTv KN3_AGT_AUDIT_TRACE

Specifies the amount of detail, maximumnumber of entries, and identifier forz/OS SAF tracing.

Define TCPmonitoringsystems memberNote: SpecifyKN3_TCPXxx_*row for eachTCP/IPmonitored stack.Global default is$$$$ (monitor allTCP/IP stacks).

v KN3_TCPXv KN3_TCPXnn_OVRD_GLBSv KN3_TCPXnn_OVRD_INTEv KN3_TCPXnn_OVRD_INTSv KN3_TCPXnn_OVRD_OSAv KN3_TCPXnn_ROWv KN3_TCPXnn_SYS_NAMEv KN3_TCPXnn_TCP_STCv KN3_TCPXnn_TCPIP_PROFILES_DSNv KN3_TCPXnn_OVRD_GLOBAL_FLAGv KN3_TCPXnn_OVRD_COLLECT_STACKv KN3_TCPXnn_OVRD_CONNv KN3_TCPXnn_OVRD_IPSECv KN3_TCPXnn_OVRD_ROUTE_TBLv KN3_TCPXnn_OVRD_ROUTE_TBL_FREQv KN3_TCP_ROUTE_TBLv KN3_TCP_ROUTE_TBL_FREQv KN3_TCPXnn_OVRD_FTPv KN3_TCPXnn_OVRD_FTP_DSPINTVv KN3_TCPXnn_OVRD_TN3270v KN3_TCPXnn_OVRD_TN3270_DSPINTVv KN3_TCPXnn_TCPIP_PROFILES_MBR

Sets the stack-specific values thatoverride the global parameters for allconfigurable parameters that are uniqueto the OMEGAMON XE for MainframeNetworks monitoring agent.

Define TN3270Telnet session linkuser values

v KN3_TN3270_DXL_APPLIDv KN3_TN3270_DXL_USERDATA

Specifies the IBM Tivoli NetView forz/OS user ID and password thatOMEGAMON XE for MainframeNetworks logs onto dynamically. Theapplid is for the Tivoli NetView on z/OSapplication. The user data is the user IDand password that must be passed toNetView for z/OS to complete the login.

Enableself-describingagent processing

v KN3_AGT_TEMA_SDA Specifies whether this monitoring agentplans to use the self-describing agentfeature.

If the Agentrequires addresstranslationsupport

v KN3_AGT_PARTITION_NAME Specifies the partition name thatidentifies the location of this TEMS(namespace) relative to the firewall(s)used for address translation.

If the Agentrequires networkinterface listsupport

v KN3_AGT_TCP_KDEB_INTERFACELIST Specifies a list of network interfaces thatthe monitoring agent uses. Thisparameter is required for sites that arerunning multiple TCP/IP interfaces ornetwork adapters on the same z/OSimage.




Persistentdatastore tablespace allocationoverrides

v KN3_PDv KN3_PD_CYLv KN3_PD_GRPv KN3_PD_ROWv KN3_X_PD_HISTCOLL_DATA_AGT_STCv KN3_X_PD_HISTCOLL_DATA_TEMS_STC

Specifies the information that is requiredfor this monitoring agent to override theglobal RTE defaults for space allocationfor the persistent data store libraries andfor overhead information such as theproduct dictionary, table records, indexrecords, and buffers to hold overflowdata.

Protocol portnumbers forAgent connectionto TEMS

v KN3_TEMS_TCP_PIPE_PORT_NUMv KN3_TEMS_TCP_PIPES_PORT_NUMv KN3_TEMS_TCP_PIPE6_PORT_NUMv KN3_TEMS_TCP_PIPE6S_PORT_NUMv KN3_TEMS_TCP_UDP_PORT_NUMv KN3_TEMS_TCP_UDP6_PORT_NUM

Specifies the port numbers that are usedby the protocols specified under "Specifycommunication protocols preference forTEMS connection" for communicationbetween the monitoring agent and TivoliEnterprise Monitoring Server.

Secondary TEMSconfiguration

v KN3_TEMS_BKUP1_NAME_NODEID Specifies the name of the secondarymonitoring server if you defined abackup Tivoli Enterprise MonitoringServer. The BKUP1 values are found inthe KN3ENV member in therhilev.midlev.rtename. RKANPARU libraryto communicate with the backup TivoliEnterprise Monitoring Server.

Secondary TEMSTCP/IPinformation

v KN3_TEMS_BKUP1_TCP_HOST Specifies TCP/IP information for abackup Tivoli Enterprise MonitoringServer if you defined a backupmonitoring server. The BKUP1 values arefound in the KN3ENV member in therhilev.midlev.rtename. RKANPARU libraryto communicate with the backup TivoliEnterprise Monitoring Server.

Secondary TEMSVTAMinformation:

v KN3_TEMS_BKUP1_VTAM_APPL_LLB_BKRv KN3_TEMS_BKUP1_VTAM_LU62_DLOGMODv KN3_TEMS_BKUP1_VTAM_NETID

Specifies VTAM or SNA information forthe backup Tivoli Enterprise MonitoringServer if you defined a backupmonitoring server. The BKUP1 values arefound in the KN3ENV member in therhilev.midlev.rtename. RKANPARU libraryto communicate with the backup TivoliEnterprise Monitoring Server.

Specifycommunicationprotocolspreference forTEMS connection

v KN3_AGT_COMM_PROTOCOLn Details the protocol possibilities forcommunication between the monitoringagent and Tivoli Enterprise MonitoringServer in the order in which theprotocols will be used.

Take Actioncommandssecurity settings

v KN3_AGT_PPI_RECEIVERv KN3_AGT_PPI_SENDERv KN3_SECURITY_ACTION_CLASS

Defines the connection betweenOMEGAMON XE for MainframeNetworks and Tivoli NetView for z/OS ifyou use Tivoli NetView for z/OS andspecifies whether to override the SAFsecurity value specified for the runtimeenvironment at the agent.




Values thatdescribe theaddress space

v KN3_AGT_CONFIGURATION_MODEv KN3_AGT_STC

Specifies the name of the address spacein which you are running and the nameof your agent PROC.

Values thatdescribe thePrimary TEMSthe Agent willconnect to

v KN3_TEMS_LOCAL_CONNECT_FLAGv KN3_TEMS_NAME_NODEID

Defines the information required toconnect to the local Tivoli EnterpriseMonitoring Server.

VTAM SecondaryProgram Operator(SPO) forCommunicationNetworkManagement(CNM) interface(optional)

v KN3_AGT_VTAM_NODE_OMXEv KN3_AGT_VTAM_APPL_CNM_SPO

Defines how the OMEGAMON XE forMainframe Networks monitoring agentcommunicates with the VTAM CNMinterface to collect monitoringinformation.

Configuring security for Take Action commandsYou must supply custom values for the security class and SAF validation for Take Action commands.

The security for Take Action commands provided with the OMEGAMON XE for Mainframe Networks isimplemented through direct System Authorization Facility (SAF) calls and is based on profiles andresource names. These commands cannot be run unless security is configured.

OMEGAMON XE for Mainframe Networks agent Take Action commands cannot be issued unless asecurity class is defined to the SAF security manager and the security class name is configured in eachruntime environment in which an OMEGAMON XE for Mainframe Networks monitoring agent isconfigured.

To secure Take Action commands, you must configure the global security parameter(RTE_SECURITY_CLASS). Optionally, you can use the SAF class name override parameter(KN3_SECURITY_ACTION_CLASS) to specify a separate class for securing OMEGAMON XE for MainframeNetworks Take Action commands. After you define each security class, you must create profiles to controlaccess to individual commands and give user IDs UPDATE access to those profiles. See “Prefixed TakeAction commands” on page 141.

Finding previous PARMGEN configuration sessionsIf you configured an RTE by using the PARMGEN method and exit the PARMGEN tool, you might havedifficulty locating your work from the previous session when you restart the PARMGEN tool.

When you open the PARMGEN Workflow Welcome panel for the second time, the fields at the top areblank, as shown in Figure 5 on page 85 and it seems that the work from your previous session is lost.


To locate your work from a previous session, you must provide values for the GBL_USER_JCL field,which displays PARMGEN global user JCL library (CONFIG DD in the started tasks). If you provide thisvalue and press Enter, then configuration information from the previous session is displayed. Also, theStatus and Date for each PARMGEN option that you completed is displayed, providing an accuraterecord of your progress.

Ensuring that your runtime environment supports the NetView for z/OSpacket trace using PARMGENIf you are using the PARMGEN configuration method, you must set values for these three parametersbefore you use NetView for z/OS packet trace.

If you plan to use the Dynamic XE to 3270 functionality that enables you to access the NetView for z/OSpacket trace function, the settings for your runtime environment must include the information that isrequired for 3270 applications to link to Tivoli NetView for z/OS.

If you are creating your runtime environment for the first time, make sure that the information for thesethree RTE_TN3270 parameters is correct:v RTE_TN3270_DXL_HOSTADDRESS for specifying the Hostnamev RTE_TN3270_DXL_TN3270PORT for specifying the Port Numberv RTE_TN3270_DXL_LUGROUP for specifying the LUGROUP

The requirements for these fields are described briefly in Table 16 on page 86 and more completely in theIBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.

--------------- PARAMETER GENERATOR (PARMGEN) WORKFLOW - WELCOME -------------OPTION ===> SCROLL ===>

Enter PARMGEN parameter values appropriate for your environment:GBL_USER_JCL: __________________________________________

PARMGEN global user JCL library (CONFIG DD in STCs)RTE_PLIB_HILEV: __________________________________________

High-Level Qualifier (HLQ) of work libraries (IK*,WCONFIG,WK*)RTE_NAME: _________ (Type ? for a list of configured RTEs)

Runtime environment (RTE) name for this LPAR

Enter n (1-11) to perform tasks. Status DateEnter ns (1s-11s) to display detailed status. --------- ---------

1. KCIJPCFG Set up PARMGEN work environment for an RTE.2. $JOBINDX Review PARMGEN job index.3. KCIJPCCF Clone customized WCONFIG members. (Optional)4. KCIJPUP1 Update interim libraries and create profiles.5. KCIJPMC1 Merge profile from backup MIG420 (Optional)6. KCIJPMC2 Merge profile from model RTE. (Optional)7. KCIJPCNV Convert an ICAT RTE Batch member. (Optional)8. MIG420 Customize PARMGEN configuration profiles.9. KCIJPVAL Validate PARMGEN profile parameter values.10. $PARSE Create the RTE members and jobs.11. SUBMIT Submit batch jobs to complete PARMGEN setup.U Utility Access PARMGEN utilities. (Optional)R New RTE Reset RTE, Status and Date fields. (Optional)

Enter=Next F1=Help F3=End/Cancel

Figure 5. PARMGEN Workflow Welcome panel on entry


Table 16. Parameters and explanations for the Update Runtime Environment (3 of 3) panel

Parameter Explanation

Hostname If the system on which you are defining a runtime environment does not have an activeTelnet listener, you can specify the network address of a system that does have an activeTelnet listener. You can specify a network address as one of the following values:v Fully qualified hostname (for example, sys.ibm.com)v First qualifier of the fully qualified hostname (for example, sys for sys.ibm.com)v 32-bit IPv4 address in dotted decimal notation (for example, 9.67.1.100)

To get this value, issue the TSO HOMETEST command on the system of the Telnetlistener.

Port number The default port number of the Telnet listener is 23. To override this value, specify theport number of the Telnet listener.

LUGROUP The Dynamic XE to 3270 (NetView for z/OS) linking feature requires the VTAMUnformatted System Services (USS) screen to accept a LOGON APPLID() DATA()command. If the default Telnet USS screen does not accept this command, supply thename of a Logical Unit (LU) group that does accept it. The TN3270 session is joined tothat LU group.

Note:

1. Complete this panel only if you are configuring products that support the Dynamic XE to 3270 (NetView forz/OS) linking feature and you need to override the default values.

2. The default values or the override values you specify on this panel are displayed during TN3270 logon and canbe modified for an individual TN3270 session.


Chapter 7. Configuring the monitoring agent using theConfiguration Tool

These factors should be considered as your begin configuration of the OMEGAMON XE for MainframeNetworks Monitoring agent using the Configuration Tool.

After the Tivoli Enterprise Monitoring Server, the next product displayed on the Product ComponentSelection Menu shown in Figure 9 on page 91 is the Tivoli OMEGAMON Enhanced User Interface. Thecomponent was installed during the SMP/E installation of the product so that its facilities are available.Configuring the Tivoli OMEGAMON Enhanced User Interface requires a new started task, a relatedVTAM node definition, and a VTAM applid. This component is installed in its own address space. Theconfiguration process for the interface defines the address space controls and logical VTAM connectionsrequired to run it. In addition, a data retrieval agent (DRA) must be enabled on the hub monitoringserver. This configuration is covered in the IBM Tivoli Monitoring: Configuring the Tivoli EnterpriseMonitoring Server on z/OS. You must configure one instance of this interface per sysplex. See “Configuringthe enhanced 3270 user interface using the Configuration Tool” for information about configuring thisinterface.

The next option is to configure OMEGAMON II for Mainframe Networks. The OMEGAMON II forMainframe Networks component was installed during the SMP/E installation of the product so that itsfacilities are available. The OMEGAMON II for Mainframe Networks configuration step is optional andshould be performed only if you want to use this 3270 component to monitor VTAM, NCP, and SNAresources. If you want to use OMEGAMON II for Mainframe Networks, see Appendix A, “Configuringthe OMEGAMON II for Mainframe Networks component,” on page 155 for information aboutconfiguring this component and Appendix B, “Customizing the OMEGAMON II components andverifying installation,” on page 185 to configure the OMEGAMON II constituent parts, such as NCPcollection and the End-to-End Response Time Feature (ETE) and to verify that the product is configuredcorrectly.

For information to help you decide whether to install the OMEGAMON II component, see “Upgradingan existing OMEGAMON II for Mainframe Networks environment” on page 72.

This section explains how to configure the OMEGAMON XE for Mainframe Networks Monitoring agent.

Before you can use the NetView packet trace function introduced in OMEGAMON XE for MainframeNetworks V4.2.0 Fix Pack 1, you must update your runtime environment to include the TN3270E Telnetsession link support override values. See “Updating your runtime environment to support the NetViewfor z/OS packet trace” on page 124 for information about how to perform this task, or refer to the IBMTivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide.

If you want additional information about any of the parameters specified by the Configuration Tool, youcan search on the Configuration Tool name of the field in the IBM Tivoli OMEGAMON XE for MainframeNetworks: Parameter Reference and learn more about these parameters.

Configuring the enhanced 3270 user interface using the ConfigurationToolIf this is the first V5.1.0 monitoring agent on z/OS you have installed, you must configure it. You shouldconfigure one instance of the Enhanced 3270 User Interface per sysplex.

To configure the interface, perform the following steps:


1. If you have not already done so, type B (Build libraries) and press Enter to allocate the new runtimelibraries.

2. From the he Product Component Selection panel , select option 2 Tivoli OMEGAMON Enhanced3270 User Interface.

3. The Configure OMEGAMON Enhanced 3270 UI / RTE: rtename panel is displayed:

4. Select option 1 Specify configuration values. The Specify Configuration Values panel is displayed:

----------------------- PRODUCT COMPONENT SELECTION MENU -----------------------COMMAND ===>

The following list of components requires configuration to make the productoperational. Refer to the appropriate configuration documentation if yourequire additional information to complete the configuration.To configure the desired component, enter the selection number on the commandline. You should configure the components in the order they are listed.

Note: It may not be necessary to configure Tivoli Enterprise Monitoring Server(TEMS) component, if listed below. Press F1 for more information.

COMPONENT TITLE

1 Tivoli Enterprise Monitoring Server2 Tivoli OMEGAMON Enhanced 3270 User Interface3 OMEGAMON II for Mainframe Networks4 OMEGAMON XE for Mainframe Networks

Figure 6. Product component selection menu panel. Product component selection menu panel

-------------- CONFIGURE OMEGAMON ENHANCED 3270 UI / RTE: rtename-------------- .. OPTION ===> .. .. Note: If you have already configured the Enhanced 3270 UI in .. the related Sysplex, you may not need to perform this .. configuration, please consult the help information; F1=Help .. .. Last selected .. Perform these configuration steps in order: Date Time .. .. I Configuration information (What’s New) .. .. 1 Specify configuration values .. 2 Create runtime members .. 3 Complete the configuration .. .. .. .. F1=Help F3=Back .. .

Figure 7. The Configure OMEGAMON Enhanced 3270 UI / RTE: rte panel


5. Accept the default values or specify your preferences for the following parameters:

OMEGAMON Enhanced 3270 UIThe started task name for the interface address space. The default is CANSTOM.

Node NameThe name of the VTAM major node for the address space. The default is CTDOBN.

Appl IDThe VTAM applid the interface will use. The default is CTDOBAP.

6. Press Enter to accept the values. The Configure OMEGAMON Enhanced 3270 UI / RTE: rte panel isredisplayed.

7. Select option 2 Create runtime members. The OB#3xxx job is displayed. Review the JCL and thensubmit it to create the runtime members.

8. Press F3 to return to the Configure OMEGAMON Enhanced 3270 UI / RTE: rtename panel.9. Select option 3 Complete the configuration to display the Complete the Configuration steps. If you

are configuring other products in this runtime environment, you can perform these steps after youhave completed all configuration. These steps include:v Perform the runtime environment Load step.v Copy the OMEGAMON Enhanced 3270 User Interface started task (CANSTOM) from RKANSAMU

to PROCLIB.v Copy the VTAM major node (CTDOBN ) from RKANSAMU to VTAMLST.v Vary the VTAM major node active.v APF-authorize the following load libraries:

– &hilev.&rte.RKANMODU– &hilev.&rte.RKANMOD– &hilev.&rte.RKANMODP

Summary of the OMEGAMON XE configuration stepsUse this summary of configuration steps to understand the flow of configuration for the OMEGAMONXE for Mainframe Networks monitoring agent.v “Accessing OMEGAMON XE configuration steps in the Configuration Tool” on page 91

This step takes you to the place in the Configuration Tool where OMEGAMON XE configuration starts.You should already have created the runtime environment needed to install this monitoring agent. If

------------------------- SPECIFY CONFIGURATION VALUES ------------------------ .. COMMAND ===> .. .. .. Started task(s): .. OMEGAMON Enhanced 3270 UI ==> CANSTOM .. .. VTAM information: .. Node Name ==> CTDOBN .. Appl ID ==> CTDOBAP .. .. .. .. .. .. .. .. .. .. Enter=Next F1=Help F3=Back F5=Advanced .

Figure 8. The Specify Configuration Values panel

Chapter 7. Configuring the monitoring agent using the Configuration Tool 89

you have not, see "Setting up and building a runtime environment" in the IBM Tivoli OMEGAMON XEand IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.

v “Step 1: Registering with local TEMS” on page 92

This step registers the OMEGAMON XE for Mainframe networks monitoring agent with the localTivoli Enterprise Monitoring Server. The registration process includes installation of product-providedsolutions such as situations, policies, and templates.

v “Step 2: Specifying configuration parameters” on page 92

This step is used to supply configuration values required by the monitoring agent.v “Step 3: Specifying agent address space parameters” on page 105

This step is used to provide information required to create the address space and communicate withthe Tivoli Enterprise Monitoring Server of your choice. In a shared address space environment, onlythe address space owner (agent that created the address space) can change these parameters.

v “Step 4: Specifying dynamic terminal integration parameters” on page 117

This step enables you to specify Telnet session link parameter values. These parameters define theconnection information that the TEP terminal emulator uses to connect to NetView for z/OS.

v “Step 5: Creating runtime members” on page 118

This step generates a batch job that creates the runtime members required to create or update theaddress space where the OMEGAMON XE for Mainframe Networks monitoring agent is running.These members are created in the runtime libraries for this RTE. This step generates the JCL job tocreate the required runtime members. Review the generated JCL job, edit it as required, and submit it.

v “Step 6: Configuring the persistent datastore (in the agent)” on page 118

This step provides a batch job that will configure a persistent data store that is added to themonitoring agent address space for historical data collection. This step also allocates the persistent datastore data sets used by the OMEGAMON XE for Mainframe Networks product.

v “Step 7: Loading the runtime libraries” on page 123

The step loads the runtime libraries from the SMP/E target libraries.v “Step 8: Completing the configuration” on page 124

These steps must be completed outside of the Configuration Tool before you can begin to useOMEGAMON XE for Mainframe Networks. (These procedures are also covered on a panel displayedwhen you select to complete the configuration using the Configuration Tool.) Before you begin thesesteps, you must load the runtime libraries (see “Step 7: Loading the runtime libraries” on page 123).

Note:

1. The Configuration Tool is updated constantly because it is updated as new products are delivered andnew requirements are introduced. Therefore, the screens in the Configuration Guide may not exactlymatch those in the Configuration Tool.

2. In the sections that follow, when you run a JCL job, the suggested return code to look for is zero.Sometimes other return codes are acceptable. Review the comments inside the generated ICAT jobs todetermine other acceptable return codes. Where a conflict arises between the JCL job comments andthe configuration guide, accept the information in the JCL job, which might have been created laterthan the information in the book.

3. If you change any of the values defined in the Configuration Tool after initial configuration, you mustRun the JCL jobs as described in “Running the JCL Jobs” to incorporate this change into production.Verify that these jobs complete successfully. When the jobs complete successfully, the values will havebeen updated.

Running the JCL JobsInstallation using the Configuration Tool requires that you run a number of JCL jobs.

In the sections that follow, some actions require that the JCL job generated in the process steps Step 4:Create Runtime Members (job N3#3xxx) and Step 3: Create Monitoring Agent Runtime Members (job


N3#5xx) need to be run to pick up changes made in the Configuration Tool and incorporate them intoproduction. When the instructions say “Run the JCL jobs”, both of these jobs should be run.v To run the N3#5xx Create Monitoring Agent Runtime Members job, return to the Specify

Configuration Parameters panel shown in Figure 11 on page 93, choose Step 3: Create MonitoringAgent Runtime Members that presents the N3#5xx job for your submission, and submit job N3#5xx toincorporate any changes into production.

v To run the N3#3xxx job Create runtime members JCL job, return to the Configure OMEGAMON XEfor Mainframe Networks panel show in Figure 10 on page 92, choose Step 4: Create RuntimeMembers that presents job N3#3xxx for your submission, and submit job N3#3xxx to incorporate anychanges into production.

Accessing OMEGAMON XE configuration steps in the ConfigurationToolTo configuration the OMEGAMON XE for Mainframe Networks monitoring agent, begin with theProduct Component Selection Menu and select the OMEGAMON XE for Mainframe Networks product.

About this task

If you have exited the Configuration Tool, do the following to access this menu:

Procedure1. From the Configuration Tool main menu, enter 3 Configure products > 1 Select product to configure

> S Tivoli OMEGAMON XE for Mainframe Networks. The Runtime Environments panel isdisplayed.

2. From the Runtime Environments panel, enter C in the Action column by the name of the SHARINGRTE (which in the following screens is HUBN3IRA). The Product Component Selection Menu shownin Figure 9 is displayed.

The last product displayed on the Product Component Selection Menu shown in Figure 9 isOMEGAMON XE for Mainframe Networks. This section describes the procedures for configuring themonitoring agent and linking it to the hub Tivoli Enterprise Monitoring Server.

3. To start the OMEGAMON XE monitoring agent configuration, from the Product ConfigurationSelection Menu shown in Figure 9, enter 4 OMEGAMON XE for Mainframe Networks. This actioncauses the Configure OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page92 to be displayed.




COMPONENT TITLE




This menu presents the steps needed to configure the OMEGAMON XE for Mainframe Networksmonitoring agent if you have defined a Tivoli Enterprise Monitoring Server in this RTE. These stepsshould be completed in the order shown in the following section.

Step 1: Registering with local TEMSRegister with the local Tivoli Enterprise Monitoring Server (TEMS) if you are installing this monitoringagent in the same runtime environment as the monitoring server.

About this task

If you are installed the OMEGAMON XE for Mainframe Networks monitoring agent in the same runtimeenvironment (RTE) with the Tivoli Enterprise Monitoring Server, use this step to register the monitoringagent with the local monitoring server.

Procedure1. Select 1 Register with local TEMS from the Configure OMEGAMON XE for Mainframe Networks

panel shown in Figure 10 and press Enter. The JCL job generated by this step registers theOMEGAMON XE for Mainframe Networks monitoring agent with the local Tivoli EnterpriseMonitoring Server.

2. Review the JCL and submit the job. Verify that the job completes successfully. If it does not, check thelog to diagnose errors and rerun the job.

3. When the JCL for registering with the hub Tivoli Enterprise Monitoring Server completes, press F3 toreturn to the Configure OMEGAMON XE for Mainframe Networks panel shown in Figure 10.

Step 2: Specifying configuration parametersUse this step to supply configuration values required by the monitoring agent.

About this task

Use this step to supply configuration values required by the monitoring agent.

----- CONFIGURE OMEGAMON XE FOR MAINFRAME NETWORKS V5.1.0 / RTE: HUBN3IRA --–-

Last selectedPerform the appropriate configuration steps in order Date Time

If you have defined a TEMS in this RTE that this Agentwill communicate with, select option 1.

I Configuration information (What’s New)

1 Register with local TEMS

2 Specify configuration parameters

3 Specify Agent address space parameters

4 Specify dynamic terminal integration parameters

5 Create runtime members

6 Configure persistent datastore (in Agent)

7 Complete the configuration

Note: This Agent is running in its own Agent address space.

Figure 10. Configure OMEGAMON XE for Mainframe Networks panel. Configure OMEGAMON XE for MainframeNetworks panel


Procedure1. Select 2 Specify configuration parameters from the Configure OMEGAMON XE for Mainframe

Networks panel shown in Figure 10 on page 92. The panel shown in Figure 11 is displayed:

This panel presents the steps to configure OMEGAMON XE for Mainframe Networks. Theseconfiguration steps must be performed in order. The options are found in Table 17.

Table 17. Parameters and explanations for the Specify Configuration Parameters panel


1 Specify componentconfiguration

This step collects information that applies to the monitoring agent, to monitoring allTCP/IP address spaces on the system, or to monitoring VTAM on the system.

2 Specify monitored systemsinformation

This step collects information to define the TCP/IP address spaces that should bemonitored and the configuration options for each monitored TCP/IP address space.

3 Create monitoring agentruntime members

This step creates the members in the runtime data sets that are read by themonitoring agent. These members determine what information is collected andwhich TCP/IP address spaces are monitored. The N3#5xxx job is created, whichupdates selected members of the RKANPARU and RKANCMDU data sets. If anymanual edits have been made to these members data sets, they will be overwrittenby this job. Selecting this option presents the N3#5xxx job to be created. Review theJCL and submit the job. Verify that the job completes successfully

Note: Perform all configuration steps found on this panel. If you change any of these values after initialconfiguration, you must Run the JCL jobs as described in “Running the JCL Jobs” on page 90 to incorporate thischange into production. Verify that these jobs complete successfully. When the jobs complete successfully, the valueswill have been updated.

2. Select 1 Specify component configuration. This action causes the Specify Component Configurationpanel shown in Figure 12 to be displayed:

Complete this panel using the information found in Table 18 on page 94.

------------ SPECIFY CONFIGURATION PARAMETERS / RTE: HUBN3IRA --------------OPTION ===>

Last selectedPerform these configuration steps in order: Date Time

1 Specify component configuration2 Specify monitored systems information3 Create monitoring agent runtime members

Figure 11. Specify configuration parameters panel. Specify configuration parameters panel

------------------- SPECIFY COMPONENT CONFIGURATION -----–-----------–------—Command ===>

Specify your site’s VIO unit name:==> VIO

Specify the following TCP/IP information:

TCP/IP data file (SYS1.TCPPARMS(TCPDATA)):==> SYS1.TCPPARMS(TCPDATA)

TCP/IP sample interval:==> 5 (1-60 minutes)

Specify Take Action Security:SAF class name override ==>

Figure 12. Specify component configuration panel. Specify component configuration panel


Table 18. Parameters and explanations for the Specify Component Configuration panel


Specify your site's VIOunit name

Provide the TCP/IP virtual input/output (VIO) unit name for your site. The VIO unit isused to allocate temporary data sets. The default is VIO.

Specify the following TCP/IP information: OMEGAMON XE for Mainframe Networks requires this informationabout the TCP/IP systems you plan to monitor.

TCP/IP data file The dsname of the library which provides parameters for TCP/IP address spaceconfiguration. This dsname can be either a sequential data set name or a partitioned dataset name and a member name (for example, TCPIP.DATA orSYS1.TCPPARMS(TCPDATA)).

Specify the data set used by the TCP/IP address space. See the TCPDATA search ordersection of the z/OS Communications Server IP Configuration Guide.

If you are monitoring multiple TCP/IP address spaces, pick the primary address spacefor the monitoring agent to connect to.

TCP/IP sample interval The frequency with which IBM Tivoli OMEGAMON XE for Mainframe Networksrequests performance data about your TCP/IP stack. The value is expressed in minutesfrom 1 to 60. The default value is 5 minutes. For every sample interval, IBM TivoliOMEGAMON XE for Mainframe Networks gathers TCP/IP performance data from thez/OS Communication Server network management interface (NMI) and the SNMPagent.

Specify Take ActionSecurity: SAF class nameoverride

Specify the security class override that will be used to validate OMEGAMON forMainframe Networks action commands.

Specify the name of the security class override. If the specified class is invalid or is notactive in the security manager, the command will not be executed. The value shouldconform to the definition rules dictated by the security manager.

The Configuration Tool generates the KN3_SECURITY_ACTION_CLASS parameter in one ofthese locations:

v In the xKANPARU(KN3ENV) member, if the KN3 Agent runs in its own Agentaddress space, that is, if KN3_AGT_CONFIGURATION_MODE = "STANDALONE"

v In the xKANPARU(KDSENV) member, if the KN3 Agent runs in the TEMS addressspace, that is , if KN3_AGT_CONFIGURATION_MODE = "CMS"

Notes®:

v If you are using ACF2 as your external security resource manager, specify a maximumof three characters.

v The SAF class name is applicable to Tivoli Enterprise Portal and OMEGAMONEnhanced 3270 User Interface Take Action security.

v Related PARMGEN CONFIG profile parameter: RTE_SECURITY_CLASS

Note:

1. If you change any of these values after initial configuration, you must Run the JCL jobs as described in“Running the JCL Jobs” on page 90 to incorporate this change into production. Verify that these jobs completesuccessfully. When the jobs complete successfully, the values will have been updated.

2. FTP data and TN3270 data are retrieved independent of this sampling interval.

When all entries on this panel are complete, press Enter to continue to the next panel in this sequence.3. This action causes the continuation of the Specify Component Configuration (Page 2) panel sequence

shown in Figure 13 on page 95 to be displayed:


This configuration panel lets you specify which types of TCP/IP performance data to collect. Thispanel defines the values that apply globally to all TCP/IP address spaces being monitored.Select global values that meet the needs of most of your monitored systems. Then in Step 2 Specifymonitored systems information on the Specify Configuration Parameters panel shown in Figure 11 onpage 93, override these values for specific TCP/IP address spaces.

Note: If you change any of these values after initial configuration, you must run the JCL jobsdescribed in “Running the JCL Jobs” on page 90 to incorporate this change into production. Verifythat these jobs complete successfully. When the jobs complete successfully, the values will have beenupdated.a. Use the information in Table 19 to complete this panel:

Table 19. Parameters and explanations for the Specify Component Configuration (Page 2) panel


OSA Statistics Collection Determines whether to collect OSA data for the system. This global parameterapplies to the entire system. Y (the default) indicates OSA data will be collected onthis system. N indicates OSA data will not be collected on this system.

Interface Statistics Collection Determines whether to collect Interface Statistics data for the system. This globalparameter applies to the entire system. Y (the default) indicates that InterfaceStatistics data will be collected on this system. N indicates Interface Statistics data isnot be collected on this system. Specifying N will also disable collection of Devicesdata.Note: For performance reasons, turn on Interface Statistics collection if RoutingTable Collection is active.

Interface Data Link ControlStatistics Collection

Determines whether to collect Interface Data Link Control (DLC) Statistics read andwrite queue data. This global parameter applies to the entire system. Y (the default)indicates Interface DLC Statistics data will be collected on this system. N indicatesInterface DLC Statistics data will not be collected on this system.

TCP/IP Stack Layer StatisticsCollection

Determines whether to collect TCP/IP Stack Layer Statistics data for the system.This global parameter applies to the entire system. Y (the default) indicates thatTCP/IP Stack Layer Statistics data will be collected on this system. N indicates thatTCP/IP Stack Layer Statistics data will not be collected on this system.

b. When all entries on this panel are complete, press Enter to go to the Specify ComponentConfiguration (Page 3) panel.

4. This action causes the continuation of the Specify Component Configuration (Page 3) panel sequenceshown in Figure 14 on page 96 to be displayed:

—------------------ SPECIFY COMPONENT CONFIGURATION (Page 2)---------------Command ===>

Specify the following global information:

OSA Statistics Collection: ==> Y (Y,N)

Interface Statistics Collection: ==> Y (Y,N)

Interface Data Link Control Statistics Collection: ==> Y (Y,N)

TCP/IP Stack Layer Statistics Collection: ==> Y (Y,N)

Figure 13. Specify component configuration (page 2) panel. Specify component configuration (pages 2) panel


This configuration panel lets you specify which types of TCP/IP performance data to collect. Thispanel defines the values that apply globally to all TCP/IP address spaces being monitored. Thedefault is for most categories of data to be collected, with the exception of IP Filters and IPSecTunnels.Select global values that meet the needs of most of your monitored systems. Then in Step 2 Specifymonitored systems information on the Specify Configuration Parameters panel shown in Figure 11 onpage 93, override these values for specific TCP/IP address spaces.

Note: If you change any of these values after initial configuration, you must run the JCL jobsdescribed in “Running the JCL Jobs” on page 90 to incorporate this change into production. Verifythat these jobs complete successfully. When the jobs complete successfully, the values will have beenupdated.a. Use the information in Table 20 to complete this panel:



TCP/IP Connection andApplication PerformanceStatistics Collection

Determines whether to collect TCP/IP Connection and Application performancestatistics globally. Y (the default) indicates TCP/IP Connection and Applicationperformance statistics will be collected. N indicates TCP/IP Connection andApplication performance statistics will not be collected.

IP Filters and IPSec TunnelsStatistics Collection

Determines whether to collect IPSec security data. Y indicates IPSec Security datawill be collected. N (the default) indicates IPSec Security data will not be collected.

Routing Table StatisticsCollection

Determines whether to collect routing table data globally. Y (the default) indicatesSNMP routing data will be collected. N indicates SNMP routing data will not becollected.

Routing Table CollectionFrequency

Determines how often the routing table information will be collected. A value of 1means that routing information is collected every collection interval. The globaldefault value of 10 means that routing information is collected once every 10collection intervals. The value is expressed as a whole number from 1 to 99. Settinga higher value means you collect the data less often, reducing overall CPUconsumption while still making the data available.

TN3270 Server StatisticsCollection

Determines whether to collect TN3270 data for all TN3270 servers running on thissystem. Y (the default) indicates TN3270 data will be collected. N indicates TN3270data will not be collected. Only TN3270 connections which started within thedisplay interval will be seen in the real-time data displays.

—------------------ SPECIFY COMPONENT CONFIGURATION (Page 3)---------------Command ===>


TCP/IP Connection and Application Performance Statistics Collection:==> Y (Y,N)

IP Filters and IPSec Tunnels Statistics Collection: ==> N (Y,N)

Routing Table Statistics Collection: ==> Y (Y,N)Routing Table Collection Frequency: ==> 10 (1-99) (Optional)

TN3270 Server Statistics Collection: ==> Y (Y,N)TN3270 Data Display Interval: ==> 2 (1-24 hours)(Optional)

FTP Data Collection: ==> Y (Y,N)FTP Data Display Interval: ==> 2 (1-24 hours)(Optional)

SNMP Configuration file (USER.PARMLIB(KN3SNMP)):==> USER.PARMLIB(KN3SNMP)



Table 20. Parameters and explanations for the Specify Component Configuration (Page 3) panel (continued)


TN3270 Data Display Interval Determines how long TN3270 server statistics will be displayed on the TivoliEnterprise Portal. This value is expressed as a whole number in hours from 1 to 24.The default is 2 hours

FTP Data Collection Determines whether to collect FTP data for all FTP servers running on this system.Y (the default) indicates FTP data will be collected for all FTP servers. N indicatesFTP data will not be collected.

FTP Data Display Interval Determines the size of the sliding window that displays all FTP transfers that werecompleted or became active within the display interval. A value of "1" means thewindow displays all data from present until 1 hour ago. This value is expressed as awhole number in hours from 1 to 24. The default is 2 hours.

SNMP Configuration File The name of the data set containing configuration entries for the SNMP managerfunctions within TCP/IP data collection. Specify either the name of a sequential dataset or the name of a partitioned data set, and the name of the member containingSNMP configuration entries.

The data set name will have a format such as USER.PARMLIB (if the data set hasphysical sequential organization) or USER.PARMLIB(KN3SNMP) (if the data set haspartitioned organization and member KN3SNMP contains SNMP configurationentries). For more information about defining the entries in this data set, see theKN3SNMP sample file in RKANSAMU. This field is required.

For more information about the format of this file, see Appendix E, “Format of theSNMP configuration file,” on page 289.

b. When all entries on this panel are complete, press Enter to go to the Specify ComponentConfiguration (Page 4) panel.

5. This action causes the Specify Component Configuration (Page 4) panel shown in Figure 15 to bedisplayed:

This panel lets you specify which types of VTAM data to collect.

Note: If you change any of these values after initial configuration, you must run the JCL jobsdescribed in “Running the JCL Jobs” on page 90 to incorporate this change into production. Verifythat these jobs complete successfully. When the jobs complete successfully, the values will have beenupdated.a. Use the information in Table 21 on page 98 to complete this panel:

-------------------- SPECIFY COMPONENT CONFIGURATION (Page 4)-----------------

Specify the following global information

Enterprise Extender and High Performance Routing Statistics Collection==> Y (Y,N)

All High Performance Routing Connections==> N (Y,N)

CSM Buffer Reporting==> Y (Y,N)

Buffer Pool/VTAM Environment Data Collection==> Y (Y,N)





Enterprise Extender and HighPerformance RoutingStatistics Collection

Determines whether to collect Enterprise Extender and High Performance Routingstatistics. Y (the default) indicates Enterprise Extender and High PerformanceRouting statistics will be collected. N indicates Enterprise Extender and HighPerformance Routing statistics will not be collected.

All High PerformanceRouting Connections

Determines if High Performance routing statistics will be collected for allconnections or only Enterprise Extender connections. Y indicates that performancedata for all High Performance Routing connections will be collected, regardless ofwhether this data flows over Enterprise Extender connections. N (the default)indicates that performance data will be collected only for High Performance Routingconnections that flow data over Enterprise Extender connections.

CSM Buffer Reporting Determines whether to collect Communications Storage Manager buffer reportingdata. Y (the default) indicates Communications Storage Manager buffer reportingdata will be collected. N indicates Communications Storage Manager bufferreporting data will not be collected.

Buffer Pool/VTAMEnvironment Data Collection

Determines whether to collect data for VTAM buffer pools, applications, extents, andaddress spaces. Y (the default) indicates VTAM data will be collected. N indicatesVTAM data will not be collected. If you specify Y, you will see an additionalconfiguration panel. You may not start or modify the collection of VTAM bufferpools or VTAM address space data using the KN3FCCMD START SNAC command unlessyou indicate Y for this parameter. For more information about this command, seeAppendix C, “KN3FCCMD and KONFCCMD command reference,” on page 203.

b. When all entries on this panel are complete, press Enter. If you specified Y as the value for BufferPool/VTAM Environment Data Collection, then you see Figure 16. If you specified N, then youare returned to the Specify Configuration Parameters panel shown in Figure 11 on page 93 exceptthat dates and times are now provided for Option 1.

6. If you specified Y as the value for Buffer Pool/VTAM Environment Data Collection, pressing Enterin the previous step causes the Specify VTAM Applid Values (Page 5) panel shown in Figure 16 tobe displayed:

This panel lets you define the collection interval for SNA data and specify the APPLID informationrequired by the monitoring agent.

Note: If you change any of these values after initial configuration, you must run the JCL jobsdescribed in “Running the JCL Jobs” on page 90 to incorporate this change into production. Verifythat these jobs complete successfully. When the jobs complete successfully, the values will have beenupdated.a. Use the information in Table 22 on page 99 to complete this panel:

-------------- SPECIFY VTAM APPLID VALUES (Page 5)--------------------


SNA data collection interval:==> 5 (1-60 minutes)

Specify the Mainframe Networks APPLID information on this panel:

Major node ==> CTDN3NCNM application ==> CTDN3SP

Figure 16. Specify VTAM applid values / RTE (Page 5) panel. Specify VTAM applid values / RTE (Page 5) panel


Table 22. Parameters and explanations for the Specify VTAM APPLID Values (Page 5) panel


SNA Data Collection Interval Determines how often VTAM buffer pool and VTAM address space performancedata will be collected. A value of “1” means that SNA data is collected everyminute. This value is expressed as a whole number from 1 to 60, indicating thecollection interval in minutes. The default is 5 minutes.

Specify the Mainframe Networks APPLID information on this panel: APPLIDs are the names by which logicalunits are known in a VTAM network. Default APPLIDs are provided by the Configuration Tool. You can keep thesedefault names or change them to match naming conventions at your site. For more information about how theConfiguration Tool processes VTAM APPLIDs, enter README APP on the command line.

Major Node Specify the name of the VTAM major node name that contains all the VTAMAPPLID definitions for OMEGAMON XE for Mainframe Networks. This membermust be moved to your VTAMLST concatenation. The name of this major node isalso the name used to activate the VTAM APPLIDs. The default is CTDN3N.

CNM Application Specify the APPLID for VTAM Secondary Program Operator. As a VTAM SecondaryProgram Operator, the OMEGAMON XE for Mainframe Networks monitoring agentcan issue VTAM commands and receive the VTAM responses. The default isCTDN3SP.

Note: Perform all configuration steps found on this panel. If you change any of these values after initialconfiguration, you must Run the JCL jobs as described in “Running the JCL Jobs” on page 90 to incorporate thischange into production. Verify that these jobs complete successfully. When the jobs complete successfully, the valueswill have been updated.

b. When all entries on this panel are complete, press Enter and you are returned to the SpecifyConfiguration Parameters panel shown in Figure 11 on page 93 except that dates and times arenow provided for Option 1.

7. Select 2 Specify TCP/IP monitored systems information and press Enter. This action causes the panelshown in Figure 17 to be displayed.

This panel provides a list of TCP/IP address spaces that OMEGAMON XE for Mainframe Networkswill monitor when configuration is complete. From this panel, you can verify that the informationshown is correct, override global values with system-specific values, or supply additional TCP/IPinformation by adding a monitored system or cloning another monitored system definition with theCopy function.By default, OMEGAMON XE for Mainframe Networks monitors all address spaces. However, in V4.2and later, you can specify which stacks are monitored on a per stack basis. Using the Specify TCP/IPMonitored Systems Information path, you define monitoring characteristics of individual systems(those that do not use the global default) by responding yes or no to the question "Do you want tomonitor this system." The value determines whether this stack is monitored. Y indicates this stack ismonitored. N indicates this stack is not monitored. The default is Y. You must use this path toexplicitly eliminate a discovered TCP/IP stack from being monitored.

-------- SPECIFY TCP/IP MONITORED SYSTEMS INFORMATION / RTE: HUBN3IRA---------

The following is a list of TCP/IP systems that will be monitoredby this product. The global override settings are determined by theselections on the TCP/IP Monitored Systems Information panel.

Actions: A Add, C Copy, D Delete, U Update, V View

TCP/IPAddress

Act Sys Space Global Override Monitor_ $$$$ $$$$$$$$ N Y_ SYSA sysname Y Y

Figure 17. Specify TCP/IP monitored system information panel. Specify TCP/IP monitored system information panel


The configuration options provided in the $$$$ entry is used whenever a specific entry in notincluded in the table for a detected TCP/IP address space. The $$$$ entry is referred to as the globaldefault. You cannot Delete (D) this value, but you can Update (U) it. If you want to apply differentmonitoring characteristics to each TCP/IP address space, you must Add (A) this address space fromthis panel.Specify one of these actions shown in Table 23 in the Act field adjacent to the system name:

Table 23. Parameters and explanations for the Specify TCP/IP Monitored Systems Information panel


A Add a system to monitor. If you want to add a system to monitor, follow the steps in “Adding,changing, or updating a monitored system definition.” When you add a new monitored system, thedefaults you specified in the Option 1 Specify Component Configuration path are displayed butall other fields are blank. All fields can be edited.

This section shows you how to add a new monitored system information for a system. This processbegins on the Specify TCP/IP Monitored Systems Information panel, shown in Figure 17 on page99.

C Copy the system monitored information. When you copy one monitored system definition to createa new monitored system, the defaults you specified in the Option 1 Specify ComponentConfiguration path for the configuration you are cloning are displayed but all fields can be edited.

D Delete a system from monitoring. When you delete a monitored system configuration, no otherpanels are displayed. The system definition is removed and no longer visible on the SpecifyTCP/IP Monitored Systems Information panel shown in Figure 17 on page 99.

U Update the system monitored information. When you update a monitored system definition, thevalues you have already specified in the Option 1 Specify Component Configuration path aredisplayed but all other fields except Sys and TCP/IP address space can be edited.

V View the system monitored information. When you select View, you can see all the values specifiedfor monitored system but you cannot change any of the information.

Note:

1. If you change any of these values after initial configuration, you must Run the JCL jobs as described in“Running the JCL Jobs” on page 90 to incorporate this change into production. Verify that these jobs completesuccessfully. When the jobs complete successfully, the values will have been updated.

2. A system name of four (4) dollar signs or a TCP/IP address space of eight (8) dollar signs is a reservedcombination. You may not change the override setting for this reserved combination. To change these globalvalues, return to the Specify Configuration Parameters panel and select Option 1 Specify TCP/IP ComponentConfiguration. See “Step 2: Specifying configuration parameters” on page 92.

3. If you are using the default global system definitions for a stack or address space, when you edit the N3#5 JCLjob, you will not see a specific command for that stack because it is covered by the global definition. Eventhough you don't see the stack listed in the JCL job, the changes for these stacks are picked up when the N3#5JCL job is run.

Perform one of these operations. At any time, you can return to the panel found in Figure 17 on page99 and press F3. When you finish configuring address spaces, choose Option 3 Create monitoringagent runtime members shown in Figure 11 on page 93 to create the N3#5xxx job, which willincorporate these changes into production.

8. Review and submit the JCL. You might want to change the jobname to match the member name sothat you can easily identify this job later on. Verify that the job completes with a return code of zero.

9. After the JCL has been submitted to create the TCP/IP monitored systems member, enter F3 to bereturned to the Specify Configuration Parameters panel shown in Figure 26. Press F3 again to bereturned to the Configure OMEGAMON XE for Mainframe Networks panel shown in Figure 10 onpage 92.

Adding, changing, or updating a monitored system definitionYou can add, change, or update a monitored system definition using these steps.


About this task

When you add, change, or update a monitored system definition, the defaults you specified in the Option1 Specify Component Configuration path are displayed.v When you add a new monitored system, the defaults you specified in the Option 1 Specify

Component Configuration path are displayed but all other fields in the Add panel sequence are blankand can be edited.

v When you copy one system definition to another, you use the cloned values from another monitoredsystem or LPAR as the starting place for configuring another. All fields in the Copy panel sequence canbe updated.

v When you update a monitored system definition, all values except the Sys and TCP/IP address spacecan be changed.

v When you view a monitored system definition, nothing can be changed.

Note: If you use the default colors for IPSF, fields highlighted in green can be changed; fields highlightedin white cannot be changed.

This process begins on the Specify TCP/IP Monitored Systems Information panel, shown in Figure 17on page 99. The example that follows explains the process for adding a new monitored system definition,though the same panels are available with the other options as well.

Procedure1. To add configuration information for a monitored TCP/IP address space, enter A in the ACT field on

the Specify TCP/IP Monitored Systems Information panel shown in Figure 17 on page 99. Thisaction causes the first of two Add TCP/IP Monitored System Info panels shown in Figure 18 isdisplayed.

Use the values in Table 24 to complete this panel:

Table 24. Parameters and explanations for the Add TCP/IP Monitored Systems Info panel


Sys The name of the system to be monitored. The default is four dollar signs ($$$$).Whenever there is not a specific entry in the table for a detected TCP/IP address space,the configuration options provided in the $$$$ entry will be used.

----------- ADD TCP/IP MONITORED SYSTEMS INFO / RTE: HUBN3IRA --------------COMMAND ===>

Complete the items on this panel:

Sys ==>

TCP/IP address space ==>

TCP/IP profile dataset name: ==>Member name ==> (Optional)

Do you want to monitor this stack? ==> (Y,N)

TCP/IP Connection Collection Override ==> (Y,N) (Optional)

IP Filters and IPSec Tunnels Collection Override ==> (Y,N) (Optional)

Routing Table Collection Override ==> (Y,N) (Optional)Routing Table Collection Frequency ==> (1-99) (Optional)

Figure 18. Add TCP/IP monitored systems information panel. Add TCP/IP monitored systems information panel


Table 24. Parameters and explanations for the Add TCP/IP Monitored Systems Info panel (continued)


TCP/IP address space The name of the TCP/IP address space on the monitored system. The default is eight (8)dollar signs. A maximum of eight (8) TCP/IP address spaces will be monitored usingglobal override specifications.

TCP/IP profile data setname

The name of the data set that contains the TCP/IP profiles. This data set can be either apartitioned data set or a sequential data set. The default is TCPIP.PROFILE.TCPIP. If youspecify a partitioned data set, then you must supply a member name. This value cannotbe altered during View (V) processing.

Member name (optional) The member name of the TCP/IP profiles in the TCP/IP profile data set. This value isrequired if you specify a partitioned data set. It is not used if you specify a sequentialdata set. This value cannot be altered during View (V) processing.

Do you want to monitorthis stack?

Determines whether to monitor this stack. Y (the default) indicates this stack will bemonitored. N indicates this stack will not be monitored. This is a required field.

TCP/IP ConnectionCollection Override

Determines whether to collect TCP/IP Connection and Application Performance Statisticsfor this address space. Y indicates TCP/IP Connection and Application PerformanceStatistics will be collected for this address space. N indicates TCP/IP Connection andApplication Performance Statistics will not be collected. See Note at the end of this tablefor additional restrictions.

IP Filters and IPSecTunnels CollectionOverride (optional)

Determines whether to collect IP Security and tunnel data for this address space. Yindicates IP Security data will be collected. N indicates IP Security data will not becollected. See the Notes at the end of this table for additional restrictions.

Routing Table CollectionOverride

Determines whether to collect routing table data will be collected for this address space.Y indicates SNMP routing data will be collected for this address space. N indicatesSNMP routing data will not be collected for this address space. See Note at the end ofthis table for additional restrictions.

Routing Table CollectionFrequency

Determines how often the routing table information will be collected for this addressspace. A value of 1 means that routing information is collected every collection interval.The value is expressed as a whole number from 1 to 99. Setting a higher value meansyou collect the data less often, reducing overall CPU consumption while still making thedata available.

Note:

1. Leaving any field blank results in the Configuration Tool using the global defaults.

2. These values cannot be altered during View (V) processing.

When you have provided these values, press Enter to save them and advance to the Add TCP/IPMonitored Systems Info2 panel.

2. This action causes the second of three Add TCP/IP Monitored Systems Info2 for the specified RTEpanel, shown in Figure 19 on page 103, to be displayed.


Use the information in Table 25 to complete this panel:

Table 25. Parameters and explanations for the Add TCP/IP Monitored Systems Info2 panel


TN3270 CollectionOverride (optional)

Determines whether to override the global TN3270 Server Statistics Collection setting forthe TN3270 server running on this system. Y indicates TN3270 data will be collected forthe TN3270 server running on this system. N indicates TN3270 data will not be collectedfor the TN3270 server running on this system. See the Note at the end of this table foradditional restrictions.

TN3270 Display IntervalOverride (optional)

Determines how long TN3270 server statistics will be displayed on the Tivoli EnterprisePortal for the TN3270 server running on this system. This value is expressed as a wholenumber in hours from 1 to 24. The default is 2 hours. See the Note at the end of thistable for additional restrictions.

FTP Collection Override Determines whether to override the global FTP Collection setting in this address space. Yindicates FTP data will be collected for this address space. N indicates FTP data will notbe collected for this address space. See the Note at the end of this table for additionalrestrictions.

FTP Display IntervalOverride

Determines how long FTP data will be displayed on the Tivoli Enterprise Portal for thisaddress space. A value of 1 means that FTP data is displayed for one hour. This value isexpressed as a whole number in hours from 1 to 24. The default is 2 hours. See the Noteat the end of this table for additional restrictions.

Note:



When you have provided these values, press Enter to save them and advance to the to the AddTCP/IP Monitoring Systems Info3 panel shown in Figure 20 on page 104.

3. This action causes the third of three Add TCP/IP Monitored Systems Info3 for the specified RTEpanel, shown in Figure 20 on page 104, to be displayed.

-------------- ADD TCP/IP MONITORED SYSTEMS INFO2 / RTE: HUBN3IRA -----------COMMAND ===>


Sys ==>



TN3270 Collection Override ==> Y (Y,N) (Optional)TN3270 Display Interval Override ==> 2 (1-24 hours) (Optional)

FTP Collection Override ==> Y (Y,N) (Optional)FTP Display Interval Override ==> 2 (1-24 hours) (Optional)

Figure 19. Add TCP/IP monitored systems info2 panel. Add TCP/IP monitored systems info2 panel



Table 26. Parameters and explanations for the Add TCP/IP Monitored Systems Info3 panel


OSA Collection Override(optional)

Determines whether to override the global OSA Collection setting for this address space.Y indicates OSA data will be collected for this address space. N indicates OSA data willnot be collected for this address space.

Interface CollectionOverride (optional)

Determines whether to override the global Interface Collection setting for this addressspace. Y indicates Interface data will be collected for this address space. N indicatesInterface data will not be collected for this address space.

Interface DLC CollectionOverride (optional)

Determines whether to override the global Interface Data Link Control (DLC) Collectionread and write queue data for interfaces defined to this address space. Y indicates thatInterface DLC read and write queue data for this address space will be collected. Nindicates Interface DLC read and write queue data for this address space will not becollected.

Stack Layer CollectionOverride (optional)

Determines whether to override the global TCP/IP Stack Layer Statistics Collectionsetting for this address space. Y indicates TCP/IP Stack Layer data will be collected forthis address space. N indicates TCP/IP Stack Layer data will not be collected for thisaddress space.

Note:



When you have provided these values, press Enter to save them and return to the Specify TCP/IPMonitoring Systems Information panel shown in Figure 17 on page 99.

4. You may add, update, or copy any of the monitored systems information using the processesdescribed in the previous steps until you have made all configuration override updates to TCP/IPaddress spaces found in Figure 17 on page 99. When you have finished adding configurationinformation for the monitored TCP/IP address spaces, you will be returned to the Specify TCP/IPMonitored Systems Information panel shown in Figure 17 on page 99.

5. Press F3 to return to the panel shown in Figure 11 on page 93. Select Option 3 Create monitoringagent runtime members to view the JCL that is generated to create the TCP/IP monitored systemmember, &rhilev.&midlev.&rtename.RKANPARU(KN3TCPMO). Submit JCL job N3#5xx. Uponsuccessful completion of this job, press F3 twice to return to the Configure OMEGAMON XE forMainframe Networks main menu panel, shown in Figure 10 on page 92.

-------------- ADD TCP/IP MONITORED SYSTEMS INFO3 / RTE: HUBN3IRA -----------COMMAND ===>


Sys ==>



OSA Collection Override ==> (Y,N) (Optional)

Interface Collection Override ==> (Y,N) (Optional)

Interface DLC Collection Override ==> (Y,N) (Optional)

Stack Layer Collection Override ==> (Y,N) (Optional)

(PF3 to CANCEL or Enter to proceed)

Figure 20. Add TCP/IP monitored systems info3 panel. Add TCP/IP monitored systems info3 panel


Step 3: Specifying agent address space parametersUse this step to create the address space in which the OMEGAMON XE for Mainframe Networksmonitoring agent will run and define how this agent will communicate with Tivoli Enterprise MonitoringServer.

About this task

This step is used to provide information required to create the address space and communicate with theTivoli Enterprise Monitoring Server of your choice. In a shared address space environment, only theaddress space owner (agent that created the address space) can change these parameters.

Procedure1. From the Configure OMEGAMON XE for Mainframe Networks shown in Figure 10 on page 92,

select 3 Specify Agent Address Space Parameters. The Specify agent address space parameters panelshown in Figure 21 is displayed. This panel is used to specify the agent address space parameters andcommunication protocol priority sequence for the monitoring agent. The values in the second sectionof the panel are used to specify communication protocols that this agent will use to connect to theTivoli Enterprise Monitoring Server. You must select a communication protocol that your TivoliEnterprise Monitoring Server was configured to support in your environment using the Specify AgentAddress Space Parameters panel, shown in Figure 21:


Table 27. Parameters and explanations for the Specify Agent Address Space Parameters panel


Agent started task Specify the started task name for the agent. This started task must be copied to yoursystem procedure library. The default is CANSN3.

-------------------- SPECIFY AGENT ADDRESS SPACE PARAMETERS -------------------COMMAND ===>

The following information is needed to define the Agent address space.Agent started task ==> CANSN3Connect to TEMS in this RTE ==> Y (Y, N)

Name of Primary TEMS ==> HUBN3IRA:CMS

Specify the communication protocols in priority sequence.IP.PIPE ==> 1 (Non-secure NCS RPC)IP.UDP ==> 2 (Non-secure NCS RPC)SNA.PIPE ==> 3 (Non-secure NCS RPC)IP6.PIPE ==> _ (IP.PIPE for IPV6)IP6.UDP ==> _ (IP.UDP for IPV6)IP.SPIPE ==> _ (Secure IP.PIPE)IP6.SPIPE ==> _ (Secure IP.PIPE for IPV6)

Note: Enable only protocol(s) in use by the Primary TEMS.

Figure 21. Specify agent address space parameters panel. Specify agent address space parameters panel


Table 27. Parameters and explanations for the Specify Agent Address Space Parameters panel (continued)


Connect to TEMS in thisRTE

Specify Y if you want to connect to a Tivoli Enterprise Monitoring Server alreadyconfigured in the RTE. This is the default when a Tivoli Enterprise Monitoring Server isdetected in the RTE. To select a different primary Tivoli Enterprise Monitoring Server toconnect to, specify N.

Press F10 (the CMS List key) to display a list Tivoli Enterprise Monitoring Serversalready configured in this RTE. The initial TEMS List is derived from local and non-localz/OS Tivoli Enterprise Monitoring Server configured in this Configuration Toolenvironment. They are defined in this RTE or another RTE that is accessible to thisinstallation library. The agent can connect to any Tivoli Enterprise Monitoring Server thatruns on any platform.

This Tivoli Enterprise Monitoring Server pertains to:

1. A Tivoli Enterprise Monitoring Server defined in another INSTLIB (or another CSI)that is not accessible to this &hilev.&midlev.INSTLIB library.Note: The monitoring agent must also be installed in the non-local INSTLIB or CSIenvironment where the primary monitoring server is installed, if this monitoringagent reports to this non-local monitoring server.

2. A Tivoli Enterprise Monitoring Server defined in another platform (non-z/OS).

If the preferred primary Tivoli Enterprise Monitoring Server is located in anotherConfiguration Tool environment or in another platform, then from theCommunication Selection Panel, press the F5=Advanced key to navigate to theSpecify Agent Primary TEMS Values panel. On this panel, specify the values for theprimary Tivoli Enterprise Monitoring Server. When no Tivoli Enterprise MonitoringServer is defined in this RTE, the default is N, and you must select a Tivoli EnterpriseMonitoring Server from the list displayed on the Communication Selection panel.

Note: If the monitoring agent must switch primary Tivoli Enterprise Monitoring Serverconnections in the future, then on the Specify Agent Address Space Parameters panel,press the F10=CMS List key to navigate to the Communication Selection panel. Thesame procedure also applies if any of the primary Tivoli Enterprise Monitoring Servervalues that this agent connects to have changed. The monitoring agent must reconnect tothe primary monitoring server to refresh the monitoring server values generated in themonitoring agent gent runtime members.

Name of primary TEMS If a primary Tivoli Enterprise Monitoring Server has been selected, it will be listed here.If a primary Tivoli Enterprise Monitoring Server has not been selected, then None will bedisplayed.Note: If the monitoring agent is connecting to the local monitoring server, and SystemVariable mode is enabled, then the System Variable monitoring server name is displayed.




Specify thecommunication protocolsin priority sequence

Specify which communication protocols you want the monitoring gent to support whenconnecting to its primary Tivoli Enterprise Monitoring Server. By default, the firstmonitoring agent configured in this RTE takes the default protocols set by the monitoringserver, if a local monitoring server is configured in this RTE. Otherwise, the defaultIP.PIPE, IP.UDP and SNA.PIPE protocol ordering is set for the monitoring agent, if bothTCP and VTAM values are provided during initial RTE creation. You must specify atleast one protocol. The communication protocols are used in the priority sequence thatyou set by numbering each protocol. They are used in the order in which they appear inthe KDE_TRANSPORT environment in the KN3ENV member in the &hilev.&midlev.&rtename.RKANPARU library.

Environment variable KDE_TRANSPORT configures the transport ID managed bycomponent KDE. Each transport ID consists of an address family and a protocolconnected by a period (for example, IP.PIPE or IP.UDP). For compatibility, IP is assumedto be an alias for IP.UDP, and SNA is assumed to be an alias of SNA.PIPE.KDE_TRANSPORT prioritizes and configures the available transports. Transport IDs andparameters are then listed in preference order.

See the Configuration Tool online help for this panel for an example of how to specifythese protocols in a mixed IPv4 and IPv6 environment.

In the second part of this panel, you specify the priority sequence for communicationprotocols. The choices are:

IP.PIPE - Non-secure NCS RPCSpecifies the use of the TCP/IP protocol for underlying communications. Thisprotocol uses non-secure Network Computing System (NCS) that conform to theNetwork Computing Architecture. NCS includes the Remote Procedure Call(RPC) runtime library, the Location Broker, and the Network Interface DefinitionLanguage (NIDL) compiler.Note: IP.PIPE should be used for communication if the z/OS system that thismonitoring agent runs on supports TCP. In addition, enable only protocols inuse by the monitoring agent's Primary monitoring server.

IP.UDP - Non-secure NCS RPCSpecifies the use of the UDP/IP (User Datagram Protocol), which is the"packet-based," connectionless-oriented protocol. This protocol uses non-secureNetwork Computing System (NCS) that conform to the Network ComputingArchitecture.Note: Enable only protocols in use by the monitoring agent's Primarymonitoring server.

IP6.PIPE - IP.PIPE for IPV6Specifies the use of the TCP/IP protocol for underlying communications. Thisprotocol uses non-secure Network Computing System (NCS) that conform to theNetwork Computing Architecture.Note: IPV6 must be installed and operational to use this protocol. Enable onlyprotocols in use by the monitoring agent's Primary monitoring server.




Specify thecommunication protocolsin priority sequence(continued)

IP6.UDP - IP.UDP for IPV6Specifies the use of the UDP/IP (User Datagram Protocol), which is the"packet-based," connectionless-oriented protocol. This protocol uses non-secureNetwork Computing System (NCS) that conform to the Network ComputingArchitecture.Note: IPV6 must be installed and operational to use this protocol. Enable onlyprotocols in use by the monitoring agent's Primary monitoring server.

IP.SPIPE - Secure IP.PIPESpecifies the use of the TCP/IP protocol for underlying communications. Thisprotocol uses secure Network Computing System (NCS) that conform to theNetwork Computing Architecture.Note: The Transparent Transport Layer Security (TTLS) feature of z/OSCommunications Server must be available to use this protocol.

IP6.SPIPE - Secure IP.PIPE for IPV6Specifies the use of the TCP/IP protocol for underlying communications. Thisprotocol uses secure Network Computing System (NCS) that conform to theNetwork Computing Architecture.Note: The Transparent Transport Layer Security (TTLS) feature of z/OSCommunications Server must be available to use this protocol.

SNA.PIPE - Non-secure NCS RPCSpecifies the use of Systems Network Architecture (SNA)/AdvancedProgram-To-Program Communications (APPC). This protocol uses non-secureNetwork Computing System (NCS) that conform to the Network ComputingArchitecture.Note: IPV6 must be installed and operational to use this protocol. Enable onlyprotocols in use by the monitoring agent's Primary monitoring server.

Note:

1. There should only be one remote Tivoli Enterprise Monitoring Server in a given z/OSimage that reports to the same hub Tivoli Enterprise Monitoring Server.

2. If the hub is using the IP.PIPE protocol for connection, the remote must also specifyIP.PIPE as one of its protocols.

Press Enter to advance to the configuration panels for the protocols you specified.2. You are presented with a panel for each protocol specified. Enter the appropriate values for each

panel, and then press Enter.v If you specified IP.PIPE, IP6.PIPE, IP.SPIPE, IP6.SPIPE as one of your protocols, you will see the

panels shown in Figure 22 on page 109:



Table 28. Parameters and explanations for the Specify Agent IP.PIPE Communication Protocol and Specify AgentIP.UDP Configuration Values panels


Network address(Hostname)

Specify the network address of the z/OS system on which this monitoring agent will run.A network address may be specified as one of the following values:

v A fully qualified hostname, for example sys.ibm.com

v The first qualifier of the fully qualified hostname, for example sys from sys.ibm.com

v An IPv4 address in dotted decimal notation, for example 9.67.1.100

To determine this value, issue the TSO HOMETEST command. If you decide to specify thehostname value for the network address, use the first qualifier of the fully qualifiedhostname if the z/OS domain name resolver configuration specifies a search path thatwould include the target domain suffix.

Otherwise, specify the fully qualified hostname when using a Domain Name Server(DNS). If you specify the IP address value for network address, use the assigned IPv4address written in dotted decimal notation. This scheme is numeric and consists of fourgroups separated by a period (.).Note: IBM managed system names are generally derived from the TCP/IP hostname ofthe machine that the product runs on. Ensure that this value is different from the nameof the Tivoli Enterprise Monitoring Server (TEMS name).

Started task You are prompted for a TCP/IP started task name when you create a runtimeenvironment and when you configure a monitoring server or monitoring agent. In a newruntime environment, the default value for the TCP/IP started task name is an asterisk(*). The default, which uses the first TCP/IP stack that was started, is suitable if thissystem contains a single TCP/IP stack.

If the system contains more than one TCP/IP stack, you can specify the started taskname of the TCP/IP stack you want to use; or you can specifiy the number sign (#),which is translated to a blank and allows the TCP/IP environment to choose the stack touse, either through TCP/IP definitions or through the use of the SYSTCPD DD statement.

------------------ SPECIFY AGENT IP.PIPE CONFIGURATION VALUES -----------------COMMAND ===>

Specify the IP.PIPE communication values for this Agent. These networkaddress-related values are for the z/OS system where the Agent runs on.

* Network address (Hostname):==> NMPIPL16.TIVLAB.RALEIGH.IBM.COM

Started task ==> * (Recommended default = *)Network interface list: (If applicable)

==>

Specify additional configuration values.

Address translation ==> N (Y, N)Partition name ==>

* Note: See F1=Help for TSO HOMETEST command instructions.

Figure 22. Specify IP.PIPE communication protocol panel. Specify IP.PIPE communication protocol panel


Table 28. Parameters and explanations for the Specify Agent IP.PIPE Communication Protocol and Specify AgentIP.UDP Configuration Values panels (continued)


Network interface list Specify a list of network interfaces you want the monitoring agent to use. This parameteris required for sites that are running multiple TCP/IP interfaces or network adapters onthe same z/OS image.

Setting this parameter allows you to direct the monitoring agent to connect to a specificTCP/IP local interface. Specify the network adapters as one or more of the followingvalues:

v A fully qualified hostname, for example sys.ibm.com

v The first qualifier of the fully qualified hostname, for example sys from sys.ibm.com

v An IPv4 address in dotted decimal notation, for example 9.67.1.100

If your site supports DNS, you can enter the short hostname or an IP address. If your sitedoes not support DNS, you must enter the fully qualified hostname. This field is onlyapplicable for networks with multiple interface cards for which a specific output networkinterface list is required.

If an interface address or a list of interface addresses is specified, the Configuration Toolgenerates the KDEB_INTERFACELIST parameter in the KN3ENV member of the&hilev.&midlev.RKANPARU library.Note: This value defaults to the IPv4 network interface list setting used by the TivoliEnterprise Monitoring Server if one is configured in this IPL16 RTE. Also, separate theentries using a blank space between interface addresses. For example:

==> 129.0.131.214 SYS1 SYS.IBM.COM

In addition, there are special considerations when specifying !<&value> or * for this field.Type README COM on the command line to see more information about network interfacelist considerations and usage.

Address translation Specify Y to configure IP.PIPE support for communication across firewalls using addresstranslation.

Partition name Specify the partition name that identifies the location of this TEMS (namespace) relativeto the firewallsi used for address translation.Note: The Tivoli Enterprise Monitoring Server that this monitoring agent connects tomust have a corresponding partition reference entry.

In this task, the partition table is populated or modified. The partition table containslabels and associated socket addresses which are provided by the firewall administrator.

The labels in the partition table are configured into and used by IBM products on anexternal network, outside a firewall, during the Tivoli Enterprise Monitoring Server(TEMS) connection establishment phase. The first part of this connection establishment isthe lb lookup, which requires that the location brokers to return the socket address of themonitoring server.

The partition table is used by the brokers, matching a partition name for a client to thelabels in the partition table. On a match, the associated socket address in the partitiontable is returned to the client outside the firewall. This socket address is used by the IBMproducts to traverse the firewall and connect to the monitoring server.

Each entry consists of a label or partition name, a protocol (IP for UDP or IP.PIPE forTCP), and a hostname or dotted-decimal IP address. The well-known port (Hub port)must be authorized by the firewall administrator.

v If UDP is the protocol configured in the partition table, then a range of (UDP) portsmust be authorized by the firewall administrator (in addition to the well-known port).

v If TCP is the protocol, no additional ports other than the well-known TEMS port needbe authorized.


After you provide the IP.PIPE configuration values, press Enter and you see the next protocol in theorder that you specified.

v If you specified IP.UDP, IP6.UDP as one of your protocols, then pressing Enter from the IP.PIPEconfiguration values panel causes the Specify Agent IP.UDP Configuration Values panel shown inFigure 23 to be displayed.

This panel is used to specify the IP.UDP (User Datagram Protocol) values for configuring where themontioring agent address space is to run on your site. These values apply to any IP.UDP-relatedprotocols you have enabled on the Specify Agent Address Space Parameters panel shown inFigure 21 on page 105.Use the information in Table 28 on page 109 to complete this panel.After you provide the values required by the Specify Agent IP.UDP Configuration Values panel,press Enter to see the next protocol in the order that you specified.

v If you specified SNA as one of your protocols, Specify Agent SNA Configuration Values

This panel is used to specify the SNA values that this monitoring agent will use to run on your site.a. Use the information in Table 29 on page 112 to complete this panel:

----------------- SPECIFY AGENT IP.UDP CONFIGURATION VALUES ------------------COMMAND ===>

Specify the IP.UDP communication values for this Agent. These networkaddress-related values are for the z/OS system where the Agent runs on.

* Network address (Hostname):==> NMPIPL16.TIVLAB.RALEIGH.IBM.COM

Started task ==> * (Recommended default = *)Network interface list: (If applicable)

==>

* Note: See F1=Help for TSO HOMETEST command instructions.

Figure 23. Specify Agent IP.UDP Configuration Values panel. Specify Agent IP.UDP Configuration Values panel

-------------------- SPECIFY AGENT SNA CONFIGURATION VALUES ------------------COMMAND ===>

Specify the SNA communication value for this Agent.

VTAM applid prefix ==> CTDN3

Figure 24. Specify Agent SNA Configuration Values panel. Specify Agent SNA Configuration Values panel


Table 29. Parameters and explanations for the Specify Agent SNA Configuration Values panel


VTAM applid prefix Specify the applid prefix to create the VTAM node and applids required by themonitoring agent. This field is required for SNA connection.Note: Type README APP on the command line to get more information on how theConfiguration Tool processes VTAM applids. Use the F6=Applids key to specify theVTAM major node and applid values.

If System Variable support is enabled, the Applid prefix must end with a dot (.) if thesymbolic used as part of the Applid prefix is at the end of the value. Type README SYS onthe command line to get more information on how the Configuration Tool processesVTAM applids using z/OS system symbols.

For detailed help about the required values, press F1.3. When you have provided all the protocol values, press Enter to save them and return to the

Configure IBM OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page 92.

Results

You might also want to specify values found on the "Specify Advanced Agent Configuration Values"panel. This panel is used to enable a secondary monitoring server or to enable communications with theIBM Tivoli NetView for z/OS product. At a minimum, you will probably want to enable TCP/IP to berecycled. The Tivoli Enterprise Monitoring Server on z/OS and the OMEGAMON XE for MainframeNetworks monitoring agent can now automatically reconnect to the TCP/IP address space when TCP/IPis recycled. This capability must be enabled on both the hub monitoring server and the monitoring agentby changing the default value of N to Y on the Specify Advanced Configuration Values panel with the"Reconnect after TCP/IP recycle" setting. If you specify Y, then if the TCP/IP stack which is used by themonitoring server is recycled, the monitoring server address space reconnects to it without beingrecycled. If this parameter is set to N (the default), then if the TCP/IP stack which is used by themonitoring server is recycled, the monitoring server address space must also be recycled to re-establishTCP/IP connectivity. See the IBM Tivoli Management Services on z/OS: Configuring the Tivoli EnterpriseMonitoring Server on z/OS for more information about this capability.

To specify these or other values found on the "Specify Advanced Agent Configuration Values" panelshown in Figure 21 on page 105, press F5=Advanced (or whatever function key is customized on yoursystem to show the Advanced options). This action causes the "Specify Advanced Agent ConfigurationValues" panel shown in Figure 25 on page 113 to be displayed:


1. Use the information in Table 30 on page 114 to complete this panel:

----------------- SPECIFY ADVANCED AGENT CONFIGURATION VALUES -------------COMMAND ===>

Enable secondary TEMS ==> N (Y, N)Name of secondary TEMS ==> None

Enable startup console messages ==> N (Y, N)Enable WTO messages ==> N (Y, N)Reconnect after TCP/IP recycle ==> N (Y, N)Intervals (hh:mm):

Storage detail logging: Hours ==> 0 (0-24) Minutes ==> 60 (0-60)Flush VSAM buffers: Hours ==> 0 (0-24) Minutes ==> 30 (0-60)

Virtual IP Address (VIPA) type ==> N (S=Static, D=Dynamic, N=None)Minimum extended storage ==> 768000 KLanguage locale ==> 1 (Press F1=Help for a list of codes)Program to Program Interface (PPI) information:

Forward Take Action commands to NetView for z/OS? ==> N (Y, N)NetView PPI receiver ==> CNMPCMDR Agent PPI sender ==>

z/OS Audit collection values:Enable/Disable z/OS audit collection ==> (M, B, D, X)Maximum in-memory cache entries ==> (10-1000)Domain ==>

Enable Self-Describing Agent processing (TEMA_SDA) ==> Y (Y, N)Enter=Next F1=Help F3=Back F5=Advanced F10=CMS List

Figure 25. Specify Advanced Agent Configuration Values panel. Specify Advanced Agent Configuration Values panel


Table 30. Parameters and explanations for the Advanced agent configuration values panel


Enable secondary TEMS Specify Y to this parameter if you want to use a secondary Tivoli Enterprise MonitoringServer (monitoring server). To remove the secondary monitoring server definition, enterN. The currently selected secondary monitoring server is displayed. If a secondarymonitoring server is defined, this agent automatically connects to it when the primarymonitoring server is unavailable or terminates. The default is N. See the "Sharing addressspace when enabling secondary TEMS" help topic for additional considerations whenenabling this feature.

To select a different secondary monitoring server to connect to, specify N. PressF10=CMS List and the Configuration Tool presents the Communication Selection Panel(KCIPCMSS) with a list of monitoring servers. The initial monitoring server list isderived from local and non-local z/OS monitoring server configured in this&rhilev.&midlev.INSTLIB.

The list of secondary monitoring servers eligible for selection has at least onecommunication protocol value in common with the primary monitoring server that thisagent connects to (for example, the TCP port number or the SNA Local Location Broker(LLB) applid). The secondary monitoring server consists of monitoring servers defined inthis RTE or another RTE that is accessible to this installation library.

The monitoring agent may connect to any monitoring server that runs on any platform.This monitoring server pertains to:

1. A monitoring server defined in another INSTLIB (or another CSI) that is notaccessible to this &rhilev.&midlev.INSTLIB installation library.Note: The monitoring agent must also be installed in the non-local INSTLIB or CSIenvironment where the secondary monitoring server is installed, if this agent willreport to this non-local monitoring server.

2. A monitoring server defined in another platform (non-z/OS). If the preferredsecondary monitoring server is located in another INSTLIB or in another platform,then, from the "Communication Selection Panel," press F5=Advanced to navigate tothe "Specify Agent Secondary TEMS Values" (KAG62P8) panel. On the KAG62P8panel, specify the secondary monitoring server values.

Note: If the agent must to switch secondary monitoring server connection in the future,then, on this "Specify Advanced Agent Configuration Values" panel, press F10=CMS Listto navigate to the KCIPCMSS panel. The same procedure also applies if any of thesecondary monitoring server values that this agent connects to has changed. Themonitoring agent must reconnect to the secondary monitoring server to refresh themonitoring server values generated in the agent runtime members.

Name of secondaryTEMS

If a secondary monitoring server has been selected, it will be listed here. If a secondarymonitoring server has not been selected, None will be displayed.

Enable startup consolemessages

Specify Y to this parameter if you want a SYSLOG message on the console to indicatewhen the monitoring agent finishes initializing. You can use this message in anautomation script. See the automation package for your site for further instructions onhow to capture the monitoring agent startup automation message IDs. If you specify Y,the KGL_WTO=YES parameter is added to the &rhilev.&midlev.&rtename.RKANPARU(KN3ENV) member. The default is N.Note: The existence of the KGL_WTO= parameter triggers the startup console messagesso the parameter must not be present in the KN3ENV member if you do not want thisfeature (i.e., if enabled later on, the parameter gets added to KN3ENV).If you wish toturn it back off, regenerate the N3#3Vxxx monitoring agent "Create runtime members" jobto refresh KN3ENV, where xxx is the JCL suffix.

Enable WTO messages Specify Y to this parameter if you want the monitoring agent address space to issueWTOs. WTOs write information and exception condition messages to the operatorconsoles. Alert messages are written to the consoles. The default is N.


Table 30. Parameters and explanations for the Advanced agent configuration values panel (continued)


Reconnect after TCP/IPrecycle

Specify Y to this parameter if you want the monitoring agent address space to reconnectto the z/OS Communications Server without having to subsequently recycle the addressspace. When this field is set to Y, the "TOLERATERECYCLE" keyword is added in theKN3INTCP member of the &rhilev.&midlev.&rtename.RKANPARU library. If this field isset to N, then when the z/OS Communications Server is recycled, the address spacemust also be recycled to establish connectivity to TCP/IP. The default is N.

Intervals

Storage detail logging Set the interval to monitor storage. The interval values are written as part of the secondEVERY command in: &rhilev.&midlev.&rtename.RKANCMDU(KN3AGST) The default is 0hours (hh) and 60 minutes (mm).

Flush VSAM buffers Set the interval to force all deferred VSAM writes to DASD. The interval values arewritten as part of the third EVERY command in: &rhilev.&midlev.&rtename.RKANCMDU(KN3AGST) The default is 0 hours (hh) and 30 minutes (mm).

Virtual IP Address(VIPA) Type

Set this parameter to the type of VIPA defined for this z/OS system. If the monitoringagent address space is a VIPA-defined application, specify if the VIPA definition is Staticor Dynamic. If VIPA is in use, then the VIPA name is resolvable through the DomainName Server (DNS).Note: The IP.PIPE protocol is required when dynamic VIPA is in use.

Minimum extendedstorage

Specify the amount of virtual storage the monitoring agent must acquire to run at yoursite. The default is 768000.

Language locale Specify the language and codeset (system's locale) that you would like the monitoringagent to use. The language locale value is used for National Language support.This fieldrequires the numeric value (1-36) representing the Language and Region in the table thatfollow. As an example, specify 1 for "English - United States". The country and characterset that this language represents (for example, country is en_US and character set isibm-037) make-up the LANG= environmental variable value generated in the KN3ENVmember in the &rhilev.&midlev.&rtename.RKANPARU library. For English - United States,LANG=en_US.ibm-037 is generated in KN3ENV.Note: For English - United States, if the z/OS UNIX System Services (USS) codepage(en_US.ibm-1047) is required, then specify en_US.ibm-1047 codepage value on theLanguage locale field.

Important: If the language is not listed in the table that follows, contact IBM SoftwareSupport to get the actual LANG= value in country and character set format, and specifythis value accordingly. In addition, this value defaults to the language locale setting usedby the TEMS if one is configured in this RTE. Otherwise, the default is 1. See the onlinehelp for the Table of Languages and Regions from which you obtain these values.

Program to Program (PPI) information:

Forward Take-Actionscommands to NetViewfor z/OS

Specify the Program to Program Interface (PPI) values that will enable forwarding ofTake Action commands to IBM Tivoli NetView for z/OS V5.2, or later. The TivoliEnterprise Portal (TEP) user ID gets passed to NetView for z/OS.




NetView PPI receiver Specify the name of the PPI receiver on NetView for z/OS which will receive Take Actioncommands. This value is required if you specified Y to the "Forward Take Actioncommands to NetView for z/OS" field.

If the specified name is invalid or the receiver is not active on NetView for z/OS, default(MGCR) command routing is performed. The value should be a 1-8 character, uniqueidentifier for the receiver program. It can contain alphabetic characters A-Z or a-z,numeric characters 0-9, and the following special characters: dollar sign ('$'), percent sign('%'), ampersand ('&'), at sign ('@'), and number sign ('#'). This value must match the"xyz" value coded on statement "AUTOTASK.?APSERV.InitCmd = APSERV xyz" inNetView's DSIPARM initialization member, CNMSTYLE.

The Configuration Tool generates the KGLHC_PPI_RECEIVER parameter in the KN3ENVmember of the &rhilev.&midlev.&rtename.RKANPARU library. This value defaults to theNetView for z/OS PPI receiver used by the TEMS if one is configured in this RTE.Otherwise, the default is CNMPCMDR. See NetView for z/OS online help for commandAPSERV for more details.

Agent PPI sender Specify the optional name of the PPI sender. The value should be a 1-8 character, uniqueidentifier for the sender program. It can contain alphabetic characters A-Z or a-z, numericcharacters 0-9, and the following special characters: dollar sign ('$'), percent sign ('%'),ampersand ('&'), at sign ('@'), and number sign ('#').

This name should not conflict with any NetView for z/OS domain name, as it is used inlogging the command and command response in the NetView for z/OS log. If a value isspecified on this field, the Configuration Tool generates the KGLHC_PPI_SENDERparameter in the KN3ENV member of the &rhilev.&midlev.&rtename.RKANPARU library.If a value is not specified on this field, the default is the current monitoring agentjobname that is the source of the command.

z/OS Audit collection values

Enable/Disable z/OSaudit collection

Indicates the trace level to pass messages. Message trace levels (from low to high) are asfollows:v X=Disabledv M=Minimumv B=Basicv D=Detai.

Higher levels trace all lower levels. The value you specify generates an AUDIT_TRACEparameter in member &rhilev.&midlev.&rtename). If AUDIT_TRACE is not specified on thepanel, AUDIT_TRACE=BASIC internal code default is set. The AUDIT_TRACE parameter isgenerated as commented out in KN3ENV.

Maximum in-memorycache entries

Indicates the maximum number of records kept in short-term memory for direct queries.Valid values range from 10 to 1000. The value you specify generates an AUDIT_MAX_HISTparameter in &rhilev.&midlev.&rtename) member. If AUDIT_MAX_HIST is not specified,AUDIT_MAX_HIST=100 internal code default is set. The AUDIT_MAX_HIST parameter isgenerated as commented out in KN3ENV.

Domain ( Audit domainname)

Specifies an identifier that may be used to associate audit records. It is suited forcommonly identifying agents that are associated with each other. An example use may befor sorting records by a particular customer. This field will also be used to create uniquenamespaces for RBAC. The value you specify generates an ITM_DOMAIN parameter inKN3ENV.




Enable Self-DescribingAgent processing(TEMA_SDA)

Indicates whether this monitoring agent supports Self-Describing Agent (SDA)processing. The value set on this field equates to the value of the TEMA_SDA parameterwritten out in the &rhilev.&midlev.&rtename) member. The default is TEMA_SDA=Y.Review the "Enable TEMA Self-Describing Agent (SDA) support" topic in the CommonTivoli Enterprise Monitoring Agent (TEMA) Configuration What's New README entryfor more information. See also the IBM Tivoli Monitoring Administrator's Guide.Note: If the TEMA_SDA is set to the value of Y, and the monitoring agent does not yetsupport Self-Describing Agent processing, the following informational message isgenerated in the output log:

KRAA0016, Ignoring TEMA_SDA Configuration. Agent SDA package not foundfor PRODUCT pp

where pp is the application agent product code.

2. When you have provided these values, press Enter to save them and return to the Specify TCP/IPMonitoring Systems Information panel shown in Figure 17 on page 99.

3. Press F3 to return to the Configure IBM OMEGAMON XE for Mainframe Networks panel shown inFigure 10 on page 92 so you can go on to the next step, Step 4 Specify dynamic terminal integrationparameters.

Step 4: Specifying dynamic terminal integration parametersUse this step to specify TN3270 Telnet session link parameter values. These parameters define theconnection information that the Tivoli Enterprise Portal terminal emulator uses to connect to NetView forz/OS.

About this task

Use this step to specify TN3270 Telnet session link parameter values. These parameters define theconnection information that the Tivoli Enterprise Portal terminal emulator uses to connect to NetView forz/OS. This panel is used to add, update, or view TN3270 data if required.

From the Configure IBM OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page92, select 4 Specify dynamic terminal integration parameters. The panel shown in Figure 26 is displayed

This panel is used to add, update, or view TN3270-related user data, if required.1. Use the information in Table 31 on page 118 to complete this panel.

------------- SPECIFY DYNAMIC TERMINAL INTEGRATION PARAMETERS —----------OPTION ===>

Dynamic link to NetView for z/OS values

NetView APPLID ==> CNM01User data ==>

Figure 26. Specify Dynamic Terminal Integration Parameters panel. Specify Dynamic Terminal Integration Parameterspanel


Table 31. Parameters and explanations for the Specify dynamic terminal integration parameters panel


NetView APPLID Specify the NetView for z/OS APPLID that the OMEGAMON XE for MainframeNetworks monitoring agent will dynamically log on to. The NetView specified must runon the same system as the OMEGAMON XE for Mainframe Networks monitoring agent.The Configuration Tool generates the KN3_DLX_APPLID parameter in the KN3ENVmember of the &rhilev.&midlev.RKANPARU library. The default is CNM01. The field is acharacter string with a maximum length of 8.

User data Specify the data to be passed to the NetView for z/OS program during logon. TheConfiguration Tool generates the KN3_DLX_USERDATA parameter in the KN3ENVmember of the &rhilev.&midlev.RKANPARU library. If no user data is specified, thedefault value is a null string. This option may be used to specify the NetViewOPERATOR ID and PASSWORD in NetView for z/OS if the LOGONPW option isenabled in NetView. The field is a character string with a maximum length of 109 in theformat userid/password.

Attention: This is an optional field. However, if you provide an operator ID in thisfield, the NetView operator ID you provide should not be configured to be a receiver ofunsolicited messages.

For more information about the format of this field, see the "Logging on to NetView froma 3270 session" topic in the IBM Tivoli NetView for z/OS: User's Guide.

For detailed help about the required values, press F1.2. When you have provided these values, press Enter to save them and return to the Configure IBM

OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page 92 so you can go onto the next step, Step 5 Create runtime members.

Step 5: Creating runtime membersThe Create runtime members option in the Configuration Tool generates JCL that should complete witha return code of 0.

About this task

The Create runtime members step generates a batch job that creates the runtime members required tocreate or update the address space where the OMEGAMON XE for Mainframe Networks monitoringagent is running. These members are created in the runtime libraries for this RTE.

Procedure1. Review the sample JCL and submit the job. You might want to change the jobname to match the

member name so that you can easily identify the jobs later on.2. Verify that the job completes successfully. You should receive a return code of 0. If you do not, check

the log to diagnose errors and rerun the job.

Results

When this job completes, press F3 to return to the Configure OMEGAMON XE for MainframeNetworks panel shown in Figure 10 on page 92. Select 6 Configure persistent datastore.

Step 6: Configuring the persistent datastore (in the agent)Use the information in this step to configure the persistent datastore associated with this monitoringagent. This step is optional and depends on whether you plan to collect historical data for your system.


About this task

Persistent data stores are associated with each Tivoli Enterprise Monitoring Server and each monitoringagent. You have already created one persistent data store for Tivoli Enterprise Monitoring Server. Thispersistent data store is for the OMEGAMON XE for Mainframe Networks monitoring agent. This step isoptional and depends on whether you plan to collect historical data for your system.

To optimize performance, configure the persistent data store at the monitoring agent, meaning that youwill have a persistent data store on each z/OS system you are monitoring.

This step provides a batch job that will configure a persistent data store that is added to the monitoringagent address space for historical data collection. This step also allocates the persistent data store datasets used by the OMEGAMON XE for Mainframe Networks product.

Note: This step allocates the persistent data store data sets at the agent. Starting collection of short-termhistory is configured at the Tivoli Enterprise Portal in the historical collection dialog. If the person whoconfigures collection at the Tivoli Enterprise Portal, chooses to Collect at TEMS, these agent data sets arenot used, and you might run out of storage for short-term history, depending on persistent data storecollection at the Tivoli Enterprise Monitoring Server. If you implement this step, configure historicalcollection to be Collect at Agent on the Tivoli Enterprise Portal. Use the historical data storeconfiguration worksheets in Appendix D, “Disk space requirements for historical data tables,” on page257 to collect information about the sizes for individual tables in the persistent data store.

Use the following procedure to configure a persistent data store for the OMEGAMON XE for MainframeNetworks monitoring agent.

Procedure1. The first panel in the persistent data store configuration flow is shown in Figure 27.

This panel is used to specify values for allocating and managing the persistent data store for use bythe OMEGAMON XE for Mainframe Networks monitoring agent.Use the information in Table 32 to complete this panel:

Table 32. Parameters and explanations for the Specify Persistent Datastore Values panel. Parameters andexplanations for the Specify Persistent Datastore Values panel


Maintenance procedureprefix

Prefix for the names of the procedures that are used to perform persistent data storemaintenance when a product data store file is full. Procedure names can be the same forall products in an RTE. Specifying the same procedure name prefix for all products isrecommended. The default prefix is KPDPROC.

--------------------- SPECIFY PERSISTENT DATASTORE VALUES ---------------------COMMAND ===>

The following values are used to allocate and maintain PersistentDatastore for standalone Agents. For efficiency, use the samemaintenance procedure prefix for all your runtime environments (RTEs).

Datastore high-level prefix: &rhilv.&midlev.HUBN3IRA

Maintenance procedure prefix ==> KPDPROCAllocation volume ==> &volserAllocation unit ==> &unitAllocation STORCLAS ==>Allocation MGMTCLAS ==>

Figure 27. Specify persistent data store values for the monitoring agent. Specify persistent data store values for themonitoring agent


Table 32. Parameters and explanations for the Specify Persistent Datastore Values panel (continued). Parametersand explanations for the Specify Persistent Datastore Values panel


Datastore high-levelprefix

High-level qualifier used in the procedure that allocates persistent data store files for thisstandalone agent. The default is &rhilev.&midlev.&rtename.

Allocation volume DASD volume used in the procedure that allocates persistent data store files for thisstandalone agent.

Allocation unit DASD unit used in the procedure that allocates persistent data store files for thisstandalone agent. Valid unit types are 3380 and 3390.

Allocation STORCLAS SMS storage class to be used in the procedure that allocates persistent data store files forthis standalone agent.

Allocation MGMTCLAS SMS management class to be used in the procedure that allocates persistent data storefiles for this standalone agent.

Complete this panel and press Enter to save your changes and continue to the Allocate PersistentDatastore Menu panel.

2. The Allocate Persistent Datastore Menu panel shown in Figure 28 is used to configure persistent datastore.

Perform the five steps shown in this panel in order.3. From the Allocation Persistent Datastore Menu shown in Figure 28, select 1 Modify and review

datastore specifications and press Enter. The Persistent Datastore Specifications panel shown inFigure 29 is displayed.

The parameters set from this panel control the size, the placement and the number of data sets thatcomprise the persistent data store. The settings on this panel are only suggestions; follow theguidelines for your site.

--------------------- ALLOCATE PERSISTENT DATASTORE MENU ---------------------OPTION ===>

Last selectedPerform these configuration steps in order: Date Time

1 Modify and review datastore specifications2 Create or edit PDS maintenance jobcard3 Create runtime members4 Edit and submit datastore allocation job5 Complete persistent datastore configuration

Figure 28. Allocate persistent data store menu for the monitoring agent. Allocate persistent data store menu for themonitoring agent

--------------------- PERSISTENT DATASTORE SPECIFICATIONS ---- Row 1 to 1 of 1COMMAND ===>

Modify persistent datastore allocation and maintenance information as required.Press Enter to accept values and then F3 to return.

Datastore high-level qualifier: &rhilev.&midlev.&rtename.

Group -Datasets in Group- Volser/ Storclas/ -Est Cyl- -Maintenance-Name Lowlev Count Unit Mgmtclas Space Backup Export Extract-------------------------------------------------------------------------------KN3 RKN3HIS 3 &volser 261__ N N N

&unit ________

Figure 29. Persistent data store specifications panel for the monitoring agent. Persistent data store specifications panelfor the monitoring agent


Use the information in Table 33 to define these values:

Table 33. Parameters and explanations for the Persistent Datastore Specifications panel. Parameters andexplanations for the Persistent Datastore Specifications panel


Group Name The name of the group. Each group contains the number of data sets specified in theGroup Count field.

Datasets Lowlev The low-level qualifier of the data sets name. It is suffixed with a 1-character value (1-9,A-Z) that indicates the data set number within a group. As an example, given a GroupCount value of 3, the following data sets with be allocated:

v &rhilev.&midlev.&rtename.RKN3HIS1



Where RKN3HISn is the low-level qualifier.

You may use the default values displayed or change them to meet your siterequirements.

Group Count Indicates the number of data sets within the group.Note:

1. You might want to increase Group Count or Est Cyl space. If you have collectedshort-term history for over 24 hours, but cannot create views at the Tivoli EnterprisePortal for a full 24 hours of data, then you need more data sets (Group Count) orlarger data sets (Est Cyl Space). Some OMEGAMON XE agents use a group count of7.

2. The supported minimum setting for this parameter is 3 for all but a limited numberof special purpose data sets. If you specify 1, additional I/O is required to deleterecords when space is reused. If you specify 2, data becomes unavailable when a datastore file fills up.

Est Cyl Space Indicates the total number of cylinders of disk space for the group. The persistent datastore processing computes how much space is needed to allocate the group data storefiles, and how much additional required space is needed to hold additional information.Additional information includes the product dictionary, table records, index records, andspare room for buffers that need to be reserved for when the data set is full. For moreinformation about sizing the persistent data store, see Appendix D, “Disk spacerequirements for historical data tables,” on page 257.Note:

1. You might want to increase Group Count or Est Cyl space. If you have collectedshort-term history for over 24 hours, but cannot create views at the Tivoli EnterprisePortal for a full 24 hours of data, then you need more data sets (Group Count) orlarger data sets (Est Cyl Space). Some OMEGAMON XE agents use a group count of7.

2. If the value has changed from last release, the existing persistent data store data setsmust be deleted so that reallocation will occur during this step. You might also wantto increase this value if you upgrading from a prior release of the product.

Backup, Export, andExtract

These fields are used for data store maintenance functions. Specify Y to turn on one ofthese maintenance functions for a group.

You can use the backup facility if you want to keep old history data. This facility invokesan IEBGENER procedure to make an exact copy of the data set being maintained. It is asimple copy of the data set to either tape or DASD. A backed-up file also has theadvantage that nothing has to be done to the file to dynamically make the data availableto the persistent data store again.Note: If none of the maintenance options is specified, the data within the data set beingmaintained will be erased.


If you update the values on this panel, you must press Enter and then F3 for your new values to takeeffect. You are returned to the Allocate persistent data store Menu panel. Select 2 Create or edit PDSmaintenance jobcard and press Enter.

4. Selecting 2 Create or edit PDS maintenance jobcard causes a jobcard to be displayed. This stepspecifies the jobcard to be used for the persistent data store maintenance jobs ( KPDPROC1 andKPDPROCC). The KPDPROC1 member is created in the &rhilev.&midlev.&rtename.RKANSAMUlibrary. The KPDPROCC member is created in the &rhilev.&midlev.&rtename.RKANSAM library. PressEnter when the jobcard is complete. You are returned to the Allocate Persistent Datastore Menupanel. Select 3 Create runtime members and press Enter.

5. Selecting 3 Create runtime members causes a JCL job to be displayed. This job creates the persistentdata store definitions. Review and edit the JCL, and submit the job. Verify that the job completessuccessfully. You should receive a return code of 0. If you do not, check the log to diagnose errors andrerun the job. During the process of running this JCL job, the information panel about persistent datastore maintenance shown in Figure 30 is displayed:Press Enter to advance when you have read this information.

When this job completes, press F3 to return to the Allocate Persistent Datastore Menu panel. Select 4Edit and submit datastore allocation job and press Enter.

6. Selecting 4 Edit and submit datastore allocation job causes a JCL job to be displayed. This joballocates and initializes all data sets required for this product's persistent data store. Review and editthe JCL, and submit the job. Verify that the job completes successfully. You should receive a returncode of 0. If you do not, check the log to diagnose errors and rerun the job.

Note: This job is used to define a new persistent data store configuration. If the persistent data storedata sets already exist, then delete or rename this product's persistent data store files if you want theConfiguration Tool to re-allocate and re-initialize the data sets. If these data sets have not beendeleted, then the persistent data store will contain residual data. This job will run with a completioncode of 0 but will not re-allocate or re-initialize the data sets. You must delete or renames the datasets and run the job again.When this job completes, press F3 to return to the Allocate Persistent Datastore Menu panel. Select 5Complete persistent datastore configuration and press Enter.

7. Enter 5 Complete persistent datastore configuration. This option describes steps you need to takeoutside the Configuration Tool to complete the configuration. This step is deferred until thecompletion of the configuration of OMEGAMON XE for Mainframe Networks. See Chapter 8,“Completing the configuration,” on page 127 for more information.

------------- UPGRADE PERSISTENT DATASTORE MAINTENANCE PROCEDURES -------------OPTION ===>

The Configure persistent datastore (PDS) historical data collectionfacility now supports a more simplified PDS maintenance procedure. Itno longer requires the submission of a KPDPROC2 batch job and the PDSjobcard (KPDJOBC) in &rhilev.&midlev.rtename.RKANSAMU is no longer required.

The enhancement requires recreating the following PDS members:- &rhilev.&midlev.rtename.RKANSAMU(KPDPROC1)- &rhilev.&midlev.rtename.(KPDPROCC)

Important:1. KPDPROC1 maintenance procedure must be refreshed in your system

procedure library to implement the new support.2. Since the REXX procedure associated with the improved persistent

datastore processing runs in a TSO environment, the KPDDSCOprogram must be enabled to execute as an authorized program underTSO. This can be done by adding the KPDDSCO name to the systemPARMLIB(IKJTSOnn) member under the AUTHPGM section.

Press F1=Help for more information on important migration considerations.

Figure 30. Allocate persistent data store menu for the monitoring agent. Allocate persistent data store menu for themonitoring agent


See IBM Tivoli Monitoring: Administrator's Guide for information about maintaining the persistent datastore.After reviewing the information displayed in the Complete the persistent datastore configurationstep, press F3 to return to the Allocate persistent datastore menu shown in Figure 28 on page 120.Then press F3 again to return to the Configure OMEGAMON XE for Mainframe Networks V4.1.0panel shown in Figure 10 on page 92.

8. Enter 7 Complete the configuration. This describes the steps that you need to take to copy themembers that you have created to your PROCLIB and VTAMLST libraries. It also identifies othersteps you must run outside of the Configuration Tool to finalize installation and configuration of thisproduct.

Results

Even though configuration of the OMEGAMON XE for Mainframe Networks monitoring agent iscomplete, do not start the monitoring agent yet. You must first load the runtime libraries and completethe configurations steps performed outside the Configuration Tool. See Chapter 8, “Completing theconfiguration,” on page 127 for more information.

Step 7: Loading the runtime librariesLoad the runtime libraries from the SMP/E target libraries after initial product configuration, afterapplying SNMP maintenance, or after configuring a new product into an existing runtime environment(RTE). The load job requires shared access to the runtime libraries, and must be performed for each RTE.

About this task

Before you can start the Tivoli Enterprise Monitoring Server and the OMEGAMON XE for MainframeNetworks monitoring agent, you must load the runtime libraries from the SMP/E target libraries. Theload job requires shared access to the runtime libraries, and must be performed for each runtimeenvironment (RTE).

You must load the runtime libraries based on the following conditions:v After initial product configurationv After applying SMP/E maintenancev After configuring a new product into an existing RTE

Type README RTE on the Configuration Tool command line for more information.

Note: In a sharing RTE configuration, only the master RTE (such as a Base RTE or a Full RTE) must beloaded after applying SMP/E maintenance because these RTE types contain copies of the SMP/E targetlibraries. If the RTE is configured to share the SMP/E target libraries directly, then this load step is notrequired after applying SMP/E maintenance. For additional information enter README RTE on theConfiguration Tool command line.

Follow these steps to load the runtime libraries from the SMP/E target libraries.

Procedure1. From the Configure Tivoli OMEGAMON XE for Mainframe Networks panel, press F3 to return to

the Product Component Selection Menu and then press F3 again to return to the RuntimeEnvironments (RTEs) panel.

2. Type L for Load in the Action field adjacent to the RTE that you have just configured and press Enter.If you are sharing RTEs, both the BASE RTE and the SHARING RTE must be loaded.

3. Review the JCL and submit the job. Verify that the job completes successfully and that the return codeis 04 or less.


4. When you are finished loading the libraries, exit the Configuration Tool.

Considerations when performing the RTE load functionLook at the README SYS and README RTE files for additions considerations when performing the RTEload function.

After initial configuration of the first product configured in an RTE, you must perform the Load allproduct libraries after SMP/E step from the Configuration Tool Runtime Environments (RTE) panel. Ifyou have additional products that you plan to configure in this RTE, perform the Load all productlibraries after SMP/E step after you have completed the configuration of all products in this RTE. If youintend to start using this product operationally before the additional products are initially configured inthis RTE, then you must perform the Load all product libraries after SMP/E step for this product beforestartup.

If you are using system variables, read the information found in the README SYS file that is part of theConfiguration Tool help.

After all required steps for this product within the Configuration Tool have been performed, then youmust perform some steps outside of the Configuration Tool to finalize installation and configuration ofthis product. Each product lists these steps in the Complete the configuration option from the productmain menu.

For more information, see the README RTE file by entering README RTE from the Configuration Toolcommand line.

Step 8: Completing the configurationPerform the Complete the Configuration steps outside the Configuration Tool or PARMGEN to enablethe monitoring agent to work with the z/OS environment.

About this task

Option 6 Complete the configuration on the Configure OMEGAMON XE for Mainframe Networksmenu displays a description of the steps you must take outside of the Configuration Tool or PARMGENto complete the configuration process and ensure that you have the definitions that have been created inthe configuration in your runtime environment. You can complete these steps following the proceduresdisplayed for completing just the agent configuration, or follow the instructions in Chapter 8,“Completing the configuration,” on page 127 which includes steps for completing the configuration of allthe components.

Type README DMC on the Configuration Tool command line for information how to generate a consolidated"Complete the Configuration" step or see the IBM Tivoli OMEGAMON XE and Tivoli Management Serviceson z/OS: Common Planning and Configuration Guide for more information.

Updating your runtime environment to support the NetView for z/OSpacket traceUse this information if you plan to use the Dynamic XE to 3270 functionality to access the NetView forz/OS packet trace function.

About this task

If you plan to use the Dynamic XE to 3270 functionality that enables you to access the NetView for z/OSpacket trace function, then the settings for your runtime environment must include the informationrequired for 3270 applications to link to NetView for z/OS. If you are creating your runtime environment


for the first time, you should ADD this functionality. If you have an existing runtime environment for theOMEGAMON XE for Mainframe Networks monitoring agent, you should update this runtimeenvironment. The following instructions show the UPDATE version of this panel.

This panel is the third in a series of panels. You access this panel using the following path in theConfiguration Tool:1. If the Configuration Tool is not already running, start it:

EX ’&shilev.INSTLIB’

2. From the Configuration Tool Main Menu, enter 3 Configure products.3. From the Configure Products panel, enter 1 Select product to configure.4. The Product Selection Menu lists the products available for configuration. Enter S (Select) adjacent to

the OMEGAMON XE for Mainframe Networks monitoring agent.5. The Runtime Environments (RTEs) panel shown in Figure 31 is displayed.

6. On the Runtime Environments (RTEs) panel, type U (Update RTE) in the Action field adjacent to thename of the runtime environment you are updating.

7. Press Enter twice to advance to the third (3 of 3) panel in the Update Runtime Environment series,shown in Figure 32:

a. Use the information in Table 34 on page 126 to complete this panel:

--------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------COMMAND ===>

*** Current product entry selected: ***product_name Vn.n.n

Actions: A Add RTE, B Build libraries, C Configure,L Load all product libraries after SMP/E,D Delete, U Update, V View values, Z UtilitiesR README Table of Contents

Action Name Type Sharing Description

U SHARING1 SHARING BASE1 Sharing runtime environment for hub and agents-------------------------------------------------------------------------------

BASE1 BASE Base runtime environment------------------------------------------------------------------------------–

Figure 31. Runtime Environments panel. Runtime Environments panel

--------------------- UPDATE RUNTIME ENVIRONMENT (3 of 3) ----------------------

If you require TN3270E Telnet session link support override, complete thesevalues:

Hostname ==>Port number ==>LUGROUP ==>

Figure 32. Update Runtime Environment (3 of 3) panel. Update Runtime Environment (3 of 3) panel


Table 34. Parameters and explanations for the Update Runtime Environment (3 of 3) panel


Hostname If the system where you are defining a runtime environment does not have an activeTelnet listener, specify the network address of a system that does have an active Telnetlistener. A network address can be specified as one of the following values:v Fully qualified hostname (for example, sys.ibm.com)v First qualifier of the fully qualified hostname (for example, sys for sys.ibm.com)v 32-bit IPv4 address in dotted decimal notation (for example, 9.67.1.100)

To get this value, issue the TSO HOMETEST command on the system of the Telnetlistener.

Port number The default port number of the Telnet listener is 23. To override this value, specify theport number of the Telnet listener.

LUGROUP The Dynamic XE to 3270 (NetView for z/OS) linking feature requires the VTAMUnformatted System Services (USS) screen to accept a LOGON APPLID() DATA()command. If the default Telnet USS screen does not accept this command, supply thename of a Logical Unit (LU) group that does accept it. The TN3270 session will be joinedto that LU group.

Note:

1. Complete this panel only if you are configuring products that support the Dynamic XE to 3270 (NetView forz/OS) linking feature and you need to override the default values.

2. The default values or the override values you specify on this panel are displayed during TN3270 logon and canbe modified then for an individual TN3270 session.

For detailed help about the required values, press F1.b. Press Enter to return to the Runtime Environments (RTEs) panel.

8. If you updated any runtime environment values, you must run the JCL job generated in “Step 5:Creating runtime members” on page 118 because Telnet session link support overrides are included inthe KN3ENV member of the RKANPARU dataset only after this job has been run.

9. When this job completes, continue pressing F3 until you exit the Configuration Tool.

See the "Setting up and building a runtime environment" section of the IBM Tivoli OMEGAMON XE andTivoli Management Services on z/OS: Common Planning and Configuration Guide for information about settingup a runtime environment.


Chapter 8. Completing the configuration

Use this information to understand the flow of tasks completed outside the Configuration Tool orPARMGEN for the OMEGAMON XE for Mainframe networks monitoring agent.

There are a number of steps you must take outside of the Configuration Tool or PARMGEN to completethe configuration of OMEGAMON XE on z/OS. Some of these steps may not be listed under Option 6Complete the configuration in the Configure OMEGAMON XE for Mainframe Networks panel, shownin Figure 10 on page 92. The remaining steps you have depend on what steps you have already taken,what options you have chosen, and what you intend to monitor.

Attention: Some steps required to complete the configuration of the OMEGAMON XE monitoring agentare not found in the online help for the Configuration Tool or PARMGEN. To ensure that you perform allthe steps required and perform them in the correct order, use this chapter for product configuration, notthe Configuration Tool online help.

Before you start the common tasks, perform agent-specific security configuration:v “Define monitoring agent access to the network management interfaces and commands” on page 128v “Give users authorization and resource access to run the VARY TCPIP DROP command” on page 130

These common tasks must be completed for every product and can be completed all at one time for allthe products.v “Add support for the SYSTCPD DDNAME in the started tasks” on page 131v “Copy the started task procedures to your procedure library” on page 132v “Vary the VTAM major node active and copy it to your VTAMLST library” on page 133v “APF authorize your libraries” on page 133v “Enable historical data store maintenance” on page 134

The following tasks are completed for the OMEGAMON XE for Mainframe Networks product only:v “Making the performance monitor interface (PMI) exit available to VTAM” on page 135v “Enabling CSA tracking to display TCP/IP CSA usage” on page 136v “Configuring the OMEGAMON XE for Mainframe Networks SNMP manager functions” on page 136v “Authorize the OMEGAMON XE for Mainframe Networks started tasks for TCP/IP privileges” on

page 137

If you intend to collect historical data:v “Configure historical data collection” on page 137

If you intend to warehouse the historical data in the Tivoli Data Warehouse, but the hub monitoringserver is not located on the same computer as the Tivoli Enterprise Portal Server:v “Enable Warehouse agents on a z/OS hub monitoring server” on page 138

Perform the following tasks to complete the configuration:v “Install application and language support” on page 139v “Verify the configuration” on page 139v “Enable security” on page 140, which includes the following tasks:

– “Enabling security at Tivoli Enterprise Portal” on page 140– “Enabling SNMP V3 passwords for autonomous agents” on page 140


– “Authorizing users to access OMEGAMON XE for Mainframe Networks managed systems on theenhanced 3270 user interface” on page 141

– “Authorizing users to issue Take Action commands” on page 141

Finally, if you use the batch facility to clone agent configuration from one LPAR to another and therelease level of z/OS is other than the release level of the system where the SMP/E installation of theOMEGAMON XE for Mainframe Network monitoring agent was installed, perform this task:v “Deploy the configuration” on page 146v “Relink the runtime environments” on page 147

Perform agent-specific security configurationAs part of the configuration done outside the Configuration Tool or PARMGEN, you must performagent-specific security configuration for the OMEGAMON XE for Mainframe Networks monitoring agent.

If your hub Tivoli Enterprise Monitoring Server is running on z/OS, then you configured RACF or yoursystem authorization facility (SAF) product to authenticate your Tivoli Enterprise Portal users when youset up your Tivoli Enterprise Monitoring Server on z/OS. Additional RACF authorization described inthe following section is required when you configure the OMEGAMON XE for Mainframe Networksmonitoring agent. User IDs were also defined on the UNIX and Windows systems that are part of yourdistributed components.

For more information about security issues in the Tivoli Management Services environment, see IBMTivoli Monitoring: Installation and Setup Guide. For more information about supported SAF products, see“Required software” on page 6.

Additionally, you must perform these two security configuration tasks for the OMEGAMON XE forMainframe Networks monitoring agent:v “Define monitoring agent access to the network management interfaces and commands”v “Give users authorization and resource access to run the VARY TCPIP DROP command” on page 130

Define monitoring agent access to the network management interfacesand commandsAs part of the configuration done outside the Configuration Tool or PARMGEN, you must definemonitoring agent access to the network management interfaces and commands for the OMEGAMON XEfor Mainframe Networks monitoring agent.

About this task

If your site has the security profiles defined for the z/OS Communications Server network managementinterfaces (NMIs), then the OMEGAMON XE for Mainframe Networks monitoring agent must beauthorized to access these interfaces. One or more of the following security profiles may be defined in theSERVAUTH class:v EZB.NETMGMT.systemname.tcpipprocname.*v EZB.NETMGMT.systemname.tcpipprocname.SYSTCPCNv EZB.NETMGMT.systemname.tcpipprocname.SYSTCPSMv EZB.NETMGMT.systemname.tcpipprocname.IPSEC.DISPLAYv IST.NETMGMT.systemname.SNAMGMT

If the security profiles are not defined in order to control access to the NMIs, the user ID under which themonitoring agent procedure runs must be a superuser. A superuser is an ID which has a numeric value of0 and which has been permitted to the BPX.SUPERUSER profile in the FACILITY class.


If your site has security profiles defined for the OPERCMDS class, then the OMEGAMON XE forMainframe Networks monitoring agent must be authorized to access the following commands:VARY TCPIP,,DROPDISPLAY NETDISPLAY TCPIPDISPLAY A

Access to these commands is controlled by the following profiles in the OPERCMDS class:MVS.VARY.TCPIP.DROPMVS.DISPLAY.NETMVS.DISPLAY.TCPIPMVS.DISPLAY.JOB

The Configuration Tool placed a sample JCL job in the &rhilev.&midlev.&rtename.RKANSAMU librarycalled KN3UAUTH that will create a new KN3USER user and grant it access to several security profiles:v IST.NETMGMT.systemname.SNAMGMT in the SERVAUTH classv EZB.NETMGMT.systemname.tcpipprocname.* in the SERVAUTH classv MVS™.VARY.TCPIP.DROP in the OPERCMDS class

Additionally, the JCL contains commented out sample statements that grant the agent access to thesecurity profiles that control access to the DISPLAY NET, DISPLAY TCPIP, and DISPLAY A commands:v MVS.DISPLAY.NET in the OPERCMDS classv MVS.DISPLAY.TCPIP in the OPERCMDS classv MVS.DISPLAY.JOB in the OPERCMDS class

The PARMGEN configuration method copies this sample JCL to your PROCLIB if you ran the JCL tocopy to your PROCLIB. Otherwis, this JCL is found in &rhilev.&midlev.&rtename.RKANSAMU.

This job is run outside of the Configuration Tool or PARMGEN. Make the following changes to this jobbefore you run it:v If your site controls access to z/OS commands by defining resources in the OPERCMDS class, you will

need to give the agent user ID access to the MVS.DISPLAY.NET , MVS.DISPLAY.TCPIP andMVS.DISPLAY.JOB resources profiles in the OPERCMDS class. To do this you can remove the commentdelimiters in front of the statements that define (RDEFINE) these resources and permit (PERMIT) theagent user ID to access them. You do not need to remove the comment delimiters on the statementsthat define the resources if they are already defined at your site.

v Change omvsgrp to a valid OMVS group in RACF and password to a valid password for yourenterprise.

v Change systemname to the system name where the monitoring agent will run.v Change agentproc to the started procedure name for the OMEGAMON XE for Mainframe Networks

monitoring agent. The default is CANSN3.v Change tcpipprocname to your TCP/IP startup procedure name for the TCP/IP stack that you want to

monitor. Repeat this pair of lines (RDEFINE and PERMIT) for every TCP/IP address space you want tomonitor.

Note:

1. The RDEFINE and PERMIT statements for IST.NETMGMT* do not need to be repeated.2. If you start your TCP/IP address space using the S procedure syntax, use procedure for

tcpipprocname. If you start your TCP/IP address space using the S procedure.identifier syntax,use identifier for tcpipprocname.

For information about values in this job that you need to edit, see comments in the JCL job.

Chapter 8. Completing the configuration 129

Your security administrator must run this job from a user ID that has RACF SPECIAL and UID(0)authority or code USERID and PASSWORD on the jobcard for an ID that has RACF SPECIAL and UID(0)authority. KN3USER is the default user ID. If you choose to use a different ID, change all occurrences ofKN3USER in the job. Make these changes and review this job before you provide it to your securitydepartment. It should run with a zero return code.

Note that a user ID defined with UID(0) authority (SUPERUSER) has automatic access to the NMIresources required by the OMEGAMON XE for Mainframe Networks agent. However, if your installationdoes not permit the creation of a UID(0) user ID, the KN3UAUTH sample job must still be run in orderto establish the proper rules required by the agent task. The KN3UAUTH job contains sample RACFstatements that demonstrate how a user ID associated with a non-zero UID can be created. In the JCLexample, the value UID(12345) is used, but any valid, non-zero number acceptable by the UID parametercan be used to define the user ID. UID(12345) is not required; it is used here to demonstrate the UID(0) isnot required since most enterprises tightly control who is granted superuser access.

If the KN3UAUTH job has defined UID(0) for the Agent User Name, then the Agent User Name attributein the Agent Status workspace will show a value of ROOT. If the UID is not UID(0), the Agent User ID isdisplayed as the KN3USER user ID (the default in the sample file) or the user ID that the systemadministrator coded on the RACF ADDUSER statement.

The KN3UAUTH job will be created every time you go through the configuration process in theConfiguration Tool. Copy this job into another data set and customize it for your environment and leave&rhilev.&midlev.&rtename.RKANSAMU as a backup copy. This job should not be run more than once forthis started task.

For the PARMGEN configuration method, all started tasks and the KN3UAUTH job are created during$PARSE processing. When you run the KCIJPSYS JCL job, the KN3UAUTH job is copied to the PROCLIBthat you specified. The default location is SYS1.PROCLIB.

Give users authorization and resource access to run the VARY TCPIPDROP commandAs part of the configuration done outside the Configuration Tool or PARMGEN, you give usersauthorization and resource access to run the VARY TCPIP DROP command for the OMEGAMON XE forMainframe Networks monitoring agent.

About this task

z/OS Communications Server protects data and other system resources accessed by applications includedin the Communications Server z/OS component. This protection requires that the identity of the userrequesting access be verified (identification and authentication) and that access be limited to only thoseresources permitted to this user (access control).

z/OS Communications Server applications use RACF for identification and authentication and for accesscontrol, though you may use other supported security access facility (SAF) programs. Users authenticatedwith a SAF program are granted access to only those z/OS resources for which they have permission.The RACROUTE macro instruction is the SAF interface for all products that provide resource control.

SAF programs must be configured correctly for the OMEGAMON XE for Mainframe Networks VARYTCPIP,tcpip_jobname,CMD=DROP,CONNECTION=connection_number command to function correctly. Thepermissions granted to a given Tivoli Enterprise Portal user determine the network resources againstwhich the DROP command can be executed.

TCP/IP uses SAF profiles in the OPERCMD resource class to determine access to network resources. TheMVS.VARY.TCPIP.DROP profile can be used by a SAF product to restrict access to the DROP command.


If the MVS.VARY.TCPIP.DROP profile is defined, the monitoring agent restricts access to the DROPcommand to only those users who have CONTROL or higher access to the MVS.VARY.TCPIP.DROPprofile.

The SAF program validates the DROP command before passing it to the appropriate service routine.v If RACROUTE verification fails for any reason, the command and a message indicating that SAF

validation has failed are written to the command log.v If RACROUTE verification is successful, or a SAF rule prohibiting access does not exist (resulting in a

NO DECISION), then the command request is queued to the service routine and executed. Thecommand response returned depends on the command issued.

The security configuration should be as follows:1. The KN3UAUTH member of RKANSAMU should be customized to enable the OMEGAMON XE for

Mainframe Networks monitoring agent to issue a DROP command anywhere in the system that theuser chooses to allow these actions.

2. When a DROP Connection command is issued from the dialog, the OMEGAMON XE for MainframeNetworks agent will check the Tivoli Enterprise Portal User ID to validate that the user issuing thecommand has CONTROL access to the MVS.VARY.TCPIP.DROP profile using a RACROUTE call.a. If the user has access to the MVS.VARY.TCPIP.DROP profile, then OMEGAMON XE for

Mainframe Networks issues the following command:VARY TCPIP,tcpip_jobname,CMD=DROP,CONNECTION=connection_number

b. If the user does not have access to the MVS.VARY.TCPIP.DROP profile, then OMEGAMON XE forMainframe Networks does not issue the following command:VARY TCPIP,tcpip_jobname,CMD=DROP,CONNECTION=connection_number

An error explaining the reason that the command was not executed is returned to the user.

Add support for the SYSTCPD DDNAME in the started tasksAs part of the configuration done outside the Configuration Tool or PARMGEN, users of othermonitoring agents must add support for the SYSTCPD DDNAME in the started tasks. This step is notnecessary for OMEGAMON XE for Mainframe Networks users. This step is performed for you as part ofa JCL job.

About this task

Note: This step is not necessary for OMEGAMON XE for Mainframe Networks users. This step isperformed for you as part of a JCL job.

SYSTCPD explicitly identifies which data set to use to obtain the parameters defined by TCPIP.DATAwhen no GLOBALTCPIPDATA statement is configured. If a monitoring server is using any of theIP.UDP-related or IP.PIPE-related communication protocols for connection, but the IP domain nameresolution is not fully configured on the z/OS system, SYSTCPD must be supported by the monitoringserver and the monitoring agents that report to it.

If you are certain that SYSTCPD is not needed at your installation, you can skip this step. However, notethat you might gain a small performance benefit by avoiding multiple dynamic data set allocations if yousupply a SYSTCPD DD statement.

To support SYSTCPD, uncomment the following statement in the started task members in RKANSAMUand provide the name of the SYSTCPD data set://*SYSTCPD DD DISP=SHR,//* DSN=TCPIP.SEZAINST(TCPDATA)


The name of the SYSTCPD data set is installation-specific. Get the correct specification from your networkadministrator.

If you reconfigure products, you will need to uncomment the statement again.

If the monitoring server is using any of the IP.UDP-related or IP.PIPE-related communication protocols forconnection, but the IP domain name resolution is not fully configured on this z/OS system, you mustspecify the SYSTCPD DDNAME in the CANSDSST started task.

The Configuration Tool generated the CANSDSST started task with the following commented out lines.Customize the SYSTCPD DDNAME accordingly if this scenario fits your environment://*SYSTCPD explicitly identifies which dataset to use to obtain//*the parameters defined by TCPIP.DATA when no GLOBALTCPIPDATA//*statement is configured. Refer to the IP Configuration Guide//*for information on the TCPIP.DATA search order. The dataset//*can be any sequential dataset or a member of a partitioned//*dataset. TCPIP.SEZAINST(TCPDATA) is the default sample file.//*TCPIP.TCPPARMS(TCPDATA) is another sample and is created as//*part of the Installation Verification Program for TCP/IP.//*Note: Uncomment out this DDNAME and point to appropriate//* TCPDATA library name supported at your site if domain//* name resolution is not fully configured.//*SYSTCPD DD DISP=SHR,//* DSN=TCPIP.SEZAINST(TCPDATA)

When you are finished, copy the procedures to PROCLIB. Since PARMGEN automatically copies theprocedures, you only need edit them in PROCLIB if you installed the monitoring agent using PARMGEN.

Copy the started task procedures to your procedure libraryAs part of the configuration done outside the Configuration Tool or PARMGEN, you must copy thestarted tasks procedures to the procedure library used by the OMEGAMON XE for Mainframe Networksmonitoring agent.

About this task

The Configuration Tool created started task procedures in &rhilev.&midlev.&rtename.RKANSAMU that youmust copy to your procedure library PROCLIB. Update your started task library as follows:1. If you have configured an agent address space, copy the OMEGAMON XE for Mainframe Networks

monitoring agent started task (the default name is CANSN3) from &rhilev.&midlev.&rtename.RKANSAMU to your PROCLIB. See Chapter 7, “Configuring the monitoring agent using theConfiguration Tool,” on page 87 for more information.

2. If you have configured a persistent data store for the OMEGAMON XE for Mainframe Networksmonitoring agent, copy the persistent data store maintenance procedures (KPDPROC1 from&rhilev.&midlev.&rtename.RKANSAMU and KPDPROC from &rhilev.&midlev.&rtename.RKANSAM) toyour PROCLIB.

Note: You might also use the sample system copy JCL to copy the system procedures and the VTAMmajor node members from the &rhilev.&midlev.&rtename.RKANSAMU library to the system libraries (ifapplicable). The sample JCL can be generated from the RTE Utility option.

To navigate to the RTE Utility menu:1. Within the Runtime Environments (RTEs) panel, type Z next to the name of the RTE you have

configured and press Enter.2. From the RTE Utility Menu, select option 7 Generate sample system procedure copy JCL, and press

Enter. Specify your system procedure library and press Enter. The JCL that creates the sample systemprocedure copy job (CB#Pxxxx) is displayed.


Vary the VTAM major node active and copy it to your VTAMLST libraryAs part of the configuration done outside the Configuration Tool, you must vary the VTAM major nodeactive and copy it to the VTAMLIST library used by the OMEGAMON XE for Mainframe Networksmonitoring agent.

About this task

The Configuration Tool created VTAM definitions and stored them in &rhilev.&midlev.&rtename.RKANSAMU. To complete the configuration, you must copy the VTAM major nodes to yourVTAMLST library. (CTDDSN is the default name of the VTAM major node definition for the TivoliEnterprise Monitoring Server on z/OS. CTDN3N is the default name of the VTAM major node definitionfor the OMEGAMON XE for Mainframe Networks monitoring agent you configured in Chapter 7,“Configuring the monitoring agent using the Configuration Tool,” on page 87).

If you have configured the OMEGAMON XE for Mainframe Networks monitoring agent as described inChapter 7, “Configuring the monitoring agent using the Configuration Tool,” on page 87, vary the VTAMnode (CTDN3N) active by issuing the following command:V NET,ACT,ID=CTDN3N

Whether the default CTDN3N VTAM major node is created will depend upon two things:v If the OMEGAMON XE for Mainframe Networks monitoring agent is running in its own address space

(as the recommended configuration suggests)v If SNA data collection is configured

If both of these conditions are true, then the CTDN3N VTAM major node needs to be copied toVTAMLST and activated before the OMEGAMON XE for Mainframe Networks monitoring agent isstarted.

Note: You might also use the sample system copy JCL to copy the system procedures and the VTAMmajor node members from the &rhilev.&midlev.&rtename.RKANSAMU library to the system libraries (ifapplicable). The sample JCL can be generated from the RTE Utility option.

To navigate to the RTE Utility menu:1. Within the Runtime Environments (RTEs) panel, type Z next to the name of the RTE you have

configured and press Enter.2. From the RTE Utility Menu, select option 7 Generate sample system VTAMLST copy JCL and press

Enter. Specify your system VTAMLST library, and press Enter. The JCL that creates the sample systemVTAMLST copy job (CB#Nxxxx) is displayed.

If you used the PARMGEN configuration method, these statements were added to PROCs. Youuncomment these statement to vary the VTAM node active. PARMGEN also copies these statements tothe VTAMLST you specified during configuration if you run the KCIJPSYS JCL jobs to do this.

APF authorize your librariesAs part of the configuration done outside the Configuration Tool or PARMGEN, you must APF authorizethe libraries used by the OMEGAMON XE for Mainframe Networks monitoring agent.

About this task

If you use APF authorization, add the following runtime load libraries to your list of APF-authorizedlibraries.


&rhilev.&midlev.&rtename.RKANMODU&rhilev.&midlev.RKANMOD&rhilev.&midlev.RKANMODL

Note: Any runtime libraries concatenated in the STEPLIB DDNAME and in the RKANMODL DDNAME of theCANSN3 started tasks must be APF-authorized. See the Complete the Configuration information in theConfiguration Tool for additional information.

The PARMGEN configiruation method updates your PROC with these statements, but you mustuncomment them.

Enable historical data store maintenanceAs part of the configuration done outside the Configuration Tool or PARMGEN, you must enablehistorical data store maintenance for the OMEGAMON XE for Mainframe Networks monitoring agent.

About this task

If you intend to enable historical data collection and have allocated and configured maintenance of thehistorical data set, you must perform three additional tasks to enable the maintenance:1. Provide access to the persistent data store files

Ensure that KPDPROC1 procedure has the necessary authority to read, write, and update thepersistent data store files. PARMGEN performs this task automatically and copies this procedure tothe PROCLIB that you specified, so you can skip this step if you ran KCIJPSYS.The KPDPROC1 procedure is used to maintain the physical files that constitute the persistent datastore. Data store files are archived, exported or recycled according to the maintenance strategy thatyou specified for persistent data store file groups for the product. The persistent data store subsystemautomatically submits maintenance jobs whenever a data store file becomes full. The maintenanceprocedure must be available in a system procedure library for the procedure to operate. Theprocedure is generic so it may be used by all runtime environments using this version of thepersistent data store.

2. Authorize the KPDDSCO module

The KPDPROCC REXX procedure runs in a TSO environment and must be enabled to run as anauthorized program under TSO. Authorize the KPDDSCO module by adding KPDDSCO to thesystem PARMLIB(IKJTSOnn) under the AUTHPGM section and refresh the IKJTSOnn member byissuing the set command (T IKJTSO=nn). You might also request that authorized system programmersperform this step so it can be scheduled with the LPAR change control processes.

3. Verify persistent data store configuration

To verify that the configuration and authorization of the procedures have been successful, perform thefollowing steps:a. Bring up the started task (for monitoring server or monitoring agent) that will collect historical

data into the product's persistent data store libraries. In the RKPDLOG DDNAME started task,find any persistent data store libraries in a non-Offline status (for example, Partial or Full status).

b. From a z/OS operator console, issue the following z/OS MODIFY command:/F &stcname,KPDCMD RECOVER FILE=DSN:&pds_dataset

(where &stcname is the name of the started task performing the persistent data store collection,and &pds_dataset is the persistent data store data set).For example, issue the following MODIFY command for the monitoring server:/F CIDSST,KPDCMD RECOVER FILE=DSN:&rhilev.&midlev.&rtename.RGENHIS1

c. Wait 5 minutes.d. In the RKPDLOG DDNAME started task, find the following Command: and KPDDSTR: references

as shown in the following monitoring server RKPDLOG DDNAME example that follows:


Command: RESUME FILE=DSN:&rhilev.&midlev.&rtename.RKN3HIS1KPDDSTR: CONNECT processing started for DataStore fileDSN:&rhilev.&midlev.&rtename.RKN3HIS1KPDDSTR: CONNECT processing ended for DataStore fileDSN:&rhilev.&midlev.&rtename.RKN3HIS1

e. If these references are not found, view the KPDPROC1 started task in SDSF and look for anyobvious errors.

If you are upgrading an existing monitoring server or monitoring agent, you must also refresh theKPDPROC1 maintenance procedure in your system procedure library. See IBM Tivoli OMEGAMON XEand Tivoli Management Services on z/OS: Upgrade Guide.

Run the ITMSUPER Tools (optional)Use the ITMSUPER Tools to learn about the health of your managed systems, situations, andenvironment configuration.

The ITMSUPER Tools are included in the IBM Support Assistant (ISA), a free local software serviceabilityworkbench that helps you resolve questions and problems with IBM software products. To install the ISAsoftware, go to http://www.ibm.com/software/support/isa.

Making the performance monitor interface (PMI) exit available to VTAMAs part of the configuration done outside the Configuration Tool or PARMGEN, you must make theperformance monitor interface exit available to VTAM for the OMEGAMON XE for Mainframe Networksmonitoring agent.

You must make the PMI exit accessible to VTAM. Choose one of these two ways to do this task: bymodifying the VTAM startup JCL or by copying the PMI Exit to VTAM.

Modifying the VTAM startup JCL

Follow these steps to modify the VTAM startup JCL.1. Add a DD statement for the library containing the PMI exit to the VTAMLIB concatenation in your

VTAM startup procedure. If you did not configure this OMEGAMON RTE to share with the SMP/Etarget libraries (that is, SHARING SMP), then you could add the following statement to the VTAMLIBconcatenation. See the note in the XE configuration section on this topic if you select this option. Addthis library: Add a DD statement for the library containing the PMI exit to the VTAMLIBconcatenation in your VTAM startup procedure. If you did not configure this OMEGAMON RTE toshare with the SMP/E target libraries (that is, SHARING SMP), then you could add the followingstatement to the VTAMLIB concatenation. See the note in the XE configuration section on this topic ifyou select this option. Add this library:&rhilev.&midlev.&rtename.RKANMOD

If you do configure the OMEGAMON RTE to share with the SMP/E libraries, then follow the steps in“Copying the PMI Exit to VTAM” on page 136.

2. Quiesce your network.3. Restart VTAM.

Note: If you do not configure this OMEGAMON RTE to share with the SMP/E target (that is,SHARING SMP) then you could use the process described in “Copying the PMI Exit to VTAM” on page136. You should not add SMP/E target libraries to the VTAMLIB concatenation because this would be aproblem when you apply maintenance in the future.


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

Copying the PMI Exit to VTAM

An alternate approach is to copy the PMI exit module and its ALIASes to an existing library in theVTAMLIB concatenation. The PMI Exit consists of module KN3AMVPX and its five ALIASesKN3AMV00-04. The PMI Exit must be found somewhere in the VTAMLIB concatenation in order for theexit to function correctly when the Tivoli OMEGAMON XE for Mainframe Networks program tries toactivate the exit.

If you do this, then there is no longer a need to quiesce VTAM when maintenance is applied.

A potential drawback to this method is that future changes to the VTAM PMI exit might not be pickedup when you apply maintenance if you forget to recopy the PMI Exit program and its ALIASes to thelibrary in the VTAMLIB concatenation after the maintenance is applied.

Another potential problem occurs if you copy the PMI exit to different libraries in the VTAMconcatenation and have multiple copies of the PMI exit in your VTAMLIB concatenation. If you choosethis approach, you must put a process in place for ensuring that the OMEGAMON XE for MainframeNetworks PMI exit program is correctly maintained.

Enabling CSA tracking to display TCP/IP CSA usageAs part of the configuration done outside the Configuration Tool or PARMGEN, you must enable CSAtracking so that TCP/IP CSA usage can be displayed for the OMEGAMON XE for Mainframe Networksmonitoring agent.

About this task

The IBM-supplied default PARMLIB member is DIAG00, which contains the following:...

VSM TRACK CSA(ON) SQA(ON)...

If this is not specified, then CSA information will not be available within the product.

Configuring the OMEGAMON XE for Mainframe Networks SNMPmanager functionsAs part of the configuration done outside the Configuration Tool or PARMGEN, you configure SNMPmanager functions for the OMEGAMON XE for Mainframe Networks monitoring agent.

About this task

Follow this process to configure the SNMP manager functions.

See Appendix E, “Format of the SNMP configuration file,” on page 289 for more information about thisfile format.

Procedure1. Confirm that the SNMP configuration file named on the KN3SNMP DD card in the sample start

procedure (CANSN3) exists. If it does not, allocate it.2. Edit this file. See sample SNMP configuration file KN3SNMP in RKANSAMU for information about

supported data characteristics and the syntax for data set allocation statements.3. Add a configuration statement for each SNMP agent from which data will be collected (one per

TCP/IP stack).4. Save this data set.


Results

When you start the Tivoli Management Services environment and the OMEGAMON XE for MainframeNetworks monitoring agent, workspaces that use data collection services dependent on SNMP shoulddisplay data.Related reference:Appendix E, “Format of the SNMP configuration file,” on page 289Since V4.2, SNMP data collection in the OMEGAMON XE for Mainframe Networks monitoring agentwas enhanced to give you greater flexibility when communicating with the SNMP agents.

Authorize the OMEGAMON XE for Mainframe Networks started tasksfor TCP/IP privilegesUse this information to define a TCP/IP OMVS segment for the user ID associated with units of workrequesting these UNIX System Services.

About this task

The OMEGAMON XE for Mainframe Networks TCP/IP data collector uses TCP/IP service componentsin z/OS Communications Server that exploit z/OS UNIX System Services. Using these componentsrequires a UNIX System Services security construct, called an OMVS segment, for the user ID associatedwith units of work requesting these services.

The OMVS segment must be defined with SuperUser authority. Authorize the OMEGAMON XE forMainframe Networks started task for TCP/IP privileges by creating an OMVS segment for RACF oranother SAF product. Identify the OMEGAMON XE for Mainframe Networks started task CANSN3 as asuperuser, as in this example:ALU CANSN3 OMVS(UID(0) HOME(/) PROGRAM(/bin/sh))

See the z/OS Communications Server IP Planning and Migration Guide for an explanation of how to providean OMVS segment for the OMEGAMON XE for Mainframe Networks started task.

Note: This command makes setting of SuperUser authority more explicit. This action has actuallyalready taken place when you ran the JCL job described in “Define monitoring agent access to thenetwork management interfaces and commands” on page 128.

If you recently migrated to z/OS v2.1, you might find OMVS errors in the system log when you launchthe OMEGAMON XE for Mainframe Networks monitoring agent. Be aware that as of z/OS V2R1, theability to use default OMVS segments has been removed. All z/OS UNIX users or groups must now haveOMVS segments defined for user and group profiles with unique user IDs (UIDs) and group IDs (GIDs).For more information about this error and workarounds, see "OMVS and SNAMGMT errors found insystem log on z/OS v2.1 systems" in the IBM Tivoli OMEGAMON XE for Mainframe Networks:Troubleshooting Guide.

Configure historical data collectionAs part of the configuration done outside the Configuration Tool or PARMGEN, you must configurehistorical data collection for the OMEGAMON XE for Mainframe Networks monitoring agent.

About this task

Tivoli Monitoring Server provides for two kinds of history data:v Short-term history data, which is stored in the persistent data store (on z/OS systems) or in files (on

distributed systems).


v Long-term history data, which is stored in the Tivoli Data Warehouse.

Both short-term and long-term history are optional features that can be enabled from the Tivoli EnterprisePortal.

The Tivoli Enterprise Portal History Collection dialog box displays all of the OMEGAMON XE forMainframe Networks attribute tables that are enabled for historical collection and reporting. To enablehistorical data collection, you must select and configure each group (attribute table) for which you wantto collect data, and then start collection of those groups. If you want to warehouse the data for long-termhistorical reporting, you must set the Warehouse Interval to the interval at which data is warehoused.

For detailed instructions on configuring history data collection, see IBM Tivoli Monitoring: Administrator'sGuideIBM Tivoli Monitoring: User’s Guide, and the Tivoli Enterprise Portal online help.

Enable Warehouse agents on a z/OS hub monitoring serverAs part of the configuration done outside the Configuration Tool or PARMGEN, you must enableWarehouse agents on a z/OS hub monitoring server for the OMEGAMON XE for Mainframe Networksmonitoring agent.

About this task

If you want to store long-term history data and your hub monitoring server is on z/OS, you musttransfer the catalog and attribute files for the Warehouse Proxy agent and the Summarization andPruning agent to the hub using Manage Tivoli Monitoring Services.

The catalog and attribute data files are installed on the Tivoli Enterprise Portal Server when you installapplication support for OMEGAMON XE for Mainframe Networks, using the IBM Tivoli OMEGAMONData Files for z/OS CD. You can then FTP the files to the hub monitoring server.

If the portal server is installed on a Windows system, you can FTP the files to a z/OS hub using ManageTivoli Monitoring Services:1. On the host of the Tivoli Enterprise Portal Server, open the Manage Tivoli Monitoring Services

application. For example:Start > IBM Tivoli Monitoring > Manage Tivoli Monitoring Services.

2. Right-click the name of the portal server and select Advanced > Utilities > FTP Catalog andAttribute files.The "Select attribute and catalog data for transfer window" dialog box is displayed.

3. Select the catalog and attribute data for the Warehouse Proxy and the Summarization and Pruningagents, then press OK.The FTP TEMS Data to z/OS dialog box is displayed.

4. Provide the following information:v The name of the hub Tivoli Enterprise Management Serverv A valid FTP user ID and passwordv The name of the domain name server of the monitoring server where the RKANDATV data set is

located

When you have completed these fields, click OK. Click OK again in the confirmation window.5. After the FTP operation is complete, you receive a message that the operation completed successfully.

Click OK to end this operation.

After you complete these steps, restart the hub monitoring server.


Install application and language supportAs part of the configuration done outside the Configuration Tool or PARMGEN, you must installapplication and language supported for the OMEGAMON XE for Mainframe Networks monitoring agent.

About this task

Before data collected by OMEGAMON XE for Mainframe Networks monitoring agents can be displayedin the Tivoli Enterprise Portal, support for the agents must be installed and enabled. Application supportfiles provide agent-specific information for workspaces, helps, situations, templates, and other data.Application support for a monitoring agent includes two types of files:v SQL files are required for adding product-provided situations, templates, and policies to the Enterprise

Information Base (EIB) tables maintained by the hub monitoring server. These SQL files are also calledseed data, and installing them on a monitoring server is also called seeding the monitoring server.

v Catalog and attribute (CAT and ATR) files are required for presenting workspaces, online help, andexpert advice for the agent in Tivoli Enterprise Portal.

Application support must be configured on all instances of the following infrastructure components:Tivoli Enterprise Management Server (both hub and remote monitoring servers), Tivoli Enterprise PortalServer, and Tivoli Enterprise Portal desktop client, if the desktop client was installed from the installationmedia. Application support for the monitoring agent is installed on the remote monitoring servers whenagents are registered with the local monitoring server.

The files required for support are contained in IBM Tivoli OMEGAMON Data Files for z/OS DVD includedin the product package. You install support on the Tivoli Enterprise Portal Server and any desktop clientson the computer on which they are installed. If your hub is on Windows or a UNIX operating system(Linux, AIX, Solaris), you install support on the monitoring server locally (that is, on the computer onwhich it is installed). If your hub is on z/OS, you install support from a Windows computer that hostseither a Tivoli Enterprise Portal Server or a Tivoli Enterprise Monitoring Server. The hub monitoringserver must be running while you are installing support.

Use the procedures documented in the IBM Tivoli Monitoring: Installation and Setup Guide to add supportto Tivoli Enterprise Portal or a hub monitoring server on Windows, AIX, or Linux. Use the instructions inIBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/OS to add support to a z/OShub.

If you want application data, online help, and expert advice to be displayed in a language other thanEnglish, you must also install language support.

You install language support from the IBM Tivoli OMEGAMON XE for Mainframe Networks Language PackCD on the same system where you install application support. Install the language packs on any systemwhere you have installed the Tivoli Enterprise Portal or where you have installed a desktop client. (If youdownload and run a desktop client using Web Start, you do not need to install the language packs on thelocal system. They are downloaded from the portal server.) Before you can install a language pack, you mustinstall the component in English.

For additional information about installing application and language support, including the mostup-to-date files, see Technote 1255545 at http://www-01.ibm.com/support/docview.wss?uid=swg21255545.

Verify the configurationThe verification task must be performed at this juncture during configuration.




About this task

Follow the instructions in “Verifying configuration if you configured both Tivoli Enterprise Portal and theenhanced 3270 user interface” on page 149 to verify that you have correctly configured the products andcomponents.

Enable securityAfter your new environment is configured correctly, you can safely enable the required level of securityon each of the components within your environment.

See “Enabling security at Tivoli Enterprise Portal”

If you are using the Tivoli Enterprise Portal to view data, you can create user accounts that authorizeusers to view the monitored data and set up authentication of those accounts by enabling securitythrough the hub monitoring server or through the portal server. For instructions on enablingauthentication on a hub monitoring server on Windows, Linux and UNIX operating systems, see the IBMTivoli Monitoring: Administrator's Guide. For instructions on enabling authentication on a hub monitoringserver on z/OS systems, see the IBM Tivoli Management Services on z/OS: Configuring the Tivoli EnterpriseMonitoring Server on z/OS.

If you intend to use autonomous agents on a z/OS system, you can enable SNMP V3 passwords if theIntegrated Cryptographic Service Facility (ICSF) subsystem is available on the z/OS system. See“Enabling SNMP V3 passwords for autonomous agents.”

If you are using the IBM Tivoli OMEGAMON enhanced 3270 user interface to view data, you can enablesecurity by following the steps described in “Authorizing users to access OMEGAMON XE forMainframe Networks managed systems on the enhanced 3270 user interface” on page 141.

In V5.1.0, the new 3270 and existing Tivoli Enterprise Portal Take Action commands fail unless explicitsecurity definitions are configured that enable these commands to be issued. Security for this monitoringagent’s Take Action commands is implemented through direct SAF (System Authorization Facility) callsand is based on resource profiles. Both user ID and command are validated. See “Authorizing users toissue Take Action commands” on page 141 to perform this security setup.

If you intend to use the OMEGAMON II user interface for a monitoring agent, enable security for it now.For instructions on implementing security, see “Configuring security” on page 190.

Enabling security at Tivoli Enterprise PortalAs part of the configuration done outside the Configuration Tool and PARMGEN, you must enablesecurity at Tivoli Enterprise Portal.

About this task

To enable security for the Tivoli Enterprise Portal through either the hub monitoring server or the TivoliEnterprise Portal Server, review the planning information in the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Common Planning and Configuration Guide and see the appropriate guide forinstructions. To enable security for OMEGAMON XE for Mainframe Networks, see “Performagent-specific security configuration” on page 128.

Enabling SNMP V3 passwords for autonomous agentsIf you intend to use autonomous agents on a z/OS system, you can enable SNMP V3 passwords if theICSF subsystem is available on the z/OS system.


See the Enabling SNMP V3 passwords for autonomous agents topic in the IBM Tivoli OMEGAMON XEand Tivoli Management Services on z/OS: Common Planning and Configuration Guide for more informationabout performing this task.

Authorizing users to access OMEGAMON XE for Mainframe Networksmanaged systems on the enhanced 3270 user interfaceLogons to the OMEGAMON XE for Mainframe Networks enhanced 3270 user interface are controlledthrough the system authorization facility (SAF) interface. In addition, the OMEGAMON enhanced 3270user interface performs SAF checks on users’ authorization to view data for specific managed systems ormanaged system types and their authorization to issue Take Action commands.

By default, if no security class is configured, everyone is allowed to log on to the OMEGAMONenhanced 3270 user interface and to view data for any managed system. All Take Action commands aredenied.

If a security class name is configured, resource profiles must be defined to control logon, data access, andTake Actions, and users must be given access to those profiles.

For instructions on configuring security for the OMEGAMON enhanced 3270 user interface, see the IBMTivoli OMEGAMON XE and Tivoli Management Services on z/OS Common Planning and Configuration Guide.

Authorizing users to issue Take Action commandsCertain commands, known as Take Action commands, can be issued from the Tivoli Enterprise Portal andOMEGAMON enhanced 3270 user interface. OMEGAMON XE for Mainframe Networks supports twotypes of Take Action commands: z/OS system commands and agent-provided commands. Users must beauthorized to issue these commands.

z/OS commands

By default, Take Action commands issued by OMEGAMON XE for Mainframe Networks are issued asz/OS system commands.

However, a monitoring server or monitoring agent address space can be configured to redirect TakeAction commands to NetView through the program to program interface (PPI). Take Action commandsthat are issued in NetView make full System Authorization Facility (SAF) calls for authorization. NetViewuses the Tivoli Enterprise Portal user ID to determine the NetView operator on which the commandauthorization is performed. If command authorization passes, the command is processed by the NetViewoperator. Messages are written to the NetView log to provide an audit trail of the commands and theusers that issued them. If you enable NetView command authorization on the monitoring server, youmust also enable NetView to execute the commands.

For more information, see "Configuring NetView authorization of z/OS commands" in IBM TivoliMonitoring: Configuring the Tivoli Enterprise Monitoring Server on z/OS.

Prefixed Take Action commands

OMEGAMON XE for Mainframe Networks provides a set of predefined Take Action commands:DropNslookupPingTracerte


These commands, which are prefixed by N3:, are known as agent commands. A subset of thesecommands, commands that cannot also be run as console commands, can be issued using the Take Actionfeature on the Tivoli Enterprise Portal. In the OMEGAMON enhanced 3270 user interface, thesecommands are available in action menus.

Security for OMEGAMON XE for Mainframe Networks Take Action commands is based on SAF securityclasses and resource profile names. During product configuration you specify the name of the SAFsecurity class that is used to validate product specific take action commands. The SAF class that is usedto validate take action commands is specified in the RTE_SECURITY_CLASS parameter in your PARMGENparm deck. You can code the KN3_SECURITY_ACTION_CLASS parameter optionally if you want to have aseparate SAF security class just for OMEGAMON for Mainframe Networks commands.

After you define the SAF security class, you define resource profiles to control access to theproduct-specific take action commands. If no resource profiles are created to control Take Actioncommands, all commands are denied. The OMEGAMON enhanced 3270 user interface validates thefollowing resource profile to see if users are authorized to issue the Take Action commands directed atz/OS Communication Server resources:KN3.msn.TAKEACTION.*

where msn is managed system name.

At a minimum, you must create a profile by using the pattern shown in the previous sample for theglobal security class (RTE_SECURITY_CLASS) and give update access to the profile to all users you wantto authorize to issue any Take Action commands from the enhanced 3270 user interface. The enhanced3270 user interface address space uses SAF validation to determine whether a user is authorized to issueany Take Action commands.

SAF validation for product specific commands is performed by the monitoring agent. Create otherprofiles for more granular access control. For example, to control all OMEGAMON XE for MainframeNetworks Take Action commands on all managed systems, use the following command:KN3.**.TAKEACTION.*

To control the ability to issue Take Action commands to an OMEGAMON XE for Mainframe Networksmonitoring agent that is running on a system with an SMFID of TSTA and stack TCPIP, you woulddefine a profile named:KN3.TCPIP:TSTA.TAKEACTION.*

To control access to individual commands, you must define at least one profile with the following formatin either the global security class or the override security class (KN3_SECURITY_ACTION_CLASS):KN3.TCPIP:TSTA.TAKEACTION.commandname

orKN3.**.TAKEACTION.commandname

where commandname is one of the supported OMEGAMON XE for Mainframe Networks Take Actioncommands.

To control access to the DROP command, create a profile in either the global security class or the overridesecurity class similar to the following:KN3.**.TAKEACTION.DROP

Note: DROP commands also check the TCPIP.MVS.DROP profile of the OPERCMDS class in addition toany SAF checking done for the OMEGAMON for Mainframe Networks DROP command resource profile.


If a user attempts to issue a Take Action command without authorization, a series of messages similar tothese messages here is written to the RKLVLOG:2012.178 04:27:37.68 KN3A907I: USER=USER3 CLASS=$KOBSEC RESOURCE=KN3.TCPIPG:SYS.TAKEACTION.PING2012.178 04:27:37.68 KN3A908I: RACROUTE VERIFY REG15=00000004 SAFPRRET=00000004 SAFPRREA=00000000

SAFPSFRC=00000000 SAFPSFRS=000002012.178 04:27:37.68 0002012.178 04:27:37.68 KN3A909I: USER=USER3 RESULT: USER NOT DEFINED TO ESM

Additionally, this message is displayed in a pop-up window in the enhanced 3270 user interface:________________________________________________________| Take Action Command Failure || || KN3A006E RACF AUTHORIZATION ERROR ||________________________________________________________|

In Tivoli Enterprise Portal or the enhanced 3270 user interface, you might also see the following messagesin the Drop Connection dialog's Command Output display.KN3A904E TAKE ACTION RACROUTE AUTH RC(FAILURE). CLASS=OPERCMDS,

COMMAND=VARY TCP, USER=SYSADMIN

This message indicates that the user was validated in the OMEGAMON for Mainframe Networksresource profile, but the user was not permitted to the TCPIP.MVS.DROP profile of the OPERCMDS class.

For more information, see the "Enable security on the IBM Tivoli OMEGAMON enhanced 3270 userinterface" topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: CommonPlanning and Configuration Guide. For information on issuing Take Action commands from the enhanced3270 user interface, see the IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 UserInterface User’s Guide.

Restricting access to the Mainframe Networks Command Log and Responseworkspace

The OMEGAMON XE for Mainframe Networks monitoring agent has a unique workspace associatedwith prefixed Take Action commands: the Command and Response Log workspace. This enhanced 3270workspace is similar to the Tivoli Enterprise Portal Command Log workspace. Commands in bothworkspaces are displayed in a “last in, first out” order. The Tivoli Enterprise Portal workspace displaysthe commands that are issued by the user ID that logged into Tivoli Enterprise Portal, unless the user isgiven UPDATE access to the KN3.**.TAKEACTION.ADMIN resource profile, in which case all commands andall responses issued by all users are displayed. A similar mechanism is available in the enhanced 3270user interface workspace, an enhanced 3270-based Command and Response Log workspace, shown inFigure 33 on page 144.


To control display of the commands and command output in the command log, create an ADMINresource profile in either the global security class or the override security class, similar to the following:KN3.**.TAKEACTION.ADMIN

where ADMIN means that a user or user group has permission to view all Take Action command andresponses for that user and other users. If this resource is not defined and users or groups are notpermitted or granted access to this resource, a user is only be allowed to see Take Action commands andresponses issued by that user. Users with UPDATE access to KN3.**.TAKEACTION.ADMIN can see commandsand command responses issued by all users. For information about setting up this command profile, seethe SAF appendix of the IBM Tivoli OMEGAMON XE for Mainframe Networks: User Guide.

Setting up a resource profile

The authority to transmit Take Action requests from the OMEGAMON enhanced 3270 user interface orTEP to an MfN agent instance is verified by checking for access to a SAF resource named in this pattern:KN3.<msn>.TAKEACTION

Figure 33. Command and Response Log workspace (KN3CRTS)


Where <msn> is a managed system name. A managed system name typically identifies a unique TivoliEnterprise Monitoring Server agent instance. In this statement, TAKEACTION is a literal. Unless amatching SAF profile exists to control access to a given Take Action command, any request to transmit anaction to the managed system name is denied.

Typically you define a resource profile that restricts the access to all users (UACC(NONE)) and thenPERMIT access to these resources for user IDs or groups. The following examples show resourcedefinitions you may wish to define:v To restrict access to issue OMEGAMON for Mainframe Networks Take Action commands from the

enhanced 3270 user interface:RDEFINE security_class KN3.**.TAKEACTION UACC(NONE)

v To restrict access to issue OMEGAMON for Mainframe Networks Take Action commands from theenhanced 3270 user interface on a particular TCPIP stack and system:RDEFINE security_class KN3.<msn>.TAKEACTION UACC(NONE)

v To restrict access to OMEGAMON for Mainframe Networks Take Action Commands:RDEFINE security_class KN3.**.TAKEACTION.* UACC(NONE)RDEFINE security_class KN3.**.TAKEACTION.PING UACC(NONE)RDEFINE security_class KN3.**.TAKEACTION.TRACERTE UACC(NONE)RDEFINE security_class KN3.**.TAKEACTION.NSLOOKUP UACC(NONE)RDEFINE security_class KN3.**.TAKEACTION.DROP UACC(NONE)

v To restrict access to view all Take Action commands:RDEFINE security_class KN3.**.TAKEACTION.ADMIN UACC(NONE)

When these resource profiles are defined, refresh the security class by using the following command:SETROPTS RACLIST(security_class) REFRESH

Note: This comment can replace all text up to the paragraph before the first PERMIT definition.

You can define a profile named KN3.<msn>.TAKEACTION by entering these commands:RDEFINE $KN3SEC KN3.<msn>.TAKEACTION UACC(NONE)SETROPTS RACLIST($KN3SEC) REFRESH

More generally, you could define a profile to control all Take Action commands:RDEFINE $KN3SEC KN3.**.TAKEACTION.* UACC(NONE)SETROPTS RACLIST($KN3SEC) REFRESH

Granting access to individual user IDs or groups

After the resources are defined, grant access to individual user IDs or groups by using definitions such asthe ones that follow:v To enable a user ID or group to issue all OMEGAMON for Mainframe Networks Take Action

commands from the enhanced 3270 user interface on any system:PERMIT KN3.**.TAKEACTION ID(userid) ACCESS(UPDATE) CLASS(security_class)

v To enable a user ID or group to issue all OMEGAMON for Mainframe Networks Take Actioncommands on any system:PERMIT KN3.**.TAKEACTION.* ID(userid) ACCESS(UPDATE) CLASS(security_class)

v To enable a user ID or group to issue all OMEGAMON for Mainframe Networks Take Actioncommands on a specific TCPIP stack and system:PERMIT KN3.<msn>.TAKEACTION.* ID(userid) ACCESS(UPDATE) CLASS(security_class)

v To enable a user ID or group to issue a specific OMEGAMON for Mainframe Networks Take Actioncommand on any system:


PERMIT KN3.**.TAKEACTION.DROP ID(userid) ACCESS(UPDATE) CLASS(security_class)PERMIT KN3.**.TAKEACTION.PING ID(userid) ACCESS(UPDATE) CLASS(security_class)PERMIT KN3.**.TAKEACTION.TRACERTE ID(userid) ACCESS(UPDATE) CLASS(security_class)PERMIT KN3.**.TAKEACTION.NSLOOKUP ID(userid) ACCESS(UPDATE) CLASS(security_class)

v To enable a user ID or group to view all OMEGAMON for Mainframe Networks Take Actioncommands and responses issued by all users:PERMIT KN3.**.TAKEACTION.ADMIN ID(userid) ACCESS(UPDATE) CLASS(security_class)

After you permit users to the various resource profiles, issue the following commands to ensure thesepermissions have taken effect.SETROPTS GENERIC(security_class) REFRESHSETROPTS RACLIST(security_class) REFRESHSETROPTS GLOBAL(*) REFRESH

You can view the current SAF class definitions and permissions by issuing the following command:RLIST security_class * AUTHUSER

If no matching SAF profile exists to protect a Take Action command, that Take Action is denied.

Deploy the configurationUsing PARMGEN or Configuration Tool Batch mode and other methods for deploying configurationsthroughout your environment are not part of this product information.

The IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning andConfiguration Guide includes scenarios that illustrate various methods for using the Configuration Tool toreplicate a configuration of Tivoli Management Services components and monitoring agents across anenterprise. These scenarios assume that you are using system variables (IBM symbolics) and consistentnaming conventions for data set names, started tasks, and VTAM applids on all your LPARs.

The following Configuration Tool deployment scenarios are covered:v Scenario 1: Standard replication methodv Scenario 2: Using common RKANPARU and RKANCMDU librariesv Scenario 3: Using batch mode to replicate a runtime environment to another LPARv Scenario 4: Using batch auto-submit to replicate a runtime environment to another LPARv Scenario 5: Using batch mode to replicate a runtime environment on the same LPARv Scenario 6: Using interactive copy to replicate a runtime environmentv Scenario 7: Copying configuration values from one instance to another of the Configuration Toolv Scenario 8: Configuring a remote monitoring server and monitoring agents in batch mode

This guide also includes a number of scenarios to assist you in maintaining your Tivoli ManagementServices environment using PARMGEN.

Scenarios are also available for PARMGEN in the IBM Tivoli OMEGAMON XE and Tivoli ManagementServices on z/OS: PARMGEN Reference. These implementation scenarios include:v Scenario PGN01: Performing a pristine install of the monitoring server and two OMEGAMON agentsv Scenario PGN02: Performing a pristine install using shared librariesv Scenario PGN03: Performing a pristine install of a high-availability hub monitoring serverv Scenario PGN04: Cloning an existing environment but converting its hub monitoring server to a remotev Scenario PGN05: Upgrading an existing environment to the current releasev Scenario PGN06: Cloning an existing environment to run on a different LPARv Scenario PGN07: Upgrading an agent-only runtime environment to PARMGEN Phase 2v Scenario PGN07A: Converting an environment from ICAT to PARMGEN


v Scenario PGN07B: Upgrading your environment to PARMGEN Phase 2

If you are already using PARMGEN, then the IBM Tivoli OMEGAMON XE and Tivoli Management Serviceson z/OS: Upgrade Guide supports the following upgrade scenarios:v Scenario A: Upgrading the z/OS monitoring server onlyv Scenario B: Upgrading the z/OS monitoring server and monitoring agentsv Scenario C: Adding a monitoring agent and upgrading the z/OS monitoring serverv Scenario D: Upgrading monitoring agents in an existing runtime environment without a z/OS

monitoring serverv Scenario E: Upgrading additional products in an upgraded environment

Relink the runtime environmentsAfter all configuration is complete and you have loaded the runtime environment, you must relink theruntime environments by editing and running a linkedit job.

About this task

If you configured this monitoring agent using the Configuration Tool, after the OMEGAMON XE forMainframe Networks RTE is loaded (as documented in “Step 7: Loading the runtime libraries” on page123), a sample linkedit job named KN3LINK is created in &rhilev.&midlev&rtename.RKANSAMU. Edit andrun this job when you run the monitoring agent on a different release of z/OS from the SMP/E installedsystem.

The linkedit job is reproduced in the following section. Read the comments in the job and update asdirected.//KN3LINK JOB (ACCT),’NAME’,MSGCLASS=A,NOTIFY=ROOT//* *******************************************************************//* LICENSED MATERIALS - PROPERTY OF IBM *//* 5698-A35 *//* (C) COPYRIGHT IBM CORPORATION 2006. ALL RIGHTS RESERVED. *//* *//* US GOVERNMENT USERS RESTRICTED RIGHTS - USE, DUPLICATION OR *//* DISCLOSURE RESTRICTED BY GSA ADP SCHEDULE CONTRACT WITH IBM CORP. *//* *******************************************************************//* IMPORTANT: Before executing this JCL, update the jobcard with//* the following values appropriate for this system ://* thilev = SMP/E target high-level qualifier//* rhilev = Runtime high-level qualifier//* mhilev = mid level qualifier//* rtename= RTE name//* ***********************************************************//* OMEGAMON XE FOR MAINFRAME NETWORKS LOAD EXTENSIONS//* ***********************************************************//LNKEDIT EXEC PGM=IEWL,REGION=0M,// PARM=’AMODE=31,MAP,XREF’//SYSLIB DD DISP=SHR,// DSN=CEE.SCEELKED//OBJMOD DD DISP=SHR,// DSN=thilev.TKANMODS//SYSLMOD DD DISP=SHR,// DSN=rhilev.midlev.rtename.RKANMODU//SYSPRINT DD SYSOUT=*//SYSLIN DD *

INCLUDE OBJMOD(KN3ACTCM)ENTRY CEESTARTSETCODE AC(1)SETSSI D4E3C500NAME KN3ACTCS(R)

/*


//* ***********************************************************//* OMEGAMON XE FOR MAINFRAME NETWORKS LOAD EXTENSIONS #2//* ***********************************************************//LNKEDT2 EXEC PGM=IEWL,REGION=0M,// PARM=’AMODE=31,MAP,XREF’//SYSLIB DD DISP=SHR,// DSN=CEE.SCEELKED// DD DISP=SHR,// DSN=SYS1.CSSLIB//OBJMOD DD DISP=SHR,// DSN=thilev.TKANMODS//SYSLMOD DD DISP=SHR,// DSN=rhilev.midlev.rtename.RKANMODU//SYSPRINT DD SYSOUT=*//SYSLIN DD *

INCLUDE OBJMOD(KN3ANMLM)ENTRY CEESTARTSETCODE AC(1)SETSSI D4E3C500NAME KN3ANMON(R)

/*

If you configured this monitoring agent using PARMGEN, this linkedit operation is an option on theParameter Generator Workflow - Welcome panel. From this menu, select option 11. Submit to display theSUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP panel. From this panel, select option 9.KCIJPLNK ASM/Link RKANMODU modules. See the IBM Tivoli OMEGAMON XE and IBM TivoliManagement Services on z/OS: Common Planning and Configuration Guide for more information aboutperforming this task in PARMGEN.


Chapter 9. Verifying the configuration

After you configure your products and complete the post-configuration tasks, you are ready to confirmthat the products and components can run and communicate with each other.

Two verification scenarios are supported:v “Verifying configuration if you configured both Tivoli Enterprise Portal and the enhanced 3270 user

interface”v “Verifying configuration if you configured only the enhanced 3270 user interface” on page 151

Verifying configuration if you configured both Tivoli Enterprise Portaland the enhanced 3270 user interfaceUse this verification procedure if you configured both Tivoli Enterprise Portal and the enhanced 3270user interface.

About this task

Start the components and verify their operation, as described in this section. If you encounter problems,see the IBM Tivoli Monitoring: Troubleshooting Guide and the troubleshooting guides for each of yourmonitoring agents. If you see error messages, see IBM Tivoli Monitoring: Messages. See also “Supportinformation” on page 299.

Procedure1. Start your hub Tivoli Enterprise Monitoring Server using the following command (shown using the

default started task procedure name). Issue the following command from the z/OS system console tostart the Tivoli Enterprise Monitoring Server:S CANSDSST

Note: Use the stop command (P CANSDSST) to stop the Tivoli Enterprise Monitoring Server.2. Verify that the Tivoli Enterprise Monitoring Server has started successfully. You should see the

following message displayed on the z/OS system console or in SYSLOG or in the RKLVLOG for themonitoring server (TEMS) started task procedure:KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.

3. From the z/OS system console, issue the following command (shown using the default started taskprocedure name) to start the OMEGAMON XE for Mainframe Networks monitoring agent.S CANSN3

Note: Use the stop command (P CANSN3) to stop the OMEGAMON XE for Mainframe Networksmonitoring agent.

4. Verify that the OMEGAMON XE for Mainframe Networks XE Monitoring Agent has startedsuccessfully. You should see the following message displayed in the z/OS SYSLOG:IST1928I SNAMGMT CONNECTION TO KN3USER IS ACTIVE

You should also see the following message displayed in the RKLVLOG for the OMEGAMON XE forMainframe Networks XE monitoring agent:KN3PN001 OMEGAMON XE FOR MAINFRAME NETWORKS INITIALIZATION COMPLETED

5. From the z/OS system console, issue the following command (shown using the default started taskprocedure name) to start the Enhanced 3270 User Interface.S CANSTOM


Note: Use the stop command (P CANSTOM) to stop the Enhanced 3270 User Interface.6. Verify that the Enhanced 3270 User Interface started successfully. You should see the following

message displayed in the SYSPRINT log for the Enhanced 3270 User Interface:KOBGW0000I: Enhanced 3270 User Interface address space initialized successfully

7. Start and from the Manage Tivoli Enterprise Monitoring Services window. You can launch theManage Tivoli Enterprise Monitoring Services window by selecting Start > All Programs > IBMTivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. Locate entries for and in theManaging Tivoli Enterprise Monitoring Server Services windows to verify that they are installed.Start these components. For example, on Windows systems, you would perform the following steps:a. Right-click Tivoli Enterprise Portal Server and choose Start to start Tivoli Enterprise Portal

Server (if it is not already started). Verify that the status is Started.b. Right-click the Tivoli Enterprise Portal Desktop and choose Start. Log on to the Tivoli Enterprise

Portal desktop client. The default user ID is sysadmin. There is no default password unless apassword has been specified by your security administrator.

c. Verify that the Tivoli Enterprise Portal starts and that the Enterprise Status window can bedisplayed.

8. Verify that the OMEGAMON XE for Mainframe Networks monitoring agent shows a status ofONLINE in the Managed Systems Status view of the Enterprise Status window.

9. Verify that the OMEGAMON XE for Mainframe Networks monitoring agent is configured correctlyto collect the data you want:a. Open Tivoli Enterprise Portal and expand the z/OS Systems leaf on the Navigation tree.b. Find the z/OS system you have just configured the OMEGAMON XE for Mainframe Networks

monitoring agent instance to monitor.c. Expand the navigation tree for that system until you can see the Mainframe Networks agent

node, mfnAgentProcName:systemSMFID:KN3AGENT.d. Click on this node to display the Agent Status workspace. This workspace lets you easily review

your Mainframe Networks configuration settings.e. Verify that you can see data in this workspace. If so, then the Tivoli Enterprise Portal, Tivoli

Enterprise Portal Server, Tivoli Enterprise Monitoring Server, and the OMEGAMON XE forMainframe Networks monitoring agent are communicating successfully.

f. Examine the information displayed in this workspace to ensure that it is consistent with how youconfigured this monitoring agent. Look for the following characteristics.v Verify that the Agent User Name and Group Name attributes are correct for your enterprise.v Verify that the collection options you specified are reflected correctly in the SNA Collector

Status and the TCP Collector Status tables.v Does the TCP Collector SNMP Parameter Dataset Name attribute in the Agent Status table have

a value of UNKNOWN? If so, SNMP data will not be collected. The agent procedure specifieda file that could not be opened or did not specify a file at all. See Appendix E, “Format of theSNMP configuration file,” on page 289.

v Does the SNA Collection Started attribute in the Agent Status table have a value of No? If youconfigured this instance of the monitoring agent to collect VTAM environment and buffer pooldata, the value should be Yes. If it is not, then there is a problem with the VTAM major nodeor the VTAM PMI exit. See “Vary the VTAM major node active and copy it to your VTAMLSTlibrary” on page 133.

v Do the IP address, SNMP Agent Port, and SNMP Version columns in the TCP Collector Statustable display correct information for the TCP/IP stacks you want to monitor? If not, you mayhave a problem with the information specified in the TCP Collector SNMP Parameter Datasetidentified in the Agent Status table. See Appendix E, “Format of the SNMP configuration file,”on page 289.

10. Continue to expand the Navigation tree until you see the leaves for a TCP/IP stack and for VTAM.Select Applications under one of the TCP/IP stacks and verify that data is being displayed.


11. Select the OSA subnode and verify that data is being displayed. If no data is being displayed andthe value for the OSA Statistics Collection attribute in the Agent Status workspace is "Yes," ensurethat the OSA-Express Direct SNMP subagent (IOBSNMP) started task is running. See “Starting theOSA adapter SNMP subagent” on page 61 for information on how to configure IOBSNMP and“Verifying the z/OS environment setup” on page 62 for information on verifying this configuration.

12. Verify that the Enhanced 3270 User Interface is configured correctly to collect the data that you want.See Step 7 of “Verifying configuration if you configured only the enhanced 3270 user interface” fordetailed information about performing this validation.

Results

For more information about using the OMEGAMON XE for Mainframe Networks data displayed in theTivoli Enterprise Portal, see Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User'sGuide.

For more information about using the Enhanced 3270 User Interface, see the IBM Tivoli OMEGAMON XEfor Mainframe Networks: Enhanced 3270 User’s Guide and the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Enhanced 3270 User Interface Guide.

Verifying configuration if you configured only the enhanced 3270 userinterfaceUse this verification procedure if did not configure Tivoli Enterprise Portal, but configured only theenhanced 3270 user interface.

About this task

Start the components and verify their operation, as described in this section. If you encounter problems,see the IBM Tivoli Monitoring: Troubleshooting Guide and the troubleshooting guides for each of yourmonitoring agents. If you see error messages, see IBM Tivoli Monitoring: Messages. See also “Supportinformation” on page 299.

Procedure1. Start your hub Tivoli Enterprise Monitoring Server using the following command (shown using the

default started task procedure name). Issue the following command from the z/OS system console tostart the Tivoli Enterprise Monitoring Server:S CANSDSST

Note: Use the stop command (P CANSDSST) to stop the Tivoli Enterprise Monitoring Server.2. Verify that the Tivoli Enterprise Monitoring Server has started successfully. You should see the

following message displayed on the z/OS system console or in SYSLOG or in the RKLVLOG for themonitoring server (TEMS) started task procedure:KO4SRV032 Tivoli Enterprise Monitoring Server (TEMS) startup complete.

3. From the z/OS system console, issue the following command (shown using the default started taskprocedure name) to start the OMEGAMON XE for Mainframe Networks monitoring agent.S CANSN3

Note: Use the stop command (P CANSN3) to stop the OMEGAMON XE for Mainframe Networksmonitoring agent.

4. Verify that the OMEGAMON XE for Mainframe Networks XE Monitoring Agent has startedsuccessfully. You should see the following message displayed in the z/OS SYSLOG:IST1928I SNAMGMT CONNECTION TO KN3USER IS ACTIVE

Chapter 9. Verifying the configuration 151

You should also see the following message displayed in the RKLVLOG for the OMEGAMON XE forMainframe Networks XE monitoring agent:KN3PN001 OMEGAMON XE FOR MAINFRAME NETWORKS INITIALIZATION COMPLETED

5. From the z/OS system console, issue the following command (shown using the default started taskprocedure name) to start the Enhanced 3270 User Interface.S CANSTOM

Note: Use the stop command (P CANSTOM) to stop the Enhanced 3270 User Interface.6. Verify that the Enhanced 3270 User Interface started successfully. You should see the following

message displayed in the SYSPRINT log for the Enhanced 3270 User Interface:KOBGW0000I: Enhanced 3270 User Interface address space initialized successfully

7. Verify that the Enhanced 3270 User Interface is configured correctly to collect the data that you want.a. Use this command to log on to the Enhanced 3270 User Interface from z/OS environment:

LOGON APPLID(CTDOBAP)

This command causes the Enhanced 3270 User Interface logon screen to be displayed.b. Log on to the Enhanced 3270 User Interface, using a valid user ID and password. If this log in

fails, ensure that you completed the configuration required in Chapter 8, “Completing theconfiguration,” on page 127, especially those tasks under “Enable security” on page 140. The firstscreen you see is the Enterprise Summary workspace (KOBSTART), which serves as a “dashboard”for the OMEGAMON XE v5.1.0 suite of products that use the enhanced 3270 user interface. Eachagent has a subpanel contained within this master panel.

c. Enter this command to display the Enterprise Network Workspaces popup options menu:.NETMENU

The Enterprise Networks Workspaces pop-up window is displayed.d. Type T on the command line and press Enter to display the Enterprise TCPIP Stack Performance

Overview workspace. In this workspace, you should see IP data.Validate that the values for the System ID and TCPIP STC Name are correct, that is, that theymatch the system ID of the system on which you configured the OMEGAMON XE for MainframeNetworks monitoring agent and the TCPIP STC entries for the TCP/IP stacks that theOMEGAMON XE for Mainframe Networks monitoring agent is configured to monitor.If you see no data, view the agent RKLVLOG and verify that the agent has successfully connectedto its the monitoring server. Search for this connection message:Successfully connected to CMS system_id:CMS using ip.pipe:#x.xx.xx.xx.xxx.

Where system_id is the name of the system on which your monitoring server is running andx.xx.xx.xx.xxx is the IP address of this system.If these values are incorrect, ensure that you performed the system setup tasks described inChapter 3, “Preparing your z/OS environment,” on page 59. See the RKLVLOG for moreinformation.

e. Type NETMENU on the command line and press Enter. The Enterprise Networks Workspacespop-up window is displayed.

f. Type M on the command line and press Enter to display the Enterprise Memory and CSMStorage Overview workspace.Validate that you seen information about memory and CSM storage. Validate that the values forthe System ID and TCPIP STC Name are correct, that is, that they match the system ID of thesystem on which you configured the OMEGAMON XE for Mainframe Networks monitoring agentand the TCPIP STC entries for the TCP/IP stacks that the OMEGAMON XE for MainframeNetworks monitoring agent is configured to monitor.


If these values are incorrect, ensure that you performed the system setup tasks described inChapter 3, “Preparing your z/OS environment,” on page 59. See the RKLVLOG for moreinformation.

g. Type NETMENU on the command line and press Enter. The Enterprise Networks Workspacespop-up window is displayed.

h. Type B on the command line and press Enter to display the Enterprise OSA Express ChannelsOverview workspace.Validate that you see correct information about the OSA Express channels in your environment.Validate that the System ID is correct, that is, that it matches the system ID of the system onwhich you configured the OMEGAMON XE for Mainframe Networks monitoring agent . Validatethat the channel numbers displayed on this workspace reflect the correct OSA-Express devicesconnected to this system.If you see no data, verify that the z/OS TCP/IP SNMP Subagent (OSNMPD by default) and theOSA Express subagent (IOBSNMP or IOASNMP by default) are started on the TCP/IP stacks thatare connected to OSA-Express devices. Ensure that you performed the OSA setup task described inChapter 3, “Preparing your z/OS environment,” on page 59. See the RKLVLOG for additionalinformation.

Note: You can easily determine if the monitoring agent is online using the KOBMSNS Only ManagedSystems workspace to determine if the OMEGAMON XE for Mainframe Networks monitoring agentis currently registered with the hub monitoring server. When the OMEGAMON XE for MainframeNetworks agent address space is active but shows the MS Online Status value as N (meaning it isoffline), this usually means that a configuration error is preventing the monitoring servicescomponents from communicating with each other. It might also be that the OMEGAMON XE forMainframe Networks agent address space had experienced an abend. More details about using thisworkspace and other troubleshooting scenarios are found in the IBM Tivoli OMEGAMON XE forMainframe Networks: Troubleshooting Guide.

Results

For more information about using the Enhanced 3270 User Interface, see the IBM Tivoli OMEGAMON XEfor Mainframe Networks: Enhanced 3270 User’s Guide and the IBM Tivoli OMEGAMON XE and TivoliManagement Services on z/OS: Enhanced 3270 User Interface Guide.

Chapter 9. Verifying the configuration 153


Appendix A. Configuring the OMEGAMON II for MainframeNetworks component

The OMEGAMON II for Mainframe Networks component provides a 3270 interface to VTAMperformance data.

This appendix provides the information about the components of OMEGAMON II for MainframeNetworks and the tasks for configuring this component. This appendix assumes that you have alreadyinstalled the FMID for OMEGAMON XE for Mainframe Networks, which includes the OMEGAMON IIfor Mainframe Networks component, using SMP/E and the program directory.

This section explains the components of OMEGAMON II and steps you through the configuration steps.

Components of OMEGAMON II for Mainframe Networks that youconfigureBefore you begin configuration of OMEGAMON II for Mainframe Networks, understand thesecomponents and the function that each performs.

Table 35 lists the characteristics of OMEGAMON II and the components available when you configureOMEGAMON II for Mainframe Networks, provides a brief description of each, and indicates the impactthis characteristic or component has on configuration.

Table 35. Product components for OMEGAMON II for Mainframe Networks. Product components for OMEGAMON IIfor Mainframe Networks

Component Description

Modes ofoperations forOMEGAMON II

Function: Specifies whether VTAM needs to be available to OMEGAMON II.

OMEGAMON II for Mainframe Networks can run in one of two modes:

v VTAM mode, which enables you to run OMEGAMON II sessions from a VTAM terminalwithout an intermediate online application, such as TSO. You can set automatic update modeso that the screen refreshes automatically. VTAM mode allows all VTAM terminal users toshare a single copy of OMEGAMON II.

v Dedicated mode, which offers high availability and does not require VTAM services.Dedicated mode uses EXCP to communicate with a terminal and refreshes the screen everyfew seconds. Dedicated mode allows OMEGAMON II to provide real-time data even whenVTAM is not available.

Configuring this characteristic: During configuration, you will be asked to select andcustomize an operating mode.

v If you specify VTAM mode, copy the VTAM major node definition created during theConfiguration Tool installation.

v If you specify Dedicated mode, you will require the availability of a locally attachednon-SNA terminal.

For more information about setting up dedicated mode, see “Running in dedicated mode” onpage 194.


Table 35. Product components for OMEGAMON II for Mainframe Networks (continued). Product components forOMEGAMON II for Mainframe Networks


Securityconfiguration andoptional NAM andTABLE databasemigrations

Function: Enables OMEGAMON II to run in a secure environment

OMEGAMON II supports the following security interfaces:

v The TMS: Engine Network Access Manager (NAM) interface.

v RACF

v Another system authorization facility (SAF) product

Configuring this characteristic: After you complete the installation and configuration processes,you must complete setting up OMEGAMON II security. For information about setting upsecurity, see “Configuring security” on page 190.

If you use NAM as your security manager and you had a previous version of OMEGAMON II,decide if you want to migrate your NAM or Table Database data or both to the current release.Refer to “Configuring security” on page 190 for more information.

You can avoid redefining the information itemized in the list that follows to OMEGAMON IIby migrating your existing NAM and Table database data sets to the current release. If youelect to do so, specify the existing data set name on the Configuration Tool panel.

The NAM database contains user preferences and user IDs and passwords (optional). The Tabledatabase contains the following information for all prior releases:

v User response time definitions table

v SMF response time definitions table

v Virtual route monitoring options table

v Administrator monitoring options

v User authorities table

v Saved VTAM traces

For more information about configuring security, see “Configuring security” on page 190. Formore information about running the migration utility, see “Step 4: Run migration utility” onpage 169.

VSAM log filerecord size

Function: Determines if the default log size is adequate

The log (trend/exception) file contains trend and exception records for display. The default formaximum trend/exception record size is the allowable VSAM maximum. This record size isdeclared as variable.

Ensure that you monitor the usage and free space of your log file carefully, as you monitor anyVSAM application file. For information about monitoring the log file, see the OMEGAMON IIfor Mainframe Networks User's Guide.




TCP/IP datacollector (optional)

Function: Provides TCP/IP performance measurements

An OMEGAMON II for Mainframe Networks address space contains a TCP/IP performancedata collector that monitors and collects the performance data for mainframe TCP/IP addressspaces and the network resources and applications controlled by these address spaces. For eachaddress space, you can display the following:

v The resources being used

v TCP/UDP connections status and statistics

v Applications connected to the address space

v Devices connected to the address space

v Gateways connected to the address space

v The statements and parameters for the configuration

OMEGAMON II for Mainframe Networks provides a TCP/IP console feature that you can useto display TCP/IP data. You can use the TCP/IP console to execute TCP/IP and z/OScommands. You can also use the SNMP browser facility to display any data collected in theTCP/IP MIBs.

Configuring this component: During the configuration process, you will be asked to specifyvalues for the TCP/IP component. If you do not want to collect TCP/IP performance data, youcan specify N (No). The default is No. Note that the TCP/IP data collected with throughOMEGAMON II for Mainframe Networks is a small subset of the data collection byOMEGAMON XE for Mainframe Networks. Use OMEGAMON XE to collect TCP/IP data.

For information about configuring the TCP/IP data collector, see “Configuring theOMEGAMON II TCP/IP component” on page 175.

End-to-EndResponse Time(optional)

Function: Provides OMEGAMON II for Mainframe Networks with response time data and isrequired if you want to use the VTAM Trace Facility.

An OMEGAMON II for Mainframe Networks address space contains an End-To-End (ETE)Response Time component that is used to collect response time data. You can use thecomponent to monitor the response time of SNA terminals connected to applications on thehost. You can also specify that OMEGAMON II for Mainframe Networks will not use ETEservices.

Using ETE, view the following information:

v The time experienced by a user who has pressed a key and is waiting for a response at theterminal (end-to-end response time)

v The time the user request and the application response spend in VTAM and in theapplication (host response time)

v The time the request and its response spend traveling through the network outside the host(network response time)

Configuring this component: During the Configuration Tool process, you will be asked tospecify the started task name for ETE. The default is CANSETE.

For information about configuring ETE, see “Customizing ETE” on page 189

Appendix A. Configuring the OMEGAMON II for Mainframe Networks component 157



NCP performancedata collector(optional)

Function: Collects data from the network performance analysis logical units (NPALUs) in NCPs

An OMEGAMON II for Mainframe Networks address space contains an NCP performance datacollector that can connect to and request data from, the NPALUs in your NCPs. AnOMEGAMON II address space can collect NCP performance data in one of these two ways:

v By using its own NCP collector (a LOCAL collector), the most common configuration shownin Figure 34:

Figure 34. NCP Collector within the OMEGAMON II address spaceIf you plan to use only one OMEGAMON II address space, and you want to collect NCP performancestatistics, specify LOCAL NCP data collection to the Configuration Tool. OMEGAMON II will obtainNCP performance statistics from the LOCAL collector in the OMEGAMON II address space you areconfiguring.

v From the collector in another OMEGAMON II address space (a REMOTE collector), as shown in thediagram that follows:

Figure 35. NCP Collector in another OMEGAMON II address spaceIf you plan to use multiple OMEGAMON II address spaces, you can use the Configuration Tool toconfigure the address spaces so that performance data from all NCPs is available to all the addressspaces. To do so, use the Configuration Tool to configure one OMEGAMON II as LOCAL and the restas REMOTEs. Connect all NPALUs to the LOCAL address space, and configure each of the REMOTEOMEGAMON IIs to obtain their NCP performance statistics from the address space that you configuredas LOCAL.

Note:

1. One NCP collector can monitor multiple NCPs.

2. One NCP can be monitored by only one NCP collector.

Configuring this component: During the Configuration Tool process, you will be asked tospecify whether the OMEGAMON II you are configuring will obtain its NCP performance datausing its own LOCAL collector, or using the collector in another OMEGAMON II address space(a REMOTE collector). If you do not want to collect NCP performance statistics, you canspecify NONE. The default is LOCAL. For information about configuring the NCP datacollector, see “Customizing NCP” on page 185.




SAS programs(optional)

Function: Provides network performance data written to SMF (SAS programs areIBM-supplied.)

If you currently use the SAS-based historical component in a prior OMEGAMON II release, youmust decide whether you want to continue using your existing SAS data sets in the currentrelease or allocate new SAS data sets for this new release.

The prior releases of the historical component SAS databases and graphics catalog are fullycompatible with the current release.

The SAS-related Configuration Tool panels generate migration JCL, if you specify to do so byentering existing data set names.

Configuring this component: For information about configuring the SAS historical collection,see “Step 7: Configuring SAS Historical Reporting and complete SAS configuration” on page179 and “SMF record considerations” on page 195. For information about historical reportingusing SAS programs, see the OMEGAMON II for Mainframe Networks Historical Reporting Guide

SAS historicalcomponent(optional)

Function: Uses the performance data collected by the SAS data to create historical reports

Configuring this component: For information about configuring the SAS historical collection,see “Step 7: Configuring SAS Historical Reporting and complete SAS configuration” on page179 and “SMF record considerations” on page 195. For information about historical reportingusing SAS programs, see the OMEGAMON II for Mainframe Networks Historical Reporting Guide

Configuring OMEGAMON II for Mainframe Networks using thePARMGEN methodInstead of configuring this product with the Configuration Tool, you can configure the product using thePARMGEN method if you meet the requirements.

The OMEGAMON II for Mainframe Networks parameters are documented in the IBM TivoliOMEGAMON XE for Mainframe Networks: Parameter Reference. To use the PARMGEN method, see theinformation in the Chapter 6, “Configuring OMEGAMON XE for Mainframe Networks using thePARMGEN method,” on page 77. When you complete the PARMGEN configuration tasks, you must stillcomplete the customization and configuration tasks described in Appendix B, “Customizing theOMEGAMON II components and verifying installation,” on page 185 before using this monitoring agent.

Configuring OMEGAMON II for Mainframe Networks using theConfiguration ToolFollow these steps to configure OMEGAMON II for Mainframe Networks using the Configuration Tool

Configuring OMEGAMON II for Mainframe Networks involves the following steps.v “Accessing OMEGAMON II configuration steps in the Configuration Tool” on page 160

This step gets you to the place in the Configuration Tool where OMEGAMON II configuration starts.You should already have created the runtime environment needed to install this monitoring agent. Ifyou have not, see "Setting up and building a runtime environment" in the IBM Tivoli OMEGAMON XEand IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.

v “Step 1: Specify configuration values” on page 162

This step defines the information required to configure OMEGAMON II for Mainframe Networks andits components. This step specifies the names for the procedures that start OMEGAMON II. You may


also specify the VTAM major node and applids for the OMEGAMON II real-time (OMEGAMON) andhistorical components, and specify historical data store allocation values, security, and otherparameters.

v “Step 2: Allocate additional runtime data sets” on page 168

This step generates the JCL job for allocating the datasets you specified in the previous step. Reviewthe generated JCL job, edit it as required, and submit it.

v “Step 3: Create runtime members” on page 169

This step generates the JCL job for create the required runtime members. Review the generated JCL job,edit it as required, and submit it.

v “Step 4: Run migration utility” on page 169

This optional step lets you migrate NAM and TABLEDB datasets that you have configured in aprevious version of OMEGAMON II for Mainframe Networks.

v “Step 5: Loading the runtime libraries and exiting the Configuration Tool” on page 170

The step loads the runtime libraries from the SMP/E target libraries.v “Step 6: Completing the configuration” on page 171

These step must be completed outside of the Configuration Tool before you can begin to useOMEGAMON II for Mainframe Networks. (These procedures are also covered on a panel displayedwhen you select to complete the configuration using the Configuration Tool.) Before you begin thesesteps, you must load the runtime libraries (see “Step 5: Loading the runtime libraries and exiting theConfiguration Tool” on page 170).

v “Relinking the runtime environments after batch processing” on page 178

Edit and run this job if you want to revert to a previous version of z/OS or if the system that wasused for the SMP/E installation of the OMEGAMON II for Mainframe Networks component is at adifferent z/OS release level that the system that the monitoring agent is running on.

v “Step 7: Configuring SAS Historical Reporting and complete SAS configuration” on page 179

This special set of Configuration Tool panels enables you to configure SAS historical reporting. Formore information about the SAS reporting tool, see the OMEGAMON II for Mainframe Networks:Historical Reporting Guide.

Accessing OMEGAMON II configuration steps in the ConfigurationToolFollow these steps to access the Configuration Tool so you can start configuration of OMEGAMON II forMainframe Networks.

About this task

This configuration begins on the Product Component Selection Menu. If you have exited theConfiguration Tool, do the following to access this menu:

Procedure1. From the Configuration Tool main menu, enter 3 Configure products > 1 Select product to configure

> S OMEGAMON II for Mainframe Networks. This action caused the Runtime Environments panelshown in Figure 36 on page 161 to be displayed:


2. Add or use an existing RTE. If you have an RTE for Tivoli OMEGAMON XE for MainframeNetworks, use the same RTE for OMEGAMON II for Mainframe Networks product or use an existingOMEGAMON II for Mainframe Networks RTE. For information about adding a new RTE see the RTEchapter in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Planning andConfiguration Guide or use the online help.

3. After you have created your RTE, the Product Component Selection Menu shown in Figure 37 isdisplayed:

4. Select 3 OMEGAMON II for Mainframe Networks. This action causes the configuration steps panelshown in Figure 38 to be displayed.

Notice that there are five steps that are part of this configuration. These steps should be completed inthe order shown here. You can omit Step 6 and 7 if you do not plan to collect SAS historical reporting

------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------COMMAND ===>

Actions: A Add RTE, B Build libraries, C Configure,L Load all product libraries after SMP/E,D Delete, U Update, V View values, Z Utilities

Action Name Type Sharing Descriptiona HUBN3IRA SHARING BASE Sharing RTE with Hub TEMS and N3 TEMA

BASE BASE Base RTE

Figure 36. Runtime environments (RTEs) panel. Runtime environments (RTEs) panel




COMPONENT TITLE



----- CONFIGURE OMEGAMON II FOR Mainframe Networks/ RTE: rtename--------OPTION==>

Last SelectedPerform these configuration steps in order: Date Time

I Configuration Information (What’s New)

1 Specify configuration values2 Allocate additional runtime datasets3 Create runtime members4 Run migration utility (optional)5 Complete the configuration

6 Configure SAS historical reporting (optional)7 Complete SAS configuration

Figure 38. Configure OMEGAMON II for Mainframe Networks/RTE: rtename panel. Configure OMEGAMON II forMainframe Networks/RTE: rtename panel


data. The Date and Time fields on this panel are blank when you first access this panel, but are filledin as you complete the tasks, helping you track your progress through this operation

5. Select 1 Specify configuration values and press Enter to begin.

Step 1: Specify configuration valuesFollow the steps outlined in the Specify Configuration Values panel sequence to configurationOMEGAMON II.

About this task

The Specify Configuration Values panel sequence is where you define the information required toconfigure OMEGAMON II for Mainframe Networks and its components.

Procedure1. Selecting 1 Specify configuration values and pressing Enter causes the panel shown in Figure 39 to

be displayed:

The Configuration Tool uses the parameters you specify in this step to create runtime members. Whenthe Configuration Tool can determine the values that should be in these fields based on previousconfiguration work you have done, these values are provided as defaults. Use default valueswherever possible.Attention: If you plan to use Tivoli OMEGAMON XE for Mainframe Networks to monitor TCP/IPnetworks, be sure to specify N for Configure the TCP/IP component.

Use the information in Table 36 to complete this panel.

Table 36. Parameters and explanations for the Specify Configuration Values panel


Started task Specify the started task name in 1 to 8 characters. The Configuration tool places theprocedure in the &rhilev.&midlev.&rtename.RKANSAMU runtime library. The default isCANSON.

After the product configuration, copy the started task procedure to your PROCLIB.

--------------- SPECIFY CONFIGURATION VALUES / RTE: rtename -------------------Command ===>

Started task ==> CANSONTrend/exception datasets:

Size of each dataset ==> 20 (cylinders)Maximum record size ==> 32760

VTAM macro library ==> SYS1.SISTMAC1VTAMLIB load library ==> SYS1.VTAMLIBApplid prefix ==> CTDON (1-6 char)Virtual terminal prefix ==> CTDON (1-6 char)Maximum number of CUA users ==> 99 (10-256)End-to-End started task ==> CANSETE

Specify security ==> NONE (RACF, ACF2, TSS, NAM, None)Macro library for ACF2 ==>Function level security resource class ==> (ACF2 max is 3 char)

Location of NCP performance collector ==> LOCAL (None, LOCAL, REMOTE)Configure the TCP/IP component? ==> N (Y, N)

Figure 39. Specify configuration values/RTE:rtename panel. Specify configuration values/RTE:rtename panel


Table 36. Parameters and explanations for the Specify Configuration Values panel (continued)


Trend/Exception datasets

The trend/exception files contain trend and exception records from which OMEGAMONII builds trend and exception panels. OMEGAMON II swaps between twotrend/exception files. Specify:

v Number of cylinders to allocate for each trend/exception data set

v Maximum record size to allocate for the trend/exception data sets

The size of the trend/exception data sets varies greatly depending on the size of yournetwork and the Monitoring Options you specify under the Options pull-down. Monitorthe usage and free space of the trend/exception data sets as you do any VSAMapplication data set. The Log File Utilization panel under the Options pull-down(fastpath OMU) provides current DASD utilization statistics for each product component.

VTAM libraries Specify the names of your VTAM libraries:

v Fully qualified data set name of the VTAM macro library containing the macrosrequired for modetab assembly. It is typically SYS1.SISTMAC1. If not specified, onlySYS1.MACLIB and SYS1.MODGEN are used to assemble the modetab table.

v Fully qualified data set name of the VTAMLIB load library in which to catalog theLU6.2 modetab. It is typically SYS1.VTAMLIB.

Applid prefix Specify the applid prefix to establish the VTAM node and applid list. The product createsa customized VTAMLST definition in the &rhilev.&midlev.&rtename.RKANSAMU library,which you then copy to your SYS1.VTAMLST library after the Configuration Tool workis complete. The default is CTDON.Note: Each product requires its own set of IDs. Make sure that the product identifiers areunique. Type README APP on the command line to get more information on how theConfiguration Tool processes VTAM applids. Use the F6=Applids key to specify theVTAM major node and applid values.Note: If System Variable support is enabled, type README SYS on the command line toget more information on how the Configuration Tool processes VTAM applids usingMVS system symbols.

Virtual terminal prefix Specify the prefix to generate a pool of virtual terminal resources for the product VTAMmajor node in the SYS1.VTAMLST library. This prefix is also used to generate the VTAMconsole applids. For console support, the Configuration Tool will append a 'C' in front ofthe numeric field to indicate that these are VTAM console definitions.

The default prefix is CTDON.Note: On the Global options in the product, specify this prefix as your OMEGAMON IIconsole applid prefix.

Maximum number ofCUA users

Specify the maximum number of VTERMS assigned to the pool. A collection of VTERMS(VTAM applids) is called a VTERM pool. Each VTERM assigned to the pool must have acorresponding VTAM applid.

Because a physical terminal (PTERM) is usually allocated only one session at a time,Tivoli Monitoring Server:Engine (TMS:Engine) creates virtual terminals (VTERM).VTERMs simulate PTERMs for sessions between users and OMEGAMON II forMainframe Networks, but each VTERM can support many sessions on behalf of manyusers, and each user can have sessions on more than one VTERM.

The default is 99.

End-to-End started task Enter the name of the End-to-End started task procedure you will use.

The default is CANSETE.

Be consistent with the ETE started task name you specified when you configured otherOMEGAMON products (such as IBM Tivoli OMEGAMON XE for z/OS).




Specify security Specify which security system to use:

v None

v RACF

v ACF2

v TSS

v NAM

If you specify ACF2 as your security system, enter the fully qualified data set name ofthe ACF2 macro library currently in use at your site. The Configuration Tool will use thisdsname to assemble the ACF2 security exit.

To use external function level security, specify the name of the function level securityresource class. Depending on which security system you use, you may be required toperform further security tasks outside of the Configuration Tool. See “Configuringsecurity” on page 190 for detailed instructions.




NCP performance datacollection

The product can collect NCP performance statistics from the NCPs in your network. Ifyou want OMEGAMON II to access NCP statistics, you must specify the location of theNCP performance collector that OMEGAMON II will use.

Each OMEGAMON II address space contains an NCP performance collector that canconnect to and request data from, the NPALUs in your NCPs. An OMEGAMON IIaddress space can collect NCP performance data using its own NCP collector (a LOCALcollector), or it can obtain NCP performance data from the collector in anotherOMEGAMON II address space (a REMOTE collector).

You must specify whether the OMEGAMON II you are configuring will obtain its NCPperformance data using its own LOCAL collector, or using the collector in anotherOMEGAMON II address space (a REMOTE collector). If you do not want to collect NCPperformance statistics, you can specify None.

If you will be using only one OMEGAMON II address space, and you want to collectNCP performance statistics, specify LOCAL. OMEGAMON II will obtain NCPperformance statistics from the LOCAL collector in the current OMEGAMON II addressspace.

If you will be using multiple OMEGAMON II address spaces, you can configure theaddress spaces so that performance data from all NCPs is available to all OMEGAMONII address spaces. To do so, configure one OMEGAMON II as LOCAL and the rest asREMOTEs. Connect all NPALUs to the LOCAL address space, and configure each of theREMOTE OMEGAMON IIs to obtain their NCP performance statistics from the addressspace that you configured as LOCAL.

Keep in mind that an NPALU can connect to only one NCP performance collector. Youcannot connect a single NPALU to more than one collector. For the OMEGAMON IIaddress space you are currently configuring, specify one of the following types of NCPdata collection:

v LOCAL: OMEGAMON II will obtain NCP performance data from an NCPperformance collector residing in the address space you are currently configuring. Weexpect this to be the most common configuration. This is the default.

v REMOTE: OMEGAMON II will obtain NCP performance data from an NCPperformance collector residing in another OMEGAMON II address space. TheOMEGAMON II you are currently configuring will use APPC communications torequest data from the other address space. The address space that is connected to theNPALU and collecting the NCP data is specified as LOCAL.

v None: No NCP statistics. NCP performance data will not be available to this product'saddress space. If you specified NCP collection, the next panel requests moreparameters.

TCP/IP support The default is N. If you plan to use IBM Tivoli OMEGAMON XE for MainframeNetworks to monitor TCP/IP networks, be sure to specify N. For better performance, useIBM Tivoli OMEGAMON XE for Mainframe Networks to monitor your TCP/IPnetworks. Configure only one, either IBM Tivoli OMEGAMON XE for MainframeNetworks or OMEGAMON II for Mainframe Networks, to monitor your TCP/IPnetworks.

Specify Y if you want to install the TCP/IP component of OMEGAMON II forMainframe Networks. An affirmative response updates member: &rhilev.&midlev.&rtename.RKANCMDU(KONSTKON) with KONFCCMD TCPC initialization commandsto start the product.

When you have completed this panel, press Enter to continue.2. The panel that you see next differs depending on whether you specified Local or Remote on the

Location of NCP performance collector in the previous panel.


v If you specified LOCAL as the Location of NCP performance collector parameter and the NCPcollector resides in the same OMEGAMON II for Mainframe Networks address space that you arecurrently configuring, you see the panel shown in Figure 40:


Table 37. Parameters and explanations for the Local NCP Data Collection panel


LU6.2 logmode name 1-8 character name used to negotiate a session between this LOCAL NCP collector andany REMOTE OMEGAMON II address space that may request services from this NCPcollector. The Configuration Tool generates a logmode entry in a new modetab using thisname.

Name of the modetabcontaining the LU6.2logmode entryreferenced previously

The Configuration Tool uses this name to create a jobstream in RKANSAMU that you willuse to assemble the modetab.

NCP collection intervalin seconds

Data is collected from each NCP on a periodic basis. For example, if you specify 300, datais collected from each NCP every 300 seconds (5 minutes).

Fully qualified data setname of the librarycontaining the VTAMsource for each of yourNCPs

This data set contains the VTAMLST OUTPUT of your NCP generation jobstreams. DONOT supply the data set containing INPUT to the NCP generation process.

Fully qualified data setname of the librarycontaining the loadmodules for each ofyour NCPs

This data set requires APF authorization and is required for NCP statistics collection.

When you have completed this panel, press Enter to continue with configuration.v If you specified REMOTE as the Location of NCP performance collector parameter and the NCP

collector resides in an OMEGAMON II for Mainframe Networks address space other than the oneyou are currently configuring, you see the panel shown in Figure 41 on page 167:

----------------- LOCAL NCP DATA COLLECTION / RTE: rtename ------------------Command ==>

You specified LOCAL NCP data collection. OMEGAMON will obtain NCPperformance statistics from the NCP collector in this OMEGAMONaddress space. Please provide the following values:

LU6.2 logmode for NCP collector ==> CANCTDSCLU6.2 modetab for NCP collector ==> KDSMTAB1

NCP collection interval ==> 300 (seconds)NCP source dsname ==> SYS1.VTAMLSTNCP load library dsname ==> SYS1.VTAMLIB

Figure 40. Local NCP data collection/RTE: rtename panel. Local NCP data collection/RTE: rtename panel



Table 38. Parameters and explanations for the Remote NCP Data Collection panel


LU6.2 logmode name A 1-8 character name used to negotiate a session between this OMEGAMON II forMainframe Networks address space and the OMEGAMON II address space containing aLOCAL NCP collector. The Configuration Tool generates a logmode entry in a newmodetab using this name.

Name of the modetabcontaining the LU6.2logmode entryreferenced previously

The Configuration Tool uses this name to create a jobstream in RKANSAMU that you willuse to assemble the modetab.

Name of the runtimeenvironment where theNCP collector resides

The mid-level data set name qualifier that identifies the RTE containing the NCP collector.

When you have completed this panel, press Enter to continue with configuration.3. If you specified Y for the Configure the TCP/IP component? parameter, the Specify TCP/IP

Component Configuration panel shown in Figure 42 is displayed.OMEGAMON II for Mainframe Networks is able to collect TCP/IP, VTAM, SNA and NCP data. Butwith Tivoli OMEGAMON XE for Mainframe Network, the OMEGAMON XE monitoring agent uses amuch more efficient method of collecting TCP/IP data. Collecting TCP/IP data using bothOMEGAMON II for Mainframe Networks and Tivoli OMEGAMON XE for Mainframe Networks willhave a negative impact on performance and provide redundant data. Consider migrating TCP/IPperformance data collection to OMEGAMON XE for Mainframe Networks.If you want to use OMEGAMON II for Mainframe Networks to collect TCP/IP performance data,then complete the panel shown in Figure 42 and press Enter to continue with configuration.

Use the information in Table 39 on page 168 to complete this panel.

----------------- REMOTE NCP DATA COLLECTION / RTE: rtename ------------------Command ==>

You specified REMOTE NCP data collection. OMEGAMON will obtain NCPperformance statistics from the LOCAL OMEGAMON RTE that you specifybelow. Please provide the following values:

LU6.2 logmode for NCP collector ==> CANCTDSCLU6.2 modetab for NCP collector ==> KDSMTAB1

RTE containing LOCAL NCP collector (mid-level qualifier)

Figure 41. Remote NCP data collection/RTE: rtename panel. Remote NCP data collection/RTE: rtename panel

------------------ SPECIFY TCP/IP COMPONENT CONFIGURATION ----------------Command ===>

Specify your site’s VIO unit name:==> VIO

Specify the following TCP/IP information:TCP/IP data file (TCPIP.DATA or SYS1.TCPPARMS(TCPDATA)):

==> USER.PARMLIB(TCPDATA)TCP/IP sample interval:

==> 5 (1-60 minutes)SNMP Configuration file (USER.PARMLIB(KONSNMP)):

==> USER.PARMLIB(KONSNMP)

Figure 42. Specify TCP/IP component configuration panel. Specify TCP/IP component configuration panel


Table 39. Parameters and explanations for the Specify TCP/IP Component Configuration panel


Specify your site's VIO unitname

Specify the TCP/IP virtual input/output (VIO) unit. The VIO unit is used for theallocation of temporary data sets.

The default is VIO.

TCP/IP data file Enter the dsname of the library described in “z/OS Communications Server: IPConfiguration”, found in the reference “Configuration Data Sets”, which providesparameters for TCP/IP client programs. Specify either a sequential data set name or apartitioned data set (PDS) member name such as TCPIP.DATA orSYS1.TCPPARMS(TCPDATA).

TCP/IP sample interval Enter the TCP/IP sample interval. The value is in minutes from 1 to 60.

The default value is 5 minutes.

This value controls the frequency at which OMEGAMON II monitors your TCP/IPstack. On the sample interval, OMEGAMON II gathers TCP/IP performance data.OMEGAMON II requests information from the IBM SNMP agent. SNMP retrieves theinformation stored in its Management Information Base (MIB) and returns it toOMEGAMON II.

SNMP Configuration file The name of the data set containing entries for the SNMP manager functions withinTCP/IP data collection. Specify either the name of a sequential data set or the name ofa partitioned data set, and the name of the member containing SNMP configurationentries. The data set name will have a format such as USER.SNMP (if the data set hasphysical sequential organization, or a format such as USER.PARMLIB(KONSNMP) (ifthe data set has partitioned organization and member KONSNMP contains SNMPconfiguration entries). For more information about defining the entries in this dataset,see the KONSNMP sample file in RKANSAMU. KONSNMP sample member iscreated in RKANSAMU when the "Create Runtime Members" step is run. This is arequired field.

For more information about the format of this file, see Appendix E, “Format of theSNMP configuration file,” on page 289.Note:

1. OMEGAMON II for Mainframe Networks has no IPv6 support, so entries withIPv6 addresses are only read and checked for syntax, not used by OMEGAMON IIfor Mainframe Networks to obtain SNMP agent information.

2. One KN3SNMP file can be used for both OMEGAMON XE for MainframeNetworks and OMEGAMON II for Mainframe Networks.

When you have completed this panel, press Enter to continue with configuration.4. When you are finished specifying this configuration information, you are returned to the

configuration steps panel shown in Figure 38 on page 161:

Step 2: Allocate additional runtime data setsThis step in the OMEGAMON II for Mainframe Networks configuration process creates the VSAM datasets for trending and exception data.

About this task

Follow the steps in this section to create VSAM data sets for trending and exception data.


Procedure1. From the Configure OMEGAMON II for Mainframe Networks panel, enter 2 Allocate additional

runtime data sets. This action causes a job to be created. Review this job and, if necessary, edit it.Then submit it. You should get a return code of 0. If you do not, check the log to diagnose errors andrerun the job.

2. When the job completes, press F3 to return to the Configure OMEGAMON II for MainframeNetworks panel shown in Figure 38 on page 161.

Note: This step creates VSAM data sets for trending and exception data. If these data sets alreadyexist when you run this JCL job, the job will fail with condition code 12. This condition code isacceptable as long as the data sets were created successfully the first time the job was run.

Step 3: Create runtime membersOnce you have allocated the data sets, create the runtime members.

About this task

Follow these steps to create the runtime members required for OMEGAMON II for Mainframe Networks.

Procedure1. From the Configure OMEGAMON II for Mainframe Networks panel, enter 3 Create runtime

members. This action causes a job to be created.2. Review this job and, if necessary, edit it. Then submit it. You should get a return code of 0. If you do

not, check the log to diagnose errors and rerun the job.3. When the job completes, press F3 to return to the Configure OMEGAMON II for Mainframe

Networks panel shown in Figure 38 on page 161.

Step 4: Run migration utilityIf you do not want to migrate NAM and TABLEDB data from a previous release, follow the steps in thissection to run the migration utility and migrate this data.

About this task

If you do not want to migrate NAM and TABLEDB data from a previous release, you can skip this step.

If you want to migrate NAM and TABLEDB data from a prior release, select Run migration utility fromthe panel shown in Figure 38 on page 161 and specify the names of the data sets. (This step is optional.)This step is used to specify the pre-existing NAM and/or TABLEDB files you want to copy to the currentruntime environment. If you have previously defined user authorities, monitoring options, response timedefinitions, or saved VTAM traces, you can also keep or replicate this information.

Procedure1. From the Configure OMEGAMON II for Mainframe Networks panel, enter 4 Run migration utility.


2. Complete this panel and press Enter. This action causes a job to be displayed that you can edit andsubmit to do the requested migration.

3. To construct this JCL, specify the following:v Name of VSAM NAM file to migrate from: This is the name of the previously defined NAM file

which you want to copy into the new NAM file allocated for this runtime environment.v Name of VSAM TABLEDB file to migrate from: This is the name of the previously defined

TABLEDB file which you want to copy into the new TABLEDB file allocated for this runtimeenvironment.

4. When the job completes, press F3 to return to the Configure OMEGAMON II for MainframeNetworks panel shown in Figure 38 on page 161.

Step 5: Loading the runtime libraries and exiting the ConfigurationToolWhen Configuration Tool tasks are complete, you should load the runtime libraries and exit theConfiguration Tool.

About this task

Before you can start the Tivoli Enterprise Monitoring Server and the OMEGAMON II for MainframeNetworks monitoring agent, you must load the runtime libraries from the SMP/E target libraries. Theload job requires shared access to the runtime libraries.

You must load the runtime libraries based on the following conditions:v After initial product configurationv After applying SMP/E maintenancev After configuring a new product into an existing RTE

Note: In a sharing RTE configuration, only the master RTE (such as a Base RTE or a Full RTE) must beloaded after applying SMP/E maintenance because these RTE types contain copies of the SMP/E targetlibraries. If the RTE is configured to share the SMP/E target libraries directly, then this load step is notrequired after applying SMP/E maintenance. For additional information enter README RTE on theConfiguration Tool command line.

Follow these steps to load the runtime libraries from the SMP/E target libraries.

Procedure1. From the Configure OMEGAMON II for Mainframe Networks panel shown in Figure 38 on page

161, press F3 to return to the Product Component Selection Menu and then press F3 again to returnto the Runtime Environments (RTEs) panel.

-------------------- RUN MIGRATION UTILITY / RTE: N3420PC ---------------------OPTION ===>

To use the contents of pre-existing NAM or TABLEDB datasets,specify the source NAM or TABLEDB dsname, or both.

Name of NAM datasetto migrate from ==>

Name of TABLEDB datasetto migrate from ==>

Figure 43. Configure OMEGAMON II for Mainframe Networks /RTE:rtename panel. Configure OMEGAMON II forMainframe Networks /RTE:rtename panel


2. Type L for Load in the Action field by the name of the RTE that you have just configured and pressEnter.

Note: If you are sharing RTEs, both the BASE RTE and the SHARING RTE must be loaded.3. Review the JCL and submit the job. Verify that the job completes successfully and that the return code

is 04 or less.4. When you are finished loading the libraries, exit the Configuration Tool.

Step 6: Completing the configurationFollow these configuration procedures outside of the Configuration Tool or PARMGEN before you canbegin to use OMEGAMON II.

About this task

This section contains the configuration procedures that you must complete outside of the ConfigurationTool or PARMGEN before you can begin to use OMEGAMON II for Mainframe Networks. (Theseprocedures are also covered on a panel displayed when you select to complete the configuration usingthe Configuration Tool. or PARMGEN)

After initial configuration of this product, perform the Load all product libraries after SMP/E step fromthe Runtime Environments (RTE) panel. If you have additional products that you plan to configure in thisRTE also, then perform the RTE Load step after you have completed the configuration of all products inthis RTE. If you intend to start using this product operationally before the additional products areinitially configured in this RTE, then you must perform the RTE Load step for this product before startup.

In the same manner, if you have additional products that you plan to configure in this RTE also, thentypically, you would want to complete configuration of all products first before performing the commonprocedures done outside of the Configuration Tool or PARMGEN.

After all required steps for this product (or any additional products) within the Configuration Tool orPARMGEN have been performed, then you must execute the following procedures outside of theConfiguration Tool or PARMGEN to finalize installation and configuration.

Note: Note: The "Load all product libraries after SMP/E" step from the RTE panel must always beperformed after SMP/E maintenance. Type README RTE for more information.

Procedure1. “Assembling and link editing the LU 6.2 logon mode table” on page 1722. “Copying the VTAM definitions to VTAMLST” on page 1723. “Copying the started task procedures to your procedure library” on page 1724. “APF authorizing your libraries” on page 1735. “APF authorizing your libraries” on page 1736. “Setting the dispatching priority” on page 1747. The tasks associated with “Configuring the OMEGAMON II TCP/IP component” on page 175 if you

plan to use OMEGAMON II to monitor TCP/IP8. “Enabling CSA tracking to display TCP/IP CSA usage” on page 1789. “Configuring TNSTATs” on page 178

Note: If you are installing multiple agents at the same time, Procedures 2 through 5 may have alreadybeen performed. See the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS:Common Planning and Configuration Guide for information about the steps performed for multipleagents.


Assembling and link editing the LU 6.2 logon mode tableIf you requested that OMEGAMON II capture NCP performance statistics, assemble and link edit anOMEGAMON II for Mainframe Networks LU62 modetab.

About this task

Edit the jobstream according to your site requirements and submit the job. Verify the job completedsuccessfully.

If, during configuration, you requested that OMEGAMON II for Mainframe Networks component captureNCP performance statistics, you must assemble and link edit an OMEGAMON II for MainframeNetworks LU62 modetab.

Procedure1. Review the jobstream that the Configuration Tool created in &rhilev.&midlev.&rtename.RKANSAMU.

The name is the name you specified in LU 6.2 modetab using the Configuration Tool.2. Submit the job.3. Verify the results.

For information about customizing the NCP data collector, see “Customizing NCP” on page 185.

Copying the VTAM definitions to VTAMLSTCopy the VTAM major node (CTDONN is the default) from RKANSAMU to VTAMLST.

About this task

The Configuration Tool created a VTAM major node in RKANSAMU. You specified the name of themajor node when you defined OMEGAMON II for Mainframe Networks configuration values.

Procedure1. Copy the VTAM major node (CTDONN is the default) from RKANSAMU to VTAMLST.

Note: You may also use the sample system copy JCL to copy the system procedures and the VTAMmajor node members from the RKANSAMU library to the system libraries. The sample JCL may begenerated from the RTE Utility option.

2. To navigate to the RTE utility menu, do the following:a. Within the Runtime Environments (RTEs) panel, type Z next to the name of the RTE you have

configured and press Enter.b. From the RTE Utility Menu, select option 7 Generate sample system VTAMLST Copy the JCL

and press Enter. The JCL that creates the sample system VTAMLST copy (CB#Nxxxx) job isdisplayed.

Note: This step is applicable only if System Variables mode is not enabled.c. Submit the generated job, if applicable.

Copying the started task procedures to your procedure libraryCopy the started task procedures that the Configuration Tool created in RKANSAMU to your procedurelibrary PROCLIB.

About this task

The Configuration Tool created started task procedures in &rhilev.&midlev.&rtename.RKANSAMU that youmust copy to your procedure library PROCLIB.

Update your started task library as follows.


Procedure1. Copy the following procedures:

v The VTAM major node from &rhilvev.&midlev.&rtename.RKANSAMU to VTAMLST. The defaultname is CTDONN (covered under “Copying the VTAM definitions to VTAMLST” on page 172).

v The OMEGAMON II for Mainframe Networks procedure from &rhilvev.&midlev.&rtename.RKANSAMU to the started task procedure. The default name is CANSON. You will needto edit the CANSON first to uncomment the following line:VARY NET,ACT,ID=CTDONN

v The End-to-End started task JCL from &rhilvev.&midlev.&rtename.RKANSAMU to PROCLIB. (If youhave already installed ETE V620, you do not have to perform the copy. You can also rename theprocedure to meet your site's requirements.) The default name is CANSETE.

2. You might also use the sample system copy JCL to copy the system procedures and the VTAM majornode members from the &rhilev.&midlev.&rtename.RKANSAMU library to the system libraries (ifapplicable). The sample JCL can be generated from the RTE Utility option. To navigate to the RTEUtility menu, do the following:a. Within the Runtime Environments (RTEs) panel, type Z next to the name of the RTE you have

configured and press Enter.b. From the RTE Utility Menu, select option 6 Generate sample system procedure copy JCL, and

press Enter. Specify your system procedure library and press Enter. The JCL that creates thesample system procedure copy job (CB#Pxxxx) is displayed.

APF authorizing your librariesIf you use APF authorization, add the required runtime load libraries to your list of APF-authorizedlibraries.

About this task

If you use APF authorization, add the following runtime load libraries to your list of APF-authorizedlibraries.&rhilev.&midlev.&rtename.RKANMODU&rhilev.&midlev.&rtename.RKANMOD&rhilev.&midlev.&rtename.RKANMODL

Note: Any runtime libraries concatenated in the STEPLIB DDNAME and in the RKANMODL DDNAME of theCANSON started tasks must be APF-authorized.

Making the performance monitor interface (PMI) exit available to VTAMUse one of these two method to make the performance monitor interface (PMI) exit available to VTAM:modifying the startup JCL or copying the PMI exit to VTAM.

About this task

You must make the PMI exit accessible to VTAM.

Follow these steps to modify the VTAM startup JCL.

Procedure

Choose one of these two ways to do this task: by make the performance monitor interface (PMI) exitavailable to VTAM:

Option Description

Choice option Choice description


Option Description

Modify the VTAM startup JCL 1. Add a DD statement for the library containing thePMI exit to the VTAMLIB concatenation in yourVTAM startup procedure. If you did not configurethis OMEGAMON II RTE to share with the SMP/Etarget libraries (that is, SHARING SMP), then youcould add the following statement to the VTAMLIBconcatenation. See the note that follows if you selectthis option. Add this library:

&rhilev.&midlev.&rtename.RKANMOD

If you do configure the OMEGAMON RTE to sharewith the SMP/E libraries, then follow the steps in the"Method

2. Quiesce your network

3. Restart VTAM.

Copy the PMI Exit on VTAM An alternate approach is to copy the PMI exit moduleand its ALIASes to an existing library in the VTAMLIBconcatenation. The PMI Exit consists of moduleKONAMVPX and its five ALIASes KONAMV00-04. ThePMI Exit must be found somewhere in the VTAMLIBconcatenation in order for the exit to function correctlywhen the OMEGAMON II program tries to activate theexit.

If you do this, then there is no longer a need to quiesceVTAM when maintenance is applied.

A potential drawback to this method is that futurechanges to the VTAM PMI exit might not be picked upwhen you apply maintenance if you forget to recopy thePMI Exit program and its ALIASes to the library in theVTAMLIB concatenation after the maintenance isapplied.

Another potential problem occurs if you copy the PMIexit to different libraries in the VTAM concatenation andhave multiple copies of the PMI exit in your VTAMLIBconcatenation. If you choose this approach, you must puta process in place for ensuring that the OMEGAMON IIfor Mainframe Networks PMI exit program is correctlymaintained.

Note: If you do not configure this OMEGAMON II RTE to share with the SMP/E target (that is,SHARING SMP) then you use the process described in the "Copying the PMI exit to VTAM" section of“Making the performance monitor interface (PMI) exit available to VTAM” on page 135. Do not addSMP/E target libraries to the VTAMLIB concatenation because this would create a problem when youapplied maintenance in the future.

Setting the dispatching prioritySet the dispatching priority for OMEGAMON II and ETE minimally equal to VTAM dispatching priority.

About this task

Do the following to ensure OMEGAMON II for Mainframe Networks availability:


Procedure1. Set the OMEGAMON II for Mainframe Networks dispatching priority equal to or greater than the

VTAM you are monitoring.2. Execute the End-to-End Response Time Feature (ETE) with a dispatching priority equal to the VTAM

you are monitoring.

Configuring the OMEGAMON II TCP/IP componentFollow these outside the Configuration Tool or PARMGEN steps to configure the OMEGAMON IITCP/IP component.

About this task

If you selected to collect TCP/IP data with OMEGAMON II for Mainframe Networks, you must alsocomplete the following configuration steps outside of the Configuration Tool.

Procedure1. Obtaining TCP/IP performance measurements requires that you answered Y to the "TCP/IP Support"

questions on the SPECIFY CONFIGURATION VALUES / RTE: rtename panel shown in Figure 39 onpage 162 and then provided the requested parameters on panel the SPECIFY TCP/IP COMPONENTCONFIGURATION panel shown in Figure 42 on page 167 during configuration with theConfiguration Tool.

2. “Defining an OMVS segment in RACF or your SAF product for the OMEGAMON II procedure”3. “Configuring the OMEGAMON II for Mainframe Networks SNMP manager functions” on page 1764. “Adding support for the SYSTCPD DDNAME in the started tasks” on page 1775. “Relinking the runtime environments after batch processing” on page 178

Defining an OMVS segment in RACF or your SAF product for the OMEGAMON II procedure:

Define a UNIX System Services OMVS segment with SuperUser authority.

About this task

The OMEGAMON II for Mainframe Networks TCP/IP data collector uses TCP/IP service components inz/OS Communications Server that exploit z/OS UNIX System Services. Using these components requiresa UNIX System Services security construct, called an OMVS segment, for the user ID associated withunits of work requesting these services.

The OMVS segment must be defined with SuperUser authority. Authorize the OMEGAMON II forMainframe Networks started task for TCP/IP privileges by creating an OMVS segment for RACF oranother SAF product. Identify the OMEGAMON II for Mainframe Networks started task CANSON as asuperuser, as in this example:ALU CANSON OMVS(UID(0) HOME(/) PROGRAM(/bin/sh))

See the z/OS Communications Server IP Planning and Migration Guide for an explanation of how to providean OMVS segment for the OMEGAMON II for Mainframe Networks started task.

Note: This command makes setting of SuperUser authority more explicit. This action has actuallyalready taken place when you ran the JCL job described in “Define monitoring agent access to thenetwork management interfaces and commands” on page 128.

If you recently migrated to z/OS v2.1, you might find OMVS errors in the system log when you launchthe OMEGAMON XE for Mainframe Networks monitoring agent. Be aware that as of z/OS V2R1, theability to use default OMVS segments has been removed. All z/OS UNIX users or groups must now haveOMVS segments defined for user and group profiles with unique user IDs (UIDs) and group IDs (GIDs).


For more information about this error and workarounds, see "OMVS and SNAMGMT errors found insystem log on z/OS v2.1 systems" in the IBM Tivoli OMEGAMON XE for Mainframe Networks:Troubleshooting Guide.

Configuring the OMEGAMON II for Mainframe Networks SNMP manager functions:

Ensure that OMEGAMON II can collect TCP/IP performance data by confirming that the SNMPsubagent in the TEP/IP address space is started.

About this task

OMEGAMON II for Mainframe Networks uses the Simple Network Management Protocol (SNMP)Management Information Base (MIB) to obtain TCPIP performance data. An SNMP agent and subagentmust be active. The chapter about SNMP in the IBM z/OS Communications Server: Configuration Guide bookexplains the configuration procedure for running the TCP/IP SNMP agent and subagent. The chapter alsoexplains how to automatically start the SNMP agent when TCP/IP starts.

The SNMP subagent, a task in the TCP/IP address space, is a z/OS UNIX system services applicationthat communicates with the SNMP agent via an AF_UNIX socket. Consequently, the AF_UNIX domainmust be configured in your BPXPRMxx member of SYS1.PARMLIB. Consult the BPXPRMxx chapter inthe IBM MVS Initialization and Tuning Reference for details about activating the AF_UNIX domain.

Confirm that the z/OS Communications Server SNMP Agent, OSNMPD, is configured correctly byissuing the z/OS UNIX snmp command from the UNIX System Services command line with thefollowing syntax.snmp —c <community_name> —h <host_name_name> -v get sysUpTime.0

Where <community_name> and <host_name_name> are the SNMP community name and host name for thez/OS system where you will be running the OMEGAMON II for Mainframe Networks monitoring agent.If OSNMPD is configured correctly you will receive the sysUpTime value. This is the time 'in secondsthat OSNMPD has been active. If the command times out, then OSNMPD is not configured correctly.

For the TCP/IP SNMP subagent, issue the z/OS UNIX snmp command from the UNIX System Servicescommand line with the following syntax:snmp —c <community_name> —h <host_name_name> -v get ibmMvsTcpipProcname.0

Where <community_name> and <host_name_name> are the SNMP community name and host name for thez/OS system where you will be running the OMEGAMON II for Mainframe Networks monitoring agent.If the TCP/IP subagent is configured correctly you will receive the name of the TCP/IP stack underwhich the subagent is running. If the command times out, or you receive a value of noSuchName ornoSuchObject, then either OSNMPD is not configured correctly or the TCP/IP subagent is not active.Verify that the TCP/IP profile statement SACONFIG has been specified correctly.

Note: There should be one SNMP Agent started per monitored TCP/IP stack.

Follow this process to configure the SNMP manager functions.

Procedure

1. Confirm that the SNMP configuration file named on the KONSNMP DD card in the sample startprocedure (CANSON) exists. If it does not, allocate it.

2. Edit this file. See sample SNMP configuration file KONSNMP in RKANSAMU for information thesyntax of the parameters in this file. You can share the same SNMP configuration file betweenOMEGAMON II for Mainframe Networks and OMEGAMON XE for Mainframe Networks. Sharingthe same SNMP configuration file could make it easier for an administrator to maintain the list ofTCP/IP stacks that each application is configured to monitor. A shared configuration can be achieved


by altering either the KN3SNMP DD card OMEGAMON XE for Mainframe Networks start procedureor the KONSNMP DD card in the OMEGAMON II for Mainframe Networks start procedure to usethe same SNMP configuration file. Note that OMEGAMON II for Mainframe Networks has no IPv6support, so entries with IPv6 addresses are only read and checked for syntax and are not used byOMEGAMON II for Mainframe Networks to obtain SNMP agent information.

3. Add a configuration statement for each SNMP agent from which data will be collected (one perTCP/IP stack).

4. Save this data set.

Results

See Appendix E, “Format of the SNMP configuration file,” on page 289 for more information about thisfile format.

Adding support for the SYSTCPD DDNAME in the started tasks:

SYSTCPD explicitly identifies which data set to use to obtain the parameters defined by TCPIP.DATAwhen no GLOBALTCPIPDATA statement is configured.

About this task

If a monitoring server is using any of the IP.UDP-related or IP.PIPE-related communication protocols forconnection, but the IP domain name resolution is not fully configured on the z/OS system, SYSTCPDmust be supported by the monitoring server and the monitoring agents that report to it.

If you are certain that SYSTCPD is not needed at your installation, you can skip this step. However, notethat you might gain a small performance benefit by avoiding multiple dynamic data set allocations if yousupply a SYSTCPD DD statement.

To support SYSTCPD, do the following:

Procedure

1. Uncomment the following statement in the started task members in RKANSAMU and provide thename of the SYSTCPD data set://*SYSTCPD DD DISP=SHR,//* DSN=TCPIP.SEZAINST(TCPDATA)

The name of the SYSTCPD data set is installation-specific. Get the correct specification from yournetwork administrator. If you reconfigure products, you will need to uncomment the statement again.

2. If the monitoring server is using any of the IP.UDP-related or IP.PIPE-related communication protocolsfor connection, but the IP domain name resolution is not fully configured on this z/OS system, youmust specify the SYSTCPD DDNAME in the CANSDSST started task. The Configuration Toolgenerated the CANSDSST started task with the following commented out lines. Customize theSYSTCPD DDNAME accordingly if this scenario fits your environment://*SYSTCPD explicitly identifies which dataset to use to obtain//*the parameters defined by TCPIP.DATA when no GLOBALTCPIPDATA//*statement is configured. Refer to the IP Configuration Guide//*for information on the TCPIP.DATA search order. The dataset//*can be any sequential dataset or a member of a partitioned//*dataset. TCPIP.SEZAINST(TCPDATA) is the default sample file.//*TCPIP.TCPPARMS(TCPDATA) is another sample and is created as//*part of the Installation Verification Program for TCP/IP.//*Note: Uncomment out this DDNAME and point to appropriate//* TCPDATA library name supported at your site if domain//* name resolution is not fully configured.//*SYSTCPD DD DISP=SHR,//* DSN=TCPIP.SEZAINST(TCPDATA)


3. When you are finished, copy the procedures to PROCLIB.

Relinking the runtime environments after batch processing:

Edit the KONLINK sample linkedit job in RKANSAMU if you use OMEGAMON II to monitor TCP/IP.

About this task

If you are using OMEGAMON II for Mainframe Networks to monitor TCP/IP, after the OMEGAMON IIfor Mainframe Networks RTE is loaded (as documented in “Step 7: Loading the runtime libraries” onpage 123), a sample linkedit job named KONLINK is created in &rhilev.&midlev.&rtename.RKANSAMU.

Procedure

1. Edit and run this sample job when you run the monitoring agent on a different release of z/OS fromthe SMP/E installed system.

2. Read the comments in the job and update as directed.

Enabling CSA tracking to display TCP/IP CSA usageEnsure that the default parmlib member contains the VSM CSA(ON) statement so that CSA informationwill be available in OMEGAMON II.

About this task

The IBM-supplied default PARMLIB member is DIAG00, which contains the following:...

VSM TRACK CSA(ON) SQA(ON)...

If this is not specified, then CSA information will not be available within the product.

Configuring TNSTATsUse TNSTATs to adjust VTAM and NCP parameters, and thereby improve VTAM performance.

About this task

VTAM records tuning statistics (TNSTATs) for the following channel-attached nodes:v Communications controllerv Adjacent host processorv SNA cluster controller

You can use TNSTATs to adjust VTAM and NCP parameters, and thereby improve VTAM performance.

To record and display TNSTATs, you must specify the TNSTAT VTAM start option, or you must turn onTNSTATs manually using the MODIFY TNSTAT command. Since TNSTATs are always recorded to theSMF data set, you must also include the SMF facility in the system during system generation.

If TNSTATs are not active, OMEGAMON II does the following:v Displays turquoise TNSTATs status lights that read NOTNSTAT on the main status panelv Displays a turquoise (Idle) condition for each device listed under TNSTATsv Displays only configuration data under TNSTATsv Does not record TNSTATs data to online trend files or SMF

For more information about TNSTATs, see the following:v ”Gathering Tuning Statistics” in the IBM z/OS Communications Server SNA Network Implementation book


v ”Tuning Statistics” in the OMEGAMON II for Mainframe Networks User's Guide.

Step 7: Configuring SAS Historical Reporting and complete SASconfigurationFollow these steps to complete configuration of SAS historical reporting.

About this task

If you plan to collect SAS historical reporting data, you must configure SAS historical reporting. If youhave exited the Configuration Tool, start it again using the information found in “AccessingOMEGAMON II configuration steps in the Configuration Tool” on page 160. Then, from the ConfigureOMEGAMON II for Mainframe Networks panel, enter 6 Configure SAS historical reporting. This actioncauses the panel shown in Figure 44 to be displayed. Complete the following steps to configure SAShistorical reporting.

For information about using the SAS reporting tool, see the OMEGAMON II for Mainframe Networks:Historical Reporting Guide.

Procedure1. Selecting 6 Configure SAS historical reporting and pressing Enter causes the panel shown in

Figure 44 to be displayed:

Use this panel to start configuring the SAS historical reporting component. If you do not use SASreporting, press the End key to return to the main configuration menu. The panel displays theproduct-provided defaults or the values from the last construction of this runtime environment.Use the information in Table 40 to complete this panel.

Table 40. Parameters and explanations for the Configure SAS Historical Reporting / RTE: rtename panel


SAS version currently installed Your SAS release. Versions 5, 6, and 8 are supported. The default is Version 6.

Name of OMEGAMON II forMainframe Networks SASprocedure

The OMEGAMON II for Mainframe Networks SAS procedure name. TheConfiguration Tool creates this procedure and stores it in RKANSAMU. Thedefault is KONSAS.

------------ CONFIGURE SAS HISTORICAL REPORTING / RTE: rtename -----------------OPTION ===>

To configure SAS reporting, enter:

SAS version currently installed ==> 6 (5, 6, 8)

Name of OMEGAMON II for Mainframe NetworksSAS procedure ==> KONSAS

Do you want to use SAS/GRAPH tocreate historical graphs? ==> Y (Y, N)

To bypass SAS reporting configuration, press the End key. (Y, N)

Figure 44. Configure SAS Historical Reporting / RTE: rtename panel: Panel 1. Configure SAS Historical Reporting /RTE: rtename panel: Panel 1


Table 40. Parameters and explanations for the Configure SAS Historical Reporting / RTE: rtename panel (continued)


Do you want to use SAS/GRAPHto create historical graphs?

The SAS historical component can generate both character-based plots andcolor SAS/GRAPH plots suitable for online viewing. If you have SAS/GRAPHand want to generate graphs, specify Yes. If you are not licensed forSAS/GRAPH or do not wish to generate graphs, specify No. The default isYes. Using the parameters you specify, the Configuration Tool creates theappropriate SAS runtime libraries and members in RKANSAMU.

When you have completed this panel, press Enter for the next SAS reporting panel, which requestsSAS libraries for the SAS version you specified.

2. Pressing Enter from Figure 44 on page 179 causes the panel shown in Figure 45 to be displayed:

Use this panel to specify the fully qualified names of your SAS product libraries: the load library, helplibrary, and message library, and the batch and TSO configuration data sets and member names. Thepanel displays the product-provided defaults or the values from the last construction of this runtimeenvironment. For more information about these parameters, see the SAS documentation.

3. Pressing Enter from Figure 45 causes the panel shown in Figure 46 to be displayed:

Use this panel to define the required SAS historical databases. You can define new historical databasesby specifying the size for these databases, or you can use existing databases by providing dsnames.Use the information in Table 40 on page 179 to complete this panel.

------------------ SAS HISTORICAL COMPONENTS / RTE: rtename --------------------OPTION ===>

Provide your SAS version 6 library names:

SAS load library ==> SAS.LIBRARYSAS help library ==> SAS.SASHELPSAS message library ==> SAS.SASMSGSAS configuration file dsnames (sequential or PDS with member):

BATCH ==> SAS.CNTL(BATCHXA)TSO ==> SAS.CNTL(TSOXA)

Figure 45. SAS Historical Components / RTE: rtename panel: Panel 2. SAS Historical Components / RTE: rtenamepanel: Panel 2

-------------- DEFINE SAS HISTORICAL COMPONENTS / RTE: rtename ------------------OPTION ===>

To define new historical databases, specify size. Or, to use existingdatabases, provide dsnames.

Create new SAS databases? ==> Y (Y, N)Daily database size in cylinders ==> 20,5 (primary,secondary)Weekly database size in cylinders ==> 15,5 (primary,secondary)Monthly database size in cylinders ==> 10,5 (primary,secondary)

To use existing databases, provide dsnames:Daily database name ==>Weekly database name ==>Monthly database name ==>

Figure 46. Define SAS Historical Components/ RTE: rtename panel: Panel 3. Define SAS Historical Components/RTE: rtename panel:: Panel 3


Table 41. Parameters and explanations for the Define SAS Historical Component / RTE: rtename panel


Create new SAS databases? Do you want to define new SAS historical databases or use existing databases?The Configuration Tool can allocate new SAS databases or migrate thedatabases you used in a previous release. Specify whether you want theConfiguration tool to allocate new SAS databases. The default is Yes.

SAS sample code and JCL to build daily, weekly, and monthly databases is supplied by the Configuration Tool.

Daily database size in cylinders Specify the size of your primary and secondary daily databases in cylinders.The default is 20 for the primary and 5 for the secondary. If you are migratingfrom an earlier release, the values shown will be those you specified in the lastconstruction of this runtime environment.

Weekly database size in cylinders Specify the size of your primary and secondary weekly databases in cylinders.The default is 15 for the primary and 5 for the secondary. If you are migratingfrom an earlier release, the values shown will be those you specified in the lastconstruction of this runtime environment.

Monthly database size in cylinders Specify the size of your primary and secondary monthly databases incylinders. The default is 10 for the primary and 5 for the secondary. If you aremigrating from an earlier release, the values shown will be those you specifiedin the last construction of this runtime environment.

If you want to migrate an existing SAS database, specify the fully qualified data set name for the followingdatabases.

Daily database size in cylinders The fully qualified data set name for the daily database.

Weekly database size in cylinders The fully qualified data set name for the weekly database.

Monthly database size in cylinders The fully qualified data set name for the monthly database.

When you have completed this panel, press Enter for the next SAS reporting panel, which requestsSAS/GRAPH configuration parameters.

4. Pressing Enter from Panel Figure 46 on page 180 causes the panel shown in Figure 47 to be displayed:

Note: To use SAS/GRAPH online with OMEGAMON II for Mainframe Networks, you must have agraphics-capable workstation.Use this panel to enter SAS/GRAPH configuration parameters. Use the information in Table 42 onpage 182 to complete this panel.

------------------- SAS HISTORICAL COMPONENTS / RTE: rtename --------------------OPTION ===>

Enter SAS/GRAPH configuration parameters.

To create a sample modetab containing queriable logmodes entries, provide:VTAM logmode table name ==> KONINCLM

To define a new graphics catalog, specify size. Or, to use an existinggraphics catalog, provide the dataset name.

Create a new SAS graphics catalog? ==> Y (Y, N)Graphics catalog size in cylinders ==> 10,5 (primary,secondary)

To use an existing graphics catalog, enter the dsname:Graphics catalog name ==>

Figure 47. SAS Historical Components / RTE: rtename panel: Panel 4. SAS Historical Components / RTE: rtenamepanel: Panel 4


Table 42. Parameters and explanations for the SAS Historical Components / RTE: rtename panel


To create a sample modetabcontaining queriable logmodesentries, provide: VTAM logmodetable name

The Configuration Tool builds a jobstream that assembles and linkedits asample mode table containing queriable logmode entries into your VTAMLIBdataset. The Configuration Tool puts the JCL in RKANSAMU. The membername is the name you specify for a graphics logmode entry. You can use thisjobstream to create queriable logmode entries if you do not already have them.The default is KONINCLM.

To define a new graphics catalog, specify size. Or, to use an existing graphics catalog, provide the dataset name.

Create a new SAS graphics catalog? Specify the SAS/GRAPH Catalog. The Configuration Tool can allocate a newSAS/GRAPH catalog or migrate the catalog you used in a previous release.Specify whether you want the Configuration Tool to allocate a newSAS/GRAPH catalog. The default is Yes.

Graphics catalog size in cylinders Specify the size of the primary and secondary graphics catalogs in cylinders.The defaults are 10 for the primary and 5 for the secondary.

To use an existing graphics catalog,enter the dsname: Graphics catalogname

If you are using an existing graphics catalog, enter the data set name. There isno default.

When you have completed this panel, press Enter and you are returned to the ConfigureOMEGAMON II for Mainframe Networks panel main menu panel.

5. From the Configure OMEGAMON II for Mainframe Networks panel, enter 7 Complete SASconfiguration. This action causes JCL job ON#CA1 to be created. Review this job and, if necessary,edit it. Then submit it. A return code of 0 is displayed. If you do not see a return code of 0, check thelog to diagnose errors and rerun the job.

6. Exit the Configuration Tool and proceed to “Completing SAS configuration” to complete the SASconfiguration steps that must be performed outside the Configuration Tool.

Completing SAS configurationComplete these procedures outside the Configuration Tool to finalize SAS configuration.

About this task

After configuring the SAS historical reporting for this product, you must perform the followingprocedures outside of the Configuration Tool to finalize configuration.

Procedure1. Copy SAS procedure to PROCLIB.

The Configuration Tool created a SAS JCL procedure in RKANSAMU that you must copy to yourprocedure library. You specified the name of the procedure when you defined SAS configurationvalues. This copy is required. Copy the SAS proc (KONSAS) from RKANSAMU to PROCLIB.

2. Complete and verify the basic SAS customization.You must perform these steps to complete the customization and verification of the basic historicalreporting features. Each step is described in more detail in the OMEGAMON II for MainframeNetworks: Historical Reporting Guide:a. Ensure that SMF recording is enabled.b. Grant security access to historical reporting data sets.c. Verify operation of the daily, weekly, and monthly database-creation jobstreams.

3. Complete and verify SAS/GRAPH customization.If you will use SAS/GRAPH to create online historical reports, you must perform the following stepsto complete and verify the SAS/GRAPH features. Each step is described in more detail in theOMEGAMON II for Mainframe Networks: Historical Reporting Guide:


a. Assemble and link edit a VTAM mode tab containing queriable logmode entries (if you do notalready have one). You must use a graphics-capable workstation to view OMEGAMON II forMainframe Networks SAS/GRAPH reports. The workstation must also be assigned a queriablelogmode entry. The Configuration Tool builds a jobstream that assembles and links a sample modetab containing queriable logmode entries into your VTAMLIB dataset. The job stream is containedin RKANSAMU. The member name is the mode tab name you specified during SAS configuration(the default name is KONINCLM). You can use this job stream to create queriable logmode entriesif you do not already have them.

b. Verify operation of the daily, weekly, and monthly graphics job streams.c. Verify the operation of the SAS CLIST used to display the SAS/GRAPH reports.d. Create a SAS/GRAPH color map for printing color graphs in colors supported by your printer, if

required for your site.e. Verify the OMEGAMON II for Mainframe Networks historical graphs interface. For more

information, see the OMEGAMON II for Mainframe Networks: Historical Reporting Guide.

Changing the parameters after you exit the Configuration ToolFollow these steps to change parameters set by the Configuration Tool after you exit the tool.

About this task

After you complete configuration, if you need to change configuration parameters, complete thefollowing steps:

Procedure1. Reinvoke the Configuration Tool.2. Use the Specify Configuration Values selection on the Configure OMEGAMON II for Mainframe

Networks panel to specify the new values.3. Be sure to select Create Runtime Members on the Configure OMEGAMON II for Mainframe

Networks panel and submit the generated JCL.4. Review the Complete the Configuration selection on the Configure OMEGAMON II for Mainframe

Networks panel. There may be some processing to perform outside of the Configuration Tool. Forexample:v If you change the OMEGAMON II proc name, recopy the proc from &rhilev.&midlev.

&rtename.RKANSAMU to PROCLIB. For this step, KPDPROCC goes to &rhilev.&midlev.&rtename.RKANSAM, but KPDPROC1 goes to &rhilev.&midlev.&rtename.RKANSAMU.

v If you change the OMEGAMON II major node definition, recopy it to VTAMLST.

Next stepsWhen you have successfully completed the configuration steps described in this section, you mustconfigure the components that you plan to use.

Go to Appendix B, “Customizing the OMEGAMON II components and verifying installation,” on page185.



Appendix B. Customizing the OMEGAMON II components andverifying installation

Be aware of these components that must be customized after you complete configuration ofOMEGAMON II.

This section contains information about the components and modes of operation for OMEGAMON II forMainframe Networks. The section provides information about the following tasks:v “Customizing NCP”v “Customizing ETE” on page 189v “Configuring security” on page 190v “Running in dedicated mode” on page 194v “SMF record considerations” on page 195v “Verifying the configuration” on page 196

Customizing NCPBe aware of these issues as you provide the definitions necessary for OMEGAMON II to monitor NCPdata.

This section provides the definitions required in the Network Control Program generation for any NCPthat you want to monitor with OMEGAMON II. You must regenerate and reload the NCP before youenable NCP data collection as described in “Enabling NCP data collection” on page 188.

Be aware of the operating requirements shown in Table 43.

Table 43. Operating requirements for NCP

Characteristic Requirement

NCP monitor component The following are required to collect NCP statistics:

v An OMEGAMON II configured for NCP collection

v A Network Control Program generation, including required NPALU and keyworddefinitions

NPALU usageBecause the OMEGAMON II NCP performance component uses the NPALU, it cannotcoexist with the NCP functions of NetSpy or NetView Performance Monitor which alsouse the NPALU.

The NPALU can be in session with only one application at a time.

NCP dynamic configurationThere is no need for you to define your NCP resources to OMEGAMON II or theNCP collector. OMEGAMON II constructs a list of your active NCPs and theirsubordinate resources dynamically during startup or at NCP activation.

NCP data collection See this section for information about these data collection topics:

v “Specifying required NCP generation parameters” on page 186

v “Displaying performance statistics using X.25 NCP generation” on page 186

v “Using the NPALU definition to connect to the NCP collector” on page 187

v “Enabling NCP data collection” on page 188

v “Disabling NCP data collection” on page 188


Specifying required NCP generation parametersUse this topic to understand the NCP generation parameters required to collect performance data for anNCP resource.

About this task

To collect performance data for any NCP resource, the following NCP generation parameters arerequired:

Procedure

Provide values for the NCP generation parameters:

NPACOLL=YESCode on group, line, PU, and LU macros.

Provides performance statistics data to OMEGAMON II.

NPATP=YESCode on SDLC group, line, and PU macros.

Provides transmission priority data to OMEGAMON II.

SPEEDCode on SDLC, BSC, CA LINE and X.25 MCH LINK macros

OMEGAMON II uses the SPEED parameter to calculate line utilization. For SDLC or BSC linesusing external clocking, be sure that your SPEED parameter value equals the speed of themodem, otherwise your utilization statistics will be invalid.

DUPLEXCode on SDLC and BSC LINE macros.

OMEGAMON II uses the DUPLEX parameter when calculating utilization statistics.

TRSPEEDCode on token-ring physical LINE macros.

OMEGAMON II uses the TRSPEED parameter when calculating utilization statistics.

For more information about these parameters, see the IBM z/OS Communications Server: Resource DefinitionSamples book.Performance-related NCP generation parameters are displayed on the resource summary panels so thatyou do not have to refer back to the gen. The value of a parameter displays as N/A if you did not code itin your gen.You can gen a parameter, such as PASSLIM, at a higher level than the PU macro (on the GROUP or LINEmacro), and have it sift down to the PU macro. Any keyword that is valid at more than one level in theNCP gen, can descend from greater to lesser levels.

Important: For OMEGAMON II performance reasons, explicitly specify the NPACOLL parameter for allresources, whether you want to collect data for them, by coding NPACOLL=YES or NPACOLL=NO. As withother keywords, NPACOLL sifts down from higher to lower levels.

Displaying performance statistics using X.25 NCP generationFollow these configuration steps to display performance statistics for X.25 resources.

About this task

In addition to the SPEED keyword on the MCH LINK macro, to display performance statistics for X.25resources, you must include the following code statements in your NCP generation:


Procedure1. On the BUILD statement, code the following statement:

NPA=YES

2. On the OPTIONS statement, code the following statement:NEWDEFN=(YES,ECHO,NOSUPP,REUSE)

3. On the X25.MCH statement, code the following statement:NPACOLL=(MCHLINK,MCHPU,VCPU)

4. On the X25.MCH statement, also code the following statement:NPPVCN=(n)

Where n is the maximum number of virtual circuits for which data is collected at the same time.For more information about these keywords, see the IBM X.25 Network Control Program PacketSwitching Interface: Planning and Installation book (SC30-3470).

Using the NPALU definition to connect to the NCP collectorUse this information to code the correct NPALU definition in OMEGAMON II for connecting to the NCPcollector.

About this task

This section shows the NPALU definition required for connection to the NCP collector. This definition isprovided in the &rhilvev.&midlev.&rtename.RKANSAMU library member KONCTNPA. The ConfigurationTool concatenates the OMEGAMON II terminal pool prefix specified during configuration with thecharacters NCP and uses that for the LOGAPPL value in KONCTNPA. The default value is KONNCP.

The NPALU definition is listed here for your information. It is required to activate the NPALU to NCPcollector applid connection.

Procedure

Code the following keywords on the NPALU LU macro:

MAXCOLLSpecifies the number of resources for which you can collect data. Add at least 10% for growth.This parameter defaults to number of lines plus number of PUs.

LOGAPPLControls automatic activation of the NPALU to the NCP collector.

Example

The screen that follows shows the sample NPALU macro definitions that automatically generate a sessionwith the NCP collector task at NCP activation.

Appendix B. Customizing the OMEGAMON II components and verifying installation 187

Enabling NCP data collectionIf the NCP collector does not connection to the NCP automatically at NCP activation, use these stepswith a previously defined NPALU.

About this task

When the required NCP definitions are generated, the NCP collector automatically connects to the NCP atNCP activation.

If the NPALU was previously defined, you can do the following:1. Ensure that the NPALU is not in session with anything else.2.

Procedure1. Ensure that the NPALU is not in session with anything else.2. Issue this command:

VARY NET,ACTIVE,ID=npalu_name,LOGON=konNCP

Where konNCP is the logon applid for the NPALU. For information about disabling NCP datacollection, see “Disabling NCP data collection.”

Disabling NCP data collectionUse this information to reconfigure OMEGAMON II to disable NCP data collection.

About this task

If you do not want OMEGAMON II to collect NCP statistics, use the Configuration Tool to reconfigureOMEGAMON II without NCP data collection. Do the following:

******************************************************************************

** NCP NPALU Definitions for Automatic Connection to **

** NCP collector task for NCP Activation **

******************************************************************************

NPGARP00 GROUP NPARSC=YES X

VIRTUAL=YES, XLNCTL=SDLC

*

NPALNE00 LINE

*

NPAPU00 PU

*

NPALU00 LU LOGAPPL=konNCP

*

Figure 48. NCP NPALU Definitions panel. NCP NPALU Definitions panel


Procedure1. If no other OMEGAMON II components are using the NCP collector, reconfigure OMEGAMON II

without the collector.2. If another OMEGAMON II component is using the NCP collector, reconfigure that OMEGAMON II to

include the collector.3. Use the Configuration Tool to reconfigure OMEGAMON II. The Configuration Tool removes the

OMEGAMON II startup commands that install and start the NCP Data Manager Task (NDMT) bymaking the following revisions to the KONSTKON member in the &rhilev.&midlev.&rtename.RKANCMDU library:a. Comment out the entire KONFCCMD INSTALL NDMT statement, which spans several lines.b. Comment out the KONFCCMD START NDMT statement.

Customizing ETEIf you have not installed ETE, use this topic to understand the flow of tasks to customize ETE.

If you already have ETE V620 installed and enabled, you can skip this section.

ETE operates under the following rules:v For OMEGAMON II to use the End-to-End facility, the IBM Tivoli OMEGAMON XE and Tivoli

Management Services: End-to-End Response Time Feature Reference must be started beforeOMEGAMON II.

v ETE V620 was designed as a common component that can be shared by multiple OMEGAMONproducts. OMEGAMON monitoring agents that use End-to-End include it as part of the productpackage.

v If ETE V620 is already installed in your system, it can be used by OMEGAMON II.v When the variable $$ETE in the NAM database is set to Y, which is the shipped default, OMEGAMON

II starts up expecting ETE to be started and tries to connect to it. If OMEGAMON II cannot connect toETE, it issues a message but continues to run.

v If you change the setting of the NAM variable $$ETE, you must restart OMEGAMON II to recognizethe new setting.

For more information about ETE, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services:End-to-End Response Time Feature Reference, Version 620

Enabling ETEUse this information to enable OMEGAMON II to use ETE.

About this task

Although the OMEGAMON II shipped default is ETE enabled, you may have previously disabled ETE.To re-enable OMEGAMON II to use ETE:

Procedure1. Start OMEGAMON II by issuing this command:

S CANSON

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool. The default is CANSON.

2. Enable ETE by issuing this command at the z/OS console:F CANSON,NAM SET OMVTAM $$ETE:Y

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool. You should see this message:


KLVOP905 $$ETE:Y FOR USERID OMVTAM

3. Stop OMEGAMON II by issuing this command:P CANSON

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool.

4. Ensure that ETE is started. You can start ETE with the console command:S CANSETE

Where CANSETE is the started task name you specified for ETE using the Configuration Tool.5. Restart OMEGAMON II by issuing this command:

S CANSON

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool. This causes OMEGAMON II to be started and to connect to ETE.

Disabling ETEUse this information to stop OMEGAMON II for running ETE.

About this task

Although OMEGAMON II can run with or without ETE, you may want to disable ETE.

Procedure

You can enter the following command from the z/OS console while OMEGAMON II is running:F CANSON,NAM SET OMVTAM $$ETE:N

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool. After you issue this command, the next time and all subsequent times thatOMEGAMON II starts, it will no longer try to connect to ETE, until you re-enable it.

Configuring securityUse this section to understand the additional tasks outside the Configuration Tool required to enable theOMEGAMON II network access manager (NAM) to work as a stand-alone security system or interfacewith another security system.

The network access manager (NAM) can serve either as a standalone security system or as an interface tothe security system of your choice.

Member &rhilev.&midlev.&rtename.RKANPARU(KONINNAM) contains security system information.KONINNAM defines one or more control points, each of which selects a security system and names aVSAM file (the NAM database) to store user profile information. When NAM is the chosen securitysystem, the VSAM file (the NAM database) also holds encrypted security information. By default,OMEGAMON II uses only one control point so that all users access OMEGAMON II through the samesecurity system.

Using the Configuration Tool panels, you began the process of defining OMEGAMON II security. Thissection describes the remaining steps you must perform to define security to NAM and to other SAFsecurity systems.

Using the NAM facility for securityUser this information to add users to the NAM database.


About this task

If you are using the NAM facility for security, you do not need to change member &rhilev.&midlev.&rtename.RKANPARU(KONINNAM) because KONINNAM automatically selects NAM. However, youmust define your users to NAM.

To add more user IDs to the NAM database, do the following:

Procedure1. Start OMEGAMON II if you have not already done so.

S CANSON


2. Issue the z/OS MODIFY command from the z/OS console. For example:F CANSON,NAM SET userid1 PASSWORD=password1F CANSON,NAM SET userid2 PASSWORD=password2


3. Verify that the users can log onto OMEGAMON II.

Displaying user IDsUse this information to display all user IDs defined to the NAM data set.

About this task

Do the following to display all user IDs that are defined to the NAM data set:

Procedure

Issue the following operator command:F CANSON,NAM LIST


Assigning user authoritiesUse this information to assigner user authorities to NAM users.

About this task

Whatever security system you use for OMEGAMON II entry validation, each user ID is assigned userauthorities by an authorized administrator through the User Authorities choice on the Options menu. Seethe chapter on user authorities in the OMEGAMON II for Mainframe Networks User's Guide for moreinformation.

As a default, the first user to log onto OMEGAMON II has administrator authority. To assign userauthorities, a product administrator follows these steps:

Procedure1. Enter O in the action bar entry field to select the Options menu.2. Select User Authorities.3. Update user authorities, as required for your site.4. Verify that your users can access the OMEGAMON II components they require.


As an alternative to internal OMEGAMON II for Mainframe Networks security, you can use yourexternal security package to authorize users to specific functions. See “Implementing externalfunction-level security.”

Using RACFUse this information to understand the changes that the Configuration Tool made to theRKANPARU(KONINNAM) member to enable communication with RACF.

The Configuration Tool process made the necessary changes to &rhilev.&midlev.&rtename.RKANPARU(KONINNAM), so that it now looks something like this:DEFAULT DSNAME(rhilev.RKONNAM) -RACF -NODB

If you want to change this member, restart OMEGAMON II to recognize the changes.

Implementing external function-level securityYour system administrator can restrict access to OMEGAMON II by defining resources rules to yourexternal security manager. Use this information to understand how to implement external function-levelsecurity.

This section describes how to implement external function-level security. Using this feature, your securityadministrator can restrict user access to OMEGAMON II for Mainframe Networks functions by definingresource rules to your external security manager. You can use this feature instead of OMEGAMON IIinternal security, which is set under the User Authorities selection of the Options menu.

Functions secured

External function level security uses your external security manager to restrict user access to any of theseOMEGAMON II functions:v OMEGAMON II accessv Administrator authorityv VTAM tracev Response timev VTAM console

Requirements

Before implementing external function level security, you must do the following:1. Enable sign-on security through your external security manager. See the previous sections of this

section describing how to set up external security using RACF or another SAF product.2. Provide a function level security resource class name when defining OMEGAMON II configuration

values to the Configuration Tool.3. Define the resource class name to your external security package.

External security resource names

The following external resource names are used to secure the five OMEGAMON II functions listed:

OMEGAMON II accessCTDONAP.KON.ACCESS

administrator authorityCTDONAP.KON.ADMIN


VTAM trace accessCTDONAP.KON.TRACE

response time accessCTDONAP.KON.RESPONSE

VTAM console accessCTDONAP.KON.CONSOLE

where CTDONAP is the logon applid you specified for OMEGAMON II for Mainframe Networks usingthe Configuration Tool.

Defining RACF resourcesUse this information to define RACF resources.

About this task

An OMEGAMON II for Mainframe Networks resource class name can be added to RACF ClassDescriptor Table (CDT). The following example shows the attributes you can use.

Procedure1. Use this example to understand the attributes you should add an OMEGAMON II resource class

name to the RACF Class Descriptor Table (CDT).XXXXXXXX ICHERCDE CLASS=xxxxxxxx,

ID=nnn,MAXLEN=24,FIRST=ALPHANUM,OTHER=ANY,POSIT=xxxx,DFTUACC=none

Follow these guidelines when you add the resource class name to the CDT.v If you code RACLIST=ALLOWED, use the ICHRFRTB macro to create a router table entry for the

class. (The ICHERCDE macro sets RACLIST=DISALLOWED as a default.)v A POSIT value must be chosen that does not conflict with any existing class.v If you define a new resource class in the RACF CDT, you must IPL your system specifying CLPA to

rebuild the PLPA.You can use the following commands.v To activate your new resource class, use the SETROPTS command.v To define the resources, use the RACF RDEF commands.v To authorize user access to the resources you defined, use the RACF PERMIT commands.A completion code 4 may result from the assembly of the CDT because of the non-standard CLASSvalue.Contact your RACF administrator if you need assistance. Also see the z/OS Security Server Macros andInterfaces manual.

2. When this feature is implemented and you select User Authorities from the OMEGAMON II Optionsmenu, the following message appears:User Authorities - External Security Active

In this system, user authorities are maintained using an external security package.Please contact the system administrator.

3. When a user selects an unauthorized function, the message displayed is the same, whether security isexternal or internal to OMEGAMON II.


Example

This is an example of using RACF to authorize only one user to the VTAM trace function.RDEFINE classname CTDONAP.KON.TRACE UACC(NONE)PERMIT CTDONAP.KON.TRACE CLASS(classname) ID(user1) ACCESS(READ)

Where:

CTDONAPIs the logon applid you specified for OMEGAMON II for Mainframe Networks using theConfiguration Tool.

classnameIs the resource class name for the OMEGAMON II trace facility.

user1 Is the user ID of the authorized user.

Running in dedicated modeIn addition to a logon through VTAM, OMEGAMON II also supports the dedicated mode of operation asan option.

This mode provides direct access to OMEGAMON II through a local VTAM terminal.

Dedicated mode is useful when normal online response time becomes poor due to problems withinVTAM. In this case, you can use a dedicated mode terminal to bypass VTAM during logon. To usededicated mode, you must have a terminal online to z/OS and not currently used by VTAM or any othersubsystem.

Activating a dedicated terminalUse one of the two approaches described in this information to activate a terminal dedicated toOMEGAMON II.

About this task

To activate a terminal dedicated to OMEGAMON II, you can take one of the following two approaches:defining the dedicated terminal at startup or allocating the dedicated terminal dynamically.

Procedure

Take one of the following two approaches.v Defining the dedicated terminal at startup

1. Insert the following line in member &rhilev.&midlev.&rtename.RKANCMDU(KONSTKON), whererhilev means RTE high-level qualifier, before the DIALOG statement:DEDICATE UNIT-xxx KONDSTRT

where xxx is the terminal's z/OS address.2. Stop OMEGAMON II.3. Restart OMEGAMON II. OMEGAMON II should begin dedicated mode operation.

v Allocating the dedicated terminal dynamically1. With OMEGAMON II running, issue the following z/OS command:

F CANSON,DEDICATE UNIT-xxx KONDSTRT

Where xxx is the terminal z/OS address and CANSON is the OMEGAMON II started task namespecified during OMEGAMON II configuration. The following message should appear on theterminal (at address xxx):


Press ENTER to start dedicated session

2. Press Enter. OMEGAMON II should begin dedicated mode operation.

Deactivating a dedicated terminalUse this information to deactivate a terminal dedicated to OMEGAMON II.

About this task

To close and free a previously dedicated terminal, do the following.

Procedure

Issue the following z/OS command:F CANSON,CLOSE UNIT-xxx

Where CANSON is the OMEGAMON II for Mainframe Networks started task procedure name and xxx isthe terminal z/OS address.

Setting the polling intervalUse this information to set the polling interval for OMEGAMON II, the time between two reads from thescreen.

About this task

The polling interval is the time between two reads from the screen. By default, this value is 1 second.You can change this value by issuing a DEDICATE command and changing the INTERVAL parameter:

Procedure

Issue a DEDICATE command and change the INTERVAL parameter:DEDICATE UNIT-xxx KONDSTRT INTERVAL(3)

Where xxx is the terminal z/OS addressIn the previous example, polling is changed to 3 seconds. Set the polling parameter to a value that doesnot exceed 5 seconds. Otherwise, delays in accepting user input may occur.

SMF record considerationsUse this information to understand how OMEGAMON II uses SMF exception and trend records.

For the OMEGAMON II components where SMF recording is enabled, OMEGAMON II creates SMFexception and trend records.

There has been no change in SMF record format between V5.2.0 and the current release. Record formatchanged from earlier versions to V5.2.0.

Check the custom-tailored programs at your site that process OMEGAMON II for Mainframe NetworksSMF exception records. They may require revisions to recognize the expanded exception record format.

You can find OMEGAMON II SMF record layouts and learn more about using SMF for historicalreporting in the OMEGAMON II for Mainframe Networks Historical Reporting Guide .

Enabling SMF recordingUse this information to enable SMF recording if you use SAS-based historical reporting.


About this task

You can produce historical reports using the SMF data generated by OMEGAMON II.

You must enable SMF and use it to collect some data before you can accomplish either of the following:v Verify operation of the SAS-based historical component.v Generate historical reports using SAS.

To set SMF recording options, follow these steps:

Procedure1. Select the Options menu from the action bar.2. Select Monitoring Options.3. From the Monitoring Options menu, select a performance category such as Buffer Pools, Virtual

Routes, or NCP Performance.4. Select Monitor Options.5. Enter S (SMF) or B (Both) in the Exception and Trend Recording fields to enable SMF recording.

See the chapter on monitoring options in the OMEGAMON II for Mainframe Networks User's Guide foradditional information on setting monitoring options.

Verifying the configurationUse the topics in this section to verify configuration of OMEGAMON II.

Follow the procedures in the sections that follow to verify that the OMEGAMON II component has beeninstalled and correctly configured.

Starting End-to-End V620Use this information to started ETE.

About this task

If you currently have an ETE subsystem running, for OMEGAMON II for Mainframe Networks to usethe End-to-End facility, do the following:

Procedure1. To bring up ETE V620, you must first quiesce both the current ETE subsystem and address space

completely by issuing this console command:ETE QUIESCE

You see these responses:ETE0086: ETE ADDRESS SPACE TERMINATED BY SUBSYSTEM QUIESCEETE0051: QUIESCE COMPLETEETE0003: COMPLETE

2. Start ETE V620 by issuing this console command:S CANSETE

where CANSETE is the started task name you specified using the Configuration Tool.You see this response:ETE0091 ETE VERSION 620 SUCCESSFULLY INITIALIZED


Running multiple copies of ETEYou might want to run multiple copies of ETE during test or migration. In that case, commands have tobe directed to a particular instance of ETE.

About this task

Under normal conditions, running multiple OMEGAMONs requires only one copy of ETE.

During test, product migration, or under special circumstances, you may need to start several copies ofETE V620, or V620 and prior releases. You can run:v Multiple copies of ETE V6.2.0v Multiple copies of a prior ETE releasev ETE V6.2.0 and a prior ETE release

When using multiple copies, to identify and run a specific copy of ETE prior to V6.2.0, you must:v Include this DD statement in each ETE JCL stream:

//RKETVTnn DD DUMMY

where nn is a unique numeric suffix between 00 and 15, identifying the subsystem.v Run a maximum of four ETE address spaces concurrently in a single domain.

Important: To identify the ETE subsystem to the OMEGAMON using it, be sure to also include thematching RKETVTnn DD DUMMY statement, as described previously in the OMEGAMON JCL stream.

If you are running multiple copies of ETE, be sure to direct ETE commands to the proper ETE.

Procedure

To direct ETE commands to the proper ETE when more than one ETE system is running, include theversion number.ETE nnn: CANSETE

Where:

nnn Three-digit ETE version number or two-digit subsystem identifier.

CANSETEThe ETE command name.

Example

To QUIESCE ETE V620, issue this command:ETE620 QUIESCE

Related reference:“Running conceurrent ETE instances with the IBM NetView Performance Monitor product”Understand these issues before you run multiples instances of ETE with NetView Performance Monitor.

Running conceurrent ETE instances with the IBM NetView Performance Monitor product:

Understand these issues before you run multiples instances of ETE with NetView Performance Monitor.

Be aware of the following special operational guidelines when running concurrent ETEs and the IBMNetwork Performance Monitor product.v ETE can coexist with NetView Performance Monitor. When NetView Performance Monitor starts, any

existing interface participants are ignored. NetView Performance Monitor is installed as the only


front-end interface to VTAM, which disables ETE operation. ETE detects this condition and reinstallsitself in conjunction with NetView Performance Monitor.

v When NetView Performance Monitor terminates, it removes itself as an interface participant but doesnot ensure the integrity of other interface participants. ETE also detects this condition and recoversfrom it.

v If NetView Performance Monitor starts or stops when more than one ETE system is running, only oneETE recovers. The ETE that recovers depends on various factors at the time the event occurs. The ETEthat does not recover does not affect the system, but does not report response time information.

Note: Do not run multiple copies of ETE with NetView Performance Monitor in your productionenvironment because of the limitations stated previously.

Activating the OMEGAMON II major nodeUse this information to activate the VTAM major node for OMEGAMON II.

About this task

The OMEGAMON II VTAM major node must be active.

Procedure

To activate the OMEGAMON II major node, issues the following z/OS command:VARY NET,ACT,ID=major_node

Where major_node is the major node name you specified for OMEGAMON II using the ConfigurationTool. The default major node is CTDONN.

Starting OMEGAMON IIUse this information to start the OMEGAMON II you just configured and customized.

Procedure

To start the OMEGAMON II you just configured, enter this command:S CANSON

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool. Depending on the components you chose during configuration, you willsee startup confirmation messages similar to the following (but not necessarily in this order):KONPN001 OMEGAMON II for MAINFRAME NETWORKS INITIALIZATION COMPLETEDKONPN005 ETE CONNECTED SUCCESSFULLYKONPN002 ACT STARTED SUCCESSFULLYKONFC010 FPON COMPONENT FUNCTIONS INSTALLATION COMPLETEKONFC015 FPCT COMPONENT FUNCTIONS INSTALLATION COMPLETEKONFC025 SEMV MVS ENVIRONMENT INSTALLATION COMPLETEKONFC020 SEVT VTAM ENVIRONMENT INSTALLATION COMPLETEKONFC050 NDMT NCP DATA MANAGER INSTALLATION COMPLETEKONND100 NCP DATA MANAGER TASK AVAILABLE FOR REQUESTSKONCT100 TCP/IP SERVICE THREAD INITIALIZATION COMPLETEKONCT100 MIB BROWSER SERVICES THREAD INITIALIZATION COMPLETEKONCT100 XMCS SERVICES THREAD INITIALIZATION COMPLETEKONCT000 TCP/IP STATISTICS COLLECTOR INITIALIZATION COMPLETEKONFC095 TCPC COLLECTOR STATUS IS ACTIVE

If you chose not to start ETE, OMEGAMON II continues to run without ETE although this messageappears:KONPN004 ETE CONNECTION FAILED


If you chose not to start the NCP collector, OMEGAMON II continues to run, although the followingmessage appears. This message appears until you use the NCP Performance Options under the Optionsmenu to turn off NCP monitoring.KONAF121 NDM STARTUP FAILED RC(return_code) SC(sense_code)

WILL RETRY EACH ACT CYCLE INTERVAL

This message is displayed only if you select NCP data collection during configuration with theConfiguration Tool and no NCP is active when OMEGAMON II for Mainframe Networks is started.

Initializing the NAM databaseUse this information to initialize the NAM database if you did not migrate the NAM file from a priorrelease.

About this task

Note: If you migrated the NAM file from a prior release to the current release, skip this step.

If you are a new OMEGAMON II user or have not migrated your NAM database, you must declare theOMEGAMON II TMS: Engine variables to the NAM database.

Procedure

Enter this command from the z/OS console:F CANSON,KONNAM

Where CANSON is the started task name you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool.You should see one or more messages in the following formatKLVOP909 variable DECLARED: LENGTH(length)

Defining the NAM user ID and passwordIf you are using NAM security, define user access to OMEGAMON II by defining a NAM user ID andpassword.

About this task

Note:

1. If you are not using NAM security, skip this step.2. If you migrated the NAM file from a prior release, skip this step.

To provide user access to OMEGAMON II, define a user ID and password to NAM.

Procedure

Issue this z/OS MODIFY command to define yourself as a user:F CANSON,NAM SET userid PASSWORD=password

Where userid is your logon ID, password is a temporary password, and CANSON is the started taskname specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool.You should see this response:KLVOP910 ACCESS CREATED FOR USERID userid

Logging onto OMEGAMON IIFollow this procedure to log on to OMEGAMON II.


About this task

Log onto the OMEGAMON II component as follows:

Procedure1. Enter the following VTAM command:

LOGON APPLID(CTDONAP)

Where CTDONAP is the logon applid you specified for OMEGAMON II for Mainframe Networksusing the Configuration Tool. The logon panel appears.

2. Enter your name and password. If you use NAM, you are prompted to enter a new password. Thefirst panel you see is the OMEGAMON II for Mainframe Networks Status Display with status lightsfor the various VTAM and NCP components. By default, as the first user, you become the productadministrator.

3. To define other users to OMEGAMON II, do the following:a. Select the Options menu from the action bar.b. Select User Authorities.c. Specify other users and their authorities. See the chapter on user authorities in the OMEGAMON II

for Mainframe Networks User's Guide.

As an alternative you can use your external security package to authorize users to functions. See“Implementing external function-level security” on page 192.

4. To specify monitoring options for yourself and other users:a. Select the Options menu from the action bar.b. Select Monitoring Options.c. Specify options, thresholds, and severities through subsequent menus and panels. See the chapter

on monitoring options in the OMEGAMON II for Mainframe Networks User's Guide.5. Navigate through various OMEGAMON II status, statistics, exception, and trend panels.

Enabling TCP/IP data collectionIf you want to use OMEGAMON II to monitor TCP/IP data, you must enable TCP/IP data collection.

About this task

To enable TCP/IP data collection, you must provide a community name and verify communications

OMEGAMON II uses the community-based security of SNMPv2c, where the community name(password) is passed with each request to the SNMP agent. You must provide a community name toauthorize obtaining data from the SNMP agent. To specify and verify a community name, perform thefollowing steps:

Procedure1. Select the Options menu on any OMEGAMON II panel.2. Select Monitoring Options.3. Select TCP/IP Options.4. Select TCP/IP Address Space Options. If you do not provide a community name, public is used as

the default.

Note: OMEGAMON II does not support the experimental user-based security of SNMPv2u.5. To verify the communications between your SNMP agent and the subagent, issue the following

OSNMP command:osnmp -c community_name -v getbulk ibmMvsTcpConnLastActivity


Note: Specify the -c community_name parameter in the previous command because if you are notusing the default community name of public, the command will time out. If you are running multiplestacks, you may wish to use the -h host_name parameter to verify that there is connectivity betweenthe SNMP subagents for each stack.This command verifies whether the SNMP agent and subagent are active and properly configured.The response from the command should be valid data, without a time-out or error condition, such as:ibmMvsTcpConnLastActivity.0.0.0.0.21.0.0.0.0.0 = 15496483

Enabling OMEGAMON II console supportTo enable OMEGAMON II console support, perform these steps online:

Procedure1. Press F10 to move the cursor to the OMEGAMON II display panel, the action bar entry field.2. Select the Options menu by entering O in the action bar entry field.3. Select Monitoring Options by entering an M on the Options menu.4. Select Global Options by entering O on the Monitoring Options menu.5. On the Global Options panel, move the cursor to the last field, OMEGAMON Console APPLID

Prefix.6. For console support, you must enter the same value that was specified for Terminal Pool Prefix in the

Configuration Tool process. This is the name of the 1 to 5 byte OMEGAMON II terminal pool prefixused when accessing the OMEGAMON II VTAM console. A pool of applids is created, where all theapplid names start with the same 5-byte prefix.

7. Press F12 until you return to the main status panel.8. Press F6 to access the VTAM console panel.9. Verify that the VTAM console feature works properly by entering the following:

D NET,APPLS

If console support is enabled, you should see a message similar to this:IST097I DISPLAY ACCEPTEDIST350I DISPLAY TYPE = APPL MAJ NODES/NAMESIST314I END

Setting thresholds and exceptionsFollow this procedure to set thresholds and exception values for OMEGAMON II in your environment.

About this task

The first user to log onto OMEGAMON II has administrator authority. An administrator uses the Optionsmenu to set thresholds and exception values in OMEGAMON II for your site. To set monitoring options,perform the following steps:

Procedure1. Select the OMEGAMON II Options menu by entering O in the action bar entry field.2. Select Monitoring Options by entering M on the Options menu.3. Select the options that you want to modify from the Monitoring Options panel. For details on each

monitoring option, see the chapter on monitoring options in the OMEGAMON II for MainframeNetworks User's Guide.

4. Return to the main status panel. The status lights on the main status panel reflect VTAM and NCPstatus based on the settings you specify for the following:v Resources to monitorv Exception conditions to monitor


v Threshold valuesv Exception severities


Appendix C. KN3FCCMD and KONFCCMD command reference

KN3FCCMD (for OMEGAMON XE) and KONFCCMD (for OMEGAMON II) commands enable ordisable data collection by component, providing more granular control over which types of data arecollected.

This section is a reference for the KN3FCCMD z/OS MODIFY commands that are supported by theOMEGAMON XE for Mainframe Networks monitoring agent and the KONFCCMD z/OS MODIFYcommands that are supported by the OMEGAMON II component. Most of this chapter provides anexplanation of the KN3FCCMD commands. For more information about the KONFCCMD commands forthe OMEGAMON II component, see “Using the KONFCCMD command” on page 253.

Introduction to the KN3FCCMD commandsThe z/OS MODIFY KN3FCCMD commands enable or disable data collection by component, providingmore granular control over which types of data are collected. These components are supported. Thecommands use this syntax.

The OMEGAMON XE for Mainframe Networks monitoring agent is made up of components that map todata types. By default, each of the components is enabled. The default collection interval is 5 minutes.

You can enable or disable data collection by component, providing more granular control over whichtypes of data are collected. These actions can be specified at the time you configure the OMEGAMON XEfor Mainframe Networks monitoring agent (the preferred method) or through the z/OS MODIFYcommand. The z/OS MODIFY command is issued when the OMEGAMON XE for Mainframe Networksmonitoring agent is running. Then you can use the z/OS MODIFY command to initialize, start, stop, anddisplay the status of components.

This section shows you how to use the z/OS MODIFY command with the following components:v CONN for TCP/IP Connection and Application performance data. You can enable or disable collection

of TCP/IP Connection and Application performance statistics by starting or stopping the CONNcomponent. The default is to start this component.

v CSM for Communications Storage Manager data. You can enable or disable the CommunicationsStorage Manager buffer reporting by starting or stopping the CSM component. The default is to startthis component.

v EEHPR for Enterprise Extender and High Performance Routing data. You can enable or disablecollection of Enterprise Extender and High Performance Routing statistics by starting or stopping theEEHPR component. The default is to start this component.

v FTP for FTP session and transfer data. You can enable or disable collection of FTP session and transferdata by starting or stopping the FTP component. Additionally, you can modify the display interval forFTP data. The default is to start this component.

v GLBS for TCP/IP Stack Layer statistics data collection. You can enable or disable collection of TCP/IPStack layer statistics by starting or stopping the GLBS component. The default is to start thiscomponent.

v INTS for Interface Statistics data collection. You can enable or disable collection of interface statisticsby starting or stopping the INTS component. The default is to start this component.

v INTE for interface Data Link Control (DLC) data collection. You can enable or disable collection ofinterface DLC statistics by starting or stopping the INTE component. The default is to start thiscomponent.

v IPSec for IPSec security extensions to the Internet Protocol. You can start or stop collection of IPSecdata. The default is not to start this component.


v OSA for OSA devices. You can stop and start OSA-enabled data collection. The default is to start thiscomponent.

v ROUTE for gateways. You can enable or disable the collection of routing information (for example, thegateway table). The default is to start this component. Additionally, the Routing Table CollectionFrequency allows you to collect data less frequently for this table.

v TN3270 for TN3270 server session data. You can enable or disable collection of TN3270 server sessiondata by starting or stopping the TN3270 component. Additionally, you can modify the display intervalfor TN3270 server session data. The default is to start this component.

On a more global level, you can start or stop collection of TCP/IP data by starting and stopping theTCPC task. Starting TCPC will initiate data collection for ALL enabled components. Stopping the TCPCtask will disable ALL data.

For a more complete view of these data types and the workspaces associated with them, see IBM TivoliOMEGAMON XE for Mainframe Networks: User's Guide.

The general syntax for KN3FCCMD commands issued as a z/OS MODIFY command is:

�� MODIFY proc_name , KN3FCCMD <command><component>

<options>

��

Where:

proc_nameIs the name of the started procedure for your monitoring agent.

componentIs the component in the monitoring agent to take action on.

commandIs the action to be taken. STATUS, HELP, INSTALL, START and STOP are supported commands.

optionsAre one or more arguments that provide further information about the action to be taken againstthe component.

Command responses are written to the RKLVLOG but are buffered in memory and might not be writtenimmediately. To immediately view the command responses, enter the following command, whereCANSN3 is the name of the OMEGAMON XE for Mainframe Networks started procedure. Thiscommand causes the buffered output to be written to RKLVLOG:F CANSN3,FLUSH

KN3FCCMD HELPThe KN3FCCMD HELP command displays the actions and options provided on the KN3FCCMDcommands.

Format

�� MODIFY proc_name , KN3FCCMD HELP ��

Purpose

Displays the actions and options provided on the KN3FCCMD commands.


Usage

Sample output of this command follows.KLVOP191 ’KN3FCCMD HELP’KN3FC005 --------+------------------------------------------------------------+KN3FC005 COMMAND | DESCRIPTION |KN3FC005 --------+------------------------------------------------------------+KN3FC005 STATUS | DISPLAY STATUS INFORMATION ABOUT INSTALLED COMPONENTS |KN3FC005 HELP | HELP INFORMATION FOR KN3FCCMD |KN3FC005 INSTALL | INSTALL COMPONENT(S) FOR PRODUCT ENVIRONMENT |KN3FC005 START | START INSTALLED COMPONENTS |KN3FC005 STOP | STOP INSTALLED COMPONENTS |KN3FC005 SEND | SEND COMMAND MESSAGES |KN3FC005 --------+-----------------------------------+------------------------+KN3FC005 OPTION | DESCRIPTION | COMMANDS |KN3FC005 --------+-----------------------------------+------------------------+KN3FC005 CONN | NMI TCP CONN/APPL DATA COLLECTION | START,STOP |KN3FC005 OSA | OSA SNMP DATA COLLECTION | START,STOP |KN3FC005 INTS | INTS SNMP DATA COLLECTION | START,STOP |KN3FC005 INTE | INTE SNMP DATA COLLECTION | START,STOP |KN3FC005 GLBS | GLBS SNMP DATA COLLECTION | START,STOP |KN3FC005 CSM | NMI CSM DATA COLLECTION | START,STOP |KN3FC005 DBUG | EXTENDED DIAGNOSTICS MODE | START,STOP,STATUS |KN3FC005 EEHPR | NMI EE/HPR DATA COLLECTION | START,STOP |KN3FC005 FPON | OMEGAMON PRODUCT FEATURES | INSTALL,STATUS |KN3FC005 FPCT | CMS DATA SERVER FEATURES | INSTALL,STATUS |KN3FC005 FTP | NMI FTP DATA COLLECTION | START,STOP |KN3FC005 IPSEC | NMI IPSEC DATA COLLECTION | START,STOP |KN3FC005 ROUTE | SNMP ROUTE DATA COLLECTION | START,STOP |KN3FC005 SEVT | VTAM ENVIRONMENT FEATURES | INSTALL,STATUS |KN3FC005 SEMV | MVS ENVIRONMENT FEATURES | INSTALL,STATUS |KN3FC005 SNAC | SNA STATISTICS COLLECTOR | START,STATUS |KN3FC005 TCPC | TCP/IP STATISTICS COLLECTOR | INSTALL,START, |KN3FC005 | | STOP,STATUS |KN3FC005 TN3270 | NMI TN3270 DATA COLLECTION | START,STOP |KN3FC005 TRACE | DIAGNOSTICS TRACE FACILITY | START,STOP,STATUS |KN3FC005 TRAP | DIAGNOSTICS TRAP FACILITY | START,STOP,STATUS |KN3FC005 --------+-----------------------------------+------------------------+KN3FC005 PARM | DESCRIPTION | OPTION |KN3FC005 --------+-----------------------------------+------------------------+KN3FC005 ALLHPR | Y=ALL HPR CONNECTIONS | EEHPR |KN3FC005 | N=HPR FLOWING OVER EE CONNECTIONS | |KN3FC005 APP | DIAGNOSTICS FOR APPLICATIONS | DBUG |KN3FC005 BASE | DIAGNOSTICS FOR BASE COLLECTOR | DBUG |KN3FC005 COMM | DIAGNOSTICS FOR COMMON FUNCTIONS | DBUG |KN3FC005 CSM | DIAGNOSTICS FOR CSM | DBUG |KN3FC005 DSPINTV | NMI DATA DISPLAY INTERVAL SUBCMD | FTP, TN3270 |KN3FC005 EEHPR | DIAGNOSTICS FOR EE AND HPR | DBUG |KN3FC005 FREQ | ROUTE COLLECTION FREQUENCY SUBCMD | ROUTE |KN3FC005 FTP | DIAGNOSTICS FOR FTP | DBUG |KN3FC005 HASH | DIAGNOSTICS FOR HASH FUNCTIONS | DBUG |KN3FC005 INIT | DIAGNOSTICS FOR INITIALIZATION | DBUG |KN3FC005 IPSEC | DIAGNOSTICS FOR IPSEC | DBUG |KN3FC005 SNA | DIAGNOSTICS FOR SNA MANAGEMENT | DBUG |KN3FC005 MAX | MAXIMUM DIAGNOSTICS LEVEL | DBUG |KN3FC005 MID | MEDIUM DIAGNOSTICS LEVEL | DBUG |KN3FC005 MIN | MINIMUM DIAGNOSTICS LEVEL | DBUG |KN3FC005 SNAC | DIAGNOSTICS FOR SNAC | DBUG |KN3FC005 SNMP | DIAGNOSTICS FOR SNMP | DBUG |KN3FC005 SYSTCP | DIAGNOSTICS FOR REAL-TIME TCP/IP | DBUG |KN3FC005 | NETWORK MONITORING NMI | DBUG |KN3FC005 SNACINTV| SNA COLLECTOR INTERVAL | SNAC |KN3FC005 TCON | DIAGNOSTICS FOR TCP CONNECTIONS | DBUG |KN3FC005 TCPC | DIAGNOSTICS FOR TCPC | DBUG |KN3FC005 TCPCINTV| TCP/IP COLLECTOR INTERVAL | TCPC |KN3FC005 TCPCTCPC| TCP/IP COLLECTOR NAME/PROFILE/COM | TCPC |

Appendix C. KN3FCCMD and KONFCCMD command reference 205

KN3FC005 TCPCVIOU| TCP/IP COLLECTOR DYNALLOC VIOUNIT | TCPC |KN3FC005 TCPNAME | TCP/IP STACK SUBCMD | TCPC |KN3FC005 TLIS | DIAGNOSTICS FOR TCP LISTENERS | DBUG |KN3FC005 TSTO | DIAGNOSTICS FOR TCP STORAGE | DBUG |KN3FC005 TN32 | DIAGNOSTICS FOR TN3270 | DBUG |KN3FC005 UDP | DIAGNOSTICS FOR UDP CONNECTIONS | DBUG |KN3FC005 GGS | DIAGNOSTICS FOR PROTOCOL STATS | DBUG |KN3FC005 GIF | DIAGNOSTICS FOR TCP INTERFACES | DBUG |KN3FC005 --------+-----------------------------------+------------------------+

KN3FCCMD INSTALL FPCTThe KN3FCCMD INSTALL FPCT command initializes the Tivoli Enterprise Monitoring Server data serverfeatures in the monitoring agent address space

Format

�� MODIFY proc_name , KN3FCCMD INSTALL FPCT ��

Purpose

Initializes the Tivoli Enterprise Monitoring Server data server features in the monitoring agent addressspace. This component is installed during monitoring agent initialization.

Usage

Sample output of this command follows.KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD INSTALL FPCT’KN3FC015 FPCT COMPONENT FUNCTIONS INSTALLATION COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD INSTALL FPONThe KN3FCCMD INSTALL FPON command initializes the OMEGAMON product features in themonitoring agent address space.

Format

�� MODIFY proc_name , KN3FCCMD INSTALL FPON ��

Purpose

Initializes the OMEGAMON product features in the monitoring agent address space. This component isinstalled during monitoring agent initialization.

Usage

Sample output of this command follows:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD INSTALL FPON’KN3FC010 FPON COMPONENT FUNCTIONS INSTALLATION COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE


KN3FCCMD INSTALL SEMVThe KN3FCCMD INSTALL SEMV command initializes the MVS environment features in the monitoringagent address space.

Format

�� MODIFY proc_name , KN3FCCMD INSTALL SEMV ��

Purpose

Initializes the MVS environment features in the monitoring agent address space. This component isinstalled during monitoring agent initialization.

Usage

Sample output of this command follows:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD INSTALL SEMV’KN3FC025 SEMV MVS ENVIRONMENT INSTALLATION COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD INSTALL SEVTThe KN3FCCMD INSTALL SEVT command initializes the VTAM environment features in the monitoringagent address space.

Format

�� MODIFY proc_name , KN3FCCMD INSTALL SEVT ��

Purpose

Initializes the VTAM environment features in the monitoring agent address space. This component isinstalled during monitoring agent initialization.

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD INSTALL SEMV’KN3FC020 SEVT VTAM ENVIRONMENT INSTALLATION COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD INSTALL TCPCThe KN3FCCMD INSTALL TCPC command initializes the TCP/IP and VTAM statistics collector.

Format

�� MODIFY INSTALL TCPC(VIO) (5)

TCPCVIOU (vio_unit) TCPCINTV (collection_interval)

��

Where:


TCPCVIOUIs the VIO unit name

vio_unitIs used for the allocation of temporary data sets. The default is VIO.

TCPCINTVIs the TCP/IP sample interval.

collection_intervalIs the TCP/IP data sampling interval. The value is specified in minutes with a valid range of 1 to60 and the default value is 5 minutes. This controls the frequency of data sampling for datacollected using SNMP as well as data collected from the NMI for the CONN, CSM, EEHPR, andIPSEC components.

Purpose

Initializes the TCP/IP and VTAM statistics collector. This component is installed during monitoring agentinitialization.

After you stop collection of TCP/IP and VTAM statistics, you must issue the following command to havecollection started again:MODIFY proc_name,KN3FCCMD START TCPC

If you want to change the value for either TCPCVIOU or TCPCINTV when you start TCPC collection,you must issue these commands:MODIFY proc_name,KN3FCCMD INSTALL TCPC TCPCVIOU(vio_unit) TCPCINTV(collection_interval)MODIFY proc_name,KN3FCCMD START TCPC

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START TCPC’KN3CT000 TCP/IP STATISTICS COLLECTOR INITIALIZATION COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START CONNThe KN3FCCMD START CONN command starts the monitoring of connections and applications.

Format

�� MODIFY proc_name , KN3FCCMD START CONN(*)

TCPNAME(tcpip_proc_name)

��

Where:

TCPNAMEIdentifies which TCP/IP address spaces this command applies to.

* Indicates that this applies to all TCP/IP address spaces.

tcpip_proc_nameIs the name of a TCP/IP address space in your environment.


Purpose

Starts the monitoring of connections and applications.

The following attribute groups and workspaces are affected by this command:

Table 44. Attribute groups and workspaces affected by the KN3FCCMD START CONN command

Workspace name Attribute group name Attribute group name prefix

Active TN3270 ServerConnections for Selected Port

TN3270 Server Sess Avail KN3TNA

Application Connections TCPIP Connections KN3TCN

Application Details TCPIP Applications KN3TAP

Application TCP Connections TCPIP Details KN3TCP

Application TCP Listeners TCP Listener KN3TCL

Application UDP Endpoints UDP Connections KN3UDP

Applications TCPIP Applications KN3TAP

Connections TCPIP Connections KN3TCN

EE Connection Summary v EE Connections Detailsv HPR Connectionsv UDP Connections

v KN3EEDv KN3HPRv KN3UDP

Enterprise Applications Health TCPIP Applications KN3TAP

Enterprise Connections Find TCPIP Details KN3TCP

Enterprise Connections Health TCPIP Details KN3TCP

Enterprise TN3270 Find TN3270 Server Sess Avail KN3TNA

Enterprise TN3270 ServerOverview

TCP Listener KN3TCL

FTP Sessions Details v FTP Sessionv TCPIP Details

v KN3FSEv KN3TCP

FTP Transfer Details v TCPIP FTPv TCPIP Details

v KN3FTPv KN3TCP

TCP Connections TCPIP Details KN3TCP

TCP Connection Details TCPIP Details KN3TCP

TCP Connections Link TCPIP Details KN3TCP

TCP Listeners TCP Listener KN3TCL

TN3270 Active Server SessionSummary for Remote IP


TN3270 Server SessionAvailability


TN3270 Server Session Details v TN3270 Response Time Bucketsv TN3270 Server Sess Avail

v KN3TNBv KN3TNA

TN3270 Server Session Pair TN3270 Server Sess Avail KN3TNA

TN3270 Server SessionSummary for Remote IP


TN3270 Server SessionSummary for SNA Name


TN3270 Server Sessions TN3270 Server Sess Avail KN3TNA


Table 44. Attribute groups and workspaces affected by the KN3FCCMD START CONN command (continued)


TN3270 Server Sessions forRemote IP

v TCPIP Address Spacev TN3270 Server Sess Avail

v KN3TASv KN3TNA

TN3270 Server Sessions forSNA Name


v KN3TASv KN3TNA

UDP Endpoints UDP Connections KN3UDP

Usage

Sample output of this command using the default value of all TCP/IP address spaces is provided in thefollowing section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START CONN’KN3C111I START FOR COMPONENT CONN ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output of this command using a specific TCP/IP address space is provided in the followingsection:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START CONN TCPNAME(TCPIP)’KN3C111I START FOR COMPONENT CONN ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START CSMThe KN3FCCMD START CSM command starts the monitoring of the Communication Storage Manager.

Format

�� MODIFY proc_name , KN3FCCMD START CSM ��

Purpose

Starts monitoring of the Communication Storage Manager.


Table 45. Attribute groups and workspaces affected by the KN3FCCMD START CSM command


CSM Buffer Pools CSM Storage Attributes KN3CSM

CSM Storage by OwnerSummary workspace

KN3 CSM Storage by Owner Attributes KN3CSO

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START CSM’KN3C112I START FOR COMPONENT CSM ACCEPTED.KN3FC000 KN3FCCMD PROCESSING COMPLETE


KN3FCCMD START DBUGThe KN3FCCMD START DBUG command starts the writing of trace messages for the TCP/IP and VTAMstatistics collector to the log files.

Format

��

�

MODIFY proc_name , KN3FCCMD START DBUGSNAC [debug_level]TACCTCPC

APPBASECOMMCSMEEHPRFTPGIFGGSHASHINITIPSECSNASNMPSYSTCPTCONTLISTSTOTN32UDP

��

Where:

SNAC Means write trace records for SNA Statistics collection.

TACC Means write trace records for the product-specific Take Action commands issued by theOMEGAMON XE for Mainframe Networks command handler.

TCPC Means write trace records for TCP/IP Statistics collections. Turning on all of the TCPCcomponent may result in large amounts of trace data being written to the monitoring agent's joblogs. To focus on the problem that you are experiencing, IBM Software Support may ask you tospecify additional parameters to only write a subset of the trace records for TCP/IP Statisticscollection. Table 46 describes those additional parameters:

Table 46. Components available from subset trace records


APP TCP/IP Application table

BASE Base data collection in the KN3ACTC4 task

COMM Common functions

CSM CSM Storage table

EEHPR Enterprise Extender and High Performance Routing tables

FTP FTP sessions and transfers tables

GIF Interface data


Table 46. Components available from subset trace records (continued)


GGS Stack Layer data

HASH Hash functions

INIT Initialization and control

IPSEC IP filters and IP security tables

SNA VTAM Summary Statistics table

SNMP SNMP data collection

SYSTCP Functions that access the real-time TCP/IP network management interface (NMI)and pass the retrieved data to the FTP and TN3270 data collection routines. For moreinformation about the real-time interface, see the IBM z/OS Communications Server: IPProgrammer's Guide and Reference.

TCON TCPIP Details table and TCP Connections data stored in the TCPIP Connections table

TLIS TCP Listener table and TCP Listener data stored in the TCPIP Connections table

TSTO TCPIP Memory Statistics table

TN32 TN3270 Server Sessions Avail and TN3270 Response Time Buckets tables

UDP UDP Connections table and UDP Connections data stored in the TCPIP Connectionstable

debug_levelIs one of the following:

Debug levelidentifier Meaning

MIN Trace data is captured only when an error is detected.

MID “Medium-detail” debugging messages are captured. These messages are used by IBM SoftwareSupport to diagnose software problems.

MAX All trace data is captured. These messages are used by IBM Software Support to diagnosesoftware problems.

Purpose

Starts the writing of trace messages for the TCP/IP and VTAM statistics collector to the log files.Additional trace messages will be written to sysout or spool data sets to facilitate investigation of aproblem. IBM Software Support might request that you issue this command and then provide a copy ofthe log files. When the STOP command is issued, the component and subcomponents will capture traceinformation only when there is an error (MIN level).

Attention: Issuing the KN3FCCMD START DBUG command with the debug level set at MAX mayresult in the rapid filling of all spool volumes. When all spool volumes fill, system failure may occur.

Usage

These usages notes apply:v You must specify a component before specifying a subcomponent. If you specify a subcomponent

without a component, Message KN3FC004 is issued.v When no subcomponent is specified when component is specified, the specified debug_level is applied

to all subcomponents of the selected component.


v When all TCPC subcomponents are enabled at the MAX debug level (either as part of one command orcumulative), warning message KN3C143W is issued indicating that a significant amount of trace datamay be written to the job log.

v When multiple subcomponent identifiers are specified, they are separated by spaces.v All components/subcomponents are started at the MIN debug level by default when the agent is

started.v Multiple subcomponents may be specified on one command with different levels for trace defined for

each component. Each START DBUG command has a cumulative effect.

Examples illustrating these usage points follow. These examples assume the default MIN level debugsetting.1. This command:

MODIFY procname,KN3FCCMD START DBUG TCPC BASE TN32 MAX

Results in the trace levels for the BASE and TN32 subcomponents of TCPC being set at MAX debuglevel. All other subcomponents of TCPC are still at the MIN debug level, and the SNAC component isat MIN debug level.Here is sample output for this command:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START DBUG TCPC BASE TN32 MAX’KN3C070I DBUG EXTENDED DIAGNOSTICS MODE STARTEDKN3FC000 KN3FCCMD PROCESSING COMPLETEKLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS DBUG’KN3AHFD3 (TCPC, BASE) KN3AHFD3 EXITKN3C074I DBUG EXTENDED DIAGNOSTICS MODE IS ACTIVEKN3C200I FOR TCPC COMPONENT, MAXIMUM TRACING IS ENABLED FOR SUBCOMPONENTS:KN3C201I TN32 BASEKN3C204I DBUG STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

2. This command:MODIFY procname,KN3FCCMD START DBUG TCPC TN32 MID

Results in the trace levels for the TN32 subcomponent being set to MID, but the trace level for theBASE subcomponent is still at MAX. All other TCPC subcomponents and the SNAC component areset at MIN by default.Here is sample output for this command:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START DBUG TCPC TN32 MID’KN3C070I DBUG EXTENDED DIAGNOSTICS MODE STARTEDKN3FC000 KN3FCCMD PROCESSING COMPLETEKLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS DBUG’KN3C074I DBUG EXTENDED DIAGNOSTICS MODE IS ACTIVEKN3C200I FOR TCPC COMPONENT, MAXIMUM TRACING IS ENABLED FOR SUBCOMPONENTS:KN3C201I BASEKN3C200I FOR TCPC COMPONENT, MEDIUM TRACING IS ENABLED FOR SUBCOMPONENTS:KN3C201I TN32KN3C204I DBUG STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

3. This command:MODIFY procname,KN3FCCMD START DBUG TCPC MAX

Results in the trace levels for all TCPC subcomponents being set to MAX. The trace level for theSNAC component is still set at MIN.Here is sample output for this command:


KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START DBUG TCPC MAX’KN3C070I DBUG EXTENDED DIAGNOSTICS MODE STARTEDKN3C143W MAX DEBUG LEVEL SET FOR COMPONENT TCPCKN3FC000 KN3FCCMD PROCESSING COMPLETEKLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS DBUG’KN3C074I DBUG EXTENDED DIAGNOSTICS MODE IS ACTIVEKN3C202I MAXIMUM TRACING FOR COMPONENT TCPC IS ENABLEDKN3C204I DBUG STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START EEHPRThe KN3FCCMD START EEHPR command starts the monitoring of Enterprise Extender and HighPerformance Routing connections.

Format

�� MODIFY proc_name , KN3FCCMD START EEHPR(N)

ALLHPR (Y)

��

Where:

ALLHPRIs an optional parameter that specifies whether the monitoring agent will collect all HighPerformance Routing (HPR) connections or only those connections that flow over EnterpriseExtender (EE) connections.

(N) Indicates that the monitoring agent is to collect data on HPR connections that flow over EEconnections.

(Y) Indicates that the monitoring agent is to collect data on all HPR connections, not just those thatflow over EE connections.

Purpose

Starts the monitoring of Enterprise Extender and High Performance Routing connections.


Table 47. Attribute groups and workspaces affected by the KN3FCCMD START EEHPR command


EE Connection Summary EE Connections Details KN3EED

HPR Connections KN3HPR

UDP Connections KN3UDP

Enterprise EE ConnectionsOverview

EE Connections Details KN3EED

Enterprise HPR ConnectionsOverview


EE Connections EE Connections KN3EEC


HPR Connection Details HPR Connections KN3HPR

HPR Connections HPR Connections KN3HPR


Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START EEHPR ALLHPR(Y)’KN3C112I START FOR COMPONENT EEHPR ACCEPTED. ALLHRP:YKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START FTPThe KN3FCCMD START FTP command starts the monitoring of FTP sessions and transfers.

Format

�� MODIFY proc_name,KN3FCCMD START FTP(*)


�

�(2)

DSPINTV(display_interval)

��

Where:

TCPNAMEIdentifies which TCP/IP address spaces this applies to.

* Indicates that this command applies to all TCP/IP address spaces.


DSPINTVSpecifies the number of hours of data that is displayed.

2 Is the default number of hours of data that is displayed.

display_intervalIs a value you specify for the DSPINTV parameter. The value must be a valid number in therange 1-24.

Purpose

Starts the monitoring of FTP sessions and transfers. The TCPNAME option identifies which TCP/IPaddress spaces this applies to. The DSPINTV option specifies the number of hours of data that isdisplayed.


Table 48. Attribute groups and workspaces affected by the KN3FCCMD START FTP command


Active FTP Sessions FTP Sessions Attributes KN3FSE

Enterprise FTP Sessions Find

FTP Sessions

FTP Sessions for Selected Filetransfer


Table 48. Attribute groups and workspaces affected by the KN3FCCMD START FTP command (continued)


Active FTP Transfers TCPIP FTP Attributes KN3FTP

Enterprise FTP Transfers Find

FTP Transfers

FTP Transfers for Session

FTP Transfers for Selected FTPSession

TCPIP FTP KN3FTP

Enterprise FTP SessionsOverview

FTP Sessions Attributes KN3FSE

TCPIP FTP Attributes KN3FTP

FTP Session Details FTP Sessions Attributes KN3FSE

TCPIP Details KN3TCP

FTP Transfer Details FTP Sessions Attributes KN3FSE


Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START FTP’KN3C110I START FOR COMPONENT FTP ACCEPTED. TCPNAME: * DSPINTV: 2KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START FTP DSPINTV(1)’KN3C110I START FOR COMPONENT FTP ACCEPTED. TCPNAME: * DSPINTV: 1KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 3:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START FTP TCPNAME(TCPIP)’KN3C110I START FOR COMPONENT FTP ACCEPTED. TCPNAME: TCPIP DSPINTV: 2KN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START GLBSThe KN3FCCMD START GLBS command starts TCP/IP stack layer statistics data collection.

Format

�� MODIFY proc_name,KN3FCCMD START GLBS(*)


��

Where:





Purpose

Starts TCP/IP stack layer statistics data collection. The following attribute groups and workspaces areaffected by this command:

Table 49. Attribute groups and workspaces affected by the KN3FCCMD START GLBS command


Address Space TCPIP Address Space KN3TAS

ICMP Statistics KN3 ICMP Global Counters KN3GCG

KN3 ICMP Type Counters KN3GCT

IP Statistics KN3 IP Counter Statistics KN3GIC

KN3 IP General Statistics KN3GIG

TCP Statistics KN3 TCP Counter Statistics KN3GTC

TCP/IP Stack Layers KN3 TCPIP Stack Layer KN3TSL

TCP/IP Stack Layers History KN3 TCPIP Stack Layer KN3TSL

TCP/IP Summary KN3 TCPIP Address Space KN3TAS

TCP/IP Summary History KN3 TCPIP Address Space KN3TAS

UDP Statistics KN3 UDP Counter Statistics KN3GUC

Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START GLBS’KN3C111I START FOR COMPONENT GLBS ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START GLBS TCPNAME(TCPIP)’KN3C111I START FOR COMPONENT GLBS ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START INTEThe KN3FCCMD START INTE command starts interface data link control (DLC) data collection.

Format

�� MODIFY proc_name,KN3FCCMD START INTE(*)


��

Where:





Purpose

Starts interface data link control (DLC) data collection.


Table 50. Attribute groups and workspaces affected by the KN3FCCMD START INTE command


Data Link Control (DLC) Read andWrite Queue Statistics

KN3 Interface Read Queue KN3IFR

KN3 Interface Write Queue KN3IFW

Enterprise HiperSockets InterfacesOverview



KN3 Interface Status KN3IFE

KN3 Interface Statistics KN3IFS

Enterprise Interfaces Overview KN3 Interface Status KN3IFE


Enterprise OSA Interfaces Overview KN3 Interface Read Queue KN3IFR




Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START INTEKN3C111I START FOR COMPONENT INTE ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START INTE TCPNAME(TCPIP)’KN3C111I START FOR COMPONENT INTE ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START INTSThe KN3FCCMD START INTS command starts interface statistics data collection.

Format

�� MODIFY proc_name,KN3FCCMD START INTS(*)


��

Where:





Purpose

Starts Interface Statistics data collection. The following attribute groups and workspaces are affected bythis command:

Table 51. Attribute groups and workspaces affected by the KN3FCCMD START INTS command













Gateways and Devices TCPIP Devices KN3TDV

Interface Statistics KN3 Interface Statistics KN3IFS

Interface Statistics History KN3 Interface Statistics KN3IFS

Interface Status KN3 Interfaces KN3IFE

Interfaces Interfaces KN3TIF

Interfaces History Interfaces KN3TIF

Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START INTSKN3C111I START FOR COMPONENT INTS ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START INTS TCPNAME(TCPIP)’KN3C111I START FOR COMPONENT INTS ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START IPSECThe KN3FCCMD START IPSEC command starts collection of IPSEC data.


Format

�� MODIFY proc_name , KN3FCCMD START IPSEC(*)


��

Where:




Purpose

Starts collection of IPSec data.


Table 52. Attribute groups and workspaces affected by the KN3FCCMD START IPSEC command


Current IP Filters Current IP Filters KN3IFC

Current IP Filters byDestination Address

Current IP Filters by FilterRule Definition Name

Current IP Filters in ScanOrder

Dynamic IP Tunnels Dynamic IP Tunnels KN3ITD

Dynamic IP Tunnels byDestination Address

Dynamic IP Tunnels by FilterRule Definition Name

Dynamic IP Tunnels by TunnelID

Dynamic IP Tunnels with ByteRate < 2048

Dynamic IP Tunnel Statistics IPSec Status KN3ISS

IKE Tunnels IKE Tunnels KN3ITI

IKE Tunnels by SecurityEndpoint

IKE Tunnels by Tunnel ID

IKE Tunnels with Byte Rate <1024

Manual IP Tunnels Manual IP Tunnels KN3ITM

Manual IP Tunnels by TunnelID


Usage

Sample output of this command using the default value of all TCP/IP address spaces is provided in thefollowing section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START IPSEC’KN3C110I START FOR COMPONENT IPSEC ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output of this command using a specific TCP/IP address space is provided in the followingsection:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START IPSEC TCPNAME(TCPIP)’KN3C110I START FOR COMPONENT IPSEC ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START OSAThe KN3FCCMD START OSA command starts collection of OSA data.

Format

�� MODIFY proc_name,KN3FCCMD START OSA(*)


��

Where:




Purpose

Starts OSA data collection. The TCPNAME option identifies which TCP/IP address spaces this applies to.


Table 53. Attribute groups and workspaces affected by the KN3FCCMD START OSA command

Workspace name Attribute group nameAttribute groupname prefix

Enterprise OSA-Express Channels Overview OSA-Express Channels KN3TCH

Enterprise OSA-Express Ports Overview OSA-Express3 Ports Errors KN3THE

OSA-Express Ports KN3TPO

OSA 10 Gigabit Ports Errors KN3TTE

OSA 10 Gigabit Ports Summary KN3TTS

OSA Channels OSA-Express Channels KN3TCH

OSA Ports OSA-Express Ports KN3TPO

OSA LPARs OSA-Express LPARs KN3TLP

OSA-Express2 10 Gigabit Port Errors OSA-Express Channels KN3TCH


Table 53. Attribute groups and workspaces affected by the KN3FCCMD START OSA command (continued)


OSA-Express2 10 Gigabit Port Control OSA 10 Gigabit Ports Control KN3TTC

OSA-Express2 10 Gigabit Ports Summary OSA 10 Gigabit Ports Summary KN3TTS

OSA-Express2 10 Gigabit Port Throughput Detail OSA 10 Gigabit PortsThroughput

KN3TTT

OSA-Express3 Port Control OSA-Express3 Ports Control KN3THC

OSA-Express3 Port Errors OSA-Express3 Ports Errors KN3THE

OSA-Express3 Ports Summary OSA-Express3 Ports Summary KN3THS

OSA-Express3 Port Throughput Detail OSA-Express3 PortsThroughput

KN3THT

Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START OSA’KN3C111I START FOR COMPONENT OSA ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START OSA TCPNAME(TCPIP)’KN3C111I START FOR COMPONENT OSA ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START ROUTEThe KN3FCCMD START ROUTE command starts the monitoring of routing information, which isdisplayed in Tivoli Enterprise Portal in the Gateways view of the Gateways and Devices workspace.

Format

�� MODIFY proc_name , KN3FCCMD START ROUTE(*)


�

�(10)

FREQ(frequency)

��

Where:





FREQ Is the number of collection intervals before the routing information will be collected. The valuemust be a valid number in the range of 1 to 99.

10 The default collection interval. With a default 5 minute collection interval, routing informationwould be collected approximately every 50 minutes.

frequencyIs specified as the number of collection intervals before the routing information will be collected.The value must be a valid number in the range of 1 to 99. An example would be a frequency of 2with a 15-minute collection interval.

Purpose

Starts the monitoring of routing information, which is displayed in Tivoli Enterprise Portal in theGateways view of the Gateways and Devices workspace. The TCPNAME option identifies which TCP/IPaddress spaces this command applies to. The FREQ option allows you to collect routing information lessfrequently than the rest of the resources because gateway tables can be large and do not change veryoften.


Table 54. Attribute groups and workspaces affected by the KN3FCCMD START ROUTE command


Gateways and Devices TCPIP Gateways KN3TGA

Usage

Sample output using default of all TCP/IP address spaces:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START ROUTE’KN3C120I START FOR COMPONENT ROUTE ACCEPTED. TCPNAME: * FREQ: 10KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output with a specific TCP/IP address space named:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START ROUTE TCPNAME(TCPIP)’KN3C120I START FOR COMPONENT ROUTE ACCEPTED. TCPNAME: TCPIP FREQ: 10KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output with frequency interval specified:KN3FC000 KN3FCCMD PROCESSING COMPLETEKLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START ROUTE FREQ(5)’KN3C120I START FOR COMPONENT ROUTE ACCEPTED. TCPNAME: * FREQ: 5KN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START SNACThe KN3FCCMD START SNAC command starts the monitoring of the SNA data collector and determineshow often data will be collected.

Format

�� MODIFY proc_name , KN3FCCMD START SNAC(5)

SNACINTV (SNA_data_collection_interval)

��


Where:

SNACINTVIs the SNA data collection interval. The default is 5 minutes.

SNA_data_collection_intervalIs the number of minutes between SNA data collection samples. This value is specified inminutes with a valid range of 1 to 60.

Purpose

Starts the monitoring of the SNA data collector and determines how often data will be collected.

When the user specifies Y for the Buffer Pool/VTAM Environment Data Collection parameter in theSPECIFY COMPONENT CONFIGURATION (Page 3) panel (shown in Figure 16 on page 98) when usingthe Configuration Tool to configure OMEGAMON XE for Mainframe Networks, the KN3FCCMD START SNACcommand is added to member KN3AGOPS of the RKANCMDU dataset. This command starts themonitoring of the SNA data collector and determines how often data will be collected. In order to collectdata using the SNA collector the user must specify Y for Buffer Pool/VTAM Environment DataCollection.

If the SNA collector is active, the KN3FCCMD START SNAC command may be used to change the collectioninterval dynamically when the command is issued using the SNACINTV keyword.


Table 55. Attribute groups and workspaces affected by the KN3FCCMD START SNAC command


Address Space VTAM Address Space KN3VAS

VTAM I/O KN3VIO

VTAM Storage KN3VIO

VTAM Buffer Pools Summary VTAM Buffer Pools KN3BPD

VTAM Buffer Pool Details VTAM Buffer Pools

VTAM Buffer Pool Extents VTAM Buffer Pool Extents KN3BPE

VTAM Buffer Usage By AddressSpace

VTAM Buffer Usage By AddressSpace

KN3BPS

VTAM Buffer Usage By Applicationfor Address Space

VTAM Buffer by Application KN3BPA

VTAM Buffer Usage By Category VTAM Buffer Usage By Category KN3BPG

VTAM SIO VTAM I/O KN3VIO

VTAM Storage VTAM I/O KN3VIO

VTAM Summary VTAM Summary Statistics KN3SNA

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START SNAC SNACINTV(1)’KN3C112I START FOR COMPONENT SNAC ACCEPTED.KN3FC000 KN3FCCMD PROCESSING COMPLETE


KN3FCCMD START TCPCThe KN3FCCMD START TCPC command starts the monitoring of TCP/IP and VTAM statistics.

Format

�� MODIFY proc_name , KN3FCCMD START TCPC ��

Purpose

Starts the monitoring of TCP/IP and VTAM statistics.

After you stop monitoring TCP/IP and VTAM statistics, issue the following commands to restartcollection:MODIFY proc_name,KN3FCCMD INSTALL TCPC

TCPCVIOU(vio_unit)TCPCINTV(collection_interval)

MODIFY proc_name,KN3FCCMD START TCPC




Table 56. Attribute groups and workspaces affected by the KN3FCCMD START TCPC command


Active FTP Sessions FTP Sessions KN3FSE



Active FTP Transfers TCPIP FTP KN3FTP








Command Log KN3 Take Action Command Attributes KN3CTA

KN3 Take Action Command ResponseAttributes

KN3RTA


CSM Buffer Pools CSM Storage KN3CSM


Table 56. Attribute groups and workspaces affected by the KN3FCCMD START TCPC command (continued)






Data Link Control (DLC) Readand Write Queue Statistics









EE Connection Summary EE Connection Details KN3EED



EE Connection Details EE Connection Details KN3EED

EE Connections EE Connection KN3EEC




Enterprise FTP Sessions Find FTP Sessions KN3FSE


FTP Sessions KN3FSE

TCPIP FTP KN3FTP

Enterprise FTP Transfers Find TCPIP FTP KN3FTP

Enterprise HiperSocketsInterfaces Overview







Enterprise OSA-ExpressChannels Overview

OSA-Express Channels KN3TCH




Enterprise OSA-Express PortsOverview

OSA-Express3 Ports Errors KN3THE




Enterprise OSA InterfacesOverview






FTP Session Details FTP Sessions KN3FSE


FTP Sessions FTP Sessions KN3FSE

FTP Sessions for selected filetransfer

FTP Sessions KN3FSE

FTP Transfer Details TCPIP FTP KN3FTP


FTP Transfers TCPIP FTP KN3FTP

FTP Transfers for link selected TCPIP FTP KN3FTP

FTP Transfers for Session TCPIP FTP KN3FTP


TCPIP Gateways KN3TGA






Interface Status KN3 Interface Status KN3IFE


Interfaces History







IKE Tunnels Statistics IPSec Status KN3ISS

IPSec Status






NetView for z/OS: PacketTrace – Start

KN3 DWL to 3270 KN3DWL3270

NetView for z/OS: PacketTrace – Stop



OSA-Express2 10 Gigabit PortErrors


OSA-Express2 10 Gigabit PortControl

OSA 10 Gigabit Ports Control KN3TTC

OSA-Express2 10 Gigabit PortsSummary


OSA-Express2 10 Gigabit PortThroughput Detail

OSA 10 Gigabit Ports Throughput KN3TTT




OSA-Express3 PortThroughput Detail

OSA-Express3 Ports Throughput KN3THT


OSA Port Interfaces OSA Port Interfaces KN3TIF







TCP/IP Memory Statistics TCPIP Memory Statistics KN3TPV

TCP/IP Stack Layers TCPIP Stack Layer KN3TSL

TCP/IP Stack Layers History TCPIP Stack Layer KN3TSL

TCP/IP Summary TCPIP Address Space KN3TAS

TCP/IP Summary History TCPIP Address Space KN3TAS













TN3270 Server Session Details TN3270 Server Sess Avail KN3TNA

TN3270 Response Time Buckets KN3TNB




Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START TCPC’KN3CT100 TCP/IP SERVICE THREAD INITIALIZATION COMPLETEKN3CT000 TCP/IP STATISTICS COLLECTOR INITIALIZATION COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETEKN3FC095 TCPC COLLECTOR STATUS IS ACTIVEKN3FC095 KONAYTGA ADDRESS IS D1D3098, KONAYFCV ADDRESS IS D1D1E20KN3FC095 SAMPLE INTERVAL IS 1 MINUTESKN3FC095 NUMBER OF TIMES COLLECTOR HAS ABENDED IS 0KN3FC095 TCPC COLLECTION IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS, FTPKN3FC095 TCPC COLLECTION IS ACTIVE FOR TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL IS 2 HOURSKN3FC095 TN3270 DISPLAY INTERVAL IS 2 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY IS ONCE EVERY 10 INTERVALSKN3FC095 VTAM COLLECTION IS ACTIVE FOR SNA, CSM, EEHPRKN3FC095 TCPC STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD START TN3270The KN3FCCMD START TN3270 command starts the monitoring of TCP/IP and VTAM statistics.

Format

�� MODIFY proc_name , KN3FCCMD START TN3270(*)


�

�(2)

DSPINTV(display_interval)

��


Where:




DSPINTVSpecifies the number of hours of data that is displayed.

2 Is the default number of hours of data that is displayed.

display_intervalIs a value you specify for the DSPINTV parameter. The value must be a valid number in therange 1-24.

Purpose

Starts the monitoring of TN3270 server sessions. The TCPNAME option identifies which TCP/IP addressspaces this applies to. The DSPINTV option specifies the number of hours of data that is displayed.


Table 57. Attribute groups and workspaces affected by the KN3FCCMD START TN3270 command


Active TN3270 Server Connectionsfor Selected Port workspace


Enterprise TN3270 Find workspace TN3270 Server Sess Avail KN3TNA

TN3270 Server Session Availability TN3270 Server Sess Avail KN3TNA







TN3270 Server Session Summary forRemote IP


TN3270 Server Session Summary forSNA Name


TN3270 Server Sessions for RemoteIP


TN3270 Server Sessions for SNAName


Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START TN3270’KN3C110I START FOR COMPONENT TN3270 ACCEPTED. TCPNAME: * DSPINTV: 2KN3FC000 KN3FCCMD PROCESSING COMPLETE


Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START TN3270 DSPINTV(1)’KN3C110I START FOR COMPONENT TN3270 ACCEPTED. TCPNAME: * DSPINTV: 1KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 3:Sample output #3:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD START TN3270 TCPNAME(TCPIP)’KN3C110I START FOR COMPONENT TN3270 ACCEPTED. TCPNAME: TCPIP DSPINTV: 2KN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STATUS DBUGThe KN3FCCMD STATUS DBUG command displays the current settings of the extended diagnosticscomponent.

Format

�� MODIFY proc_name , KN3FCCMD STATUS DBUG ��

Purpose

Display the current settings of the extended diagnostics component.

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS DBUG’KN3FC074 DBUG EXTENDED DIAGNOSTICS MODE IS INACTIVEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STATUS FCPTThe KN3FCCMD STATUS FCPT command displays the status of the Tivoli Enterprise Monitoring Serverdata server features.

Format

�� MODIFY proc_name , KN3FCCMD STATUS FCPT ��

Purpose

Displays the status of the Tivoli Enterprise Monitoring Server data server features.

Usage

Sample output of this command is provided in the following section:KLVOP191 ’KN3FCCMD STATUS FPCT’KN3FC017 KONAYFCV AT 0D1D1E20KN3FC017 FPCT COMPONENT FUNCTIONS INSTALLEDKN3FC017 FUNCTION PACKAGE KN3AZCFV LOADED AT 0D1517D8KN3FC000 KN3FCCMD PROCESSING COMPLETE


KN3FCCMD STATUS FPONThe KN3FCCMD STATUS FPON command displays the status of the OMEGAMON product features.

Format

�� MODIFY proc_name , KN3FCCMD STATUS FPON ��

Purpose

Displays the status of the OMEGAMON product features.

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS FPON’KN3FC012 KONAYFCV AT 0D1D1E20KN3FC012 FPON COMPONENT FUNCTIONS INSTALLEDKN3FC012 FUNCTION PACKAGE KN3AZOFV LOADED AT 0D15BF08KN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STATUS SEMVThe KN3FCCMD STATUS SEMV command displays the status of the MVS environment features.

Format

�� MODIFY proc_name , KN3FCCMD STATUS SEMV ��

Purpose

Displays the status of the MVS environment features.

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS SEMV’KN3FC027 KONAYFCV AT 0D1D1E20KN3FC027 SEMV MVS ENVIRONMENT INSTALLEDKN3FC027 MVS DICTIONARY KN3AZD2C LOADED AT 90780B9CKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STATUS SEVTThe KN3FCCMD STATUS SEVT command displays the status of the VTAM environment features.

Format

�� MODIFY proc_name , KN3FCCMD STATUS SEVT ��

Purpose

Displays the status of the VTAM environment features.


Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS SEVT’KN3FC023 KONAYFCV AT 0D1D1E20KN3FC023 SEVT VTAM ENVIRONMENT INSTALLEDKN3FC023 VTAM DICTIONARY KN3AZD1E LOADED AT 90781C7CKN3FC023 SRT HASH FLAG IS 40KN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STATUS SNACThe KN3FCCMD STATUS SNAC command displays the status of the SNA data collector.

Format

�� MODIFY proc_name , KN3FCCMD STATUS SNAC ��

Purpose

Displays the status of the SNA data collector.

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS SNAC’KN3C130I SNA COLLECTOR STATUS IS ACTIVEKN3C131I KONAYPWK ADDRESS IS 4CB000, KONAYACT ADDRESS IS EB41300KN3C132I MONITORING VTAM ADDRESS SPACE NAMED VTAMKN3C133I SNA COLLECTION INTERVAL IS 1KN3C134I ACB PREFIX IS OVTAMC, PMI ACB NAME IS N341N3SPKN3C136I SAMPLE INTERVAL IS 6000 HUNDREDTH SECONDSKN3C138I CYCLE COUNT IS 15KN3C141I SNA COLLECTOR STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STATUS TCPCThe KN3FCCMD STATUS TCPC command displays the status of the TCP/IP and VTAM statisticscomponent.

Format

�� MODIFY proc_name , KN3FCCMD STATUS TCPC ��

Purpose

Displays the status of the TCP/IP and VTAM statistics component.

Usage

Sample output of this command is provided in the following section:KN3FC095 TCPC COLLECTOR STATUS IS ACTIVEKN3FC095 KONAYTGA ADDRESS IS 108C9D20, KONAYFCV ADDRESS IS 108C8560KN3FC095 SAMPLE INTERVAL IS 1 MINUTES


KN3FC095 NUMBER OF TIMES COLLECTOR HAS ABENDED IS 0KN3FC095 TCPC COLLECTION IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS, FTPKN3FC095 TCPC COLLECTION IS ACTIVE FOR TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL IS 2 HOURSKN3FC095 TN3270 DISPLAY INTERVAL IS 2 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY IS ONCE EVERY 10 INTERVALSKN3FC095 TCPC COLLECTION FROM TCPIP IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS,KN3FC095 TCPC COLLECTION FROM TCPIP IS ACTIVE FOR FTP, TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL FOR TCPIP IS 24 HOURSKN3FC095 TN3270 DISPLAY INTERVAL FOR TCPIP IS 24 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY FOR TCPIP IS ONCE EVERY 15 INTERVALSKN3FC095 VTAM COLLECTION IS ACTIVE FOR SNA, CSM, EEHPRKN3FC095 EEHPR OPTIONS: ALLHPR(Y)KN3FC095 TCPC STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output for a system with three TCP/IP address spaces:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STATUS TCPC’KN3FC095 TCPC COLLECTOR STATUS IS ACTIVEKN3FC095 KONAYTGA ADDRESS IS D4320C0, KONAYFCV ADDRESS IS D430E48KN3FC095 SAMPLE INTERVAL IS 5 MINUTESKN3FC095 NUMBER OF TIMES COLLECTOR HAS ABENDED IS 0KN3FC095 TCPC COLLECTION IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS, FTPKN3FC095 TCPC COLLECTION IS ACTIVE FOR TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL IS 2 HOURSKN3FC095 TN3270 DISPLAY INTERVAL IS 2 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY IS ONCE EVERY 10 INTERVALSKN3FC095 TCPC COLLECTION FROM TCPIP IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS,KN3FC095 TCPC COLLECTION FROM TCPIP IS ACTIVE FOR FTP, TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL FOR TCPIP IS 2 HOURSKN3FC095 TN3270 DISPLAY INTERVAL FOR TCPIP IS 2 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY FOR TCPIP IS ONCE EVERY 10 INTERVALSKN3FC095 TCPC COLLECTION FROM TCPIPB IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS,KN3FC095 TCPC COLLECTION FROM TCPIPB IS ACTIVE FOR FTP, TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL FOR TCPIPB IS 2 HOURSKN3FC095 TN3270 DISPLAY INTERVAL FOR TCPIPB IS 2 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY FOR TCPIPB IS ONCE EVERY 10 INTERVALSKN3FC095 TCPC COLLECTION FROM TCPIPC IS ACTIVE FOR TCPC, CONN, OSA, INTS, INTE, GLBS,KN3FC095 TCPC COLLECTION FROM TCPIPC IS ACTIVE FOR FTP, TN3270, ROUTEKN3FC095 FTP DISPLAY INTERVAL FOR TCPIPC IS 2 HOURSKN3FC095 TN3270 DISPLAY INTERVAL FOR TCPIPC IS 2 HOURSKN3FC095 ROUTE COLLECTION FREQUENCY FOR TCPIPC IS ONCE EVERY 10 INTERVALSKN3FC095 VTAM COLLECTION IS ACTIVE FOR SNA, CSM, EEHPRKN3FC095 EEHPR options: ALLHPR(Y)KN3FC095 TCPC STATUS DISPLAY COMPLETEKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP CONNThe KN3FCCMD STOP CONN command stops the monitoring of connections and applications.

Format

�� MODIFY proc_name , KN3FCCMD STOP CONN(*)


��

Where:





Purpose

Stops the monitoring of connections and applications.


Table 58. Attribute groups and workspaces affected by the KN3FCCMD STOP CONN command











EE Connection Summary v EE Connections Detailsv HPR Connectionsv UDP Connections

v KN3EEDv KN3HPRv KN3UDP





Enterprise TN3270 ServerOverview

TCP Listener KN3TCL

FTP Sessions Details v FTP Sessionv TCPIP Details

v KN3FSEv KN3TCP

FTP Transfer Details v TCPIP FTPv TCPIP Details

v KN3FTPv KN3TCP









TN3270 Server Session Details v TN3270 Response Time Bucketsv TN3270 Server Sess Avail

v KN3TNBv KN3TNA





Table 58. Attribute groups and workspaces affected by the KN3FCCMD STOP CONN command (continued)







v KN3TASv KN3TNA



v KN3TASv KN3TNA


Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP CONN’KN3C115I STOP FOR COMPONENT CONN ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP CONN TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT CONN ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP CSMThe KN3FCCMD STOP CSM command stops the monitoring of Communications Storage Manager.

Format

�� MODIFY proc_name , KN3FCCMD STOP CSM ��

Purpose

Stops the monitoring of Communications Storage Manager.


Table 59. Attribute groups and workspaces affected by the KN3FCCMD STOP CSM command


CSM Buffer Pools CSM Storage Attributes KN3CSM

CSM Storage by OwnerSummary workspace

KN3 CSM Storage by Owner Attributes KN3CSO

Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP CSM’KN3C116I STOP FOR COMPONENT CSM ACCEPTED.KN3FC000 KN3FCCMD PROCESSING COMPLETE


KN3FCCMD STOP DBUGThe KN3FCCMD STOP DBUG command stops the writing of trace messages for the TCP/IP and VTAMstatistics collector to the log files.

Format

�� MODIFY proc_name , KN3FCCMD STOP DBUGSNACTACCTCPC

APPBASECOMMCSMEEHPRFTPGIFGGSHASHINITIPSECSNASNMPSYSTCPTCONTLISTSTOTN32UDP

��

Where:

SNAC Means to stop writing trace records for SNA Statistics collection.

TACC Means to stop writing trace records for the product-specific Take Action commands issued by theOMEGAMON XE for Mainframe Networks command handler.

TCPC Means to stop writing trace records for TCP/IP Statistics collections. Any of the following TCPCcomponents can be stopped. Table 60describes those additional parameters:

Table 60. Components available from subset trace records


APP TCP/IP Application table

BASE Base data collection in the KN3ACTC4 task

COMM Common functions

CSM CSM Storage table

EEHPR Enterprise Extender and High Performance Routing tables

FTP FTP sessions and transfers tables

GIF Interface data

GGS Stack Layer data

HASH Hash functions

INIT Initialization and control

IPSEC IP filters and IP security tables


Table 60. Components available from subset trace records (continued)


SNA VTAM Summary Statistics table

SNMP SNMP data collection

SYSTCP Functions that access the real-time TCP/IP network management interface (NMI)and pass the retrieved data to the FTP and TN3270 data collection routines. For moreinformation about the real-time interface, see the IBM z/OS Communications Server: IPProgrammer's Guide and Reference.

TCON TCPIP Details table and TCP Connections data stored in the TCPIP Connections table

TLIS TCP Listener table and TCP Listener data stored in the TCPIP Connections table

TSTO TCPIP Memory Statistics table

TN32 TN3270 Server Sessions Avail and TN3270 Response Time Buckets tables

UDP UDP Connections table and UDP Connections data stored in the TCPIP Connectionstable

Purpose

Stops the writing of trace messages for the TCP/IP and VTAM statistics collector to the log files.

Usage

These usages notes apply:v You must specify a component before specifying a subcomponent. If you specify a subcomponent

without a component, Message KN3FC004 is issued.v When all TCPC subcomponents are enabled at the MAX debug level (either as part of one command or

cumulative), warning message KN3C143W is issued indicating that a significant amount of trace datamay be written to the job log.

v When multiple subcomponent identifiers are specified, they are separated by spaces.v All components/subcomponents are started at the MIN debug level by default when the agent is

started. When the STOP command is issued, the component and subcomponents will capture traceinformation only when there is an error (MIN level).

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP DBUG TCPC’KN3FC072 DBUG EXTENDED DIAGNOSTICS MODE STOPPEDKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP EEHPRThe KN3FCCMD STOP DBUG command stops the writing of Enterprise Extender and High PerformanceRouting connections.

Format

�� MODIFY proc_name , KN3FCCMD STOP EEHPR ��


Purpose

Stops the writing of Enterprise Extender and High Performance Routing connections.


Table 61. Attribute groups and workspaces affected by the KN3FCCMD STOP EEHPR command


EE Connection Summary EE Connections Details KN3EED



Enterprise EE ConnectionsOverview


Enterprise HPR ConnectionsOverview


EE Connections EE Connections KN3EEC


HPR Connection Details HPR Connections KN3HPR


Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP EEHPR’KN3C116I STOP FOR COMPONENT EEHPR ACCEPTED.KN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP FTPThe KN3FCCMD STOP FTP command stops the monitoring of FTP sessions and transfers.

Format

�� MODIFY proc_name , KN3FCCMD STOP FTP(*)


��

Where:




Purpose

Stops the monitoring of FTP sessions and transfers.



Table 62. Attribute groups and workspaces affected by the KN3FCCMD STOP FTP command


Active FTP Sessions FTP Sessions Attributes KN3FSE

Enterprise FTP Sessions Find

FTP Sessions

FTP Sessions for Selected Filetransfer

Active FTP Transfers TCPIP FTP Attributes KN3FTP

Enterprise FTP Transfers Find

FTP Transfers

FTP Transfers for Session

FTP Transfers for Selected FTPSession

TCPIP FTP KN3FTP


FTP Sessions Attributes KN3FSE

TCPIP FTP Attributes KN3FTP

FTP Session Details FTP Sessions Attributes KN3FSE


FTP Transfer Details FTP Sessions Attributes KN3FSE


Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP FTP’KN3C115I STOP FOR COMPONENT FTP ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP FTP TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT FTP ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP GLBSThe KN3FCCMD STOP GLBS command stops TCP/IP stack layer statistics data collection.

Format

�� MODIFY proc_name , KN3FCCMD STOP GLBS(*)


��

Where:





Purpose

Stops TCP/IP stack layer statistics data collection. The following attribute groups and workspaces areaffected by this command:

Table 63. Attribute groups and workspaces affected by the KN3FCCMD STOP GLBS command








TCP/IP Stack Layers KN3 TCPIP Stack Layer KN3TSL

TCP/IP Stack Layers History KN3 TCPIP Stack Layer KN3TSL

TCP/IP Summary KN3 TCPIP Address Space KN3TAS

TCP/IP Summary History KN3 TCPIP Address Space KN3TAS


Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP GLBS’KN3C115I STOP FOR COMPONENT GLBS ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP GLBS TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT GLBS ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP INTEThe KN3FCCMD STOP INTE command stops interface data link control (DLC) data collection.

Format

�� MODIFY proc_name , KN3FCCMD STOP INTE(*)


��

Where:





Purpose

Stops interface data link control (DLC) data collection.


Table 64. Attribute groups and workspaces affected by the KN3FCCMD STOP INTE command


Data Link Control (DLC) Read andWrite Queue Statistics














Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP INTEKN3C115I STOP FOR COMPONENT INTE ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP INTE TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT INTE ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP INTSThe KN3FCCMD STOP INTS command stops interface statistics data collection.

Format

�� MODIFY proc_name , KN3FCCMD STOP INTS(*)


��

Where:





Purpose

Stops interface statistics data collection. The following attribute groups and workspaces are affected bythis command:

Table 65. Attribute groups and workspaces affected by the KN3FCCMD STOP INTS command
















Interface Status KN3 Interfaces KN3IFE


Interfaces History Interfaces KN3TIF

Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP INTSKN3C115I STOP FOR COMPONENT INTS ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP INTS TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT INTS ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP IPSECThe KN3FCCMD STOP IPSEC command stops collection of IPSEC data.


Format

�� MODIFY proc_name , KN3FCCMD STOP IPSEC(*)


��

Where:




Purpose

Stops collection of IPSec data.


Table 66. Attribute groups and workspaces affected by the KN3FCCMD STOP IPSEC command



















Usage

Sample output of this command using the default value of all TCP/IP address spaces is provided in thefollowing section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP IPSEC’KN3C110I STOP FOR COMPONENT IPSEC ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output of this command using a specific TCP/IP address space is provided in the followingsection:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP IPSEC TCPNAME(TCPIP)’KN3C110I STOP FOR COMPONENT IPSEC ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP OSAThe KN3FCCMD STOP OSA command stops data collection for OSA.

Format

�� MODIFY proc_name , KN3FCCMD STOP OSA(*)


��

Where:




Purpose

Stops data collection for OSA. The following attribute groups and workspaces are affected by thiscommand:

Table 67. Attribute groups and workspaces affected by the KN3FCCMD STOP OSA command


Enterprise OSA-Express Channels Overview OSA-Express Channels KN3TCH

Enterprise OSA-Express Ports Overview OSA-Express3 Ports Errors KN3THE







OSA-Express2 10 Gigabit Port Errors OSA-Express Channels KN3TCH


Table 67. Attribute groups and workspaces affected by the KN3FCCMD STOP OSA command (continued)


OSA-Express2 10 Gigabit Port Control OSA 10 Gigabit Ports Control KN3TTC

OSA-Express2 10 Gigabit Ports Summary OSA 10 Gigabit Ports Summary KN3TTS

OSA-Express2 10 Gigabit Port Throughput Detail OSA 10 Gigabit PortsThroughput

KN3TTT




OSA-Express3 Port Throughput Detail OSA-Express3 PortsThroughput

KN3THT

Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP OSAKN3C115I STOP FOR COMPONENT OSA ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP OSA TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT OSA ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP ROUTEThe KN3FCCMD STOP ROUTE command stops the monitoring of routing information, which isdisplayed in Tivoli Enterprise Portal in the Gateway workspace.

Format

�� MODIFY proc_name , KN3FCCMD STOP ROUTE(*)


��

Where:




Purpose

Stops the monitoring of routing information, which is displayed in Tivoli Enterprise Portal in theGateway workspace. The TCPNAME option identifies which TCP/IP address spaces this commandapplies to.



Table 68. Attribute groups and workspaces affected by the KN3FCCMD STOP ROUTE command


Gateways and Devices TCPIP Gateways KN3TGA

Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP ROUTE’KN3C115I STOP FOR COMPONENT ROUTE ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE

Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP ROUTE TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT ROUTE ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

KN3FCCMD STOP TCPCThe KN3FCCMD STOP TCPC command stops the monitoring of TCP/IP and VTAM statistics.

Format

�� MODIFY proc_name , KN3FCCMD STOP TCPC ��

Purpose

Stops the monitoring of TCP/IP and VTAM statistics.




Table 69. Attribute groups and workspaces affected by the KN3FCCMD STOP TCPC command


Active FTP Sessions FTP Sessions KN3FSE



Active FTP Transfers TCPIP FTP KN3FTP





Table 69. Attribute groups and workspaces affected by the KN3FCCMD STOP TCPC command (continued)






Command Log KN3 Take Action Command Attributes KN3CTA

KN3 Take Action Command ResponseAttributes

KN3RTA


CSM Buffer Pools CSM Storage KN3CSM





Data Link Control (DLC) Readand Write Queue Statistics









EE Connection Summary EE Connection Details KN3EED



EE Connection Details EE Connection Details KN3EED

EE Connections EE Connection KN3EEC




Enterprise FTP Sessions Find FTP Sessions KN3FSE


FTP Sessions KN3FSE

TCPIP FTP KN3FTP

Enterprise FTP Transfers Find TCPIP FTP KN3FTP




Enterprise HiperSocketsInterfaces Overview







Enterprise OSA-ExpressChannels Overview

OSA-Express Channels KN3TCH

Enterprise OSA-Express PortsOverview

OSA-Express3 Ports Errors KN3THE




Enterprise OSA InterfacesOverview






FTP Session Details FTP Sessions KN3FSE


FTP Sessions FTP Sessions KN3FSE

FTP Sessions for selected filetransfer

FTP Sessions KN3FSE

FTP Transfer Details TCPIP FTP KN3FTP


FTP Transfers TCPIP FTP KN3FTP

FTP Transfers for link selected TCPIP FTP KN3FTP

FTP Transfers for Session TCPIP FTP KN3FTP


TCPIP Gateways KN3TGA






Interface Status KN3 Interface Status KN3IFE


Interfaces History










IKE Tunnels Statistics IPSec Status KN3ISS

IPSec Status



NetView for z/OS: PacketTrace – Start


NetView for z/OS: PacketTrace – Stop



OSA-Express2 10 Gigabit PortErrors


OSA-Express2 10 Gigabit PortControl

OSA 10 Gigabit Ports Control KN3TTC

OSA-Express2 10 Gigabit PortsSummary


OSA-Express2 10 Gigabit PortThroughput Detail

OSA 10 Gigabit Ports Throughput KN3TTT




OSA-Express3 PortThroughput Detail

OSA-Express3 Ports Throughput KN3THT


OSA Port Interfaces OSA Port Interfaces KN3TIF







TCP/IP Memory Statistics TCPIP Memory Statistics KN3TPV

TCP/IP Stack Layers TCPIP Stack Layer KN3TSL

TCP/IP Stack Layers History TCPIP Stack Layer KN3TSL

TCP/IP Summary TCPIP Address Space KN3TAS

TCP/IP Summary History TCPIP Address Space KN3TAS


















Usage

Sample output of this command is provided in the following section:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP TCPC’KN3CT004 TCP/IP STATISTICS COLLECTOR IS TERMINATINGKN3CT104 TCP/IP SERVICE THREAD IS TERMINATINGKN3CT107 TCP/IP SERVICE THREAD COMPLETED TERMINATIONKN3CT007 TCP/IP STATISTICS COLLECTOR COMPLETED TERMINATION.KN3FC000 KN3FCCMD PROCESSING COMPLETEKN3IR005 TCP SUBNODE DEREGISTERED FOR ORIGINNODE TCPIP:0239KN3IR006 TCP SUBNODE MONITOR STOPPED FOR ORIGINNODE TCPIP:0239KN3IR005 VTAM SUBNODE DEREGISTERED FOR ORIGINNODE VTAM:0239KN3IR006 VTAM SUBNODE MONITOR STOPPED FOR ORIGINNODE VTAM:0239

Note: Buffer Pool And VTAM Environment Data Collection continues to be collected by the SNACcollector, but the following data collection is stopped with the STOP TCPC command:v Enterprise Extender and High Performance Routing Statistics Collectionv ALL High Performance Routing Connections Collectionv CSM Buffer Reporting Collectionv TCP/IP Connection and Application Performance Statistics Collectionv IP Security Statisticsv Collection Routing Table Statistics Collectionv TN3270 Server Statistics Collectionv FTP Data Collection

KN3FCCMD STOP TN3270The KN3FCCMD STOP TCPC command stops the monitoring of TN3270 server sessions


Format

�� MODIFY proc_name , KN3FCCMD STOP TN3270(*)


��

Where:




Purpose

Stops the monitoring of TN3270 server sessions. The TCPNAME option identifies which TCP/IP addressspaces this applies to.


Table 70. Attribute groups and workspaces affected by the KN3FCCMD STOP TN3270 command


Active TN3270 Server Connectionsfor Selected Port workspace


Enterprise TN3270 Find workspace TN3270 Server Sess Avail KN3TNA

TN3270 Server Session Availability TN3270 Server Sess Avail KN3TNA







TN3270 Server Session Summary forRemote IP


TN3270 Server Session Summary forSNA Name


TN3270 Server Sessions for RemoteIP


TN3270 Server Sessions for SNAName


Usage

Sample output 1:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP TN3270’KN3C115I STOP FOR COMPONENT TN3270 ACCEPTED. TCPNAME: *KN3FC000 KN3FCCMD PROCESSING COMPLETE


Sample output 2:KLVOP191 REPLY FROM *MASTER*:KLVOP191 ’KN3FCCMD STOP TN3270 TCPNAME(TCPIP)’KN3C115I STOP FOR COMPONENT TN3270 ACCEPTED. TCPNAME: TCPIPKN3FC000 KN3FCCMD PROCESSING COMPLETE

Introduction to the KONFCCMD commandsUse the KONFCCMD commands to implement the NPALU collector task and the TCP/IP collector taskand component.

KONFCCMD commands are required to implement the following in the OMEGAMON II address space:v The NPALU collector task and the NCP monitor componentv The TCP/IP collector task and the TCP/IP component

The appropriate commands are provided in the RKANCMDU library.

You define your configuration parameter values during configuration and the Configuration Tool updatesthe runtime libraries. Usually these IBM-supplied commands will suffice.

This section describes the arguments and options available with KONFCCMD in case you use thiscommand for other purposes.

Using the KONFCCMD commandUse this information to construct a valid KONFCCMD command.

KONFCCMD is a TMS: Engine operator command that you can use to do the following to anOMEGAMON II address space:v Install specific components into specific address spaces.v Start, stop, or display the status of specific components within an address space.

You can invoke this command in any of the following ways:v Through the MCS console via the z/OS modify commandv Through the specifications in the RKANCMD filev Through the KLV operator interface

The KLV operator is provided for each application which runs under CT/Engine. In OMEGAMON IIfor Mainframe Networks, it may be accessed by logging on to the APPLID specified by the chosenAPPL prefix + OP. For example, if the APPL prefix chosen was ON620 then the APPLID of the KLVoperator (also known as the CUA operator) would be ON620OP. Once you have logged on to thisoperator [for example, logon applid (ON620OP)], you can perform such actions as viewing tables inthe table database and issuing commands.

When using KONFCCMD, adhere to the following guidelines:v You must use a command argument once per command invocation.v The first invocation of KONFCCMD must use the INSTALL command argument.v You can install, start, stop, or status a number of components simultaneously.

The command format is as follows options:KONFCCMD argument option1 option2...option

Where:


argumentIs one of the following:

INSTALLInstall the specified features.

STARTInitiate® the specified features.

STOP Shut down the specified features.

STATUSDisplay the status of the specified features.

HELP Display how to use this command.

option Is some combination of the following:

FPON Install functions specific to the OMEGAMON II address space.

FPCT Install functions specific to the NCP collector

NCPC Install, start, stop, or display status of the NCP collector. The following options arespecific to NCPC:

NCPCPATH(LUCS,COLLECTOR=collappl.)Specifies the applid of the NCP collector task that talks to other OMEGAMON IIaddress spaces.

NCPCACBN(ncpappl.)Specifies the applid of the NCP collector task that talks to the NPALU in theNCP.

NCPCINTV(nn.)Specifies the numeric interval, in seconds, for the NCP collector task samplingrate.

NDMTInstall, start, stop, or display status of the NCP Data Manager (NDM) within anOMEGAMON II address space. The following options are specific to NDMT:

NDMTPATH(LUCS,LOCAL)Specifies the NCP collector task resides in the same (local) OMEGAMON IIaddress space.

NDMTPATH(LUCS,LOCALID=locappl, COLLECTOR=collappl, MODE=mode62.)Specifies the NCP collector task resides in a remote OMEGAMON II addressspace, where locappl resides in the local address space and talks to collappl whichresides in the remote address space containing the NCP collector.

SEVT Install functions specific to the VTAM execution environment for an OMEGAMON IIaddress space.

TCPC Install, start, stop, or display status of the TCP/IP collector.

Starting TCPC will initiate data collection for ALL enabled components. Stopping theTCPC task will disable ALL data.

SEMV Install functions specific to the MVS execution environment for an OMEGAMON IIaddress space.

TCPCVIOU(vio_unit_name)Specifies the collection interval (data sampling interval) for the TCP/IP component,where .vio_unit_name is the VIO unit name for the TCP/IP collector to use whendynamically allocating files. If omitted, the default VIO is used.


KONFCCMD examplesThese examples show how to use the KONFCCMD command.

The examples that follow illustrate the KONFCCMD statements required for each of three possibleOMEGAMON II and NCP collector configurations. Depending on the type of configuration you specify,the Configuration Tool builds the required KONFCCMD statements in the KONSTKON member of&rhilev.&midlev.&rtename.RKANSAMU.v Variables

The examples include the following variables:

collapplApplid of the NCP collector task that talks to other OMEGAMON II address spaces to provideNCP data. It is built by the Configuration Tool from the specified OMEGAMON II applidprefix.

ncpapplApplid of the NCP collector task that talks to the NPALU to obtain NCP data. It is built by theConfiguration Tool from the specified OMEGAMON II applid prefix.

locapplApplid in the OMEGAMON II without the NCP collector that talks to the OMEGAMON IIcontaining the NCP collector. It is built by the Configuration Tool from the specifiedOMEGAMON II applid prefix.

nn NCP collection interval which may be different than the collection interval specified during theconfiguration.

mode62Logmode entry specified during configuration for the LU 6.2 session between OMEGAMON IIand the NCP collector in another address space.

v NCP collector in OMEGAMON II address spaceThese are the statements required when the NCP collector is included in the OMEGAMON II addressspace:KONFCCMD INSTALL SEVT SEMV FPCT FPONKONFCCMD INSTALL NCPC -

NCPCPATH(LUCS,COLLECTOR=collappl,NCPCACBN=ncpappl) -NCPCINTV(nn)

KONFCCMD START NCPCKONFCCMD INSTALL NDMT -

NDMTPATH(LUCS,LOCAL)KONFCCMD START NDMT

v NCP collector in another OMEGAMON II address spaceThese are the statements required when OMEGAMON II gathers NCP statistics from the NCP collectorin another OMEGAMON II address space.KONFCCMD INSTALL SEVT SEMV FPCT FPONKONFCCMD INSTALL NDMT -

NDMTPATH(LUCS,LOCALID=locappl,COLLECTOR=collappl,MODE=mode62)KONFCCMD START NDMT

v TCP/IP data collectionThese are the statements required when OMEGAMON II starts TCP/IP data collection.KONFCCMD INSTALL TCPC -

TCPCVIOU(VIO) -TCPCINTV(1)

KONFCCMD START TCPCKONFCCMD STATUS TCPC

v OMEGAMON II client only


When you do not require OMEGAMON II to gather NCP performance statistics and the OMEGAMONII address space does not include an NCP collector, no KONFCCMD statements are required.


Appendix D. Disk space requirements for historical datatables

You can calculate the amount of DASD required to support the persistent data store for storing historicaldata in Tivoli Data Warehouse.

This section provides the information you will need to determine space allocations in the persistent datastore for each monitoring agent. Therefore, the disk space requirements in the tables in this appendix arefor short-term history, which is stored on z/OS systems in the OMEGAMON XE persistent data store.

Network size and the type of network resources managed vary widely between enterprises. The amountand type of historical data that you choose to retain will greatly affect the amount of storage required.Wide differences between networks make it difficult to provide one size for the persistent data store thatreflects the needs of most enterprises.

The default storage allocation is efficient for a very small network. Most users will need to allocateadditional storage and data sets. Increase the default number of data sets from 3 to 5 or more. Increasingthe number of data sets, using the Group Count parameter in the Control Program, is explained in thefollowing section under “Allocating additional storage and data sets” on page 258.

This appendix provides you with the following information:v Alternative methods for determining storagev Effective allocation of additional storage and data sets (if needed)v A list of attribute tables supported by short-term historyv Record size for each attribute tablev Worksheets to help you estimate the storage required

Note: If you are upgrading from V4.1 or 4.2 and did this exercise for one of these releases, it isrecommended that you do it again for V5.1. The upgraded versions contain new attribute tables, and newattributes are included in existing tables.

Alternative methods of determining storage requirementsOne way to determine the amount of DASD required for your persistent data is trial and error.

Many users who estimate the storage requirements for collecting historical data do it by trial and error.The main problems with this approach are twofold:1. Every time you adjust storage parameters (number of cylinders and number of data sets), you must

stop the agent. This might be unacceptable if implemented in a production network.2. The network you use to determine storage parameters might not be comparable in size to the network

where you will collect short-term history

If trial and error is not an acceptable approach in your environment, then you can use the information inthis appendix to estimate storage size.


Trial and error approachAbout this task

To compute space requirements by trial and error, start historical collection for all resources you need tostore in short-term history, and collect at least 25 hours of data. If you cannot draw a report containingthe last 24 hours of data, for any attribute table, then you need to allocate additional storage or data setsor both.

If you are collecting short-term history, you can also create a rough estimate of the hours of measurementdata you can store by looking in the RKPDLOG log of the OMEGAMON XE for Mainframe Networksmonitoring agent. This log can be viewed from MVS/TSO in the SDSF Status window. To perform thisestimate, do the following:1. Examine the RKPDLOG log.2. Record the elapsed time between the message:

KPDIFIL: Initial output file selection completed successfully for group KN3

And the message:KPDDSTR: File rhilev.&midlev.RKN3HIS3 is full

This rough estimator works whether you have the default 3 history data sets (RKN3HIS1 – RKN3HIS3)or more data sets. Short-term history first fills the data set with the highest suffix (for example,RKN3HIS7) and then works its way down to RKN3HIS1, before it wraps back to the data set with thehighest suffix.

If the elapsed time is 24 hours or greater, you should have enough storage allocated for users to viewreports with 24 hours of data. If the elapsed time is less than 24 hours, then you need to allocateadditional storage or data sets or both.

If you need to increase space allocation, and estimate how much to allocate, you should understand therelationship between the two configurable storage parameters: allocated Cylinders and Group Count,explained under “Allocating additional storage and data sets.”

Estimating approachThe information and worksheets in this section can be used to estimate storage requirements. You willneed to know the following:1. Resource types (attribute tables) that need to be collected for history.2. Approximate quantity of each resource type that will be monitored. If the number of monitored

resources varies widely between different LPARs, and different TCP/IP stacks, you might want toestimate the different storage requirements for each LPAR and each TCP/IP stack.

3. Historical collection interval.

Allocating additional storage and data setsYou can override the default storage sizes that the Configuration Tool provided for short-term historydata sets. Understand the varied roles that short-term history plays and how to change the size of yourpersistent data store.

The Configuration Tool provides default storage size values for short-term history data sets in thepersistent data store. You can override these defaults. The OMEGAMON XE for Mainframe Networksmonitoring agent storage size defaults are shown in Table 71 on page 259.


Table 71. Definition and default values for cylinders and group count parameters

Storage parameters Default values

Cylinders

Cylinders is a measure of storage capacity on a disk drive. Consideringcontrol blocks and indexing, the persistent data store can storeapproximately 717 KB of measurement data on one cylinder of 3390 diskdrive.

After you determine the number of cylinders you need for yourenvironment, add 37 to it to account for the RN3SGRPx data sets. Thisvalue is then entered into the Est Cyl Space field of the PersistentDatastore Specifications panel. See “Step 6: Configuring the persistentdatastore (in the agent)” on page 118 for more information.

261

(for the persistent data stores, 224 forthe RKN3HISx data sets + 37 for theRN3SGRPx data sets)

Group Count

Group Count refers to the number of persistent data store data sets. TheJCL job to allocate the persistent data store datasets is generated by theConfiguration Tool in Step 6 under“Step 6: Configuring the persistentdatastore (in the agent)” on page 118. Each persistent data store datasetwill be allocated with (Cylinders / Group Count) number of cylinders.AGroup Count of 3 means that 3 RKN3HISx data sets will be allocated formeasurement data.

3

Short-term history is more than a place to store data. It enables:v Continuous operations without manual attention to pruning outdated datav Dynamic data set switching (data wrapping without losing data)v Display of a full 24 hours of data, in a Tivoli Enterprise Portal report, at any point in time

These features require that one of the data sets be temporarily unavailable in preparation for data setswitching. In addition, preserving the ability to display a full 24 hours of data in a report at any time ofday might require that an additional data set be allocated to accommodate when the data set beingwritten to is almost empty.

To account for the extra data sets needed to enable these features, apply a Group Count factor to the totalnumber of cylinders required to store 24 hours of data in your network. The Group Count factorexpresses the storage relationship of Group Count to the number of cylinders to allocate. That is:Cylinders to Allocate = Cylinders needed for 24 hours data X Group Count Factor

Where:Group Count Factor = (Group Count / (Group Count - 2))

These two examples illustrate the effect of the Group Count Factor. These examples show how increasingthe Group Count value can use the allocated cylinders of space more efficiently (that is, requires lessspace for the same amount of data). Note that warehousing (exporting data to Tivoli Data Warehouse)and short-term historical queries are more efficient in smaller persistent data store data sets (that is,higher group count).

This formula is used to calculate DASD for both examples:

Cylinders to Allocate = Cylinders needed for 24 hours data X (Group Count / (Group Count - 2))Cylinders to Allocate = 10 X (3/(3-2) = 30

Figure 49. Formula for calculating DASD

Appendix D. Disk space requirements for historical data tables 259

Modelling some alternate Group Count values illustrates the impact that modifying this parameter has onthe amount of DASD (Cylinders of 3390) to be allocated.

Table 72. Sample group count and cylinders to allocate to enable viewing of 24 hours of data

Cylinders needed for 24hours of data Group count Group count factor Cylinders to allocate

Example 1: a very small test network requiring only 70 cylinders of 3390 DASD for 24 hours of data

70 3 3.00 210

70 4 2.00 140

70 5 1.67 119

70 6 1.50 105

70 7 1.40 105

70 8 1.33 91

70 9 1.29 91

70 10 1.25 91

Example 2: a somewhat larger network requiring 500 cylinders of 3390 DASD for 24 hours of data

500 3 3.00 1500

500 4 2.00 1000

500 5 1.67 830

500 6 1.50 750

500 7 1.40 700

500 8 1.33 670

500 9 1.29 640

500 10 1.25 630

For the small network in Example 1, retaining the default Group Count value of 3 (or at most, increasingto 4) is adequate. However, for the larger network in Example 2, you would need to increase group countand cylinders, possibly to 6 or 7 and 750 or 700. For a monitored network with more than 10,000 TCP/IPconnections, consider using a Group Count of at least 7.

When you consider these examples in light of the default values that ship with this product (Cylinders3390 = 261 and Group Count = 3), you can accept the defaults with no loss of function for the smallnetwork. However, for the larger network in Example 2, you could not accept the defaults andconfidently expect that users could view a report with 24 hours of data at any time of day. However, ifyou increased Group Count to at least 6 (and your network size estimate is correct), you should be ableto provide this support by allocating 750 cylinders (+37) of additional DASD to short-term history.

Estimating the space requirementsBefore providing sizings for historical data collection tables, understand how this data is collected.

You can collect historical data for the OMEGAMON XE for Mainframe Networks attribute tables listed inTable 73 on page 261. The columns in Table 73 on page 261 are explained in the section that follows:

Attribute TableIs the name of the attribute table in which historical data is stored.

FilenameIs the name of the file that corresponds to the name of the attribute table.


DefaultSpecifies whether the table is configured if you select Default Groups in the Historical Collectiondialog.

Estimated Storage RequiredIs the estimated space required to store 24 hours of data per monitored resource.

A row stored in short-term history consists of all the attributes in the real-time row, plus 28 bytes per rowto account for the additional fields maintained for all historical records. Space requirements for real-timedata are described under “Understanding how historical data is collected” on page 48.

For most attribute groups, real-time data is only kept for the most recent measurement. For historicalcollection, data is stored for each history collection interval.

You might also choose to configure long-term history, and therefore store data for periods longer than 24hours. Long-term history is stored in the Tivoli Data Warehouse. Fortunately, the space requirements perrow of data are the same for a row of data in short-term history (in the persistent data store) and a rowof data in long-term history (in a relational database).

Some clients use the archiving feature of short-term history to save backups and to collect more than 24hours of data for analysis in a third-party statistical software package. Disk space requirements forarchives are not included in the basic disk space requirements that are shown in Table 73.

Historical data tablesTo understand how to size your historical data tables, look at this table, which displays the storage usedwhen monitoring one resource for 24 hours for every attribute group.

Table 73 lists the OMEGAMON XE for Mainframe Networks attribute tables available for historicalcollection. This table displays the storage used when monitoring one resource for 24 hours, assumingcollection intervals of 15 minutes.

Table 73. Historical data tables

Attribute table File name Default*

Estimated storagerequired for onedata set (in KB)

Estimated storage requiredfor one data set (3390cylinders; No. of cylinders= KB/717)

Agent

KN3 Agent Status KN3AGS Yes 24 0.0329

KN3 SNA Collector Status KN3SCS Yes 12 0.0173

KN3 TCP Collector Status KN3TCS Yes 73.5 0.1025

TCP/IP

Current IP Filters KN3IFC No 79 0.1098

Dynamic IP Tunnels KN3ITD No 99 0.1376

FTP Sessions KN3FSE Yes 0.8 0.0011

Interfaces KN3TIF Yes 47 0.0654

IKE Tunnels KN3ITI No 65 0.0905

IPSec Status KN3ISS Yes 36 0.0507


KN3GCG No 12 0.0167

KN3 ICMP Type Counters KN3GCT No 10 0.0141

KN3 Interface Address KN3IFA No 15 0.0209


Table 73. Historical data tables (continued)




KN3 Interface Read Queue KN3IFR No 32 0.0445

KN3 Interface Statistics KN3IFS No 31 0.0434

KN3 Interface Status KN3IFE No 35 0.0486

KN3 Interface Write Queue KN3IFW No 21 0.0298

KN3 IP Counter Statistics KN3GIC No 24 0.0340

KN3 IP General Statistics KN3GIG No 11 0.0146


KN3GTC No 29 0.0403


KN3GUC No 15 0.0204

Manual IP Tunnels KN3ITM No 37 0.0513

OSA-Express Channels KN3TCH Yes 42 0.0581

OSA-Express LPARS KN3TLP Yes 201 0.2803

OSA-Express Ports KN3TPO Yes 75 0.1041


KN3TTC No 39 0.0547


KN3TTE Yes 42 0.0591


KN3TTS Yes 48 0.0664


KN3TTT No 42 0.0586


KN3THC No 39 0.0547

OSA-Express3 Ports Errors KN3THE Yes 48 0.0664


KN3THS Yes 58 0.0811


KN3THT No 48 0.0669

TCP Listener KN3TCL Yes 28 0.0387

TCPIP Address Space KN3TAS Yes 61 0.0853

TCPIP Applications KN3TAP Yes 64 0.0894

TCPIP Connections KN3TCN Yes 62 0.0863

TCPIP Details KN3TCP Yes 60 0.0842

TCPIP Devices KN3TDV Yes 43 0.0601

TCPIP FTP (FTP transfers) KN3FTP Yes 5 0.0068

TCPIP Gateways KN3TGA Yes 59 0.0821

TCPIP Memory Statistics KN3TPV Yes 47 0.0654

TCPIP Stack Layer KN3TSL Yes 60 0.0832

TN3270 Server Sess Avail KN3TNA Yes 15 0.0207


Table 73. Historical data tables (continued)




UDP Connections KN3UDP Yes 36 0.0507

VTAM

CSM Storage KN3CSM Yes 19 0.0267

EE Connections KN3EEC Yes 26 0.0361

EE Connection Details KN3EED Yes 126 0.1752

HPR RTP Connections KN3HPR Yes 56 0.0779

KN3 CSM Storage byOwner

KN3CSO No 18 0.0256

VTAM Address Space KN3VAS Yes 26 0.0356

VTAM Buffer Pool Extents KN3BPE No 12 0.0162

VTAM Buffer Pools KN3BPD Yes 239 0.3332


KN3BPS Yes 9 0.0131

VTAM Buffer Usage byApplication for AddressSpace

KN3BPA Yes 10 0.0141


KN3BPG Yes 108 0.1506

VTAM I/O KN3VIO Yes 56 0.0785

VTAM Summary Statistics KN3SNA Yes 9 0.0131

Total 2642.5 KB 3.6855 cylinders

*Indicates the attribute groups for which product developers have defined historical views. You must configurethese attribute groups if you want to see historical data in the predefined workspaces.

Tools for estimating data storage requirementsUse the worksheets in this section to understand the formula for historical collection, the attribute grouprecord sizes, and the space requirements for the various data types for historical data storage.

The following types of formulas and data type combinations are included in this product:v Agent historical data storagev TCP/IP historical data storagev VTAM historical data storagev FTP historical data storagev TN3270 historical data storage

The following formulas and worksheets provide the information needed to estimate storage requirementsfor each of the data types.

Agent historical data storageUse this information to understand the formula for historical collection, the attribute group record sizes,and the space requirements for Agent historical data storage.v Agent formula


Storage assumptions:– Historical collection interval: 15 minutes– Quantity of each resource types monitored: 1

v Attribute group record sizes

This data is collected once every collection interval for the agent. The number of rows returned mayvary depending on the table. For example, the number of rows returned for the TCP Collector Statustable depends on how many TCP/IP stacks the agent is monitoring.

Table 74. Agent data collected

Type of dataHistorical data attributetable


Subtotalstoragerequired

Agent KN3 Agent Status 252 1 row 24 KB

KN3 SNA CollectorStatus

132 1 row 12 KB

KN3 TCP CollectorStatus

784 1 row per monitored stack 73.5 KB

v Space requirement worksheets

Use the worksheets shown in Tables 72 through 74 to estimate the disk space requirements for yoursite. A sample calculation is provided for each historical data collection table.– Each worksheet is for one agent per LPAR.– For an LPAR, there can be one VTAM address space and one or more TCP/IP address spaces being

monitored by the agent. The number of rows returned for the TCP Collector Status table depends onhow many TCP/IP address spaces the agent is monitoring. You will need to multiply the requiredstorage by the number of TCP/IP address spaces being monitored.

– If you are monitoring multiple LPARs, complete a worksheet for each LPAR, or one worksheet thatrepresents the average LPAR.

KN3 Agent Status (KN3AGS) worksheetUse the KN3 Agent Status (KN3AGS) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Figure 50. Formula for Agent historical collection data storage


Table 75. KN3 Agent Status (KN3AGS) worksheet

IntervalRecordsize Formula Agent

Agentaddressspace

Expectedstoragerequired for24 hours

15minutes

252 4 x 24 x 252 x1 x 1 / 1024 1 1 24 KB

KN3 TCP Collector Status (KN3TCS) worksheetUse the KN3 TCP Collector Status (KN3TCS) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 76. TCP Collector Status (KN3TCS) worksheet


MonitoredTCP/IPaddressspaces


15minutes

784 4 x 24 x 784 x 1 x 1 / 1024 1 1 73.5 KB

KN3 SNA Collector Status (KN3SCS) worksheetUse the KN3 SNA Collector Status (KN3SCS) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 77. SNA Collector Status (KN3SCS) worksheet


VTAMaddressspace


15minutes

132 4 x 24 x 132 x 1 x 1 / 1024 1 1 12 KB

TCP/IP historical data storageUse this information to understand the formula for historical collection, the attribute group record sizes,and the space requirements for TCP/IP historical data storage.v TCP/IP formula




This data is collected once every collection interval for each TCP/IP stack. If you have an LPAR withmultiple TCP/IP stacks, combine the storage required for each stack you will monitor.




Subtotal storagerequired (KB)


TCPIP Memory Statistics 500 1 row per TCP/IP address space 47

TCP/IP Stack layerStatistics

TCPIP Address Space 652 1 row per TCPIP address space 61


128 1 row per TCP/IP address space 12

KN3 ICMP TypeCounters

108 1 row per ICMP type per ICMPversion

10

KN3 IP CounterStatistics

260 Up to 2 rows per TCP/IPaddress space

24

KN3 IP GeneralStatistics






TCPIP Stack Layer 636 1 row per TCP/IP address space 60

Interfaces statistics Interfaces 500 1 row per interface 47

KN3 Interface Address 160 1 row per TCP/IP interfaceaddress

15

KN3 Interface Statistics 332 1 row per active strategicTCP/IP interface

31

KN3 Interface Status 372 1 row per TCP/IP interface 35

TCPIP Devices 460 1 row per device 43

Figure 51. Formula for TCP/IP historical collection data storage. Formula for TCP/IP historical collection data storage





Subtotal storagerequired (KB)

Interface Data LinkControl statisticscollection


340 1 row per read queue per activeOSA Queued Direction I/O(QDIO) or HiperSocketsinterface

32

KN3 Interface WriteQueue

228 1 row per configured queuepriority per OSA-ExpressQueued Direct I/O (QDIO) orHiperSocket interface

21

OSA statistics collection OSA-Express Channels 444 1 row per OSA Channel 42

OSA-Express LPARS 134 1 row per OSA LPAR 201

OSA-Express Ports 796 1 row per OSA Port 75


418 1 row per OSA-Express 2 10Gigabit Port

39



42



48



42


418 1 row per OSA-Express3 Port 39

OSA-Express3 PortsErrors






TCP/IP Connection andApplication Performancestatistics collection

TCPIP Applications 684 1 row per TCP/IP application 64

TCPIP Connections 660 1 row per TCPIP connection 62

TCPIP Details 644 1 row per TCP connection 60

TCP Listener 296 1 row per TCP listener 28

UDP Connections 388 1 row per UDP endpoint 36

Routing Table StatisticsCollection

TCPIP Gateways 628 1 row per TCP/IP gatewaycollected on Routing TableCollection Frequency

59

IPSec Security collection IPSec Status 388 1 row per TCP/IP address space 36

Current IP Filters 840 1 row per IP filter 79

Dynamic IP Tunnels 1052 1 row per dynamic IP tunnel 99

IKE Tunnels 692 1 row per IKE tunnel 65

Manual IP Tunnels 392 1 row per manual IP tunnel 37


Use the worksheets shown in Tables 76 through 109 to estimate the disk space requirements for yoursite. A sample calculation is provided for each historical data collection table.– Each worksheet is for one monitored resource per LPAR or per TCP/IP stack.


– Typically you are monitoring more than one resource (that is, one TCP/IP address space, connection,or session, for example). You need to multiply the required storage by the number of resources.


– If you are monitoring more than one TCP/IP stack in an LPAR, multiply by the number of TCP/IPstacks.

Current IP Filters (KN3IFC) worksheetUse the Current IP Filters (KN3IFC) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 79. Current IP Filters (KN3IFC) worksheet

IntervalRecordsize Formula

TCP/IPaddressspaceresources IP Filters


15minutes

840 4 x 24 x 840 x 1 x 1 / 1024 1 1 79 KB

Dynamic IP Tunnels (KN3ITD) worksheetUse the Dynamic IP Tunnels (KN3ITD) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 80. Dynamic IP Tunnels (KN3ITD) worksheet


TCP/IPaddressspaceresources

Dynamic IPTunnels


15minutes

1052 4 x 24 x 1052 x 1 x 1 / 1024 1 1 99 KB

Interfaces (KN3TIF) worksheetUse the Interfaces (KN3TIF) worksheet to calculate the amount of DASD required by this attribute groupin the persistent data store.

Table 81. Interfaces (KN3TIF) worksheet


TCP/IPinterface

TCP/IPstack


15minutes

500 4 x 24 x 500 x 1 x 1 x 1/ 1024 1 1 47 KB

IKE Tunnels (KN3ITI) worksheetUse the IKE Tunnels (KN3ITI) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.


Table 82. IKE Tunnels (KN3ITI) worksheet



Dynamic IPTunnels


15minutes

692 4 x 24 x 692 x 1 x 1 / 1024 1 1 65 KB

IPSec Status (KN3ISS) worksheetUse the IPSec Status (KN3ISS) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 83. IPSec Status (KN3ISS) worksheet


TCP/IPaddressspaceresources TCP/IP stack


15minutes

388 4 x 24 x 388 x 1 x 1 / 1024 1 1 36 KB

KN3 ICMP Global Counters (KN3GCG) worksheetUse the KN3 ICMP Global Counters (KN3GCG) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 84. KN3 ICMP Global Counters (KN3GCG) worksheet


ICMPprotocol

ICMPVersion

TCP/IPstack


15minutes

128 4 x 24 x 128 x 1 x 1 x 1 / 1024 1 1 1 12 KB

KN3 ICMP Type Counters (KN3GCT) worksheetUse the KN3 ICMP Type Counters (KN3GCT) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 85. KN3 ICMP Type Counters (KN3GCT) worksheet

IntervalRecordsize Formula ICMP type

TCP/IPstack


15minutes

108 4 x 24 x 108 x 1 x 1 / 1024 1 1 10 KB

KN3 Interface Address (KN3IFA) worksheetUse the KN3 Interface Address (KN3IFA) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.


Table 86. KN3 Interface Address (KN3IFA) worksheet


TCP/IPinterfaceaddress

TCP/IPinterface

TCP/IPstack


15minutes

160 4 x 24 x 160 x 1 x 1 x 1 / 1024 1 1 1 15 KB

KN3 Interface Read Queue (KN3IFR) worksheetUse the KN3 Interface Read Queue (KN3IFR) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 87. KN3 Interface Read Queue (KN3IFR) worksheet


Readqueue

Active TCP/IPQDIO orHiperSocketsinterface

TCP/IPstack


15minutes

340 4 x 24 x 340 x 1 x 1 x 1 / 1024 1 1 1 32KB

KN3 Interface Statistics (KN3IFS) worksheetUse the KN3 Interface Statistics (KN3IFS) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 88. KN3 Interface Statistics (KN3IFS) worksheet


ActiveTCP/IPstrategicinterface*

TCP/IPstack


15minutes

332 4 x 24 x 332 x 1 x 1 / 1024 1 1 31 KB

* The strategic interfaces have one of the following values for the Interface Type attribute on KN3 workspaces:Loopback, OSA-Express Queued Direct I/O (QDIO) Ethernet, HiperSockets, or Multipath Channel Point-To-Point(MPCPTP)

KN3 Interface Status (KN3IFE) worksheetUse the KN3 Interface Status (KN3IFE) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 89. KN3 Interface Status (KN3IFE) worksheet


TCP/IPinterface

TCP/IPstack


15minutes

372 4 x 24 x 372 x 1 x 1 / 1024 1 1 35 KB


KN3 Interface Write Queue (KN3IFW) worksheetUse the KN3 Interface Write Queue (KN3IFW) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 90. KN3 Interface Write Queue (KN3IFW) worksheet


Writequeue

Active TCP/IPQDIO orHiperSocketsinterface

TCP/IPstack


15minutes

228 4 x 24 x 228 x 1 x 1 x 1 / 1024 1 1 1 21 KB

KN3 IP Counter Statistics (KN3GIC) worksheetUse the KN3 IP Counter Statistics (KN3GIC) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 91. KN3 IP Counter Statistics (KN3GIC) worksheet


IP counterstatistics IP version

TCP/IPstack


15minutes

260 4 x 24 x 260 x 1 x 1 x 1 / 1024 1 1 1 24 KB

KN3 IP General Statistics (KN3GIG) worksheetUse the KN3 IP General Statistics (KN3GIG) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 92. IP General Statistics (KN3GIG) worksheet

IntervalRecordsize Formula IP protocol

TCP/IPstack


15minutes

112 4 x 24 x 112 x 1 x 1 / 1024 1 1 11 KB

KN3 TCP Counter Statistics (KN3GTC) worksheetUse the KN3 TCP Counter Statistics (KN3GTC) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 93. KN3 TCP Counter Statistics (KN3GTC) worksheet


TCP/IPprotocol

TCP/IPstack


15minutes

308 4 x 24 x 308 x 1 x 1 / 1024 1 1 29 KB


KN3 UDP Counter Statistics (KN3GUC) worksheetUse the KN3 UDP Counter Statistics (KN3GUC) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 94. KN3 UDP Counter Statistics (KN3GUC) worksheet

IntervalRecordsize Formula UDP protocol

TCP/IPstack


15minutes

156 4 x 24 x 156 x 1 x 1 / 1024 1 1 15 KB

Manual IP Tunnels (KN3ITM) worksheetUse the Manual IP Tunnels (KN3ITM) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 95. Manual IP Tunnels (KN3ITM) worksheet



Manual IPTunnels


15minutes

392 4 x 24 x 392 x 1 x 1 / 1024 1 1 37 KB

OSA-Express Channels (KN3TCH) worksheetUse the OSA-Express Channels (KN3TCH) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 96. OSA-Express Channels (KN3TCH) worksheet


OSA-Expresschannels TCP/IP stack


15minutes

444 4 x 24 x 444 x 1 x 1 x 1 / 1024 1 1 42 KB

OSA-Express LPARS (KN3TLP) worksheetUse the OSA-Express LPARS (KN3TLP) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 97. OSA-Express LPARS (KN3TLP) worksheet


OSA-ExpressChannels

OSAExpressLPARS

TCP/IPstack


15minutes

134 4 x 24 x 134 x 1 x 16 x 1 / 1024 1 16 1 201


OSA-Express Ports (KN3TPO) worksheetUse the OSA-Express Ports (KN3TPO) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 98. OSA-Express Ports (KN3TPO) worksheet


OSA-Express port TCP/IP stack


15minutes

796 4 x 24 x 796 x 1 x 1 x 1 / 1024 1 1 75 KB

OSA 10 Gigabit Ports Control (KN3TTC) worksheetUse the OSA 10 Gigabit Ports Control (KN3TTC) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 99. OSA 10 Gigabit Ports Control (KN3TTC) worksheet


OSA 10Gigabitportscontrol TCP/IP stack


15minutes

418 4 x 24 x 418 x 1 x 1 x 1 / 1024 1 1 39

OSA 10 Gigabit Ports Errors (KN3TTE) worksheetUse the OSA 10 Gigabit Ports Errors (KN3TTE) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 100. OSA 10 Gigabit Ports Errors (KN3TTE) worksheet


OSA 10Gigabitports errors TCP/IP stack


15minutes

452 4 x 24 x 452 x 1 x 1 x 1 / 1024 1 1 42 KB

OSA 10 Gigabit Ports Summary (KN3TTS) worksheetUse the OSA 10 Gigabit Ports Summary (KN3TTS) worksheet to calculate the amount of DASD requiredby this attribute group in the persistent data store.

Table 101. OSA 10 Gigabit Ports Summary (KN3TTS) worksheet


OSA 10Gigabit port TCP/IP stack


15minutes

508 4 x 24 x 508 x 1 x 1 x 1 / 1024 1 1 48 KB


OSA 10 Gigabit Ports Throughput (KN3TTT) worksheetUse the OSA 10 Gigabit Ports Throughput (KN3TTT) worksheet to calculate the amount of DASDrequired by this attribute group in the persistent data store.

Table 102. OSA 10 Gigabit Ports Throughput (KN3TTT) worksheet


OSA 10Gigabitportsthroughput TCP/IP stack


15minutes

448 4 x 24 x 448 x 1 x 1 x 1 / 1024 1 1 42

OSA-Express3 Ports Control (KN3THC) worksheetUse the OSA-Express3 Ports Control (KN3THC) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 103. OSA-Express3 Ports Control (KN3THC) worksheet


OSA-Express3portscontrol TCP/IP stack


15minutes

418 4 x 24 x 418 x 1 x 1 x 1 / 1024 1 1 39

OSA-Express3 Ports Errors (KN3THE) worksheetUse the OSA-Express3 Ports Errors (KN3THE) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 104. OSA-Express3 Ports Errors (KN3THE) worksheet


OSA-Express3ports errors TCP/IP stack


15minutes

508 4 x 24 x 508 x 1 x 1 x 1 / 1024 1 1 48 KB

OSA-Express3 Ports Summary (KN3THS) worksheetUse the OSA-Express3 Ports Summary (KN3THS) worksheet to calculate the amount of DASD requiredby this attribute group in the persistent data store.

Table 105. OSA-Express3 Ports Summary (KN3THS) worksheet


OSA-Express3port TCP/IP stack


15minutes

620 4 x 24 x 620 x 1 x 1 x 1 / 1024 1 1 58 KB


OSA-Express3 Ports Throughput (KN3THT) worksheetUse the OSA-Express3 Ports Throughput (KN3THT) worksheet to calculate the amount of DASD requiredby this attribute group in the persistent data store.

Table 106. OSA-Express3 Ports Throughput (KN3THT) worksheet


OSA-Express3portsthroughput TCP/IP stack


15minutes

512 4 x 24 x 512 x 1 x 1 x 1 / 1024 1 1 48

TCP Listener (KN3TCL) worksheetUse the TCP Listener (KN3TCL) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 107. TCP Listener (KN3TCL) worksheet


TCPlisteners TCP/IP stack


15minutes

296 4 x 24 x 296 x 1 x 1 / 1024 1 1 28 KB

TCPIP Address Space (KN3TAS) worksheetUse the TCPIP Address Space (KN3TAS) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 108. TCPIP Address Space (KN3TAS) worksheet


TCP/IPaddressspaceresources TCP/IP stack


15minutes

652 4 x 24 x 652 x 1 x 1 / 1024 1 1 61 KB

TCPIP Applications (KN3TAP) worksheetUse the TCPIP Applications (KN3TAP) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 109. TCPIP Applications (KN3TAP) worksheet


TCP/IPapplications

TCP/IPstack


15minutes

684 4 x 24 x 684 x 1 x 1 / 1024 1 1 64 KB


TCPIP Connections (KN3TCN) worksheetUse the TCPIP Connections (KN3TCN) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 110. TCPIP Connections (KN3TCN) worksheet


TCP/IPconnections

TCP/IPstack


15minutes

660 4 x 24 x 660 x 1 x 1 / 1024 1 1 62 KB

TCPIP Details (KN3TCP) worksheetUse the TCPIP Details (KN3TCP) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 111. TCPIP Details (KN3TCP) worksheet


TCPconnections TCP/IP stack

Expectedstoragerequired for 24hours

15minutes

644 4 x 24 x 644 x 1 x 1 / 1024 1 1 60 KB

TCPIP Devices (KN3TDV) worksheetUse the TCPIP Devices (KN3TDV) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 112. TCPIP Devices (KN3TDV) worksheet


TCP/IPdevices TCP/IP stack


15minutes

460 4 x 24 x 460 x 1 x 1 / 1024 1 1 43 KB

TCPIP Gateways (KN3TGA) worksheetUse the TCPIP Gateways (KN3TGA) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 113. TCPIP Gateways (KN3TGA) worksheet

IntervalRecordsize Formula Gateways TCP/IP stack


15minutes

628 4 x 24 x 628 x 1 x 1 x 1 / 1024 1 1 59 KB


TCPIP Memory Statistics (KN3TPV) worksheetUse the TCPIP Memory Statistics (KN3TPV) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 114. TCPIP Memory Statistics (KN3TPV) worksheet


TCP/IPaddressspaces TCP/IP stack


15minutes

500 4 x 24 x 500 x 1 x 1 x 1 / 1024 1 1 47 KB

TCPIP Stack Layer (KN3TSL) worksheetUse the TCPIP Stack Layer (KN3TSL) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 115. TCPIP Stack Layer (KN3TSL) worksheet


TCP/IPaddressspaces TCP/IP stack


15minutes

636 4 x 24 x 636 x 1 x 1 x 1 / 1024 1 1 60 KB

UDP Connections (KN3UDP) worksheetUse the UDP Connections (KN3UDP) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 116. UDP Connections (KN3UDP) worksheet


UDPconnections TCP/IP stack


15minutes

388 4 x 24 x 388 x 1 x 1 / 1024 1 1 36 KB

VTAM historical data storageUse this information to understand the formula for historical collection, the attribute group record sizes,and the space requirements for VTAM historical data storage.v VTAM formula




The following data is collected once every historical collection interval. This data is collected for eachLPAR you will monitor.




Subtotalstoragerequired inKB


VTAM SummaryStatistics

100 1 row 9

Enterprise Extender (EE)and High PerformanceRouting (HPR) statisticscollection

EE Connections 276 1 row per EE connection 26

EE Connections Details 268 5 rows per EE connection 126

HPR RTP Connections 596 1 row per HPR RTP connection 56

Communications StorageManager (CSM) bufferreporting

CSM Storage 204 1 row 19

KN3 CSM Storage byOwner

196 1 row per address space that ownsCSM storage

18

Buffer Pool and VTAMenvironment collection

VTAM Address Space 272 1 row 26

VTAM I/O 100 1 row for each of 6 resources 56

VTAM Buffer Pools 182 1 row for each of 14 resources 239

VTAM Buffer PoolExtents

124 1 row per buffer pool extent 12


100 1 row per address space usingIO00 or CRPL buffers

9

VTAM Buffer Usage byApplication for AddressSpace

108 1 row per application per addressspace using IO00 buffers

10


96 1 row for each of 12 resources 108


Use the worksheets shown in Tables 111 through 121 to estimate the disk space requirements for yoursite. A sample calculation is provided for each historical data collection table.– Each worksheet is for one monitored resource per LPAR.– Typically you are monitoring more than one resource (that is, one connection). You need to multiply

the required storage by the number of resources.

Figure 52. Formula for VTAM historical collection data storage



CSM Storage (KN3CSM) worksheetUse the CSM Storage (KN3CSM) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 118. CSM Storage (KN3CSM) worksheet

Interval Record size FormulaCSM storageresources

Expected storagerequired for 24hours

15 minutes 204 4 x 24 x 204 x 1 x 1/ 1024 1 19 KB

EE Connection Details (KN3EED) worksheetUse the EE Connection Details (KN3EED) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 119. EE Connection Details (KN3EED) worksheet

Interval Record size FormulaEE connectionresources


15 minutes 268 4 x 24 x 268 x 1 x 5 / 1024 1 126 KB

EE Connections (KN3EEC) worksheetUse the EE Connections (KN3EEC) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 120. EE Connections (KN3EEC) worksheet

Interval Record size FormulaEE connectionresources


15 minutes 276 4 x 24 x 276 x 1 x 5 / 1024 1 26 KB

HPR RTP Connections (KN3HPR) worksheetUse the HPR RTP Connections (KN3HPR) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 121. HPR RTP Connections (KN3HPR) worksheet

Interval Record size Formula

HPR RTPconnectionresources


15 minutes 596 4 x 24 x 596 x 1 x 1/ 1024 1 56 KB

KN3 CSM Storage by Owner (KN3CSO) worksheetUse the KN3 CSM Storage by Owner (KN3CSO) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.


Table 122. KN3 CSM Storage by Owner (KN3CSO) worksheet

Interval Record size Formula

CSM Storageby Ownerresources


15 minutes 196 4 x 24 x 196 x 1 x 1/ 1024 1 18 KB

VTAM Address Space (KN3VAS) worksheetUse the VTAM Address Space (KN3VAS) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 123. VTAM Summary Statistics (KN3VAS) worksheet

Interval Record size FormulaVTAM address spaceresources


15 minutes 272 4 x 24 x 272 x 1 / 1024 1 26 KB

VTAM Buffer Pool Extents (KN3BPE) worksheetUse the VTAM Buffer Pool Extents (KN3BPE) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 124. VTAM Buffer Pool Extents (KN3BPE) worksheet

Interval Record size Formula Number of resources


15 minutes 124 4 x 24 x 124 x 1 x 1 / 1024 1 12 KB

VTAM Buffer Pools (KN3BPD) worksheetUse the VTAM Buffer Pools (KN3BPD) worksheet to calculate the amount of DASD required by thisattribute group in the persistent data store.

Table 125. VTAM Buffer Pools (KN3BPD) worksheet



15 minutes 182 4 x 24 x 182 x 14 x 1 / 1024 14 239 KB

VTAM Buffer Usage by Address Space (KN3BPS) worksheetUse the VTAM Buffer Usage by Address Space (KN3BPS) worksheet to calculate the amount of DASDrequired by this attribute group in the persistent data store.

Table 126. VTAM Buffer Usage by Address Space (KN3BPS) worksheet



15 minutes 100 4 x 24 x 100 x 1 x 1 / 1024 1 9 KB


VTAM Buffer Usage by Application for Address Space (KN3BPA) worksheetUse the VTAM Buffer Usage by Application by Address Space (KN3BPA) worksheet to calculate theamount of DASD required by this attribute group in the persistent data store.

Table 127. VTAM Buffer Usage by Application for Address Space (KN3BPA) worksheet



15 minutes 108 4 x 24 x 108 x 1 x 1 / 1024 1 10 KB

VTAM Buffer Usage by Category (KN3BPG) worksheetUse the VTAM Buffer Usage by Category (KN3BPG) worksheet to calculate the amount of DASDrequired by this attribute group in the persistent data store.

Table 128. VTAM Buffer Usage by Category (KN3BPG) worksheet



15 minutes 96 4 x 24 x 96 x 12 x 1 / 1024 12 108 KB

VTAM I/O (KN3VIO) worksheetUse the VTAM I/O (KN3VIO) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 129. VTAM I/O (KN3VIO) worksheet



15 minutes 100 4 x 24 x 100x 6 x 1 / 1024 6 56 KB

VTAM Summary Statistics (KN3SNA) worksheetUse the VTAM Summary Statistics (KN3SNA) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 130. VTAM Summary Statistics (KN3SNA) worksheet

Interval Record size Formula SNA resources


15 minutes 100 4 x 24 x 100 x 1 / 1024 1 10 KB

FTP historical data storageUse this information to understand the formula for historical collection, the attribute group record sizes,and the space requirements for FTP historical data storage.v FTP formula




The following FTP data is collected when a new session or transfer is opened or when an existingsession or transfer is closed. This data is collected when z/OS Communications Server notifies themonitoring agent that there is data available and therefore does not adhere to a collection interval. Forthese three attribute tables, storage per monitored resource is relatively low because only one record isstored per active session or transfer, plus one record per completed session or transfer. However, youmight have thousands of sessions or transfers in 24 hours, and thus storage cost for FTP sessions couldbe significant.FTP data is collected for each TCP/IP stack. If you have LPARs with multiple TCP/IP stacks, total thestorage required for each stack you will monitor.

Table 131. FTP data collected




FTP Data Collection FTP Sessions 412 2 rows per FTP session 0.8 KB

TCPIP FTP 2464 2 rows per FTP transfer 5 KB


Use the worksheets shown in Tables 124 and 125 to estimate the disk space requirements for your site.A sample calculation is provided for each historical data collection table.– Each worksheet applies to one monitored resource per TCP/IP stack.– Typically you are monitoring more than one resource (that is, one session or transfer, for example).

You need to multiply the required storage by the number of resources.– If you are monitoring multiple LPARs, complete a worksheet for each LPAR, or one worksheet that

represents the average LPAR.– If you are monitoring more than one TCP/IP stack in an LPAR and each TCP/IP stack has an FTP

server, multiply by the number of TCP/IP stacks.

FTP Sessions (KN3FSE) worksheetUse the FTP Sessions (KN3FSE) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 132. FTP Sessions (KN3FSE) worksheet

Recordsize Formula FTP sessions TCP/IP stack

Expectedstorage requiredfor 24 hours

412 412 x 1 x 2 x 1 / 1024 1 1 0.8 KB

Figure 53. Formula for FTP historical collection data storage


TCPIP FTP (KN3FTP) worksheetUse the TCPIP FTP (KN3FTP) worksheet to calculate the amount of DASD required by this attributegroup in the persistent data store.

Table 133. TCPIP FTP (KN3FTP) worksheet

Recordsize Formula FTP transfers TCP/IP stack


2464 (2464 x 1 x 2 x 1) / 1024 1 1 5 KB

TN3270 historical data storageUse this information to understand the formula for historical collection, the attribute group record sizes,and the space requirements for 3270 historical data storage.v TN3270 formula

Storage assumptions:– Historical collection interval: 15 minutes– Quantity of each resource types monitored: 1– TN3270 session is active for 8 hours, and then is closed


The TN3270 data provides information about open, closed and active TN3270 sessions for a TCP/IPaddress space. A record is stored for each TN3270 session that closed since historical data was lastcollected or that is active when historical data is collected. The record for a TN3270 session will bestored when new data is available at the time that historical data is collected (i.e. the same, unchangedrecord will not be stored twice). New data is available each collection interval starting when thesession opened until the collection interval after the session closed.Thirty-two (32) records a day (4 per hour for 8 hours) will be stored for each active TN3270 session.

Figure 54. Formula for TN3270 historical collection data storage


Table 134. TN3270 data collected




TN3270 Server StatisticsData Collection

TN3270 Server SessAvail

460 1 row per active TN3270 serversession

+

1 row per closed TN3270 serversession

15 KB


Use the worksheet shown in Table 127 to estimate the disk space requirements for your site. A samplecalculation is provided for each historical data collection table.– Each worksheet is for one monitored resource per TCP/IP stack.– Typically you are monitoring more than one resource (that is, one session). You need to multiply the

required storage by the number of resources.– If you are monitoring multiple LPARs, complete a worksheet for each LPAR, or one worksheet that

represents the average LPAR.– If you are monitoring more than one TCP/IP stack in an LPAR and each TCP/IP stack has a

TN3270 server, multiply by the number of TCP/IP stacks.

TN3270 Server Sess Avail (KN3TNA) worksheetUse the TN3270 Server Sess Avail (KN3TNA) worksheet to calculate the amount of DASD required bythis attribute group in the persistent data store.

Table 135. TN3270 Server Sess Avail (KN3TNA) worksheet

Recordsize Formula

TN3270serversessions TCP/IP stack


460 ((4 x 8 x 460 x 1 x 1 x 1) + (460 x 1 x 1 x 1)) / 1024 1 1 15 KB

OMEGAMON XE for Mainframe Networks disk space summaryworksheetUse this worksheet to summarize the historical database calculations you have made in previous attributegroup-specific worksheets.

The disk space summary worksheet for OMEGAMON XE for Mainframe Networks follows.

Table 136. Disk space summary

Historical attribute tableHistorical attribute table size inKB (for a 24-hour period)

Subtotal of storage required incylinders

Agent Historical Data Collection Interval

Agent Status

SNA Collector Status

TCP Collector Status

TCP/IP and VTAM (required collection

TCPIP Memory Statistics


Table 136. Disk space summary (continued)



TCP/IP Stack Layer Statistics

TCPIP Address Space

KN3 ICMP Global Counters

KN3 ICMP Type Counters

KN3 IP Counter Statistics

KN3 IP General Statistics

KN3 TCP Counter Statistics

KN3 UDP Counter Statistics

TCPIP Stack Layer

Interfaces statistics collection

Intterfaces

KN3 Interface Address

KN3 Interface Statistics

KN3 Interface Status

TCPIP Devices


KN3 Interface Write Queue

OSA statistics collection

OSA-Express Channels

OSA-Express LPARS

OSA-Express Ports

OSA 10 Gigabit Ports Control

OSA 10 Gigabit Ports Errors

OSA 10 Gigabit Ports Summary

OSA 10 Gigabit Ports Throughput

OSA-Express3 Ports Control

OSA-Express3 Ports Errors

OSA-Express3 Ports Summary

OSA-Express3 Ports Throughput

TCP/IP Connection and Application Performance statistics collection

TCPIP Applications

TCPIP Connections

TCPIP Details

TCP Listener

UDP Connections

Routing Table statistics collection

TCPIP Gateways

IPSec Security collection

IPSec Status


Table 136. Disk space summary (continued)



Current IP Filters

Dynamic IP Tunnels

IKE Tunnels

Manual IP Tunnels

VTAM Historical Data Collection Interval

VTAM Summary Statistics

EE Connections

EE Connections Details

HPR RTP Connections

CSM Storage

VTAM Address Space

VTAM I/O

VTAM Buffer Pools

VTAM Buffer Pool Extents

VTAM Buffer Pool Usage by AddressSpace

VTAM Buffer Pool Usage byApplication

VTAM Buffer Pool Usage byCategory

FTP Data Storage

FTP Sessions

TCPIP FTP

TN3270 Data Storage

TN3270 Server Sess Avail

Total Storage Required

Estimating the storage required per LPARThese formulas help you estimate the amount of storage required for historical data tables on a per LPARbasis.

Use the following formula to estimate the cylinders of 3390 DASD required.

If you estimated in cylinders, you can use the following formula:

Figure 55. KB formula for total storage required per LPAR for cylinders of 3390 DASD


Figure 56. Cylinder formula for total storage required per LPAR in cylinders of 3390 DASD



Appendix E. Format of the SNMP configuration file

Since V4.2, SNMP data collection in the OMEGAMON XE for Mainframe Networks monitoring agentwas enhanced to give you greater flexibility when communicating with the SNMP agents.

SNMP data collection supports the use of IPv6 interfaces in the configuration. See “IPv6 considerations”on page 36 for more information.

Before you can use this enhanced SNMP function, you must configure it. This section describes thesyntax of the SNMP manager configuration file.

Note: Do not modify or point your PROCs to this sample copy. This copy will be regenerated when theRTE is loaded. Make a copy of this sample and modify it to your needs.

When to create the SNMP configuration fileCreate your site's SNMP configuration file after you run the Configuration Tool or PARMGEN, but beforeyou start the OMEGAMON XE for Mainframe Networks monitoring agent.

Sample files are generated by the Configuration Tool when the Create Runtime Members job is run andare stored in &hilev.&midlev.&rtename.RKANSAMU. These sample files are named KN3SNMP (forOMEGAMON XE for Mainframe Networks) and KONSNMP (for the OMEGAMON II for MainframeNetworks component).

For PARMGEN, the sample files are created when you run the KCIJPW2R JCL job. The members arestored in &hilev.&midlev.&rtename.RKANSAMU. These sample files are named KN3SNMP (forOMEGAMON XE for Mainframe Networks) and KONSNMP (for the OMEGAMON II for MainframeNetworks component).

The SNMP configuration file can be a sequential data set or a member of a partitioned data set. TheSNMP configuration file does not have to have the same attributes as the &rhilev.&midlev.&rtename.RKANSAMU data set. The data set might have fixed or variable record format with a recordlength of up to and including 2048 bytes.

Format of the SNMP manager configuration fileInformation entered into the SNMP configuration file should be in this format.

For each SNMP agent with which OMEGAMON XE for Mainframe Networks or OMEGAMON II forMainframe Networks will communicate when monitoring one or more TCP/IP stacks, you must add aline to the SNMP manager configuration files in the format shown in the following section:ip_address port_number snmp_version community_name

Where:

ip_addressIs the IP address of the SNMP agent associated with the TCP/IP stack being monitored. InOMEGAMON XE for Mainframe Networks, the IP address can be an IPv6 address. Thisparameter is required because there is no default value.

port_numberIs the port number on which the SNMP agent is listening for SNMP requests. The port number


can be between 1-65535, inclusive. The parameter is required, but a hyphen (dash) may be codedto indicate that the default value of 161 is to be used.

snmp_versionIs the version of SNMP protocol to be used when communicating with the SNMP agent. Thisparameter is required as there is no default value. Code snmpv2.

community_nameIs the community name (password) to be used to request data from the SNMP agent. The value isa character string that is between 1 and 255 characters, inclusive, in length. This parameter isrequired, but a hyphen (dash) may be coded to indicate that the default value of public is to beused.

Note: You can share the same SNMP configuration file between OMEGAMON II for MainframeNetworks and OMEGAMON XE for Mainframe Networks. Sharing the same SNMP configuration filecould make it easier for an administrator to maintain the list of TCP/IP stacks that each application isconfigured to monitor. A shared configuration can be achieved by altering either the KN3SNMP DD cardOMEGAMON XE for Mainframe Networks start procedure or the KONSNMP DD card in theOMEGAMON II for Mainframe Networks start procedure to use the same SNMP configuration file. Notethat OMEGAMON II for Mainframe Networks has no IPv6 support, so entries with IPv6 addresses areonly read and checked for syntax, not used by OMEGAMON II for Mainframe Networks to obtain SNMPagent information.

When creating this configuration file, these rules apply:v All parameters for an entry must be contained on one line in the configuration file.v You may insert comments into this file. Comments begin with a # character in column 1.

Sample configuration fileHere is a sample configuration file:000001 #######################################################################000002 # Licensed Materials - Property of IBM #000003 # 5698-A35 #000004 # (C) Copyright IBM Corporation 2006. All rights reserved. #000005 # #000006 # US Government Users Restricted Rights - Use, duplication or #000007 # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. #000008 #######################################################################000009 # #000010 # KN3SNMP - Sample SNMP Configuration File #000011 # #000012 # This sample provides information for configuring SNMP manager #000013 # functions used by TCP/IP data collection. The entries define SNMP #000014 # agents with which the SNMP manager functions may communicate. They #000015 # also provide additional information to enable the communication. #000016 # #000017 # It is possible to share the same SNMP configuration file between #000018 # OMEGAMON II for Mainframe Networks and OMEGAMON XE for Mainframe #000019 # Networks. Sharing the same SNMP configuration file could make #000020 # it easier for an administrator to maintain the list of TCP/IP #000021 # stacks that each application is configured to monitor. A shared #000022 # configuration can be achieved by altering either the KN3SNMP DD #000023 # in card OMEGAMON XE for Mainframe Networks start procedure or the #000024 # KONSNMP DD card OMEGAMON II for Mainframe Networks start procedure #000025 # to use the same SNMP configuration file. OMEGAMON II for Mainframe #000026 # Networks has no IPV6 support, so entries with IPv6 addresses are #000027 # only read and checked for syntax, not used by OMEGAMON II for #000028 # Mainframe Networks to obtain SNMP agent information. #000029 # #000030 # This file may have fixed or variable record format and a record #000031 # length up to and including 2048 bytes. #


000032 # #000033 # The rules for the entries in this file are as follows. #000034 # #000035 # - Comments begin with a # character in column 1 #000036 # - All parameters for an entry must be contained on one line #000037 # #000038 # An entry in this file is made up of the following positional #000039 # parameters. #000040 # #000041 # - SNMP agent address #000042 # #000043 # IP address of an SNMP agent with which the SNMP manager #000044 # functions of TCP/IP data collection may communicate. #000045 # This parameter is required and there is no default value. #000046 # #000047 # - SNMP agent port number #000048 # #000049 # Port number on which an SNMP agent is listening for #000050 # requests. The value may be between 1 and 65535, inclusive. #000051 # This parameter is required; however, a dash (-) may be #000052 # coded to indicate that the conventional SNMP request #000053 # port number 161 is to be used. #000054 # #000055 # - SNMP version #000056 # #000057 # Version of the SNMP protocol whose requests are being used #000058 # to communicate with an SNMP agent. This parameter is #000059 # required. "snmpv2" is the only supported value. #000060 # #000061 # - Community name #000062 # #000063 # The community name (password) to be used in requests sent to #000064 # an SNMP agent. The value may be between 1 and 255 #000065 # characters, inclusive, in length. This parameter is #000066 # required; however, a dash (-) may be coded to indicate that #000067 # the default community name of "public" is to be used. #000068 # #000069 # Sample definitions for SNMP agents appear below. They are for #000070 # illustrative purposes only. #000071 # #000072 # CHANGE ACTIVITY #000073 # --------------- #000074 # #000075 # ID Reason Date Author Description #000076 # ---- -------- -------- ------ --------------------------------- #000077 # #000078 #######################################################################000079 10.10.3.72 2161 snmpv2 public000080 10.10.3.73 - snmpv2 -000081 FF01::0001 8161 snmpv2 publicv6000082 FE80:1234:5678:9ABC:DEF0:1234:5678:9ABC 65161 snmpv2 -

Appendix E. Format of the SNMP configuration file 291


Documentation library

This appendix contains information about the publications related to IBM Tivoli Monitoring and to thecommonly shared components of Tivoli Management Services.

These publications are listed in the following categories:v “IBM Tivoli OMEGAMON XE for Mainframe Networks publications”v “OMEGAMON XE and Tivoli Management Services on z/OS common library” on page 294v IBM Tivoli Monitoring libraryv “Related publications” on page 296

See the IBM Tivoli Monitoring Documentation Guide for information about accessing and using thepublications. You can find the Documentation Guide in the IBM Tivoli Monitoring and OMEGAMON XEInformation Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp. To open theDocumentation Guide in the information center, select Using the publication in the Contents pane.

To find a list of new and changed publications, click What's new on the Welcome page of the IBM TivoliMonitoring and OMEGAMON XE Information Center. To find publications from the previous version ofa product, click Previous versions under the name of the product in the Contents pane.

IBM Tivoli OMEGAMON XE for Mainframe Networks publicationsThe following publications provide information common to the OMEGAMON XE products.v IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide, SC27-4447

Summarizes the planning and configuration tasks for the OMEGAMON XE for Mainframe Networksand the OMEGAMON II for Mainframe Networks monitoring agents.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference, SC27-4449Provides a reference guide for using the PARMGEN method of installation to configure OMEGAMONXE for Mainframe Networks and the OMEGAMON II for Mainframe Networks monitoring agents.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide, SC27-4446Introduces the features, workspaces, attributes, and predefined situations for the OMEGAMON XE forMainframe Networks product and supplements the user assistance provided with this product. Thisdocument is written for network operators.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User Interface Guide, SC27-4450Provides workspace names and descriptions, navigation, and scenarios for the Enhanced 3270 UserInterface, a z/OS-based interface that supports Enterprise and cross-product views of the informationtypes monitored by OMEGAMON XE for Mainframe Networks: TCP/IP stack layers, applications, TCPlisteners, interfaces, OSA, and TN3270.

v IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide, SC27-4448Provides explanations for the messages issued by the OMEGAMON XE for Mainframe Networksproduct, OMEGAMON II for Mainframe Networks component, and problem determinationinformation.

v OMEGAMON II for Mainframe Networks: User's Guide, GC32-9274-00,Provides information about using the OMEGAMON II CUA interface to monitor the SNA elements inyour network and tune VTAM, your NCPs and the PUs and LUs connected to them.

v OMEGAMON II for Mainframe Networks: Historical Reporting Guide, GC32-9272-00Describes how to produce reports or graphs of network usage and activity over selected time periods.This book explains how to use the SMF records created by OMEGAMON II for Mainframe Networks



to produce reports and graphs with SAS and view SAS graphs. It also describes the SAS samplereports that the product provides. This book is intended for a network performance analyst, networkcapacity planner, or network designer.

v OMEGAMON II for Mainframe Networks: NCP Monitoring Guide, GC32-9273-00Explains how to use the NCP Monitor component of OMEGAMON II for Mainframe Networks tomonitor and tune your network, including your NCPs and the PUs and LUs connected to them. Thisguide also describes how to set NCP monitoring options and thresholds.

OMEGAMON XE and Tivoli Management Services on z/OS commonlibraryThe following publications provide information that is common to the OMEGAMON XE products:v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Quick Start Guide,GI11-8918

Describes the procedure for installing a new monitoring agent on z/OS. If you are upgrading amonitoring agent and Tivoli Management Services, refer to the OMEGAMON XE and Tivoli ManagementServices on z/OS: Upgrade Guide.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Parameter Reference Guide,SC14-7280

Provides reference information about the parameters that are used for setting and storing configurationvalues for the common components of Tivoli Management Services on z/OS and for the runtimeenvironments in which the OMEGAMON XE monitoring agents are configured.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Common Planning and ConfigurationGuide,SC23-9734

Gives instructions for planning and configuration tasks common to the components of TivoliManagement Services on z/OS and the OMEGAMON XE monitoring agents on z/OS.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Upgrade Guide,SC23-9745

Gives instructions for complete and staged upgrades to V5.1.0 of the OMEGAMON XE products.v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: PARMGEN Reference,SC22-5435

Gives common scenarios that you can reference when using the PARMGEN configuration methodwhen using V5.1.0 of the OMEGAMON XE products.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: OMEGAMON Enhanced 3270 UserInterface Guide,SC22-5426

Describes the features of the interface and provides operating instructions and reference material.v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: End-to-End Response Time Feature

Reference,SC27-2303

Provides instructions and reference information for the End-to-End Response Time Feature, whichsupplies response time data to several OMEGAMON XE products.

v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/OS: Reports for Tivoli CommonReporting,SC27-2304

Explains how to use the Tivoli Common workspacing tool to create workspaces from data displayed inthe Tivoli Enterprise Portal and stored in the Tivoli Data Warehouse database.

IBM Tivoli Monitoring libraryThe following publications provide information about IBM Tivoli Monitoring and about the commonlyshared components of Tivoli Management Services:v Quick Start Guide

Introduces the components of IBM Tivoli Monitoring.v Installation and Setup Guide, GC32-9407

Provides instructions for installing and configuring IBM Tivoli Monitoring components on Windows,Linux, and UNIX systems.


v Program Directory for IBM Tivoli Management Services on z/OS, GI11-4105Gives instructions for the SMP/E installation of the Tivoli Management Services components on z/OS.

v Configuring the Tivoli Enterprise Monitoring Server on z/OS, SC27-2313Provides instructions for preparing, configuring, and customizing your monitoring servers on z/OS.This guide complements the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OSCommon Planning and Configuration Guide and the IBM Tivoli Monitoring Installation and Setup Guide.

v High Availability Guide for Distributed Systems, SC23-9768Gives instructions for several methods of ensuring the availability of the IBM Tivoli Monitoringcomponents.

v IBM Tivoli zEnterprise Monitoring Agent Installation and Configuration Guide, SC14-7358Provides instructions for installing and configuring Tivoli zEnterprise® monitoring agent componentson Windows, Linux, and UNIX systems. Also includes migration and backup information, EnterpriseCommon Collector troubleshooting, Hardware Management Console configuration, and use of thecommand line interface or APIs to customize the collector. This guide complements the TivolizEnterprise Monitoring Agent User’s Guide.

v Administrator's Guide, SC32-9408Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,including Tivoli Enterprise Portal user administration.

v Command Reference, SC32-6045Provides detailed syntax and parameter information, as well as examples, for the commands you canuse in IBM Tivoli Monitoring.

v Messages, SC23-7969Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-basedTivoli Management Services components (such as Tivoli Enterprise Monitoring Server on z/OS andTMS:Engine).

v Troubleshooting Guide, GC32-9458Provides information to help you troubleshoot problems with the software.

v Tivoli Enterprise Portal online helpProvides context-sensitive reference information about all features and customization options of theTivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli EnterprisePortal.

v Tivoli Enterprise Portal User's Guide, SC32-9409Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons anddetailed instructions for all Tivoli Enterprise Portal features.

v Agent Builder User's Guide, SC32-1921Explains how to use the Agent Builder for creating monitoring agents and their installation packages,and for adding functions to existing agents.

v Tivoli Universal Agent User’s Guide, SC32-9459Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM TivoliUniversal Agent enables you to use the monitoring and automation capabilities of IBM TivoliMonitoring to monitor any type of data you collect.

v Performance Analyzer User’s Guide, SC27-4004Explains how to use the Performance Analyzer to understand resource consumption trends, identifyproblems, resolve problems more quickly, and predict and avoid future problems.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and providesdescriptions, syntax, and return status codes for the API calls and command-line interface commands.

v IBM Tivoli zEnterprise Monitoring Agent User’s Guide, SC14-7359

Documentation library 295

Complements the Tivoli zEnterprise monitoring agent online help. The guide provides referenceinformation about the interface, usage scenarios, agent troubleshooting information, and informationabout Tivoli Common Reporting reports. This guide complements the Tivoli zEnterprise MonitoringAgent Installation and Configuration Guide.

Documentation for the base agentsIf you purchased IBM Tivoli Monitoring as a product, you received a set of base monitoring agents aspart of the product. If you purchased a monitoring agent product (for example, an OMEGAMON XEproduct) that includes the commonly shared components of Tivoli Management Services, you did notreceive the base agents.

The following publications provide information about using the base agents.v Operating system agents:

– Windows OS Agent User's Guide, SC32-9445– UNIX OS Agent User's Guide, SC32-9446– Linux OS Agent User's Guide, SC32-9447– i5/OS Agent User's Guide, SC32-9448– UNIX Log Agent User's Guide, SC32-9471

v Agentless operating system monitors:– Agentless Monitoring for Windows Operating Systems User's Guide, SC23-9765– Agentless Monitoring for AIX Operating Systems User's Guide, SC23-9761– Agentless Monitoring for HP-UX Operating Systems User's Guide, SC23-9763– Agentless Monitoring for Solaris Operating Systems User's Guide, SC23-9764– Agentless Monitoring for Linux Operating Systems User's Guide, SC23-9762

v Warehouse agents:– Warehouse Summarization and Pruning Agent User's Guide, SC23-9767– Warehouse Proxy Agent User's Guide, SC23-9766

v System P agents:– AIX Premium Agent User's Guide, SA23-2237– CEC Base Agent User's Guide, SC23-5239– HMC Base Agent User's Guide, SA23-2239– VIOS Premium Agent User's Guide, SA23-2238

v Other base agents:– Tivoli Log File Agent User’s Guide, SC14-7484– Systems Director base Agent User’s Guide, SC27-2872– Monitoring Agent for IBM Tivoli Monitoring 5.x Endpoint User's Guide, SC32-9490

Related publicationsYou can find useful information about related products in the IBM Tivoli Monitoring and OMEGAMONXE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp.

Other sources of documentationYou can also obtain technical documentation about IBM Tivoli Monitoring and related products from thefollowing sources:v Service Management Connect

http://www.ibm.com/software/brandcatalog/ismlibrary/



http://www.ibm.com/developerworks/servicemanagement

Connect, learn, and share with Service Management professionals. Get access to developers andproduct support technical experts who provide their perspectives and expertise. Using SMC, you can:– Become involved with transparent development, an ongoing, open engagement between external

users and developers of Tivoli products where you can access early designs, sprint demos, productroadmaps, and pre-release code.

– Connect one-on-one with the experts to collaborate and network about Tivoli and Integrated ServiceManagement. Find matching user profiles.

– Benefit from the expertise and experience of others using blogs– Collaborate with the broader user community using wikis and forums

v IBM Integrated Service Management Libraryhttp://www.ibm.com/software/brandcatalog/ismlibrary/IBM Integrated Service Management Library is an online catalog that contains integrationdocumentation and other downloadable product extensions.

v Redbooks®

http://www.redbooks.ibm.com/IBM Redbooks and Redpapers include information about products from platform and solutionperspectives.

v TechnotesTechnotes provide the latest information about known product limitations and workarounds. You canfind Technotes through the IBM Software Support Web site at http://www.ibm.com/software/support/.

v Tivoli wikis on the IBM developerWorks® Web siteTivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the homefor interactive wikis that offer best practices and scenarios for using Tivoli products. The wikis containwhite papers contributed by IBM employees, and content created by customers and business partners.Two of these wikis are of particular relevance to IBM Tivoli Monitoring:– Tivoli Distributed Monitoring and Application Management Wiki at http://www.ibm.com/

developerworks/wikis/display/tivolimonitoring/Home provides information about IBM TivoliMonitoring and related distributed products, including IBM Tivoli Composite ApplicationManagement products.

– Tivoli System z® Monitoring and Application Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home provides information about theOMEGAMON XE products, NetView for z/OS, Tivoli Monitoring Agent for z/TPF, and otherSystem z monitoring and application management products.

Documentation library 297

http://www-01.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

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

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

http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

http://www.ibm.com/developerworks/wikis/display/tivolimonitoring/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home


Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides thefollowing ways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/support/servicerequest and followthe instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceability workbench that helps youresolve questions and problems with IBM software products. The ISA provides quick access tosupport-related information and serviceability tools for problem determination. To install the ISAsoftware, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the product's Troubleshooting Guide.


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

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


Index

Numerics3270 interface 2

Aabend S306 173accessibility features 303activate

dedicated terminal 194activating the VTAM major node for

OMEGAMON II 198adding support for the SYSTCPD

DDNAME in the started tasks 131adding support for the SYSTCPD

DDNAME in the started tasks forOMEGAMON II 177

Agent historical data storageattribute group record sizes 263formula 263

agent started task 105Agent Status workspace 149allocating

terminal dynamically 194allocating additional runtime data sets for

OMEGAMON II 168APF

authorization 173APF-authorizing your libraries 133, 173applid 92applid, NCP collector 187assembling and link editing the LU 6.2

logon mode table for OMEGAMONII 172

attribute group record sizesAgent 263FTP 281TCP/IP 265TN3270 283VTAM 277

Attribute updates 23authorizing agent started tasks for

TCP/IP privileges 137, 175authorizing users 191

external function level security 193autonomous agents

Enabling SNMP V3 passwords forautonomous agents 141

Bbatch processing

relinking the runtime environmentsafter in OMEGAMON II 178

CCannot find previous PARMLIB

configuration session information 84CAT and ATTR files 139

changes, exception record 195changing the parameters after you exit

the Configuration Tool forOMEGAMON II 183

CL jobsrunning 90

cloning a configuration toolenvironment 70

cloning an existing SMP/Eenvironment 70

CNM application 92collection interval

by LPAR 41defining 46for new sessions or transfers 41impact on performance 41

collection, NCP data 186X.25 186

commands 203general syntax 204KN3FCCMD HELP 204KN3FCCMD INSTALL FPCT 206KN3FCCMD INSTALL FPON 206KN3FCCMD INSTALL SEMV 207KN3FCCMD INSTALL SEVT 207KN3FCCMD INSTALL TCPC 207KN3FCCMD START CONN 208KN3FCCMD START CSM 210KN3FCCMD START DBUG 211KN3FCCMD START EEHPR 214KN3FCCMD START FPT 215KN3FCCMD START GLBS 216KN3FCCMD START INTE 217KN3FCCMD START INTS 218KN3FCCMD START IPSEC 220KN3FCCMD START OSA 221KN3FCCMD START ROUTE 222KN3FCCMD START SNAC 223KN3FCCMD START TCPC 225KN3FCCMD START TN3270 229KN3FCCMD STATUS DBUG 231KN3FCCMD STATUS FCPT 231KN3FCCMD STATUS FPON 232KN3FCCMD STATUS SEMV 232KN3FCCMD STATUS SEVT 232KN3FCCMD STATUS SNAC 233KN3FCCMD STATUS TCPC 233KN3FCCMD STOP CONN 234KN3FCCMD STOP CSM 236KN3FCCMD STOP DBUG 237KN3FCCMD STOP EEHPR 238KN3FCCMD STOP FTP 239KN3FCCMD STOP GLBS 240KN3FCCMD STOP INTE 241KN3FCCMD STOP INTS 242KN3FCCMD STOP IPSEC 244KN3FCCMD STOP OSA 245KN3FCCMD STOP ROUTE 246KN3FCCMD STOP TCPC 247KN3FCCMD STOP TN3270 252

Common features of all version 5.1.0OMEGAMON monitoring agents 20

Communications Storage Managerbuffer reporting 92

community name 200complete the configuration

OMEGAMON II 171completing the configuration

OMEGAMON XE for MainframeNetworks

completing the configuration 127components of OMEGAMON II for

Mainframe Networks 155configuration 159

adding support for the SYSTCPDDDNAME in the started tasks 131,177

adding TCP/IP-specific collectionparameters for the monitoringagent 92

APF-authorizing your libraries 133,173

assembling and link editing the LU6.2 logon mode table 172

authorizing agent started tasks forTCP/IP privileges 137, 175

changing the parameters after you exitthe Configuration Tool 183

completing for the monitoringagent 124

completing outside the ConfigurationTool

adding support for the SYSTCPDDDNAME in the startedtasks 131, 177

APF-authorizing yourlibraries 133, 173



changing the parameters after youexit the Configuration Tool 183

configuring the OMEGAMON IISNMP manager functions 176

configuring TNSTATs 178copying the started task

procedures to you procedurelibrary 132, 172

copying the VTAM definition toVTAMLST 133

copying the VTAM definitions toVTAMLST 172

defining monitoring agent accessto the network monitoringinterface and commands 128

enabling CSA tracking to displayTCP/IP CSA usage 136, 178

enabling historical data storemaintenance 134


configuration (continued)completing outside the Configuration

Tool (continued)enabling security at Tivoli

Enterprise Portal 139, 140enabling Warehouse agents on a

z/OS hub monitoringserver 138

giving users authorization andresource access to run the VARYTCPIP DROP command 130

making the performance monitorinterface (PMI) exit available toVTAM 135, 173

operating systemconsiderations 147

performing agent-specific securityconfiguration 128

relinking the runtimeenvironments after batchprocessing 178

running the ITMSUPER Tools 135setting the dispatching

priority 174completing outside the Configuration

Tool or PARMGENconfiguring SNMP manager

functions 136configuring SNMP manager

functions 136configuring the enhanced 3270 user

interface using PARMGEN 78configuring the enhanced 3270 user

interface using the ConfigurationTool 87


configuring the persistent data storefor the monitoring agent 119

configuring TNSTATs 178copying the started task procedures to

your procedure library 132, 172copying the VTAM definition to

VTAMLST 133copying the VTAM definitions to

VTAMLST 172creating runtime members for the

monitoring agent 118defining monitoring agent access to

the network monitoringinterface 128

dynamic, NCP 185enabling CSA tracking to display

TCP/IP CSA usage 136, 178enabling historical data store

maintenance 134enabling security at Tivoli Enterprise

Portal 139, 140enabling Warehouse agents on a z/OS

hub monitoring server 138giving users authorization and

resource access to run the VARYTCPIP DROP command 130

historical data collection 137KONFCCMD usage 253

configuration (continued)making the performance monitor

interface (PMI) exit available toVTAM 135, 173

NCP generation 187NPALU macro definitions 187OMEGAMON II for Mainframe

Networksallocating additional runtime data

sets 168components 155creating runtime members 169loading the runtime libraries and

exiting the ConfigurationTool 170

OMEGAMON II for MainframeNetworks monitoring agent 89

operating system considerations 147performing agent-specific security

configuration 128recommended 75relinking the runtime environments

after batch processing 178running the ITMSUPER Tools 135setting the dispatching priority 174SMF consideration 195specifying agent address space

parameters 105specifying communication protocols

for the monitoring agent 105specifying configuration values for the

monitoring agent 92specifying dynamic terminal

integration parameters 117Tivoli OMEGAMON XE for

Mainframe Networks monitoringagent 87

updating global default values for themonitoring agent 92

verifying 140configuration planning 39configuration profile 79Configuration Tool

abbreviations 36configuring the enhanced 3270 user

interface 87Load all product libraries after

SMP/E 124panels

Add TCP/IP monitored systemsinfo2 101


add TCP/IP monitored systemsinformation 101

allocate persistent data storemenu 119

configure OMEGAMON XE forMainframe Networks 91

persistent data storespecifications 119

product component selectionmenu 91, 160

Specify advanced agentconfiguration values panel 112

specify agent address spaceparameters 105

Configuration Tool (continued)panels (continued)

Specify Agent IP.UDPConfiguration Values panel 105

Specify Agent SNA ConfigurationValues 111

specify component configuration(page 2) 92



specify configurationparameters 92

specify persistent data store valuesfor the monitoring agent 119

specify TCP/IP componentconfiguration 92

specify TCP/IP monitored systeminformation 92

Specify VTAM applid values /RTE (Page 5) 92

SNMP configuration 92tasks performed outside the

configuration tool for OMEGAMONII 171

Configuration Tool configurationOMEGAMON II for Mainframe

Network 159, 162configuration tool environment

cloning 70configuring SNMP manager




configuring the OMEGAMON II SNMPmanager functions for OMEGAMONII 176

configuring TNSTATs 178CONN component

z/OS MODIFY commands 203control points 190controlling ETE 189copying the started task procedures to

you procedure library 132, 172copying the VTAM definition to


VTAMLST for OMEGAMON II 172CPU usage

monitoring networks on z/OS 39reducing

by changing routing tablecollection frequency 46

by decreasing the frequency ofdata collect 46

creating runtime members forOMEGAMON II 169

CSA usage 136, 178CSM buffer reporting 92CSM component

z/OS MODIFY commands 203CSM Storage (CSM) (KN3CSM) historical

data storage worksheet 279


Current IP Filters (KN3IFC) worksheethistorical data storage worksheet 268

customizationconsole support 201dedicated mode 194End-to-End 189NCP definitions 186security 190

Cylindersdefaults 258definition 258

Ddata collection

changing collection options 53reducing frequency 46verifying 149, 151

data collection, NCP 185deactivate dedicated terminal 195deallocate terminal dynamically 195debugging 211, 231, 237DEDICATE command 194, 195dedicated mode 194dedicated terminal, activate 194define terminal at startup 194defining a SAF general resource

class 141defining display intervals 47defining monitoring agent access to the

network monitoring interface andcommands 128

defining RACF resources usingICHERCDE 193

defining the NAM user ID andpassword 199

direct ETE command to ETE version 197disabling

End-to-End 190disabling NCP data collection 188disk space requirements for historical

data tables 257, 284per LPAR 286

display interval 92defining 47

DLC Interface Collection Override 101DUPLEX parameter, NCP gen 186dynamic configuration, NCP 185Dynamic IP Tunnels (KN3ITD)

worksheet 268dynamic terminal

allocation 194deallocation 195

dynamic terminal integration parametersconfiguration 117

EEE Connection Details (KN3EED)

historical data storage worksheet 279EE Connections (KN3EEC) historical data

storage worksheet 279EEHPR component

z/OS MODIFY commands 203enabling

End-to-End 189

enabling CSA tracking to display TCP/IPCSA usage 136, 178


enabling NCP data collection 188enabling OMEGAMON II console

support 201enabling security 140enabling security at Tivoli Enterprise

Portal 139, 140Enabling SNMP V3 passwords for

autonomous agents 141enabling TCP/IP data collection on

OMEGAMON II 200enabling Warehouse agents on a z/OS

hub monitoring server 138encrypted security, NAM 190End-to-End

considerations 189disabling 190multiple systems

NPM considerations 197NPM considerations 197quiesce 196rules 189running multiple copies 197

NPM considerations 197start 196

multiple systems 197SYSTEMS argument 196variable $$ETE 189

End-to-End Response Time 155enhanced 3270 interface 2Enhanced 3270 interface 20Enterprise Extender

statistics collection 92ETE 155, 189

NPM considerations 197ETE command

direct to ETE version 197exception

record changes 195settings 201

external security resource class 192external security resource names 192

Ffile format 289finalizing security 190FPCT parameter 253FPON parameter 253FTP

data display collection 92data display interval 92

FTP and TN3270 historical datastorage 263

FTP collection override 101FTP component

z/OS MODIFY commands 203FTP display interval override 101FTP historical data storage

attribute group record sizes 281formula 281space requirement worksheets 281

TCPIP FTP (KN3FTP)worksheet 283

FTP historical data storage (continued)space requirement worksheets

(continued)TN3270 Sessions (KN3FSE)

worksheet 282FTP monitoring

enabling 59FTP Sessions (KN3FSE) historical data

storage worksheet 282function level security 192, 200functions secured externally 192

GGBL_USER_JCL field 84generation parameters, NCP 186

X.25 186giving users authorization and resource

access to run the VARY TCPIP DROPcommand 130

GLBS componentz/OS MODIFY commands 203

Group Count parameter 257applying a Group Count factor 258

example analysis 258examples 258

defaults 258definition 258specifying for the monitoring

agent 119

Hhardware

prerequisites 8required 8

high availability hub monitoring server,configuring 68

High Performance Routing 92statistics collection 92

historical data collection 48, 137attributes groups that impact

performance 50changing the default value for

short-term history from 24hours 53

configuring 137estimating tools 263


TCP/IP historical datastorage 263

VTAM historical data storage 263installation 137long-term 48

row of data defined 260maintaining data stores 50rate of accumulation 49short-term 48

function 258row of data defined 260

types of data to collect 50historical data storage

Agent 263attribute group record sizes 263

FTP 263, 281

Index 303

historical data storage (continued)attribute group record sizes 281

TCP/IP 263attribute group record sizes 265

TN3270 263, 283attribute group record sizes 283

VTAM 263, 277attribute group record sizes 277

historical data store maintenance 134historical data tables 261

determining storagerequirements 257, 261

allocating additional storage anddata sets 258

estimating approach 258trial and error approach 258

disk space requirements 257disk space summary worksheet 284

totaling storage per LPAR 286estimating space requirements 260formula for totaling storage per

LPAR 286Group Count parameter 257

historical reportingSMF 196

HPRrouting table collection

frequency 101HPR RTP Connections (KN3HPR)

historical data storage worksheet 279

IIBM Support Assistant 299IBM Tivoli OMEGAMON XE for

Mainframe Networksintegration 5integration with other product 5interoperability 5

ICHERCDE 193IKE Tunnels (KN3ITI) worksheet 269initialization

error 173initializing the OMEGAMON II NAM

database 199INSTALL parameter 253installation 1

command KONFCCMD 253historical data collection 137verification 196

INTE componentz/OS MODIFY commands 203

Interface Collection Override 101Interfaces (KN3TIF) historical data

storage worksheet 268interoperability with other products 5INTERVAL parameter 195interval, dedicated mode polling 195INTS component

z/OS MODIFY commands 203IP filters

collection override 101IP tunnels

collection override 101IP.PIPE 105IP.SPIPE 105IP.UDP 105

IP6.PIPE 105IP6.SPIPE 105IP6.UDP 105IPSec component

z/OS MODIFY commands 203IPSec monitoring

enabling 59IPv4

workspaces mapping IPv4 address toIPv6 36

IPv6 36ISA 299

Kkeywords, NCP macro 186KN3 Agent Status (KN3AGS) historical

data storage worksheet 265KN3 CSM Storage by Owner (KN3CSO)

historical data storage worksheet 280KN3 ICMP Global Counters (KN3GCG)

historical data storage worksheet 269KN3 ICMP Type Counters (KN3GCT)

historical data storage worksheet 269KN3 Interface Address (KN3IFA)

historical data storage worksheet 270KN3 Interface Read Queue (KN3IFR)

historical data storage worksheet 270KN3 Interface Statistics (KN3IFS)

historical data storage worksheet 270KN3 Interface Status (KN3IFE) historical

data storage worksheet 270KN3 Interface Write Queue (KN3IFW)

historical data storage worksheet 271KN3 IP Counter Statistics (KN3GIC)

historical data storage worksheet 271KN3 IP General Statistics (KN3GIG)

historical data storage worksheet 271KN3 SNA Collector Status (KN3SCS)

historical data storage worksheet 265KN3 TCP Collector Status (KN3TCS)

historical data storage worksheet 265KN3 TCP Counter Statistics (KN3GTC)

historical data storage worksheet 271KN3 UDP Counter Statistics (KN3GUC)

historical data storage worksheet 272KN3FCCMD command reference 203KN3FCCMD HELP command 204KN3FCCMD INSTALL FPCT

command 206KN3FCCMD INSTALL FPON

command 206KN3FCCMD INSTALL SEMV

command 207KN3FCCMD INSTALL SEVT

command 207KN3FCCMD INSTALL TCPC

command 207KN3FCCMD START CONN

command 208KN3FCCMD START CSM command 210KN3FCCMD START DBUG

command 211KN3FCCMD START EEHPR

command 214KN3FCCMD START FTP command 215

KN3FCCMD START GLBScommand 216

KN3FCCMD START INTEcommand 217

KN3FCCMD START INTScommand 218

KN3FCCMD START IPSECcommand 220

KN3FCCMD START OSA command 221KN3FCCMD START ROUTE

command 222KN3FCCMD START SNAC

command 223KN3FCCMD START TCPC

command 225KN3FCCMD START TN3270

command 229KN3FCCMD STATUS DBUG

command 231KN3FCCMD STATUS FCPT

command 231KN3FCCMD STATUS FPON

command 232KN3FCCMD STATUS SEMV

command 232KN3FCCMD STATUS SEVT

command 232KN3FCCMD STATUS SNAC

command 233KN3FCCMD STATUS TCPC

command 233KN3FCCMD STOP CONN

command 234KN3FCCMD STOP CSM command 236KN3FCCMD STOP DBUG

command 237KN3FCCMD STOP EEHPR

command 238KN3FCCMD STOP FPT command 239KN3FCCMD STOP GLBS command 240KN3FCCMD STOP INTE command 241KN3FCCMD STOP INTS command 242KN3FCCMD STOP IPSEC command 244KN3FCCMD STOP OSA command 245KN3FCCMD STOP ROUTE

command 246KN3FCCMD STOP TCPC command 247KN3FCCMD STOP TN3270

command 252KN3LINK 147KN3UAUTH 65

editing and submitting 128KONCTNPA member 187KONFCCMD command 188, 253

syntax 253KONFCCMD command reference 203KONFCCMD commands

examples 255introduction 253

KONINNAM member 190, 191KONSTKON member 194

Llanguage support 139libraries

APF-authorize 173


libraries (continued)OMEGAMON II for Mainframe

Networks 293OMEGAMON XE for Mainframe

Networks 293RKANPARU 190, 191

line utilization 186Load all product libraries after

SMP/E 124loading the runtime libraries and exiting


LOCALID parameter 253LOGAPPL Keyword 187logon, OMEGAMON II 200LUGROUP 124

Mmacro

NCP gen keywords 186NPALU definition 187

making the performance monitorinterface (PMI) exit available toVTAM 135

making the performance monitorinterface (PMI) exit available to VTAMfor OMEGAMON II 173

Manual IP Tunnels (KN3ITM)worksheet 272

MAXCOLL keyword 187member name 101migration

of historical data in the Tivoli DataWarehouse 71

migration tool 169modem speed 186MODIFY command 41MODIFY command, z/OS 199monitoring agent

configuring 87new in this release 9, 20, 23overview 1

monitoring agentsre-registering 70

monitoring options 200, 201

NNAM

adding users 191customization 190database 191encrypted security 190MODIFY command, z/OS 191password 199security system 190user ID 191, 199variable $$ETE 189

NAM database 155, 199NCP 155

activating 185collection

applid 187KONFCCMD command

usage 253

NCP (continued)collection (continued)

requirements 185data collection, NCP 186Data Manager 253disabling data collection 188dynamic configuration 185enabling data collection 186, 188generation 186, 187NPACOLL parameter 186NPACOLL parameter, NCP gen 186OMEGAMON II

performance 186performance, OMEGAMON II 186requirements 185sift down 186with NetSpy 185with NPM 185

NCPC parameter 253NCPCACBN parameter 253NCPCINTV parameter 253NCPCPATH parameter 253NDM 253NDMT parameter 188, 253NDMTPATH parameter 253NetSpy

with NCP component 185NetView APPLID parameter 117NetView for z/OS

Configuration Tool enablement ofpacket trace 85, 124

packet trace 117additional configuration 85, 124Hostname parameter 124LUGROUP parameter 124NetView APPLID parameter 117Port number parameter 124User data parameter 117

NetView Performance Monitor 197new features 9, 20, 23new in this release 9, 20, 23

enhanced 3270 interface 2new publications 20NODB parameter 192NPACOLL parameter, NCP gen 186NPALU

application 185definition 187KONFCCMD command usage 253macro definitions 187NCP collector connection 187usage 185

NPATP parameter, NCP gen 186NPM considerations 197NPM with NCP component 185

OOMEGAMON enhanced 3270 user

interface 5OMEGAMON II 185

activating the VTAM major node 198adding support for the SYSTCPD

DDNAME in the started tasks 177arelinking the runtime environments

after batch processing 178

OMEGAMON II (continued)assembling and link editing the LU

6.2 logon mode table 172changing the parameters after you exit

the Configuration Tool 183completing the configuration 171components

customizing 185configuring 155configuring the OMEGAMON II

SNMP manager functions 176configuring the TCP/IP

component 175configuring TNSTATs 178copying the VTAM definitions to

VTAMLST 172defining the NAM user ID and

password 199enabling console support 201enabling TCP/IP data collection 200ETE 185initializing the NAM database 199KONFCCMD command usage 253logon 200making the performance monitor

interface (PMI) exit available toVTAM 173

NCP 185OMEGAMON II

dedicated mode 185security 185SMF records 185

planning 56security

OMEGAMON II 185setting the dispatching priority 174setting thresholds and

exceptions 201SMF records 185starting 198when to use 56with NetSpy 185with NPM 185

OMEGAMON II for MainframeNetwork 169

configuring using PARMGEN 159configuring using the Configuration

Tool 159, 162running the migration utility 169specify configuration values 162

OMEGAMON II for Mainframe networksKONFCCMD command

examples 255KONFCCMD commands 253

OMEGAMON II for MainframeNetworks

allocating additional runtime datasets 168

components 155creating runtime members 169End-to-End Response Time 155loading the runtime libraries and

exiting the Configuration Tool 170modes of operation 155security 155upgrading 72upgrading to a new release 67

Index 305

OMEGAMON II for MainframeNetworks (continued)

overview 67VSAM log size 155

OMEGAMON II for MainframeNetworks environment

Prepare User Libraries utility 72OMEGAMON II for Mainframe

Networks monitoring agentconfiguring 89

OMEGAMON II migrationsrunning the migration tool 169

OMEGAMON monitoring agents onz/OS

version 5.1.0new common features 20updates to attributes and

workspaces 23OMEGAMON subsystem 5OMEGAMON XE common

components 5OMEGAMON XE for Mainframe

Networks 1completing the configuration 127new in this release 9

common features of all version5.1.0 OMEGAMON monitoringagents 20

overview 1upgrading to a new release 67

overview 67version 5.1.0 9, 20, 23

OMEGAMON XE for MainframeNetworks new features 9

Enhanced 3270 interface 20new attributes and attribute

values 23new publications 20PARMGEN 20PARMLIB 20self-describing agent 20updates to workspaces 23

OMEGAMON XE for UNIX SystemServices 70

OMEGAMON XE publicationscommon 294

OMNIMON base 5operator command, KONFCCMD 253options for monitoring, OMEGAMON

II 201OSA 10 Gigabit Ports Control (KN3TTC)

historical data storage worksheet 273OSA 10 Gigabit Ports Errors (KN3TTE)

historical data storage worksheet 273OSA 10 Gigabit Ports Summary

(KN3TTS) historical data storageworksheet 273

OSA 10 Gigabit Ports Throughput(KN3TTT) historical data storageworksheet 274

OSA adapter 59, 61OSA adapter SNMP subagent 61OSA collection override 101OSA data collection 92OSA express adapters 8OSA-Express Channels (KN3TCH)


OSA-Express LPARS (KN3TLP) historicaldata storage worksheet 272

OSA-Express Ports (KN3TPO) historicaldata storage worksheet 273

OSA-Express3 Ports Control (KN3THC)historical data storage worksheet 274

OSA-Express3 Ports Errors (KN3THE)historical data storage worksheet 274

OSA-Express3 Ports Summary (KN3THS)historical data storage worksheet 274

OSA-Express3 Ports Throughput(KN3THT) historical data storageworksheet 275

OSNMP daemon 59overview 1

Ppacket trace configuration 85, 117, 124parameters 79PARMGEN 20, 171

configuring the enhanced 3270 userinterface 78

PARMGEN configurationOMEGAMON II for Mainframe

Network 159PARMGEN configuration method

cannot find previous PARMLIBconfiguration sessioninformation 84

configuration profile 79defined 79groupings of parameters 79parameters used by 79

PARMGEN Workflow Welcome panel 84PARMLIB 20performance considerations 39

CPU usage for monitoring networkson z/OS 39

data collection interval 46data types to collect 41historical data collection 48real-time data collection 40situations 47systems to monitor 40workspace design 51


persistent data storeconfiguring for the monitoring

agent 119disk space requirements 119monitoring agent

completing 119database allocation job 119maintenance jobcard 119runtime members 119

upgrading 71planning

OMEGAMON II 56understanding how real-time data is

collected 40planning for configuration 39planning for OMEGAMON II 56planning security 55polling interval 195Port number 124

Prepare User Libraries utility 72Preparing your z/OS environment

Enabling SNMP managerfunctions 60

preparing z/OS environment 59prerequisites

hardware 5OSA-Express adapters 8z/OS systems 8

software 5SAF products 6Tivoli Data Warehouse 6Tivoli Enterprise Management

Server on distributed 6Tivoli Enterprise Management

Server on z/OS 6Tivoli Enterprise Portal 6Tivoli Enterprise Portal Server 6z/OS versions supported 6

profiles for users 190protocols

specifying communications protocolsfor the monitoring agent 105

publicationsOMEGAMON II for Mainframe


Networks 293

Qquiesce

ETE 196

RRACF 192


RACF Class Descriptor Table 193RACF parameter 192re-registering monitoring agents 70real-time data collection 40

data spaces used 40total storage associated with 40

recommended configuration 75configuring the Tivoli OMEGAMON

Enhanced User Interface 87configuring the Tivoli OMEGAMON

XE for Mainframe Networksmonitoring agent 87

scenario 75record layouts, SMF 195registering monitoring agents 70registering the monitoring agent with the

local Tivoli Enterprise ManagementServer 92

relinking the runtime environments afterbatch processing for OMEGAMONII 178

requirements, external function levelsecurity 192

resource names, external security 192restart OMEGAMON II 192


restricting access to the MainframeNetworks command log and responseworkspace 141

RKANCMDU library 253RKANPAR library

KONSTKON member 188RKANPARU library 190, 191RKANSAMU library 187RKONNAM library 192ROUTE component

z/OS MODIFY commands 203routing table collection frequency 92,

101routing table statistics collection 92RTE load function 124rules, ETE 189running different product versions during

upgrading 72running JCL jobs 90running the ITMSUPER Tools 135runtime environment

updating for NetView for z/OSpacket trace 85, 124

runtime librariesloading 123

runtime members 118

SS306 abend 173SAF product


SAF programs 130SAS

completing SAS configuration 179,182

configuring SAS historicalreporting 179

SAS historical reporting 179SDA

See self describing agentsecurity 140

alternative to User Authorities 192defining monitoring agent access to

the network managementinterface 65

function level 192KN3UAUTH member 128planning 55RACF 192support SAF products 6user authorities 191user IDs 191

self describing agent feature 68self-describing agent 20

enabling 68SEMV parameter 253setting the dispatching priority for

OMEGAMON II 174SEVT parameter 253sift down, NCP gen 186situations

autostarting to improveperformance 47

defining 47grouping to improve performance 47

situations (continued)running 47

SMFconsiderations 195enabling recording 196recording options 196trend/exception records 195

SNAcopying the VTAM definition to

VTAMLST 133data collection interval 92

SNA monitoringenabling 59

SNA.SPIPE 105SNMP 60, 176

configuration file 92sample configuration file 290

SNMP configuration 289SNMP configuration file

when to create 289SNMP manager functions 136

enabling 60SNMP subagent 59SNMP V3 passwords 141software


Software Support 299space requirements for historical data

tablesestimating 260

specify configuration values 162Specify TN3270 Configuration Parameters

panel 117speed of modem 186SPEED parameter, NCP gen 186SSYSTCPD DDNAME 131, 177Stack Layer Collection Override 101staged upgrade 72START parameter 253starting OMEGAMON II 198starting the SNMP subagent 61starting the Tivoli OMEGAMON XE for

Mainframe Networks monitoringagent 149, 151

starting your hub Tivoli EnterpriseMonitoring Server 149, 151

startupterminal definition 194

STATUS parameter 253STOP parameter 253storage considerations 39storage requirements for historical data

tablesallocating additional storage and data

sets 258determining 257


support assistant 299SYSTCPD DDNAME 131SYSTEMS argument, ETE 196

TTake Action commands

authorizing users to enter 141

Take Action commands (continued)defining a SAF general resource

class 141enhanced 3270 user interface 140,

141prefixed commands 141restricting access to the Mainframe

Networks command log andresponse workspace 141

TCP Listener (KN3TCL) historical datastorage worksheet 275

TCP/IPKONFCCMD command 253

TCP/IP address space 101TCP/IP and VTAM historical data

storagespace requirement worksheets

Current IP Filters (KN3IFC)worksheet 268

Dynamic IP Tunnels (KN3ITD)worksheet 268

IKE Tunnels (KN3ITI)worksheet 269

KN3 Agent Status (KN3AGS)worksheet 265

KN3 SNA Collector Status(KN3SCS) worksheet 265

KN3 TCP Collector Status(KN3TCS) worksheet 265


TCPIP Address Space (KN3TAS)worksheet 269

TCP/IP component of OMEGAMON IIconfiguring 175

TCP/IP connection and applicationperformance statistics collection 92

TCP/IP data collection 46TCP/IP historical data storage 263

attribute group record sizes 265formula 265space requirement worksheets

Interfaces (KN3TIF)worksheet 268

KN3 ICMP Global Counters(KN3GCG) worksheet 269

KN3 ICMP Type Counters(KN3GCT) worksheet 269

KN3 Interface Address (KN3IFA)worksheet 270

KN3 Interface Read Queue(KN3IFR) worksheet 270

KN3 Interface Statistics (KN3IFS)worksheet 270

KN3 Interface Status (KN3IFE)worksheet 270

KN3 Interface Write Queue(KN3IFW) worksheet 271

KN3 IP Counter Statistics(KN3GIC) worksheet 271

KN3 IP General Statistics(KN3GIG) worksheet 271

KN3 TCP Counter Statistics(KN3GTC) worksheet 271

KN3 UDP Counter Statistics(KN3GUC) worksheet 272

Index 307

TCP/IP historical data storage (continued)space requirement worksheets

(continued)OSA 10 Gigabit Ports Control

(KN3TTC) 273OSA 10 Gigabit Ports Errors

(KN3TTE) worksheet 273OSA 10 Gigabit Ports Summary

(KN3TTS) worksheet 273OSA 10 Gigabit Ports Throughput

(KN3TTT) worksheet 274OSA-Express Channels (KN3TCH)

worksheet 272OSA-Express LPARS (KN3TLP)

worksheet 272OSA-Express Ports (KN3TPO)

worksheet 273OSA-Express3 Ports Control

(KN3THC) worksheet 274OSA-Express3 Ports Errors

(KN3THE) worksheet 274OSA-Express3 Ports Summary

(KN3THS) worksheet 274OSA-Express3 Ports Throughput

(KN3THT) worksheet 275TCP Listener (KN3TCL)

worksheet 275TCPIP Address Space (KN3TAS)

worksheet 275TCPIP Applications (KN3TAP)

worksheet 275TCPIP Connections (KN3TCN)

worksheet 276TCPIP Details (KN3TCP)

worksheet 276TCPIP Devices (KN3TDV)

worksheet 276TCPIP Gateways (KN3TGA)

worksheet 276TCPIP Memory Statistics

(KN3TPV) worksheet 277TCPIP Stack Layer (KN3TSL)

worksheet 277UDP Connections (KN3UDP)

worksheet 277TCP/IP historical data storage

space requirementworksheets 265

worksheetsTCP/IP historical data storage

space requirements 265TCP/IP profile data set name 101TCPC 203TCPC parameter 253TCPCVIOU parameter 253TCPIP Address Space (KN3TAS)

historical data storage worksheet 269,275

TCPIP Applications (KN3TAP) historicaldata storage worksheet 275

TCPIP Connections (KN3TCN) historicaldata storage worksheet 276

TCPIP Details (KN3TCP) historical datastorage worksheet 276

TCPIP Devices (KN3TDV) historical datastorage worksheet 276

TCPIP FTP (KN3FTP) historical datastorage worksheet 283

TCPIP Gateways (KN3TGA) historicaldata storage worksheet 276

TCPIP Memory Statistics (KN3TPV)historical data storage worksheet 277

TCPIP Stack Layer (KN3TSL) historicaldata storage worksheet 277

terminalallocation, dynamic 194deallocation, dynamic 195definition 194

thresholdsetting 201

Tivoli Data Warehouse 71, 260migrating 71

Tivoli Enterprise Monitoring Serverstarting 149, 151

Tivoli Enterprise Portalstarting 149, 151

Tivoli Enterprise Portal Serverstarting 149, 151

Tivoli Management Servicescomponents 3defined 3

Tivoli OMEGAMON XE for MainframeNetworks

features 1Tivoli OMEGAMON XE for Mainframe

Networks monitoring agentcompleting the configuration 124configuring 87, 91

adding TCP/IP-specific collectionparameters 92

creating runtime members 118registering with the local

TEMS 92specifying agent address space

parameters 105specifying configuration

parameters 92updating global default values 92

configuring the persistent datastore 119

dynamic terminal integrationparameters 117

specifying communicationprotocols 105

starting 149, 151TMS: Engine

KONFCCMD command 253TN3270

connection collection override 101data display interval 92server statistics collection 92

TN3270 collection override 101TN3270 component

z/OS MODIFY commands 203TN3270 display interval override 101TN3270 historical data storage

attribute group record sizes 283formula 283space requirement worksheets 263,

283TN3270 Server Sess Avail

(KN3TNA) worksheet 284

TN3270 monitoringenabling 59

TN3270 Server Sess Avail (KN3TNA)historical data storage worksheet 284

TNSTATs 178TRSPEED parameter, NCP gen 186tuning components

changing data collection options 53changing the default value for


UUDP Connections (KN3UDP) historical

data storage worksheet 277upgrade considerations 71upgrading 68

enabling new features 68of an existing OMEGAMON II for

Mainframe Networksenvironment 72

running different productversions 72

SNMP issues 71SNMP upgrade issues 71

upgrading a persistent data store 71upgrading to a new release 67

overview 67user

authorities 191, 200displaying IDs 191external function level security 192ID, NAM 199password, NAM 199profiles 190

User data parameter 117

VVARY TCPIP DROP command 130verification

Agent Status workspace 149procedures 196starting the Tivoli OMEGAMON XE

for Mainframe Networks monitoringagent 149, 151


Tivoli Enterprise Portal 149, 151Tivoli Enterprise Portal Server 149,

151Tivoli OMEGAMON XE for

Mainframe Networks monitoringagent data collection 149, 151

verifying configuration 140VSAM encrypted security 190VSAM log size for OMEGAMON II for

Mainframe Networks 155VTAM

applid for secondary programoperator 92

major node 92setting the applid 92

VTAM Address Space (KN3VAS)historical data storage worksheet 280


VTAM Buffer Pool Extents (KN3BPE)historical data storage worksheet 280

VTAM Buffer Poolsconfiguration

CNM application 92major node 92SNA data collection 92

sample interval 92TCP/IP data file for monitoring agent

configuration 92VTAM Buffer Pools (KN3BPD) historical

data storage worksheet 280VTAM Buffer Usage by Address Space

(KN3BPS) historical data storageworksheet 280

VTAM Buffer Usage by Application forAddress Space (KN3BPA) historical datastorage worksheet 281

VTAM Buffer Usage by Category(KN3BPG) historical data storageworksheet 281

VTAM historical data storage 263attribute group record sizes 277formula 277space requirement worksheets 277

CSM Storage (KN3CSM)worksheet 279

EE Connection Details (KN3EED)worksheet 279

EE Connections (KN3EEC)worksheet 279

HPR RTP Connections (KN3HPR)worksheet 279

KN3 CSM Storage by Owner(KN3CSO) worksheet 280

VTAM Address Space (KN3VAS)worksheet 280

VTAM Buffer Pool Extents(KN3BPE) worksheet 280

VTAM Buffer Pools (KN3BPD)worksheet 280

VTAM Buffer Usage by AddressSpace (KN3BPS) worksheet 280

VTAM Buffer Usage byApplication for Address Space(KN3BPA) worksheet 281

VTAM Buffer Usage by Category(KN3BPG) worksheet 281

VTAM I/O (KN3VIO)worksheet 281

VTAM Summary Statistics(KN3SNA) worksheet 281

VTAM I/O (KN3VIO) historical datastorage worksheet 281

VTAM PMI exit 135VTAM Summary Statistics (KN3SNA)

historical data storage worksheet 281VTAMLST 172

Wworksheets

FTP historical data storage spacerequirements 281

historical data tables disk spacesummary worksheet 284

worksheets (continued)TN3270 historical data storage space

requirements 263, 283VTAM historical data storage space

requirements 277Workspace updates 23workspaces

creating 39designing 51

auto-refresh rate 51number of attributes retrieved 51number of rows retrieved 51queries to multiple views 51

modifying 39

XX.25 NCP generation 186

Zz/OS commands

MODIFY 41z/OS Communication Server

network management interfaces 40z/OS Communications Server

network management interface 59enabling IPSec, FTP, and TN3270

monitoring 59enabling SNA monitoring 59

network management interfaceAPIs 65

z/OS environmentenabling IPSec monitoring 59enabling IPSec, FTP, and TN3270

monitoring 59enabling the SNA NMI 59preparing 59verifying 62

z/OS MODIFY commands 203components 203general syntax 204KN3FCCMD HELP 204KN3FCCMD INSTALL FPCT 206KN3FCCMD INSTALL FPON 206KN3FCCMD INSTALL SEMV 207KN3FCCMD INSTALL SEVT 207KN3FCCMD INSTALL TCPC 207KN3FCCMD START CONN 208KN3FCCMD START CSM 210KN3FCCMD START DBUG 211KN3FCCMD START EEHPR 214KN3FCCMD START FTP 215KN3FCCMD START GLBS 216KN3FCCMD START INTE 217KN3FCCMD START INTS 218KN3FCCMD START IPSEC 220KN3FCCMD START OSA 221KN3FCCMD START ROUTE 222KN3FCCMD START SNAC 223KN3FCCMD START TCPC 225KN3FCCMD START TN3270 229KN3FCCMD STATUS DBUG 231KN3FCCMD STATUS FCPT 231KN3FCCMD STATUS FPON 232KN3FCCMD STATUS SEMV 232

z/OS MODIFY commands (continued)KN3FCCMD STATUS SEVT 232KN3FCCMD STATUS SNAC 233KN3FCCMD STATUS TCPC 233KN3FCCMD STOP CONN 234KN3FCCMD STOP CSM 236KN3FCCMD STOP DBUG 237KN3FCCMD STOP EEHPR 238KN3FCCMD STOP FPT 239KN3FCCMD STOP GLBS 240KN3FCCMD STOP INTE 241KN3FCCMD STOP INTS 242KN3FCCMD STOP IPSEC 244KN3FCCMD STOP OSA 245KN3FCCMD STOP ROUTE 246KN3FCCMD STOP TCPC 247KN3FCCMD STOP TN3270 252

z/OS systemsCPU usage for monitoring

networks 39

Index 309


Accessibility

Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, touse software products successfully. OMEGAMON XE monitoring products support several userinterfaces. Product functionality and accessibility features vary according to the interface.

The major accessibility features in this product enable users in the following ways:v Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear what

is displayed on the screen. Consult the product documentation of the assistive technology for detailson using those technologies with this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the following features to aidaccessibility:v All documentation is available in both HTML and convertible PDF formats to give the maximum

opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users with vision

impairments can understand the contents of the images.

The IBM Tivoli Monitoring and OMEGAMON XE Information Center, and its related publications, areaccessibility-enabled. The accessibility features of the information center are described athttp://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html.

Interface information

The Tivoli Enterprise Portal interface offers the greatest range of functionality, but is not entirelyaccessible. The OMEGAMON enhanced 3270 user interface offers more limited functionality, but isentirely accessible. (The enhanced 3270 user interface supports all the accessibility features supported byyour emulator. If you are using IBM Personal Communications, you can find information on itsaccessibility features at http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm. If you are using a third-party emulator, seethe documentation for that product for accessibility information.)

The OMEGAMON ("classic") and OMEGAMON II (CUA) 3270 interfaces use an ISPF style interface.Standard and custom PF Key settings, menu options, and command-line interface options allow for shortcuts to commonly viewed screens. While basic customization options allow for highlights and othereye-catcher techniques to be added to the interface, the customization options are limited.

Related accessibility information

You can view the publications for OMEGAMON XE for Mainframe Networks Adobe Portable DocumentFormat (PDF) using the Adobe Acrobat Reader. The PDFs are provided on a CD that is packaged withthe product, or you can access them at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon_xezos.doc/welcome_omxezos510.htm.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about the commitment thatIBM has to accessibility.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm

http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp.

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp.

http://www.ibm.com/able/index.html


Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However, it is the user'sresponsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not give you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY ORFITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore,this statement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurement may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal withoutnotice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conformingto IBM‘s application programming interfaces.


Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:

© IBM 2012. Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.previous releases to 2012.

If you are viewing this information in softcopy form, the photographs and color illustrations might not bedisplayed.

Privacy policy considerationsIBM Software products, including software as a service solutions, (“Software Offerings”) may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may use session cookies that collecteach user’s user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies cannot be disabled.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, SeeIBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement athttp://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and OtherTechnologies” and the “IBM Software Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.

Privacy policy considerationsIBM Software products, including software as a service solutions, (“Software Offerings”) may use cookiesor other technologies to collect product usage information, to help improve the end user experience, totailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable you tocollect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may use session cookies that collecteach user’s user name for purposes of session management, authentication, and single sign-onconfiguration. These cookies cannot be disabled.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes, SeeIBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement athttp://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and OtherTechnologies” and the “IBM Software Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.

Notices 315

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, and Intel Xeon, are trademarks or registered trademarks of Intel Corporation or itssubsidiaries in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, orboth.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.


Index

Numerics3270 interface 2

Aabend S306 173accessibility features 303activate

dedicated terminal 194activating the VTAM major node for

OMEGAMON II 198adding support for the SYSTCPD

DDNAME in the started tasks 131adding support for the SYSTCPD

DDNAME in the started tasks forOMEGAMON II 177

Agent historical data storageattribute group record sizes 263formula 263

agent started task 105Agent Status workspace 149allocating

terminal dynamically 194allocating additional runtime data sets for

OMEGAMON II 168APF

authorization 173APF-authorizing your libraries 133, 173applid 92applid, NCP collector 187assembling and link editing the LU 6.2

logon mode table for OMEGAMONII 172

attribute group record sizesAgent 263FTP 281TCP/IP 265TN3270 283VTAM 277

Attribute updates 23authorizing agent started tasks for

TCP/IP privileges 137, 175authorizing users 191

external function level security 193autonomous agents

Enabling SNMP V3 passwords forautonomous agents 141

Bbatch processing

relinking the runtime environmentsafter in OMEGAMON II 178

CCannot find previous PARMLIB

configuration session information 84CAT and ATTR files 139

changes, exception record 195changing the parameters after you exit


CL jobsrunning 90

cloning a configuration toolenvironment 70

cloning an existing SMP/Eenvironment 70

CNM application 92collection interval

by LPAR 41defining 46for new sessions or transfers 41impact on performance 41

collection, NCP data 186X.25 186

commands 203general syntax 204KN3FCCMD HELP 204KN3FCCMD INSTALL FPCT 206KN3FCCMD INSTALL FPON 206KN3FCCMD INSTALL SEMV 207KN3FCCMD INSTALL SEVT 207KN3FCCMD INSTALL TCPC 207KN3FCCMD START CONN 208KN3FCCMD START CSM 210KN3FCCMD START DBUG 211KN3FCCMD START EEHPR 214KN3FCCMD START FPT 215KN3FCCMD START GLBS 216KN3FCCMD START INTE 217KN3FCCMD START INTS 218KN3FCCMD START IPSEC 220KN3FCCMD START OSA 221KN3FCCMD START ROUTE 222KN3FCCMD START SNAC 223KN3FCCMD START TCPC 225KN3FCCMD START TN3270 229KN3FCCMD STATUS DBUG 231KN3FCCMD STATUS FCPT 231KN3FCCMD STATUS FPON 232KN3FCCMD STATUS SEMV 232KN3FCCMD STATUS SEVT 232KN3FCCMD STATUS SNAC 233KN3FCCMD STATUS TCPC 233KN3FCCMD STOP CONN 234KN3FCCMD STOP CSM 236KN3FCCMD STOP DBUG 237KN3FCCMD STOP EEHPR 238KN3FCCMD STOP FTP 239KN3FCCMD STOP GLBS 240KN3FCCMD STOP INTE 241KN3FCCMD STOP INTS 242KN3FCCMD STOP IPSEC 244KN3FCCMD STOP OSA 245KN3FCCMD STOP ROUTE 246KN3FCCMD STOP TCPC 247KN3FCCMD STOP TN3270 252

Common features of all version 5.1.0OMEGAMON monitoring agents 20

Communications Storage Managerbuffer reporting 92

community name 200complete the configuration

OMEGAMON II 171completing the configuration

OMEGAMON XE for MainframeNetworks

completing the configuration 127components of OMEGAMON II for

Mainframe Networks 155configuration 159

adding support for the SYSTCPDDDNAME in the started tasks 131,177

adding TCP/IP-specific collectionparameters for the monitoringagent 92

APF-authorizing your libraries 133,173



changing the parameters after you exitthe Configuration Tool 183

completing for the monitoringagent 124

completing outside the ConfigurationTool

adding support for the SYSTCPDDDNAME in the startedtasks 131, 177

APF-authorizing yourlibraries 133, 173



changing the parameters after youexit the Configuration Tool 183


configuring TNSTATs 178copying the started task

procedures to you procedurelibrary 132, 172

copying the VTAM definition toVTAMLST 133

copying the VTAM definitions toVTAMLST 172

defining monitoring agent accessto the network monitoringinterface and commands 128

enabling CSA tracking to displayTCP/IP CSA usage 136, 178



configuration (continued)completing outside the Configuration

Tool (continued)enabling security at Tivoli

Enterprise Portal 139, 140enabling Warehouse agents on a

z/OS hub monitoringserver 138

giving users authorization andresource access to run the VARYTCPIP DROP command 130

making the performance monitorinterface (PMI) exit available toVTAM 135, 173

operating systemconsiderations 147


relinking the runtimeenvironments after batchprocessing 178

running the ITMSUPER Tools 135setting the dispatching

priority 174completing outside the Configuration

Tool or PARMGENconfiguring SNMP manager

functions 136configuring SNMP manager





configuring the persistent data storefor the monitoring agent 119

configuring TNSTATs 178copying the started task procedures to

your procedure library 132, 172copying the VTAM definition to


VTAMLST 172creating runtime members for the

monitoring agent 118defining monitoring agent access to

the network monitoringinterface 128

dynamic, NCP 185enabling CSA tracking to display

TCP/IP CSA usage 136, 178enabling historical data store

maintenance 134enabling security at Tivoli Enterprise

Portal 139, 140enabling Warehouse agents on a z/OS

hub monitoring server 138giving users authorization and

resource access to run the VARYTCPIP DROP command 130

historical data collection 137KONFCCMD usage 253

configuration (continued)making the performance monitor

interface (PMI) exit available toVTAM 135, 173

NCP generation 187NPALU macro definitions 187OMEGAMON II for Mainframe

Networksallocating additional runtime data

sets 168components 155creating runtime members 169loading the runtime libraries and

exiting the ConfigurationTool 170

OMEGAMON II for MainframeNetworks monitoring agent 89

operating system considerations 147performing agent-specific security

configuration 128recommended 75relinking the runtime environments

after batch processing 178running the ITMSUPER Tools 135setting the dispatching priority 174SMF consideration 195specifying agent address space

parameters 105specifying communication protocols

for the monitoring agent 105specifying configuration values for the

monitoring agent 92specifying dynamic terminal

integration parameters 117Tivoli OMEGAMON XE for

Mainframe Networks monitoringagent 87

updating global default values for themonitoring agent 92

verifying 140configuration planning 39configuration profile 79Configuration Tool

abbreviations 36configuring the enhanced 3270 user

interface 87Load all product libraries after

SMP/E 124panels



add TCP/IP monitored systemsinformation 101

allocate persistent data storemenu 119

configure OMEGAMON XE forMainframe Networks 91

persistent data storespecifications 119

product component selectionmenu 91, 160

Specify advanced agentconfiguration values panel 112

specify agent address spaceparameters 105

Configuration Tool (continued)panels (continued)

Specify Agent IP.UDPConfiguration Values panel 105

Specify Agent SNA ConfigurationValues 111




specify configurationparameters 92

specify persistent data store valuesfor the monitoring agent 119

specify TCP/IP componentconfiguration 92

specify TCP/IP monitored systeminformation 92

Specify VTAM applid values /RTE (Page 5) 92

SNMP configuration 92tasks performed outside the

configuration tool for OMEGAMONII 171

Configuration Tool configurationOMEGAMON II for Mainframe

Network 159, 162configuration tool environment

cloning 70configuring SNMP manager




configuring the OMEGAMON II SNMPmanager functions for OMEGAMONII 176

configuring TNSTATs 178CONN component

z/OS MODIFY commands 203control points 190controlling ETE 189copying the started task procedures to

you procedure library 132, 172copying the VTAM definition to


VTAMLST for OMEGAMON II 172CPU usage

monitoring networks on z/OS 39reducing

by changing routing tablecollection frequency 46

by decreasing the frequency ofdata collect 46

creating runtime members forOMEGAMON II 169

CSA usage 136, 178CSM buffer reporting 92CSM component

z/OS MODIFY commands 203CSM Storage (CSM) (KN3CSM) historical

data storage worksheet 279


Current IP Filters (KN3IFC) worksheethistorical data storage worksheet 268

customizationconsole support 201dedicated mode 194End-to-End 189NCP definitions 186security 190

Cylindersdefaults 258definition 258

Ddata collection

changing collection options 53reducing frequency 46verifying 149, 151

data collection, NCP 185deactivate dedicated terminal 195deallocate terminal dynamically 195debugging 211, 231, 237DEDICATE command 194, 195dedicated mode 194dedicated terminal, activate 194define terminal at startup 194defining a SAF general resource

class 141defining display intervals 47defining monitoring agent access to the

network monitoring interface andcommands 128

defining RACF resources usingICHERCDE 193

defining the NAM user ID andpassword 199

direct ETE command to ETE version 197disabling

End-to-End 190disabling NCP data collection 188disk space requirements for historical

data tables 257, 284per LPAR 286

display interval 92defining 47

DLC Interface Collection Override 101DUPLEX parameter, NCP gen 186dynamic configuration, NCP 185Dynamic IP Tunnels (KN3ITD)

worksheet 268dynamic terminal

allocation 194deallocation 195

dynamic terminal integration parametersconfiguration 117

EEE Connection Details (KN3EED)

historical data storage worksheet 279EE Connections (KN3EEC) historical data

storage worksheet 279EEHPR component

z/OS MODIFY commands 203enabling

End-to-End 189

enabling CSA tracking to display TCP/IPCSA usage 136, 178


enabling NCP data collection 188enabling OMEGAMON II console

support 201enabling security 140enabling security at Tivoli Enterprise

Portal 139, 140Enabling SNMP V3 passwords for

autonomous agents 141enabling TCP/IP data collection on

OMEGAMON II 200enabling Warehouse agents on a z/OS

hub monitoring server 138encrypted security, NAM 190End-to-End

considerations 189disabling 190multiple systems

NPM considerations 197NPM considerations 197quiesce 196rules 189running multiple copies 197

NPM considerations 197start 196

multiple systems 197SYSTEMS argument 196variable $$ETE 189

End-to-End Response Time 155enhanced 3270 interface 2Enhanced 3270 interface 20Enterprise Extender

statistics collection 92ETE 155, 189

NPM considerations 197ETE command

direct to ETE version 197exception

record changes 195settings 201

external security resource class 192external security resource names 192

Ffile format 289finalizing security 190FPCT parameter 253FPON parameter 253FTP

data display collection 92data display interval 92


FTP collection override 101FTP component

z/OS MODIFY commands 203FTP display interval override 101FTP historical data storage

attribute group record sizes 281formula 281space requirement worksheets 281

TCPIP FTP (KN3FTP)worksheet 283

FTP historical data storage (continued)space requirement worksheets

(continued)TN3270 Sessions (KN3FSE)

worksheet 282FTP monitoring

enabling 59FTP Sessions (KN3FSE) historical data

storage worksheet 282function level security 192, 200functions secured externally 192

GGBL_USER_JCL field 84generation parameters, NCP 186

X.25 186giving users authorization and resource

access to run the VARY TCPIP DROPcommand 130

GLBS componentz/OS MODIFY commands 203

Group Count parameter 257applying a Group Count factor 258

example analysis 258examples 258

defaults 258definition 258specifying for the monitoring

agent 119

Hhardware


high availability hub monitoring server,configuring 68

High Performance Routing 92statistics collection 92

historical data collection 48, 137attributes groups that impact

performance 50changing the default value for


configuring 137estimating tools 263


TCP/IP historical datastorage 263

VTAM historical data storage 263installation 137long-term 48

row of data defined 260maintaining data stores 50rate of accumulation 49short-term 48

function 258row of data defined 260

types of data to collect 50historical data storage

Agent 263attribute group record sizes 263

FTP 263, 281

Index 319

historical data storage (continued)attribute group record sizes 281

TCP/IP 263attribute group record sizes 265

TN3270 263, 283attribute group record sizes 283

VTAM 263, 277attribute group record sizes 277

historical data store maintenance 134historical data tables 261

determining storagerequirements 257, 261

allocating additional storage anddata sets 258


disk space requirements 257disk space summary worksheet 284

totaling storage per LPAR 286estimating space requirements 260formula for totaling storage per

LPAR 286Group Count parameter 257

historical reportingSMF 196

HPRrouting table collection

frequency 101HPR RTP Connections (KN3HPR)


IIBM Support Assistant 299IBM Tivoli OMEGAMON XE for

Mainframe Networksintegration 5integration with other product 5interoperability 5

ICHERCDE 193IKE Tunnels (KN3ITI) worksheet 269initialization

error 173initializing the OMEGAMON II NAM

database 199INSTALL parameter 253installation 1

command KONFCCMD 253historical data collection 137verification 196

INTE componentz/OS MODIFY commands 203

Interface Collection Override 101Interfaces (KN3TIF) historical data

storage worksheet 268interoperability with other products 5INTERVAL parameter 195interval, dedicated mode polling 195INTS component

z/OS MODIFY commands 203IP filters

collection override 101IP tunnels

collection override 101IP.PIPE 105IP.SPIPE 105IP.UDP 105

IP6.PIPE 105IP6.SPIPE 105IP6.UDP 105IPSec component

z/OS MODIFY commands 203IPSec monitoring

enabling 59IPv4

workspaces mapping IPv4 address toIPv6 36

IPv6 36ISA 299

Kkeywords, NCP macro 186KN3 Agent Status (KN3AGS) historical

data storage worksheet 265KN3 CSM Storage by Owner (KN3CSO)

historical data storage worksheet 280KN3 ICMP Global Counters (KN3GCG)

historical data storage worksheet 269KN3 ICMP Type Counters (KN3GCT)

historical data storage worksheet 269KN3 Interface Address (KN3IFA)

historical data storage worksheet 270KN3 Interface Read Queue (KN3IFR)

historical data storage worksheet 270KN3 Interface Statistics (KN3IFS)

historical data storage worksheet 270KN3 Interface Status (KN3IFE) historical

data storage worksheet 270KN3 Interface Write Queue (KN3IFW)

historical data storage worksheet 271KN3 IP Counter Statistics (KN3GIC)

historical data storage worksheet 271KN3 IP General Statistics (KN3GIG)

historical data storage worksheet 271KN3 SNA Collector Status (KN3SCS)

historical data storage worksheet 265KN3 TCP Collector Status (KN3TCS)

historical data storage worksheet 265KN3 TCP Counter Statistics (KN3GTC)

historical data storage worksheet 271KN3 UDP Counter Statistics (KN3GUC)

historical data storage worksheet 272KN3FCCMD command reference 203KN3FCCMD HELP command 204KN3FCCMD INSTALL FPCT

command 206KN3FCCMD INSTALL FPON

command 206KN3FCCMD INSTALL SEMV

command 207KN3FCCMD INSTALL SEVT

command 207KN3FCCMD INSTALL TCPC

command 207KN3FCCMD START CONN

command 208KN3FCCMD START CSM command 210KN3FCCMD START DBUG

command 211KN3FCCMD START EEHPR

command 214KN3FCCMD START FTP command 215

KN3FCCMD START GLBScommand 216

KN3FCCMD START INTEcommand 217

KN3FCCMD START INTScommand 218

KN3FCCMD START IPSECcommand 220

KN3FCCMD START OSA command 221KN3FCCMD START ROUTE

command 222KN3FCCMD START SNAC

command 223KN3FCCMD START TCPC

command 225KN3FCCMD START TN3270

command 229KN3FCCMD STATUS DBUG

command 231KN3FCCMD STATUS FCPT

command 231KN3FCCMD STATUS FPON

command 232KN3FCCMD STATUS SEMV

command 232KN3FCCMD STATUS SEVT

command 232KN3FCCMD STATUS SNAC

command 233KN3FCCMD STATUS TCPC

command 233KN3FCCMD STOP CONN

command 234KN3FCCMD STOP CSM command 236KN3FCCMD STOP DBUG

command 237KN3FCCMD STOP EEHPR

command 238KN3FCCMD STOP FPT command 239KN3FCCMD STOP GLBS command 240KN3FCCMD STOP INTE command 241KN3FCCMD STOP INTS command 242KN3FCCMD STOP IPSEC command 244KN3FCCMD STOP OSA command 245KN3FCCMD STOP ROUTE

command 246KN3FCCMD STOP TCPC command 247KN3FCCMD STOP TN3270

command 252KN3LINK 147KN3UAUTH 65

editing and submitting 128KONCTNPA member 187KONFCCMD command 188, 253

syntax 253KONFCCMD command reference 203KONFCCMD commands

examples 255introduction 253

KONINNAM member 190, 191KONSTKON member 194

Llanguage support 139libraries

APF-authorize 173


libraries (continued)OMEGAMON II for Mainframe


Networks 293RKANPARU 190, 191

line utilization 186Load all product libraries after

SMP/E 124loading the runtime libraries and exiting


LOCALID parameter 253LOGAPPL Keyword 187logon, OMEGAMON II 200LUGROUP 124

Mmacro

NCP gen keywords 186NPALU definition 187

making the performance monitorinterface (PMI) exit available toVTAM 135

making the performance monitorinterface (PMI) exit available to VTAMfor OMEGAMON II 173


MAXCOLL keyword 187member name 101migration

of historical data in the Tivoli DataWarehouse 71

migration tool 169modem speed 186MODIFY command 41MODIFY command, z/OS 199monitoring agent

configuring 87new in this release 9, 20, 23overview 1

monitoring agentsre-registering 70

monitoring options 200, 201

NNAM

adding users 191customization 190database 191encrypted security 190MODIFY command, z/OS 191password 199security system 190user ID 191, 199variable $$ETE 189

NAM database 155, 199NCP 155

activating 185collection

applid 187KONFCCMD command

usage 253

NCP (continued)collection (continued)

requirements 185data collection, NCP 186Data Manager 253disabling data collection 188dynamic configuration 185enabling data collection 186, 188generation 186, 187NPACOLL parameter 186NPACOLL parameter, NCP gen 186OMEGAMON II

performance 186performance, OMEGAMON II 186requirements 185sift down 186with NetSpy 185with NPM 185

NCPC parameter 253NCPCACBN parameter 253NCPCINTV parameter 253NCPCPATH parameter 253NDM 253NDMT parameter 188, 253NDMTPATH parameter 253NetSpy

with NCP component 185NetView APPLID parameter 117NetView for z/OS

Configuration Tool enablement ofpacket trace 85, 124

packet trace 117additional configuration 85, 124Hostname parameter 124LUGROUP parameter 124NetView APPLID parameter 117Port number parameter 124User data parameter 117

NetView Performance Monitor 197new features 9, 20, 23new in this release 9, 20, 23

enhanced 3270 interface 2new publications 20NODB parameter 192NPACOLL parameter, NCP gen 186NPALU

application 185definition 187KONFCCMD command usage 253macro definitions 187NCP collector connection 187usage 185

NPATP parameter, NCP gen 186NPM considerations 197NPM with NCP component 185

OOMEGAMON enhanced 3270 user

interface 5OMEGAMON II 185

activating the VTAM major node 198adding support for the SYSTCPD

DDNAME in the started tasks 177arelinking the runtime environments

after batch processing 178

OMEGAMON II (continued)assembling and link editing the LU

6.2 logon mode table 172changing the parameters after you exit

the Configuration Tool 183completing the configuration 171components

customizing 185configuring 155configuring the OMEGAMON II

SNMP manager functions 176configuring the TCP/IP

component 175configuring TNSTATs 178copying the VTAM definitions to

VTAMLST 172defining the NAM user ID and

password 199enabling console support 201enabling TCP/IP data collection 200ETE 185initializing the NAM database 199KONFCCMD command usage 253logon 200making the performance monitor

interface (PMI) exit available toVTAM 173

NCP 185OMEGAMON II

dedicated mode 185security 185SMF records 185

planning 56security

OMEGAMON II 185setting the dispatching priority 174setting thresholds and

exceptions 201SMF records 185starting 198when to use 56with NetSpy 185with NPM 185

OMEGAMON II for MainframeNetwork 169

configuring using PARMGEN 159configuring using the Configuration

Tool 159, 162running the migration utility 169specify configuration values 162

OMEGAMON II for Mainframe networksKONFCCMD command

examples 255KONFCCMD commands 253

OMEGAMON II for MainframeNetworks

allocating additional runtime datasets 168

components 155creating runtime members 169End-to-End Response Time 155loading the runtime libraries and

exiting the Configuration Tool 170modes of operation 155security 155upgrading 72upgrading to a new release 67

Index 321

OMEGAMON II for MainframeNetworks (continued)

overview 67VSAM log size 155

OMEGAMON II for MainframeNetworks environment

Prepare User Libraries utility 72OMEGAMON II for Mainframe

Networks monitoring agentconfiguring 89

OMEGAMON II migrationsrunning the migration tool 169

OMEGAMON monitoring agents onz/OS

version 5.1.0new common features 20updates to attributes and

workspaces 23OMEGAMON subsystem 5OMEGAMON XE common

components 5OMEGAMON XE for Mainframe

Networks 1completing the configuration 127new in this release 9

common features of all version5.1.0 OMEGAMON monitoringagents 20

overview 1upgrading to a new release 67

overview 67version 5.1.0 9, 20, 23

OMEGAMON XE for MainframeNetworks new features 9

Enhanced 3270 interface 20new attributes and attribute

values 23new publications 20PARMGEN 20PARMLIB 20self-describing agent 20updates to workspaces 23

OMEGAMON XE for UNIX SystemServices 70

OMEGAMON XE publicationscommon 294

OMNIMON base 5operator command, KONFCCMD 253options for monitoring, OMEGAMON

II 201OSA 10 Gigabit Ports Control (KN3TTC)

historical data storage worksheet 273OSA 10 Gigabit Ports Errors (KN3TTE)

historical data storage worksheet 273OSA 10 Gigabit Ports Summary

(KN3TTS) historical data storageworksheet 273

OSA 10 Gigabit Ports Throughput(KN3TTT) historical data storageworksheet 274

OSA adapter 59, 61OSA adapter SNMP subagent 61OSA collection override 101OSA data collection 92OSA express adapters 8OSA-Express Channels (KN3TCH)


OSA-Express LPARS (KN3TLP) historicaldata storage worksheet 272

OSA-Express Ports (KN3TPO) historicaldata storage worksheet 273

OSA-Express3 Ports Control (KN3THC)historical data storage worksheet 274

OSA-Express3 Ports Errors (KN3THE)historical data storage worksheet 274

OSA-Express3 Ports Summary (KN3THS)historical data storage worksheet 274

OSA-Express3 Ports Throughput(KN3THT) historical data storageworksheet 275

OSNMP daemon 59overview 1

Ppacket trace configuration 85, 117, 124parameters 79PARMGEN 20, 171

configuring the enhanced 3270 userinterface 78

PARMGEN configurationOMEGAMON II for Mainframe

Network 159PARMGEN configuration method

cannot find previous PARMLIBconfiguration sessioninformation 84

configuration profile 79defined 79groupings of parameters 79parameters used by 79

PARMGEN Workflow Welcome panel 84PARMLIB 20performance considerations 39

CPU usage for monitoring networkson z/OS 39

data collection interval 46data types to collect 41historical data collection 48real-time data collection 40situations 47systems to monitor 40workspace design 51


persistent data storeconfiguring for the monitoring

agent 119disk space requirements 119monitoring agent

completing 119database allocation job 119maintenance jobcard 119runtime members 119

upgrading 71planning

OMEGAMON II 56understanding how real-time data is

collected 40planning for configuration 39planning for OMEGAMON II 56planning security 55polling interval 195Port number 124

Prepare User Libraries utility 72Preparing your z/OS environment

Enabling SNMP managerfunctions 60

preparing z/OS environment 59prerequisites

hardware 5OSA-Express adapters 8z/OS systems 8

software 5SAF products 6Tivoli Data Warehouse 6Tivoli Enterprise Management

Server on distributed 6Tivoli Enterprise Management

Server on z/OS 6Tivoli Enterprise Portal 6Tivoli Enterprise Portal Server 6z/OS versions supported 6

profiles for users 190protocols

specifying communications protocolsfor the monitoring agent 105

publicationsOMEGAMON II for Mainframe


Networks 293

Qquiesce

ETE 196

RRACF 192


RACF Class Descriptor Table 193RACF parameter 192re-registering monitoring agents 70real-time data collection 40

data spaces used 40total storage associated with 40

recommended configuration 75configuring the Tivoli OMEGAMON

Enhanced User Interface 87configuring the Tivoli OMEGAMON

XE for Mainframe Networksmonitoring agent 87

scenario 75record layouts, SMF 195registering monitoring agents 70registering the monitoring agent with the

local Tivoli Enterprise ManagementServer 92

relinking the runtime environments afterbatch processing for OMEGAMONII 178

requirements, external function levelsecurity 192

resource names, external security 192restart OMEGAMON II 192


restricting access to the MainframeNetworks command log and responseworkspace 141

RKANCMDU library 253RKANPAR library

KONSTKON member 188RKANPARU library 190, 191RKANSAMU library 187RKONNAM library 192ROUTE component

z/OS MODIFY commands 203routing table collection frequency 92,

101routing table statistics collection 92RTE load function 124rules, ETE 189running different product versions during

upgrading 72running JCL jobs 90running the ITMSUPER Tools 135runtime environment

updating for NetView for z/OSpacket trace 85, 124

runtime librariesloading 123

runtime members 118

SS306 abend 173SAF product


SAF programs 130SAS

completing SAS configuration 179,182

configuring SAS historicalreporting 179

SAS historical reporting 179SDA

See self describing agentsecurity 140

alternative to User Authorities 192defining monitoring agent access to

the network managementinterface 65

function level 192KN3UAUTH member 128planning 55RACF 192support SAF products 6user authorities 191user IDs 191

self describing agent feature 68self-describing agent 20

enabling 68SEMV parameter 253setting the dispatching priority for

OMEGAMON II 174SEVT parameter 253sift down, NCP gen 186situations

autostarting to improveperformance 47

defining 47grouping to improve performance 47

situations (continued)running 47

SMFconsiderations 195enabling recording 196recording options 196trend/exception records 195

SNAcopying the VTAM definition to

VTAMLST 133data collection interval 92

SNA monitoringenabling 59

SNA.SPIPE 105SNMP 60, 176

configuration file 92sample configuration file 290

SNMP configuration 289SNMP configuration file

when to create 289SNMP manager functions 136

enabling 60SNMP subagent 59SNMP V3 passwords 141software


Software Support 299space requirements for historical data

tablesestimating 260

specify configuration values 162Specify TN3270 Configuration Parameters

panel 117speed of modem 186SPEED parameter, NCP gen 186SSYSTCPD DDNAME 131, 177Stack Layer Collection Override 101staged upgrade 72START parameter 253starting OMEGAMON II 198starting the SNMP subagent 61starting the Tivoli OMEGAMON XE for

Mainframe Networks monitoringagent 149, 151


startupterminal definition 194

STATUS parameter 253STOP parameter 253storage considerations 39storage requirements for historical data

tablesallocating additional storage and data

sets 258determining 257


support assistant 299SYSTCPD DDNAME 131SYSTEMS argument, ETE 196

TTake Action commands

authorizing users to enter 141

Take Action commands (continued)defining a SAF general resource

class 141enhanced 3270 user interface 140,

141prefixed commands 141restricting access to the Mainframe

Networks command log andresponse workspace 141

TCP Listener (KN3TCL) historical datastorage worksheet 275

TCP/IPKONFCCMD command 253

TCP/IP address space 101TCP/IP and VTAM historical data

storagespace requirement worksheets

Current IP Filters (KN3IFC)worksheet 268

Dynamic IP Tunnels (KN3ITD)worksheet 268

IKE Tunnels (KN3ITI)worksheet 269

KN3 Agent Status (KN3AGS)worksheet 265

KN3 SNA Collector Status(KN3SCS) worksheet 265

KN3 TCP Collector Status(KN3TCS) worksheet 265


TCPIP Address Space (KN3TAS)worksheet 269

TCP/IP component of OMEGAMON IIconfiguring 175

TCP/IP connection and applicationperformance statistics collection 92

TCP/IP data collection 46TCP/IP historical data storage 263

attribute group record sizes 265formula 265space requirement worksheets

Interfaces (KN3TIF)worksheet 268

KN3 ICMP Global Counters(KN3GCG) worksheet 269

KN3 ICMP Type Counters(KN3GCT) worksheet 269

KN3 Interface Address (KN3IFA)worksheet 270

KN3 Interface Read Queue(KN3IFR) worksheet 270

KN3 Interface Statistics (KN3IFS)worksheet 270

KN3 Interface Status (KN3IFE)worksheet 270

KN3 Interface Write Queue(KN3IFW) worksheet 271

KN3 IP Counter Statistics(KN3GIC) worksheet 271

KN3 IP General Statistics(KN3GIG) worksheet 271

KN3 TCP Counter Statistics(KN3GTC) worksheet 271

KN3 UDP Counter Statistics(KN3GUC) worksheet 272

Index 323

TCP/IP historical data storage (continued)space requirement worksheets

(continued)OSA 10 Gigabit Ports Control

(KN3TTC) 273OSA 10 Gigabit Ports Errors

(KN3TTE) worksheet 273OSA 10 Gigabit Ports Summary

(KN3TTS) worksheet 273OSA 10 Gigabit Ports Throughput

(KN3TTT) worksheet 274OSA-Express Channels (KN3TCH)

worksheet 272OSA-Express LPARS (KN3TLP)

worksheet 272OSA-Express Ports (KN3TPO)

worksheet 273OSA-Express3 Ports Control

(KN3THC) worksheet 274OSA-Express3 Ports Errors

(KN3THE) worksheet 274OSA-Express3 Ports Summary

(KN3THS) worksheet 274OSA-Express3 Ports Throughput

(KN3THT) worksheet 275TCP Listener (KN3TCL)

worksheet 275TCPIP Address Space (KN3TAS)

worksheet 275TCPIP Applications (KN3TAP)

worksheet 275TCPIP Connections (KN3TCN)

worksheet 276TCPIP Details (KN3TCP)

worksheet 276TCPIP Devices (KN3TDV)

worksheet 276TCPIP Gateways (KN3TGA)

worksheet 276TCPIP Memory Statistics

(KN3TPV) worksheet 277TCPIP Stack Layer (KN3TSL)

worksheet 277UDP Connections (KN3UDP)

worksheet 277TCP/IP historical data storage

space requirementworksheets 265

worksheetsTCP/IP historical data storage

space requirements 265TCP/IP profile data set name 101TCPC 203TCPC parameter 253TCPCVIOU parameter 253TCPIP Address Space (KN3TAS)

historical data storage worksheet 269,275

TCPIP Applications (KN3TAP) historicaldata storage worksheet 275

TCPIP Connections (KN3TCN) historicaldata storage worksheet 276

TCPIP Details (KN3TCP) historical datastorage worksheet 276

TCPIP Devices (KN3TDV) historical datastorage worksheet 276

TCPIP FTP (KN3FTP) historical datastorage worksheet 283

TCPIP Gateways (KN3TGA) historicaldata storage worksheet 276

TCPIP Memory Statistics (KN3TPV)historical data storage worksheet 277

TCPIP Stack Layer (KN3TSL) historicaldata storage worksheet 277

terminalallocation, dynamic 194deallocation, dynamic 195definition 194

thresholdsetting 201

Tivoli Data Warehouse 71, 260migrating 71

Tivoli Enterprise Monitoring Serverstarting 149, 151

Tivoli Enterprise Portalstarting 149, 151

Tivoli Enterprise Portal Serverstarting 149, 151

Tivoli Management Servicescomponents 3defined 3

Tivoli OMEGAMON XE for MainframeNetworks

features 1Tivoli OMEGAMON XE for Mainframe

Networks monitoring agentcompleting the configuration 124configuring 87, 91

adding TCP/IP-specific collectionparameters 92

creating runtime members 118registering with the local

TEMS 92specifying agent address space

parameters 105specifying configuration

parameters 92updating global default values 92

configuring the persistent datastore 119

dynamic terminal integrationparameters 117

specifying communicationprotocols 105

starting 149, 151TMS: Engine

KONFCCMD command 253TN3270

connection collection override 101data display interval 92server statistics collection 92

TN3270 collection override 101TN3270 component

z/OS MODIFY commands 203TN3270 display interval override 101TN3270 historical data storage

attribute group record sizes 283formula 283space requirement worksheets 263,

283TN3270 Server Sess Avail

(KN3TNA) worksheet 284

TN3270 monitoringenabling 59

TN3270 Server Sess Avail (KN3TNA)historical data storage worksheet 284

TNSTATs 178TRSPEED parameter, NCP gen 186tuning components

changing data collection options 53changing the default value for


UUDP Connections (KN3UDP) historical

data storage worksheet 277upgrade considerations 71upgrading 68

enabling new features 68of an existing OMEGAMON II for

Mainframe Networksenvironment 72

running different productversions 72

SNMP issues 71SNMP upgrade issues 71

upgrading a persistent data store 71upgrading to a new release 67

overview 67user

authorities 191, 200displaying IDs 191external function level security 192ID, NAM 199password, NAM 199profiles 190

User data parameter 117

VVARY TCPIP DROP command 130verification

Agent Status workspace 149procedures 196starting the Tivoli OMEGAMON XE

for Mainframe Networks monitoringagent 149, 151


Tivoli Enterprise Portal 149, 151Tivoli Enterprise Portal Server 149,

151Tivoli OMEGAMON XE for

Mainframe Networks monitoringagent data collection 149, 151

verifying configuration 140VSAM encrypted security 190VSAM log size for OMEGAMON II for

Mainframe Networks 155VTAM

applid for secondary programoperator 92

major node 92setting the applid 92

VTAM Address Space (KN3VAS)historical data storage worksheet 280


VTAM Buffer Pool Extents (KN3BPE)historical data storage worksheet 280

VTAM Buffer Poolsconfiguration

CNM application 92major node 92SNA data collection 92

sample interval 92TCP/IP data file for monitoring agent

configuration 92VTAM Buffer Pools (KN3BPD) historical

data storage worksheet 280VTAM Buffer Usage by Address Space

(KN3BPS) historical data storageworksheet 280

VTAM Buffer Usage by Application forAddress Space (KN3BPA) historical datastorage worksheet 281

VTAM Buffer Usage by Category(KN3BPG) historical data storageworksheet 281

VTAM historical data storage 263attribute group record sizes 277formula 277space requirement worksheets 277

CSM Storage (KN3CSM)worksheet 279

EE Connection Details (KN3EED)worksheet 279

EE Connections (KN3EEC)worksheet 279

HPR RTP Connections (KN3HPR)worksheet 279

KN3 CSM Storage by Owner(KN3CSO) worksheet 280

VTAM Address Space (KN3VAS)worksheet 280

VTAM Buffer Pool Extents(KN3BPE) worksheet 280

VTAM Buffer Pools (KN3BPD)worksheet 280

VTAM Buffer Usage by AddressSpace (KN3BPS) worksheet 280

VTAM Buffer Usage byApplication for Address Space(KN3BPA) worksheet 281

VTAM Buffer Usage by Category(KN3BPG) worksheet 281

VTAM I/O (KN3VIO)worksheet 281

VTAM Summary Statistics(KN3SNA) worksheet 281

VTAM I/O (KN3VIO) historical datastorage worksheet 281

VTAM PMI exit 135VTAM Summary Statistics (KN3SNA)

historical data storage worksheet 281VTAMLST 172

Wworksheets

FTP historical data storage spacerequirements 281

historical data tables disk spacesummary worksheet 284

worksheets (continued)TN3270 historical data storage space

requirements 263, 283VTAM historical data storage space

requirements 277Workspace updates 23workspaces

creating 39designing 51

auto-refresh rate 51number of attributes retrieved 51number of rows retrieved 51queries to multiple views 51

modifying 39

XX.25 NCP generation 186

Zz/OS commands

MODIFY 41z/OS Communication Server

network management interfaces 40z/OS Communications Server

network management interface 59enabling IPSec, FTP, and TN3270

monitoring 59enabling SNA monitoring 59

network management interfaceAPIs 65

z/OS environmentenabling IPSec monitoring 59enabling IPSec, FTP, and TN3270

monitoring 59enabling the SNA NMI 59preparing 59verifying 62

z/OS MODIFY commands 203components 203general syntax 204KN3FCCMD HELP 204KN3FCCMD INSTALL FPCT 206KN3FCCMD INSTALL FPON 206KN3FCCMD INSTALL SEMV 207KN3FCCMD INSTALL SEVT 207KN3FCCMD INSTALL TCPC 207KN3FCCMD START CONN 208KN3FCCMD START CSM 210KN3FCCMD START DBUG 211KN3FCCMD START EEHPR 214KN3FCCMD START FTP 215KN3FCCMD START GLBS 216KN3FCCMD START INTE 217KN3FCCMD START INTS 218KN3FCCMD START IPSEC 220KN3FCCMD START OSA 221KN3FCCMD START ROUTE 222KN3FCCMD START SNAC 223KN3FCCMD START TCPC 225KN3FCCMD START TN3270 229KN3FCCMD STATUS DBUG 231KN3FCCMD STATUS FCPT 231KN3FCCMD STATUS FPON 232KN3FCCMD STATUS SEMV 232

z/OS MODIFY commands (continued)KN3FCCMD STATUS SEVT 232KN3FCCMD STATUS SNAC 233KN3FCCMD STATUS TCPC 233KN3FCCMD STOP CONN 234KN3FCCMD STOP CSM 236KN3FCCMD STOP DBUG 237KN3FCCMD STOP EEHPR 238KN3FCCMD STOP FPT 239KN3FCCMD STOP GLBS 240KN3FCCMD STOP INTE 241KN3FCCMD STOP INTS 242KN3FCCMD STOP IPSEC 244KN3FCCMD STOP OSA 245KN3FCCMD STOP ROUTE 246KN3FCCMD STOP TCPC 247KN3FCCMD STOP TN3270 252

z/OS systemsCPU usage for monitoring

networks 39

Index 325



��

Printed in USA

SC27-4447-01

Date post:	27-Mar-2020
Category:	Documents
Upload:	others
View:	8 times
Download:	0 times

IBMTivoli OMEGAMON XE for Mainframe Networks Version 5.1 · IBMTivoli OMEGAMON XE for Mainframe...

Documents