Planning and Configuration Guide

Transcription

1 IBM Tivoli OMEGAMON XE for Mainframe Networks Version Planning and Configuration Guide SC

2

3 IBM Tivoli OMEGAMON XE for Mainframe Networks Version Planning and Configuration Guide SC

4 Note Before using this information and the product it supports, read the information in Notices on page 313. This edition applies to version of IBM Tivoli OMEGAMON XE for Mainframe Networks (product number 5698-T03) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2006, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Figures vii Tables ix Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 1 Enhanced 3270 user interface Tivoli Management Services OMEGAMON XE common components Interoperability and integration Software and hardware prerequisites Required software Supported hardware New in this release New in Version New common features of all OMEGAMON version monitoring agents on z/os New function added since Version Fix Pack IPv6 considerations Abbreviations used by the Configuration Tool Chapter 2. Planning for configuration 39 CPU usage for monitoring networks on z/os systems Understanding how real-time data is collected Determining which systems and TCP/IP address spaces to monitor Determining which types of real-time data to collect 41 Defining data collection intervals Defining display intervals Defining and running situations Understanding how historical data is collected.. 48 Determining which types of historical data to collect 50 Designing workspaces Tuning OMEGAMON XE components Planning security Planning for OMEGAMON II for Mainframe Networks Chapter 3. Preparing your z/os environment Enabling the z/os Communications Server network management interface Enabling SNMP manager functions Starting the OSA adapter SNMP subagent Verifying the z/os environment setup Defining monitoring agent access to the NMI and commands Chapter 4. Upgrading to the new release Upgrade overview Upgrading to the new release Configuring a high availability hub and converting a static hub to a remote Enabling new features Performing a staged upgrade Upgrade considerations for the OMEGAMON XE for Mainframe Networks monitoring agent Upgrading a persistent data store Migrating historical data in the Tivoli Data Warehouse for Tivoli Enterprise Portal Upgrade issues related to SNMP configuration 71 Upgrade issues related to running different product versions Upgrading an existing OMEGAMON II for Mainframe Networks environment Chapter 5. Configuration Chapter 6. Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method Configuring the enhanced 3270 user interface using the PARMGEN method Mainframe Networks configuration parameters.. 79 Configuring security for Take Action commands.. 84 Finding previous PARMGEN configuration sessions 84 Ensuring that your runtime environment supports the NetView for z/os packet trace using PARMGEN Chapter 7. Configuring the monitoring agent using the Configuration Tool.. 87 Configuring the enhanced 3270 user interface using the Configuration Tool Summary of the OMEGAMON XE configuration steps Running the JCL Jobs Accessing OMEGAMON XE configuration steps in the Configuration Tool Step 1: Registering with local TEMS Step 2: Specifying configuration parameters Adding, changing, or updating a monitored system definition Step 3: Specifying agent address space parameters 105 Step 4: Specifying dynamic terminal integration parameters Step 5: Creating runtime members Step 6: Configuring the persistent datastore (in the agent) Step 7: Loading the runtime libraries Considerations when performing the RTE load function Step 8: Completing the configuration Updating your runtime environment to support the NetView for z/os packet trace Copyright IBM Corp. 2006, 2012 iii

6 Chapter 8. Completing the configuration Perform agent-specific security configuration Define monitoring agent access to the network management interfaces and commands Give users authorization and resource access to run the VARY TCPIP DROP command Add support for the SYSTCPD DDNAME in the started tasks Copy the started task procedures to your procedure library Vary the VTAM major node active and copy it to your VTAMLST library APF authorize your libraries Enable historical data store maintenance Run the ITMSUPER Tools (optional) Making the performance monitor interface (PMI) exit available to VTAM Enabling CSA tracking to display TCP/IP CSA usage Configuring the OMEGAMON XE for Mainframe Networks SNMP manager functions Authorize the OMEGAMON XE for Mainframe Networks started tasks for TCP/IP privileges Configure historical data collection Enable Warehouse agents on a z/os hub monitoring server Install application and language support Verify the configuration Enable security Enabling security at Tivoli Enterprise Portal Enabling SNMP V3 passwords for autonomous agents Authorizing users to access OMEGAMON XE for Mainframe Networks managed systems on the enhanced 3270 user interface Authorizing users to issue Take Action commands Deploy the configuration Relink the runtime environments Chapter 9. Verifying the configuration 149 Verifying configuration if you configured both Tivoli Enterprise Portal and the enhanced 3270 user interface Verifying configuration if you configured only the enhanced 3270 user interface Appendix A. Configuring the OMEGAMON II for Mainframe Networks component Components of OMEGAMON II for Mainframe Networks that you configure Configuring OMEGAMON II for Mainframe Networks using the PARMGEN method Configuring OMEGAMON II for Mainframe Networks using the Configuration Tool Accessing OMEGAMON II configuration steps in the Configuration Tool Step 1: Specify configuration values Step 2: Allocate additional runtime data sets Step 3: Create runtime members Step 4: Run migration utility Step 5: Loading the runtime libraries and exiting the Configuration Tool Step 6: Completing the configuration Step 7: Configuring SAS Historical Reporting and complete SAS configuration Changing the parameters after you exit the Configuration Tool Next steps Appendix B. Customizing the OMEGAMON II components and verifying installation Customizing NCP Specifying required NCP generation parameters 186 Displaying performance statistics using X.25 NCP generation Using the NPALU definition to connect to the NCP collector Enabling NCP data collection Disabling NCP data collection Customizing ETE Enabling ETE Disabling ETE Configuring security Using the NAM facility for security Using RACF Implementing external function-level security 192 Running in dedicated mode Activating a dedicated terminal Deactivating a dedicated terminal Setting the polling interval SMF record considerations Enabling SMF recording Verifying the configuration Starting End-to-End V Activating the OMEGAMON II major node Starting OMEGAMON II Initializing the NAM database Logging onto OMEGAMON II Enabling TCP/IP data collection Enabling OMEGAMON II console support Setting thresholds and exceptions Appendix C. KN3FCCMD and KONFCCMD command reference Introduction to the KN3FCCMD commands KN3FCCMD HELP KN3FCCMD INSTALL FPCT KN3FCCMD INSTALL FPON KN3FCCMD INSTALL SEMV KN3FCCMD INSTALL SEVT KN3FCCMD INSTALL TCPC KN3FCCMD START CONN KN3FCCMD START CSM KN3FCCMD START DBUG KN3FCCMD START EEHPR KN3FCCMD START FTP iv IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

7 KN3FCCMD START GLBS KN3FCCMD START INTE KN3FCCMD START INTS KN3FCCMD START IPSEC KN3FCCMD START OSA KN3FCCMD START ROUTE KN3FCCMD START SNAC KN3FCCMD START TCPC KN3FCCMD START TN KN3FCCMD STATUS DBUG KN3FCCMD STATUS FCPT KN3FCCMD STATUS FPON KN3FCCMD STATUS SEMV KN3FCCMD STATUS SEVT KN3FCCMD STATUS SNAC KN3FCCMD STATUS TCPC KN3FCCMD STOP CONN KN3FCCMD STOP CSM KN3FCCMD STOP DBUG KN3FCCMD STOP EEHPR KN3FCCMD STOP FTP KN3FCCMD STOP GLBS KN3FCCMD STOP INTE KN3FCCMD STOP INTS KN3FCCMD STOP IPSEC KN3FCCMD STOP OSA KN3FCCMD STOP ROUTE KN3FCCMD STOP TCPC KN3FCCMD STOP TN Introduction to the KONFCCMD commands Using the KONFCCMD command KONFCCMD examples Appendix D. Disk space requirements for historical data tables Alternative methods of determining storage requirements Trial and error approach Estimating approach Allocating additional storage and data sets Estimating the space requirements Historical data tables Tools for estimating data storage requirements Agent historical data storage TCP/IP historical data storage VTAM historical data storage FTP historical data storage TN3270 historical data storage OMEGAMON XE for Mainframe Networks disk space summary worksheet Estimating the storage required per LPAR Appendix E. Format of the SNMP configuration file When to create the SNMP configuration file Format of the SNMP manager configuration file 289 Sample configuration file Documentation library IBM Tivoli OMEGAMON XE for Mainframe Networks publications OMEGAMON XE and Tivoli Management Services on z/os common library IBM Tivoli Monitoring library Documentation for the base agents Related publications Other sources of documentation Support information Index Accessibility Notices Privacy policy considerations Privacy policy considerations Trademarks Index Contents v

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

9 Figures 1. Tivoli Management Services architecture The Enterprise Networks view in the OMEGAMON XE for Mainframe Networks Tivoli Enterprise Portal Navigator Enterprise Networks Navigation view Typical configuration for deployment of the OMEGAMON XE for Mainframe Networks monitoring agent PARMGEN Workflow Welcome panel on entry Product component selection menu panel The Configure OMEGAMON Enhanced 3270 UI / RTE: rte panel The Specify Configuration Values panel Product component selection menu panel Configure OMEGAMON XE for Mainframe Networks panel Specify configuration parameters panel Specify component configuration panel Specify component configuration (page 2) panel Specify component configuration (page 3) panel Specify component configuration (page 4) panel Specify VTAM applid values / RTE (Page 5) panel Specify TCP/IP monitored system information panel Add TCP/IP monitored systems information panel Add TCP/IP monitored systems info2 panel Add TCP/IP monitored systems info3 panel Specify agent address space parameters panel Specify IP.PIPE communication protocol panel Specify Agent IP.UDP Configuration Values panel Specify Agent SNA Configuration Values panel Specify Advanced Agent Configuration Values panel Specify Dynamic Terminal Integration Parameters panel Specify persistent data store values for the monitoring agent Allocate persistent data store menu for the monitoring agent Persistent data store specifications panel for the monitoring agent Allocate persistent data store menu for the monitoring agent Runtime Environments panel Update Runtime Environment (3 of 3) panel Command and Response Log workspace (KN3CRTS) NCP Collector within the OMEGAMON II address space NCP Collector in another OMEGAMON II address space Runtime environments (RTEs) panel Product component selection menu panel Configure OMEGAMON II for Mainframe Networks/RTE: rtename panel Specify configuration values/rte:rtename panel Local NCP data collection/rte: rtename panel Remote NCP data collection/rte: rtename panel Specify TCP/IP component configuration panel Configure OMEGAMON II for Mainframe Networks /RTE:rtename panel Configure SAS Historical Reporting / RTE: rtename panel: Panel SAS Historical Components / RTE: rtename panel: Panel Define SAS Historical Components/ RTE: rtename panel: Panel SAS Historical Components / RTE: rtename panel: Panel NCP NPALU Definitions panel Formula for calculating DASD Formula for Agent historical collection data storage Formula for TCP/IP historical collection data storage Formula for VTAM historical collection data storage Formula for FTP historical collection data storage Formula for TN3270 historical collection data storage KB formula for total storage required per LPAR for cylinders of 3390 DASD Cylinder formula for total storage required per LPAR in cylinders of 3390 DASD Copyright IBM Corp. 2006, 2012 vii

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

11 Tables 1. z/os common components New workspaces displayed in Tivoli Enterprise Portal New workspaces displayed in the enhanced 3270 user interface New attributes and attribute values New attributes and attribute values Configuration Tool abbreviations Names and sizes for data spaces used during data collection Data collected every time the Agent or TCP/IP subnode workspaces are displayed or refreshed Data collected once every collection interval Data collected for each monitored LPAR FTP data collected TN3270 data collected Preconfiguration tasks Tasks to complete before configuring OMEGAMON XE for Mainframe Networks OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configuration profile Parameters and explanations for the Update Runtime Environment (3 of 3) panel Parameters and explanations for the Specify Configuration Parameters panel Parameters and explanations for the Specify Component Configuration panel Parameters and explanations for the Specify Component Configuration (Page 2) panel Parameters and explanations for the Specify Component Configuration (Page 3) panel Parameters and explanations for the Specify Component Configuration (Page 4) panel Parameters and explanations for the Specify VTAM APPLID Values (Page 5) panel Parameters and explanations for the Specify TCP/IP Monitored Systems Information panel Parameters and explanations for the Add TCP/IP Monitored Systems Info panel Parameters and explanations for the Add TCP/IP Monitored Systems Info2 panel Parameters and explanations for the Add TCP/IP Monitored Systems Info3 panel Parameters and explanations for the Specify Agent Address Space Parameters panel Parameters and explanations for the Specify Agent IP.PIPE Communication Protocol and Specify Agent IP.UDP Configuration Values panels Parameters and explanations for the Specify Agent SNA Configuration Values panel Parameters and explanations for the Advanced agent configuration values panel Parameters and explanations for the Specify dynamic terminal integration parameters panel Parameters and explanations for the Specify Persistent Datastore Values panel Parameters and explanations for the Persistent Datastore Specifications panel Parameters and explanations for the Update Runtime Environment (3 of 3) panel Product components for OMEGAMON II for Mainframe Networks Parameters and explanations for the Specify Configuration Values panel Parameters and explanations for the Local NCP Data Collection panel Parameters and explanations for the Remote NCP Data Collection panel Parameters and explanations for the Specify TCP/IP Component Configuration panel Parameters and explanations for the Configure SAS Historical Reporting / RTE: rtename panel Parameters and explanations for the Define SAS Historical Component / RTE: rtename panel Parameters and explanations for the SAS Historical Components / RTE: rtename panel Operating requirements for NCP Attribute groups and workspaces affected by the KN3FCCMD START CONN command Attribute groups and workspaces affected by the KN3FCCMD START CSM command Components available from subset trace records Attribute groups and workspaces affected by the KN3FCCMD START EEHPR command Attribute groups and workspaces affected by the KN3FCCMD START FTP command Attribute groups and workspaces affected by the KN3FCCMD START GLBS command Attribute groups and workspaces affected by the KN3FCCMD START INTE command Attribute groups and workspaces affected by the KN3FCCMD START INTS command Attribute groups and workspaces affected by the KN3FCCMD START IPSEC command Attribute groups and workspaces affected by the KN3FCCMD START OSA command Attribute groups and workspaces affected by the KN3FCCMD START ROUTE command Attribute groups and workspaces affected by the KN3FCCMD START SNAC command Attribute groups and workspaces affected by the KN3FCCMD START TCPC command Attribute groups and workspaces affected by the KN3FCCMD START TN3270 command. 230 Copyright IBM Corp. 2006, 2012 ix

12 58. Attribute groups and workspaces affected by the KN3FCCMD STOP CONN command Attribute groups and workspaces affected by the KN3FCCMD STOP CSM command Components available from subset trace records Attribute groups and workspaces affected by the KN3FCCMD STOP EEHPR command Attribute groups and workspaces affected by the KN3FCCMD STOP FTP command Attribute groups and workspaces affected by the KN3FCCMD STOP GLBS command Attribute groups and workspaces affected by the KN3FCCMD STOP INTE command Attribute groups and workspaces affected by the KN3FCCMD STOP INTS command Attribute groups and workspaces affected by the KN3FCCMD STOP IPSEC command Attribute groups and workspaces affected by the KN3FCCMD STOP OSA command Attribute groups and workspaces affected by the KN3FCCMD STOP ROUTE command Attribute groups and workspaces affected by the KN3FCCMD STOP TCPC command Attribute groups and workspaces affected by the KN3FCCMD STOP TN3270 command Definition and default values for cylinders and group count parameters Sample group count and cylinders to allocate to enable viewing of 24 hours of data Historical data tables Agent data collected KN3 Agent Status (KN3AGS) worksheet TCP Collector Status (KN3TCS) worksheet SNA Collector Status (KN3SCS) worksheet Data collected once every collection interval Current IP Filters (KN3IFC) worksheet Dynamic IP Tunnels (KN3ITD) worksheet Interfaces (KN3TIF) worksheet IKE Tunnels (KN3ITI) worksheet IPSec Status (KN3ISS) worksheet KN3 ICMP Global Counters (KN3GCG) worksheet KN3 ICMP Type Counters (KN3GCT) worksheet KN3 Interface Address (KN3IFA) worksheet KN3 Interface Read Queue (KN3IFR) worksheet KN3 Interface Statistics (KN3IFS) worksheet KN3 Interface Status (KN3IFE) worksheet KN3 Interface Write Queue (KN3IFW) worksheet KN3 IP Counter Statistics (KN3GIC) worksheet IP General Statistics (KN3GIG) worksheet KN3 TCP Counter Statistics (KN3GTC) worksheet KN3 UDP Counter Statistics (KN3GUC) worksheet Manual IP Tunnels (KN3ITM) worksheet OSA-Express Channels (KN3TCH) worksheet OSA-Express LPARS (KN3TLP) worksheet OSA-Express Ports (KN3TPO) worksheet OSA 10 Gigabit Ports Control (KN3TTC) worksheet OSA 10 Gigabit Ports Errors (KN3TTE) worksheet OSA 10 Gigabit Ports Summary (KN3TTS) worksheet OSA 10 Gigabit Ports Throughput (KN3TTT) worksheet OSA-Express3 Ports Control (KN3THC) worksheet OSA-Express3 Ports Errors (KN3THE) worksheet OSA-Express3 Ports Summary (KN3THS) worksheet OSA-Express3 Ports Throughput (KN3THT) worksheet TCP Listener (KN3TCL) worksheet TCPIP Address Space (KN3TAS) worksheet TCPIP Applications (KN3TAP) worksheet TCPIP Connections (KN3TCN) worksheet TCPIP Details (KN3TCP) worksheet TCPIP Devices (KN3TDV) worksheet TCPIP Gateways (KN3TGA) worksheet TCPIP Memory Statistics (KN3TPV) worksheet TCPIP Stack Layer (KN3TSL) worksheet UDP Connections (KN3UDP) worksheet Data collected once every collection interval CSM Storage (KN3CSM) worksheet EE Connection Details (KN3EED) worksheet EE Connections (KN3EEC) worksheet HPR RTP Connections (KN3HPR) worksheet KN3 CSM Storage by Owner (KN3CSO) worksheet VTAM Summary Statistics (KN3VAS) worksheet VTAM Buffer Pool Extents (KN3BPE) worksheet VTAM Buffer Pools (KN3BPD) worksheet VTAM Buffer Usage by Address Space (KN3BPS) worksheet VTAM Buffer Usage by Application for Address Space (KN3BPA) worksheet VTAM Buffer Usage by Category (KN3BPG) worksheet VTAM I/O (KN3VIO) worksheet VTAM Summary Statistics (KN3SNA) worksheet FTP data collected FTP Sessions (KN3FSE) worksheet TCPIP FTP (KN3FTP) worksheet TN3270 data collected TN3270 Server Sess Avail (KN3TNA) worksheet Disk space summary x IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

13 Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks IBM Tivoli OMEGAMON XE for Mainframe Networks is a monitoring agent that is located on each z/os image you want to monitor. This monitoring agent assists you in anticipating network performance problems and warns you when critical events take place on your systems. OMEGAMON XE for Mainframe Networks Version is equivalent to Version with APARs OA42339 and OA42422 applied. You can upgrade from OMEGAMON XE for Mainframe Networks V5.1.0 by installing the PTFs and fix pack that are associated with APARs OA42339 and OA42422, or you can upgrade from V4.1.0 or later by ordering and installing OMEGAMON XE for Mainframe Networks V5.1.1 PID: 5698-T03. If you have enabled the self-describing agent feature, and you do not use the Tivoli Enterprise Portal desktop client, you do not need to install the distributed fix pack that goes with the APARs. Refer to the Version Program Directory for pre-requisites and installation instructions. With OMEGAMON XE for Mainframe Networks, you can monitor and manage the health of TCP/IP and VTAM resources (in addition to NCP performance monitoring, which is provided by the OMEGAMON II for Mainframe Networks component) within your IBM z/os environments. OMEGAMON XE for Mainframe Networks is designed to analyze TCP/IP performance among CICS, DB2, IMS, and other key applications to identify resource loss and unstable connections. The power to monitor the user experience 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 VTAM v Monitors file transfer protocol (FTP) and TN3270 sessions v Monitors High-Performance Routing (HPR) links and Enterprise Extender (EE) connections v Monitors performance of OSA adapters v Provides information about application connections, ports, packet size, and volume v Measures IP discards, reassemblies, and fragmentation v Provides detailed analysis of TCP/IP connections that are slow, unstable, or down v Displays information for each TCP/IP connection such as application name and IP addresses v Measures transaction round-trip time using the OMEGAMON II for Mainframe Networks ETE component v 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 Management Services, 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 conditions are 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, that promote 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 and IBM Tivoli Monitoring products. Copyright IBM Corp. 2006,

14 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 the OMEGAMON II component. See Appendix A, Configuring the OMEGAMON II for Mainframe Networks component, on page 155 and Appendix B, Customizing the OMEGAMON II components and verifying installation, on page 185 for information about OMEGAMON II. The configuration information for the enhanced 3270 user interface is found in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. This information assumes you are ready to configure the OMEGAMON XE for Mainframe Networks monitoring agent and (optionally) the OMEGAMON II for Mainframe Networks component. Before you begin 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 docview.wss?uid=swg Additional planning information for the OMEGAMON XE for Mainframe Networks monitoring agent is also found in Chapter 2, Planning for configuration, on page 39. v Set up your z/os environment using the information found in Chapter 3, Preparing your z/os environment, on page 59. v Study and review the progression of tasks defined in the IBM Tivoli OMEGAMON XE Monitoring Agents on z/os: Quick Start Guide if you are installing an OMEGAMON monitoring agent for the first time. Review the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide and Chapter 4, Upgrading to the new release, on page 67 if you are upgrading from a previous version. v Set up or upgrade your Tivoli Management Services environment to match the versions described in the IBM Tivoli Monitoring: Installation and Setup Guide under Software and hardware prerequisites on page 5. v Use the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference to configure this monitoring agent and the z/os components of your environment using the PARMGEN method. Choose the scenario that best matches your requirements, and use the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Parameter Reference to understand configuration parameters common to the Tivoli Management Services environment, and the IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference to understand configuration parameters associated with this monitoring agent. See Chapter 6, Configuring OMEGAMON XE for Mainframe Networks 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/os components of your environment. The preferred method is PARMGEN. See Chapter 7, Configuring the monitoring agent using the Configuration Tool, on page 87. v Configure your Tivoli Enterprise Monitoring Server on z/os using the information in IBM Tivoli Monitoring: 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 Tivoli Enterprise Portal and the enhanced 3270 user interface on page 149. Enhanced 3270 user interface The OMEGAMON enhanced 3270 user interface is a component within the OMEGAMON XE for Mainframe Networks base product. The OMEGAMON enhanced 3270 user interface component is the latest generation of 3270 interfaces for the 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

15 features of the earlier OMEGAMON II (CUA) interface, but extends the functionality to include many new features, including cross-system and cross-product reporting. You can use the OMEGAMON enhanced 3270 user interface component to monitor the performance of your z/os systems, applications, and devices in your environment and helps you identify and troubleshoot problems with those monitored resources. The OMEGAMON enhanced 3270 user interface is developed using the common OMNIMON base component. In the interface, data is presented in workspaces and subpanels in which thecollected data and relevant information are displayed. You can use the predefined workspaces in OMEGAMON XE for Mainframe Networks to quickly and easily diagnose 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 Management Services on z/os: OMEGAMON Enhanced 3270 User Interface Reference and the IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User Interface Guide. Tivoli Management Services OMEGAMON XE for Mainframe Networks takes advantage of the Tivoli Management Services infrastructure. Tivoli Management Services provides security, data transfer and storage, notification mechanisms, user interface presentation, and communication services for a number of products, including IBM Tivoli Monitoring and OMEGAMON XE monitoring agents, in an agent-server-client implementation. This set of relationships is shown in Figure 1 on page 4. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 3

16 Figure 1. Tivoli Management Services architecture Some components of Tivoli Management Services, such as Tivoli Enterprise Portal and the Warehouse Proxy and Summarization and Pruning agents, run only on distributed systems (Windows, AIX, and Linux). The Tivoli Enterprise Monitoring Server and the Tivoli Data Warehouse can run on either distributed or mainframe systems. The Tivoli Management Services: Engine (TMS: Engine) runs only on mainframe systems. The components of Tivoli Management Services are described in detail in the IBM Tivoli 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 the IBM Tivoli Monitoring and OMEGAMON Information Center. Note: The shared components of the IBM Tivoli Management Services on z/os product are not automatically included in the product package for a monitoring agent on z/os systems. Be sure to include IBM Tivoli Management Services on z/os in your order. If you have not ordered any monitoring agents on a z/os system but you want to install a monitoring server on a z/os system, you can order IBM Tivoli Management Services on z/os by itself. The IBM Tivoli Management Services on z/os product includes both mainframe and distributed components of Tivoli Management Services (IBM Tivoli Monitoring). OMEGAMON XE common components OMEGAMON XE monitoring agents on z/os share several components (referred to as common components: see Table 1). These common components, along with the monitoring agent software are included on the OMEGAMON XE for Mainframe Networks V5.1.0 product tape. 4 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

17 Table 1. z/os common components Component Function End-to-End Response Time Provides response time data for several OMEGAMON XE products. collector V6.2.0 OMNIMON base V7.0.0 Provides a set of common code that is used by OMEGAMON Classic (realtime collectors) components and the OMEGAMON enhanced 3270 user interface to control initialization, security, and I/O for all sessions. OMNIMON Base has two components: v OMEGAMON Subsystem (formerly Candle Subsystem): A z/os subsystem, running in its own address space, that enables OMEGAMON IIs running in other address spaces to monitor dynamic device activity. A single OMEGAMON Subsystem can support multiple copies of OMEGAMON II and multiple OMEGAMON II products on a single z/os image. Some OMEGAMON XE monitoring products, including OMEGAMON XE 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 the Tivoli Enterprise Monitoring Server and the supporting OMEGAMON XE on z/os monitoring agents. One instance of the interface must be installed in each Sysplex for use by all supporting agents. Note: If you install OMEGAMON XE for Mainframe Networks into an existing environment, in which the components are already at the required level, for example, if you have already installed another OMEGAMON XE agent, you might need to delete the FMIDs for these components from the SMP/E install jobs to avoid errors because they are already installed. See the IBM Tivoli OMEGAMON XE for Mainframe Networks: Program Directory for more information. Interoperability and integration OMEGAMON XE for Mainframe Networks is designed to integrate with all products that use Tivoli Management Services. These products exploit the ability of the Tivoli Enterprise Portal to integrate and correlate performance and availability information from a variety of sources. For example, with OMEGAMON DE, you can create custom workspaces composed of data from a range of Tivoli monitoring solutions (IBM Tivoli Monitoring, IBM Tivoli Composite Application Manager, and IBM Tivoli NetView for z/os, and OMEGAMON XE monitoring agents). You can also create context-sensitive links between product workspaces to obtain additional information about systems, subsystems, resources, or network components that are being monitored by other monitoring agents, or links that access related screens in TN3270-based applications. OMEGAMON XE products are being integrated with an increasing number of other Tivoli and IBM products. Situation events reported by OMEGAMON XE for Mainframe Networks can be forwarded to Tivoli Event Console or Tivoli Netcool/OMNIbus for event correlation and management. From the Tivoli Enterprise Portal you can "launch in context" into other Web-based or Web-enabled Tivoli applications without having to re-enter user credentials, and you can "launch in context" into Tivoli Enterprise Portal workspaces from applications such as IBM Tivoli Business Services Manager. Software and hardware prerequisites Tivoli Management Services must already be installed. Versions of all the required products for Mainframe 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 your enterprise, you can use the currently installed Tivoli Management Service components. A complete list of Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 5

18 the product components is found in the IBM Tivoli OMEGAMON XE Monitoring Agents on z/os: Quick Start Guide, and the z/os prerequisites are found in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Program Directory. Information about z/os and distributed prerequisites are found in the sections that follow. Required software The 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 are explained in the section that follows. Software product and levels The following software products and levels are required for running the Tivoli Management Services components and the OMEGAMON XE for Mainframe Networks monitoring agent. PARMGEN configuration requirements OMEGAMON XE for Mainframe Networks and OMEGAMON II for Mainframe Networks are configured by using the PARMGEN method. Configuration using the PARMGEN method requires a minimum of IBM Tivoli Management Services v6.2.3 Fix Pack 1 with APAR OA39890 or later or PTFs UA66332 and UA69076 (for LIMIT support) applied. If the hub monitoring server and the remote monitoring server reside on z/os, they must also be modified to use LIMIT(24,X). Follow the process outlined in the Configuring the Tivoli Enterprise Monitoring Server on z/os book and ensure that the Maximum storage request size (Extended) value is set to greater than or equal to 24. Also, you cannot migrate or configure an OMEGAMON monitoring agent on z/os earlier than v4.2.0 by using the PARMGEN method. See the PARMGEN Technote found at docview.wss?uid=swg for additional requirements. See also the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference. Configuration Tool requirements If you install this monitoring agent using the Configuration Tool, use v or later of the Configuration Tool, which is included in the product package. If you have an earlier version of the Configuration Tool on your z/os system in the same consolidated software inventory (CSI), it is automatically replaced by v or later of the Configuration Tool during installation. The preferred method of configuration is PARMGEN. Software requirements for Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Tivoli Data Warehouse on distributed operating systems Before you install the OMEGAMON XE for Mainframe Networks monitoring agent into an existing Tivoli Management Services environment, ensure that you have upgraded this environment to version Fix Pack 1 or later. Best practice: Version Fix Pack 3 or later. If you are already running v6.3.0 of IBM Tivoli Monitoring components, then v6.3.0 Fix Pack 1 is the best practice recommendation. Detailed software requirements for all distributed components of the Tivoli Management Services (Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal, Tivoli Enterprise Portal Server, and Tivoli Data 6 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

19 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 UA66193 or later. Best practice: PTF UA 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 in IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. Other environment planning decisions about the Tivoli Enterprise Monitoring Server on z/os are also 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 in IBM 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 Enterprise Monitoring Server on z/os Security on Tivoli Enterprise Monitoring Server on z/os is based on password validation that uses the local operating system. You can use the Resource Access Control Facility (RACF ), which is part of the z/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 the runtime environment to control access to the OMEGAMON XE for Mainframe Networks commands, or you can use a separate security class. Unlike previous releases, these commands fail RACF authorization unless SAF security is configured. See Authorizing users to issue Take Action commands on page 141 for information about configuring SAF security for Take Action commands. Supported versions of z/os for the OMEGAMON XE for Mainframe Networks monitoring agent z/os systems on which zseries monitoring agents such as OMEGAMON XE for Mainframe Networks are installed must be running z/os V1.12 or later. For information about APARs required, see the IBM Tivoli OMEGAMON XE for Mainframe Networks: Program Directory. For late-breaking information, see the Preventive 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 launch the OMEGAMON XE for Mainframe Networks monitoring agent. Be aware that as of z/os V2R1, the ability to use default OMVS segments has been removed. All z/os UNIX users or groups must now have OMVS 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 in system log on z/os v2.1 systems" in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 7

20 Supported versions of Tivoli NetView for z/os If you want to use the Tivoli NetView dynamic workspace links (DWL) feature or launch the NetView 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 APAR OA For more information about DWL links between NetView for z/os and the OMEGAMON XE for Mainframe Networks monitoring agent, refer to the overview of product-provided workspaces section of the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide. For more information about running the NetView packet trace feature from the OMEGAMON XE for Mainframe Networks monitoring agent, see the section on accessing NetView for z/os packet trace by using dynamic links to 3270 applications in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide. Optional software Tivoli NetView Performance Monitor V2R7 is provided as an optionally orderable, no-cost feature to support customers using SNA or moving from SNA to IP. Tivoli NetView Performance Monitor runs as a z/os Communications Server application program. You can use Tivoli NetView Performance Monitor to collect and monitor performance data, collect accounting data, and determine problems in the network for SNA networks. NetView Performance Monitor is provided as part of the IBM Tivoli OMEGAMON XE for Mainframe Networks product package. For more information about Tivoli NetView Performance Monitor, see infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.perfmon.doc_2.7/toc.xml. Supported hardware Most of the hardware that is required to run OMEGAMON XE for Mainframe Networks is determined by operating system considerations. For example, the requirements for the UNIX systems where parts of the IBM Tivoli Monitoring platform are running are determined by the operating system. For most hardware prerequisites, see the IBM Tivoli Monitoring: 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 that can run z/os V1.12 or higher. You must also ensure that you have adequate direct access storage device (DASD) space to accommodate the products you are installing. Before you install your OMEGAMON products, you must review the space requirements and considerations for an SMP/E installed environment to make sure that sufficient DASD storage is available. Note: Program directories cover DASD requirements for SMP/E target and distribution data sets. You can also use the Job Generator (JOBGEN) Reallocation Facility to analyze your DASD requirements and compute your persistent data store requirements. Remember that you also have DASD requirements for runtime libraries and short-term history. Ensure that you define enough DASD for short-term historical data storage. See Appendix D, Disk space requirements for historical data tables, on page 257 for more information about sizing your persistent data store. See docview.wss?uid=swg and for information about the JOBGEN tool. 8 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

21 The Tivoli OMEGAMON XE for Mainframe Networks: Program Directory contains the approximate DASD space requirements for the OMEGAMON II for Mainframe Networks and OMEGAMON XE for Mainframe Networks products. Be aware that this estimate presupposes that these products are installed as standalone applications. When multiple OMEGAMON products are installed into a shared CSI environment, DASD requirements can be less. The Tivoli OMEGAMON XE for Mainframe Networks: Program Directory provides the basic space requirements for the Tivoli Enterprise Monitoring Server, the Tivoli Enterprise Portal, the Tivoli Enterprise Portal Server, and for the monitoring agents. These basic space requirements do not include additional space that is required for maintaining historical data files. Because of the variations in design characteristics such as client distributed systems, system size, and number of managed systems, providing specific disk space requirements for historical data collection is difficult. You might want to experiment to determine how much space you need. Start out by using the default 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 run once a day. Use the information in Appendix D, Disk space requirements for historical data tables, on page 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 adapters in your environment. OSA-Express and OSA-Express2 (except OSA-Express2 10 Gigabit) adapters are supported 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 (SA ) v zenterprise 196, System z10, System z9, and eserver zseries Open Systems Adapter-Express Customer's Guide and Reference (SA ) 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 the OSA-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: 01.ibm.com/servers/resourcelink/lib03010.nsf/pages/osaLibrary?OpenDocument&pathID=&Start=1 -. New in this release The following updates were made to the Tivoli OMEGAMON XE for Mainframe Networks monitoring agent for Version v New in Version on page 10 v New function added since Version Fix Pack 3 on page 23 v New common features of all OMEGAMON version monitoring agents on z/os on page 20 Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 9

22 New in Version The following changes were introduced to OMEGAMON XE for Mainframe Networks in Version Changes to the Navigator in Tivoli Enterprise Portal A new logical view that contains a set of Enterprise Networks workspaces is available from the OMEGAMON XE for Mainframe Networks Navigator in Tivoli Enterprise Portal, an addition to the existing Navigator view. These Enterprise Networks workspaces are accessed by right-clicking the Enterprise_Networks folder of the Enterprise Networks physical Navigator view, as shown in Figure 2. Figure 2. The Enterprise Networks view in the OMEGAMON XE for Mainframe Networks Tivoli Enterprise Portal Navigator The Enterprise Networks workspaces require that an administrator has assigned the Tivoli Enterprise Portal user access to the Enterprise Networks navigator view from the Navigator Views tab of the Administer 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 Mainframe Networks users in the new enhanced 3270 user interface. In version 5.1.1, these enterprise views are made available to users who prefer Tivoli Enterprise Portal using the new set of Enterprise Networks workspaces, 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 network issues. This view provides a cross-lpar, real-time view of the z/os Communications Server network focused on specific application and networking issues. This set of workspaces moves away from LPAR-scope views to enterprise-wide views. These new workspaces eliminate many of the mouse clicks previously required to get to key issues, dramatically improving system availability with faster problem resolution through built-in problem solving scenarios. They also facilitate new enterprise-wide searches based 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 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

23 Table 2. New workspaces displayed in Tivoli Enterprise Portal Workspace name Description Enterprise Applications Health workspace Displays a summary of applications, applications with percent out-of-order segments >=5% or total out-of-order segments >=15%, applications with connections in backlog >= 10 OR total backlog connections rejected > 10, and applications with percent segments retransmitted > 3% OR total segments retransmitted > 10 for applications throughout your enterprise. This workspace also displays 3 Top 5 application bar charts for total backlog connections rejected, total segments retransmitted, and total out-of-order segments. Enterprise Connections Find workspace Displays performance metrics for connections matching search criteria specified by the end user. Enterprise Connections Health workspace Displays connections with time since last activity greater than 10 minutes, connections with connection state not equal to the established state, and connections with inbound or outbound bytes buffered throughout your enterprise. Enterprise EE Connections Overview workspace Displays performance data for Enterprise Extender (EE) links across the enterprise when the IP address for one end of an EE link is located on a monitored z/os system image. Enterprise FTP Sessions Find workspace Displays performance metrics for all FTP sessions matching search criteria specified by the end user. All active or complete FTP sessions captured within the configured FTP display interval that match the search criteria are displayed Enterprise FTP Sessions Overview workspace Displays all FTP sessions that were completed or became active within the display interval across the enterprise. Active sessions that were established or closed prior to the display interval are not displayed. Enterprise FTP Transfers Find Displays performance metrics for all FTP transfers matching search criteria specified by the end user. All active or completed FTP transfers captured within the configured FTP display interval that match the search criteria are displayed. Enterprise HiperSockets Interfaces Overview Displays errors, statistics, configuration and status data for all HiperSockets 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 a monitored z/os system image. Enterprise Interfaces Overview Displays errors, statistics, configuration and status data for all interfaces across the enterprise. Enterprise OMEGAMON for Mainframe Networks Health Enterprise OSA Express Channels Enterprise OSA Express Ports workspace Enterprise OSA Interfaces Overview workspace Displays configuration and status information for OMEGAMON XE for Mainframe Networks monitoring agents across the enterprise. Displays a channel summary for all OSA channels in your enterprise. Displays summary information for all OSA-Express3 ports, OSA-Express2 10 Gigabit ports, OSA-Express 4s, and OSA-Express ports across your enterprise Displays errors, statistics, configuration and status data for all OSA interfaces across the enterprise. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 11

24 Table 2. New workspaces displayed in Tivoli Enterprise Portal (continued) Workspace name Enterprise TN3270 Find Enterprise TN3270 Server Overview Description Displays performance metrics for all TN3270 server connections matching search criteria specified by the end user. All TN3270 server connections captured within the configured TN3270 display interval that match the search criteria display regardless of the status of the session (Active, Completed or None). Displays the current status of all TN3270 Server ports across the enterprise. You can also access these new workspaces using the Enterprise Networks Navigation view found in every Enterprise_Networks workspace. The Enterprise Networks Navigation view is a scrollable list of workspaces available from the Enterprise_Networks view. This view also includes Enterprise-level Find workspaces used to locate groups of like resources. The Enterprise Networks Navigation view is found in every Enterprise workspace immediately adjacent to the Navigator. This view is shown in Figure 3: Figure 3. Enterprise Networks Navigation view To access one of the Enterprise Networks workspaces from the Enterprise Networks Navigation view, do the 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 displayed that 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 Tivoli Enterprise Portal, accessed through the Enterprise Networks workspaces: v Under the Applications Navigator item: Workspace name Application Details Description Displays connection data, throughput data, and datagram data for the selected application. v Under the Connections Navigator item: 12 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

25 Workspace name TCP Connection Details Description Displays status and response time, retransmissions and out-of-order segments, statistics, window size, configuration, security, and TN3270 information for the selected connection. v Under the EE Navigator item: Workspace name EE Connection Summary Description Displays performance data for a selected Enterprise Extender (EE) connection. v Under the HPR Navigator item: Workspace name HPR Connection Details Description Displays performance data for a selected High-Performance Routing (HPR) Rapid Transfer Protocol (RTP) connection (pipe). v Under the FTP Navigator item: Workspace name FTP Session Details FTP Transfer Details FTP Transfers for Session Description Displays IP addresses and ports, application name, user IDs, and sessions for the selected FTP session. Displays detailed information for the selected FTP transfer including IP addresses, ports, transmission details, user IDs, commands, dataset, security, and connection attributes Displays all FTP transfers that were completed or became active within the display interval for a selected FTP session v Under the TN3270 Navigator item: Workspace name Active TN3270 Server Connections for Selected Port Description Displays the current status of all active TN3270 Server connections on a given system, TCP/IP stack name and port. The workspace displays both active TN3270 server sessions and active TN3270 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 Summary KN3CSOS Displays the following for a selected system: workspace v Communications Storage Manager (CSM) storage by owner v CSM storage allocated by pool v CSM storage EE Connection Summary for EE_PU_NAME workspace KN3EEDS Displays the following performance data for the selected Enterprise Extender (EE) link: v Enterprise Extender Connection Details v HPR Connections Summary Enterprise Active FTP Transfers Overview workspace KN3FTPO Displays all FTP transfers that became active within the display interval across the enterprise. Active transfers that were initiated before the display interval are not displayed. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 13

26 Table 3. New workspaces displayed in the enhanced 3270 user interface (continued) Workspace Panel ID Description Enterprise EE and HPR Connections Health workspace Enterprise EE and HPR Connections Health workspace Enterprise FTP Sessions Overview workspace Enterprise HiperSocket Interfaces Overview workspace Enterprise HPR Connections Overview workspace KN3EECO2 KN3EECO KN3FSEO KN3IFSO2 KN3HPRO Displays Enterprise Extender (EE) and High Performance Routing (HPR) connections throughout your enterprise that meet the following criteria: v EE connections with high percent packets retransmitted v HPR connections with ARB mode = yellow or red v HPR connections experiencing path switches v HPR connections with high unacknowledged buffers v HPR connections with high out of sequence buffers v HPR connections with long routes v HPR connections with actual < initial throughput rate Displays performance data for EE connections throughout your enterprise. Displays the following for all FTP Sessions that were completed or became active within the display interval across the enterprise. Active sessions that were established prior to the display interval are not displayed. v FTP sessions summary v FTP login failures summary v FTP session failures summary Displays the following information for HiperSocket interfaces throughout your enterprise: v HiperSocket interface statistics v HiperSocket interface status v HiperSocket interface write queue statistics v HiperSocket interface read queue statistics Displays performance data for High-Performance Routing (HPR) Rapid Transfer Protocol (RTP) connections (pipes) when one endpoint of an HPR connection is located on a monitored z/os system image. FTP Session Details workspace KN3FSED Displays the following data for the selected FTP session: v IP Addresses and ports v Application name and user ID v Session v Security v TCP connections FTP Transfers by Session for Application_Name workspace KN3FTPS Displays all FTP transfers that were completed or became active within the display interval for a selected FTP session. Active transfers that were initiated before the display interval are not included. FTP Transfer Details workspace KN3FTPD Displays the following for the selected FTP transfer: v IP Addresses and Ports v Transmission v User ID and Command v Dataset v Security v Transfer TCP Connection v Session TCP Connection 14 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

27 Table 3. New workspaces displayed in the enhanced 3270 user interface (continued) Workspace Panel ID Description HPR Connection Details workspace KN3HPRD Displays the following detailed statistics about the HPR connections in your enterprise: v ARB, Throughput, and Response Time v Retransmissions, Out of Sequence, and Unacknowledged v Path Switches, Sessions, and Links v SNA Links v Bytes and Packets Statistics v Configuration The name of the KN3START workspace has been changed from Enterprise Applications Health to Enterprise Network Health. New attributes and attributes groups Table 4. New attributes and attribute values Attribute group Table prefix New or changed information EE KN3EEC The following attributes were added. Connections 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 EE Connections Details KN3EED Additionally, the following attributes are now deprecated: v Bytes Received (in GB) v Bytes Sent (in GB) 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. Additionally, the following attributes are now deprecated: v Bytes Received (in GB) v Bytes Sent (in GB) FTP Sessions KN3FSE The following attributes were added. v Cipher Specification v Local Port. The old version of this attribute was deprecated. v Login Method v Remote Port. The old version of this attribute was deprecated. v Security Mechanism v Security Protocol Level v Session Protection Level v Total Bytes Transferred v Total Files Transferred v Transfer Protection Level Enumerated values 9 (Certificate not valid) and 10 (Client name does not match user name) were also added to the Login Failure Reason Description, and enumerated value 0 (Normal session end) was added to Session End Reason Description. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 15

28 Table 4. New attributes and attribute values (continued) Attribute group Table prefix New or changed information HPR Connections KN3 CSM Storage by Owner OSA Express Ports OSA- Express3 Ports Summary OSA 10 Gigabit Ports Summary KN3HPR KN3CSO KN3TPO KN3THS KN3TTS The following new attribute was added: v VTAM STC Name The following attributes were updated from 32-bit integers to 64-bit integers (long long integers). v Bytes Received. The old version of this attribute was deprecated. v Bytes Sent. The old version of this attribute was deprecated. Additionally, the following attributes are now deprecated: v Bytes Received (in GB) v Bytes Sent (in GB) This is a new attribute group. Use the CSM Storage by Owner attributes to create situations that monitor applications that are using Communications Storage Manager (CSM) buffer pools shared between VTAM and TCP/IP. This attribute group contains the following attributes: v Application Name. v ASID v Average Storage in Use Across DSP Pools v Average Storage in Use Across ECSA Pools v Average Storage in Use Across Pools v Collection Time v DSP4K Pool Storage In Use v DSP16K Pool Storage In Use v DSP32K Pool Storage In Use v DSP60K Pool Storage In Use v DSP180K Pool Storage In Use v ECSA4K Pool Storage In Use v ECSA16K Pool Storage In Use v ECSA32K Pool Storage In Use v ECSA60K Pool Storage In Use v ECSA180K Pool Storage In Use v Origin Node v Percent DSP Storage In Use v Percent ECSA Storage In Use v Storage In Use Across Pools v Storage In Use Across DSP Pools v Storage In Use Across ECSA Pools v System ID v VTAM STC Name The zos Release attribute has been designated IBM internal use only. The zos Release attribute has been designated IBM internal use only. 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. 16 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

29 Table 4. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Address Space KN3TAS The following attributes were added: v Input Packets. This attribute replaces the earlier attributes representing the same value, Input Packet Count, which are now deprecated. v Output Packets. This attribute replaces the earlier attributes representing the same value, Output Packet Count, which are now deprecated. v TCP Input Segments. This attribute replaces the earlier attribute representing the same value, TCP Input Segment Count, which are now deprecated. v TCP Output Segments. This attribute replaces the earlier attributes representing the same value, TCP Output Segment Count, which are now deprecated. v UDP Input Datagrams. This attribute replaces the earlier attributes representing the same value, UDP Input Datagram Count, which are now deprecated. v UDP Output Datagrams. This attribute replaces the earlier attributes representing the same value, UDP Output Datagram Count, which are now deprecated. The following additional attributes are now deprecated: v Input Packet Count v Input Packet Count (in G) v Output Packet Count v Output Packet Count (in G) v TCP Input Segment Count v TCP Input Segment Count (in G) v TCP Output Segment Count v 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) TCPIP Applications TCPIP Details KN3TAP KN3TCP The zos Release attribute has been designated IBM internal use only. The following attributes were updated from 32-bit integers to 64-bit integers (long long 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) 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. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 17

30 Table 4. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP FTP KN3FTP The following attributes were added. v Application Name v Bytes Transferred. This attribute replaces the earlier attributes representing the same value, Bytes Transmitted and Bytes Transmitted (in GB), which are now deprecated. 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 same value, 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 Name v Client User ID v Last Reply to Client Description v User ID on Server Extended TN3270 Server Sess Avail KN3TNA Additionally, the following attributes are now deprecated: v Bytes Transmitted v Bytes Transmitted (in GB) v Local IP Port v Remote IP Port The following attributes were updated from 32-bit integers to 64-bit integers (long long 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) 18 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

31 Table 4. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Stack Layer KN3TSL The following attributes were updated from 32-bit integers to 64-bit integers (long long 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 new default workspace is Interface Status. This change was made because beginning at z/osv1.12, z/os Communications Server implemented callable network management interfaces (NMIs) that provide additional metrics for Interfaces, metrics not available in earlier releases of z/os. The Interfaces Status workspace and the workspaces that it links to were designed to exploit the new data available in the NMI. 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 new Enterprise_Networks Enterprise Connections Find workspace. The advantage of this new access point is that the Enterprise Connections Find workspace allows you to specify search criteria to quickly identify the connection whose packets you are about to trace. Configuration changes In Version and earlier, the default value for the LIMIT extended (X) parameter in the sample KN3SYSIN and KONSYSIN files was 23. That default value has been increased to 24. You see this change reflected in the default values for the KN3_X_AGENT_STORAGE_LIMIT_EXTEND parameter and in the updated defaults for the sample KN3SYSIN file. If you are monitoring a large number of a resources, such as TN3270 sessions, you might want to increase the 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 address space, the TEMS value applies to both the TEMS and the monitoring agent, and the monitoring agent does not have its own value. If the monitoring agent is configured stand-alone, then the monitoring agent value for each parameter overrides the TME:Engine value, and the TEMS value has no effect on the Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 19

32 monitoring agent. If the TEMS value can override the monitoring agent value in your environment, you will 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 message were 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 to by the PARMGEN profile parameter KN3_SNMP_CONFIG_FILE. When PARMGEN adds the IP address, the address is padded with leading zeros. This may prevent the SNMP Manager from connecting properly to the SNMP Agent. To address this problem, if leading zeros are present, remove them from the IP address that PARMGEN places in the member pointed to by KN3_SNMP_CONFIG_FILE. For example, if PARMGEN adds this IP address: Change it to the following: 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 monitoring agents on z/os The following sections describe new features of the framework, the Configuration Tool, or the product itself that affect deployment and configuration of the monitoring agent. If you are already using Tivoli Management Services components at V6.2.3 or later, you might already be familiar with some of the changes described here. The following topics are covered: v Configuration methods, including PARMGEN and the Configuration Tool v 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 local monitoring server v New shared publications on page 23 v 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 products and components in a runtime environment. You then submit a series of jobs to create a complete runtime environment with the parameter values that you specified. A workflow "wrapper" leads you through the configuration process. The PARMGEN configuration method is the preferred configuration method and is intended to replace the Configuration Tool (ICAT). The PARMGEN method is particularly suitable for the following types of customers: 20 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

33 Existing OMEGAMON XE customers in environments in which one person is responsible for configuring all OMEGAMON XE products and components New OMEGAMON XE customers who are already accustomed to supplying z/os parameter values directly 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 support/docview.wss?uid=swg If you have been using the PARMGEN (formerly PARMLIB) configuration method previously, be aware of the following new addition. The KN3_SECURITY_ACTION_CLASS parameter was added to override the RTE_SECURITY_CLASS value specified for the runtime environment, allowing the use of a separate security class to control command-level security for OMEGAMON XE for Mainframe Networks monitoring agent Take Action commands. v Configuration Tool OMEGAMON XE for Mainframe Networks requires version 3 release 1 modification level 24 (version ) or higher of the Installation and Configuration Assistance tool, which is included in the product package. If you have an earlier version of the Configuration Tool on your z/os operating system in the same consolidated software inventory (CSI), it is automatically replaced by version of the Configuration Tool during installation. The IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide extensively documents the new features of the Configuration Tool. Tivoli Management Services OMEGAMON XE for Mainframe Networks supports Tivoli Management Services V6.2.3 Fix Pack 1. The following topics introduce new features that can affect deployment and configuration. If you are already using Tivoli Management Services components at V6.2.3 or later, you might already be familiar with some of the features. For detailed descriptions of all the new features in Tivoli Management Services V6.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 with dynamic virtual IP addressing (DVIPA) and shared DASD. A high-availability hub is configured in its own runtime environment, without any monitoring agents, and can be configured on the same LPAR with a remote monitoring server. This configuration enables the hub monitoring server to be relocated to any suitable LPAR in the sysplex with no changes, and with minimal disruption to the components connecting to the hub. For information about configuring a high-availability hub on the z/os operating system, and conversion 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 the high 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 distributes each agent's operating configuration directly to the local monitoring server. The server then distributes those agent configuration files first to the hub monitoring server (if necessary) and then to the various IBM Tivoli Monitoring components that require it. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 21

34 Before IBM Tivoli Monitoring V6.2.3, before an agent could connect to a Tivoli Enterprise Monitoring Server, you were required to manually update the monitoring server, as well as other Tivoli Management Services components such as the Tivoli Enterprise Portal Server and the Tivoli Data Warehouse, 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 the self-describing capability of monitoring agents ensures that the proper level of application data is installed on monitoring servers and the Tivoli Enterprise Portal. If the self description feature is activated, runtime verification checks for updated application data. If inconsistent conditions are detected, application data is propagated from the agent to the various monitoring servers, which are automatically 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 should configure a high availability hub. For more information, see IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/os. When you run your hub server on a distributed platform before connecting your OMEGAMON XE for Mainframe Networks agent and before you install your OMEGAMON XE for Mainframe Networks agent, 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 is reporting to, the application support file updates are automatically synchronized, and, if relevant, the updates are deployed to the Tivoli Enterprise Monitoring Server and the connected Tivoli Enterprise Portal Server. The following OMEGAMON XE for Mainframe Networks agent TMS:Engine parameter values increased 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 (without communicating directly with a monitoring server). When running autonomously, a monitoring agent can retain event information when communications with its monitoring server are interrupted. The agent can run private situations that generate events that can be sent to a Netcool/OMNIbus ObjectServer as EIF events or as SNMP alerts, and can collect private history in local short-term storage of 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 configuring Netcool/OMNIbus ObjectServers to receive the events. For information on specifying which situation events to forward, see the Tivoli Enterprise Portal online help and the IBM Tivoli Monitoring: Tivoli Enterprise Portal User's Guide. For information about parameters to set for an autonomous agent, and about defining private situations, private history, and SNMP alerts for private situations, see the "Agent autonomy" 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$PENV member of the PARMGEN WCONFIG library or by using the Specify Nonstandard Parameters panel in 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 and Configuration Guide for more information. For instructions on enabling SNMP V3 passwords for autonomous agents, see the Enabling SNMP V3 passwords for autonomous agents topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. v Automatic registration of products with the local monitoring server 22 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

35 The runtime environment load processing option now automatically copies the product attribute and catalog members from the &thilev.tkandatv target data set that was installed by SMP/E to the runtime environment &rhilev.&rte.rkandatv library. If you apply maintenance that updates the product attribute and catalog members only, you do not have to regenerate and rerun the "Register with local TEMS" job for each product in the runtime environment. Instead, you can just reload the runtime environment to refresh the members. New shared publications The following new publications have been added to the OMEGAMON XE for Mainframe Networks library, 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 new 3270 interface. v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference: describes the use of the PARMGEN tool for the initial deployment and configuration of Tivoli Management Services on z/os components such as the Tivoli Enterprise Monitoring Server and the Tivoli Enterprise monitoring 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 for Mainframe 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 Fix Pack 3 The following changes were introduced to OMEGAMON XE for Mainframe Networks after Version Fix Pack 3. OMEGAMON XE for Mainframe Networks data available from the enhanced 3270 user interface OMEGAMON XE for Mainframe Networks now supports the IBM Tivoli OMEGAMON enhanced 3270 user interface. The enhanced 3270 user interface is the latest generation of 3270-based user interfaces for the OMEGAMON monitoring products. When you use the enhanced 3270 user interface in conjunction with OMEGAMON XE monitoring agents and the Tivoli Enterprise Monitoring Server, you can monitor the performance of the z/os systems, applications, and devices in your environment and helps you identify and troubleshoot problems with those monitored resources. The enhanced interface offers the following features: v Enterprise-wide and single-system views of data v Autodiscovery of and autoconnection to data sources v Customizable workspaces v Support for screen sizes up to 62 x 160 v Dynamic behavior and operation v Take Action commands v 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 Fix Pack 3. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 23

36 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 a more 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. KN3 Interface Statistics OSA 10 Gigabit Ports Errors OSA Express Channels KN3IFS KN3TTE KN3TCH Session Duration The duration of the session. The following attributes were added: Bytes Received or Transmitted The number of bytes sent and received during the most recent sampling interval. The format is an unsigned long long integer. Total Bytes Received or Transmitted The number of bytes sent and received during the most recent sampling interval. The format is an unsigned long long integer. These attributes are not currently in the product-provided Tivoli Enterprise Portal workspaces. They can be added to any user-customizable workspace. The following attribute was added: Interface Index The interface index associated with this port. The format is a four-byte integer. This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. It can be added to any user-customizable workspace. The following attributes were updated with new valid values, as indicated in bold. Channel Hardware Level The hardware model of the channel. This value is stored as an integer but displayed 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 Type The type of channel for this interface. This value is stored as an integer but displayed as a string. The possible values are: v 16 = OSAExpress v 17 = OSADirectExpress v 48 = osaintraensembledata v 49 = osaintraensemblemanage 24 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

37 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information OSA Express3 Ports Errors KN3THE The following attribute was added: Interface Index The interface index associated with this port. The format is a four-byte integer. This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. It can be added to any user-customizable workspace. TCP Listener KN3TCL The following attribute was added. This attribute is in addition to the a two-byte integer version of the same attribute. Local Port The local port for this connection. The format is a four-byte integer. This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. It can be added to any user-customizable workspace. The following new attribute was added: Listener Type Indicates 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 an unsigned integer. The following are valid values: v 0 = Unknown v 1 = TN3270_Server This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. 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 a more 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 Time The amount of time that the server has been idle since the most recent connection was accepted. This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. It can be added to any user-customizable workspace. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 25

38 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Address Space KN3TAS The following new attribute was added: Telnet Session Count The number of Telnet connections that are currently in session with an application. The format is an integer. This attribute is displayed in the Address Space workspace, the TN3270 workspaces, 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 Release The version and release level of z/os on which this monitoring agent is running. This value is stored as an integer and displayed as a string. The following 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_ IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

39 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Applications KN3TAP The following attributes were updated from 32-bit integers to 64-bit integers (long long integers). Byte Rate The number of bytes per minute transmitted to or sent from this application during the most recent time interval. The format is a long long integer. The old version of this attribute was deprecated and has "_32" appended to its name. Bytes Received The number of bytes received on all connections for this application that existed at the end of the most recent time interval. The format is a long long integer. The old version of this attribute was deprecated and has "_32" appended to its name. Bytes Sent The number of bytes sent on all connections for this application that existed at the end of the most recent time interval. The format is a long long integer. The old version of this attribute was deprecated and has "_32" appended to its name. Bytes Sent or Received The number of bytes sent or received on all connections for this application that existed at the end of the most recent time interval. The format is a long long integer. The old version of this attribute was deprecated and has "_32" appended to its name. Receive Byte Rate The number of bytes that was received, per minute, during the most recent time interval. The format is a long long integer. The old version of this attribute was deprecated and has "_32" appended to its name. Transmit Byte Rate The number of bytes that was transmitted, per minute, during the most recent time interval. The format is a long long integer. The old version of this attribute was deprecated and has "_32" appended to its name. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 27

40 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Applications (continued) KN3TAP The following attributes were added. The existing versions of these attributes were displayed as bytes in Tivoli Enterprise Portal. The new versions are displayed sin the most significant unit to better accommodate the column width in the enhanced 3270 user interface. Total Bytes The total number of bytes sent or received on all connections for this application that existed at the end of the most recent time interval. The format is a long long integer. Total Bytes Received The total number of bytes received on all connections for this application that existed at the end of the most recent time interval. The format is an integer. Total Bytes Sent The total number of bytes sent on all connections for this application that existed at the end of the most recent time interval. The format is an integer. These attributes are not currently in the product-provided Tivoli Enterprise Portal workspaces. They can be added to any user-customizable workspace. The following new attribute was added: Application Type Indicates whether this application is a TN3270 server. A value of x 01 indicates that the application is acting as a TN3270 Server. The format is an unsigned integer. The following are valid values: v 0 = Unknown v 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 a more 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. TCPIP Connections KN3TCN Time Since Last Activity The average time since the most recent activity on all connections for this application that existed at the end of the most recent time interval. The following attribute that expresses time spans as the seconds, centiseconds, or milliseconds since an event took place was updated to report time spans in a more 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. Time Since Last Activity The time since the most recent activity on this connection. 28 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

41 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Details KN3TCP The following attributes, which express time spans as the seconds, centiseconds, or milliseconds since an event took place, were updated to report time spans in a more 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 operation takes. Connection Duration The amount of time since this connection was created. Time Since Last Activity The time since the most recent activity on this connection. The following attribute was added. This is in addition to the a two-byte integer version of the same attribute. Local Port The local port for this connection. The format is a four-byte integer. This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. It can be added to any user-customizable workspace. The zos Release attribute was updated to accommodate the latest version of z/os, as indicated in bold. zos Release The version and release level of z/os on which this monitoring agent is running. This value is stored as an integer and displayed as a string. The following 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 a more 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 Duration The amount of time required for the transfer or command to be completed. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 29

42 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Gateways KN3TGA The following attribute was updated to add a new valid value, as indicated in bold: Route Type The type of route used by this gateway. This value is stored as an integer and displayed as a string. Valid values are: v 0 = (blank) v 1 = Other v 2 = Static v 4 = ICMP v 8 = RIP v 13 = OSPF v 129 = Router Advertisement v 130 = Replaceable Static TCPIP Stack Layer KN3TSL The following attributes were added. The existing versions of these attributes were displayed as bytes in Tivoli Enterprise Portal. The new versions are displayed as in the most significant unit to better accommodate the column width in the enhanced 3270 user interface. Input Packet Count The number of IP segments that this TCP/IP address space received from the network since TCP/IP initialization. The format is a long long integer. Output Packet Count The number of IP segments that this TCP/IP address space sent to the network since TCP/IP initialization. The format is a long long integer. TCP Input Segment Count The count of TCP segments that this TCP/IP address space received from the network since TCP/IP initialization. The format is a long long integer. TCP Output Segment Count The count of TCP segments that this TCP/IP address space delivered to the network since TCP/IP initialization. The format is a long long integer. UDP Input Datagram Count The number of UDP datagrams received since TCP/IP initialization. The format is a long long integer. UDP Output Datagram Count The number of datagrams this host sent since TCP/IP initialization. The format is a long long integer. These attributes are not currently in the product-provided Tivoli Enterprise Portal workspaces. They can be added to any user-customizable workspace. The following new attribute was added. UDP Total Datagram Count The total number of UDP datagrams received, including those with errors, since TCP/IP initialization. The format is a long long integer. This attribute is not currently in the product-provided Tivoli Enterprise Portal workspaces. It can be added to any user-customizable workspace. 30 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

43 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TCPIP Summary KN3TCP The zos Release attribute was updated to accommodate the latest version of z/os, as indicated in bold. zos Release The version and release level of z/os on which this monitoring agent is running. This value is stored as an integer and displayed as a string. The following 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 Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 31

44 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TN3270 Server Sess Avail KN3TNA The following attributes were updated to add the information shown in bold. Session Type The session type. While a TN3270 session is active, the Session Type attribute always displays as Unknown if the session is not monitored by means of a MONITORGROUP definition. At session termination, more granular descriptions of the SSL status are available and the SECURE session's status will be updated to reflect the session's status. This value is stored as an integer and displayed as a string. Valid values are: v 0 = Unknown v 1 = TN3270 v 2 = TN3270E v 3 = Linemode v 4 = DBCSTransform v 5 = Binary SSL Status The Secure Sockets Layer (SSL) status for the session. This value is stored as 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. The SECURE and NON_SSL statuses are only available if the session is monitored by means of a MONITORGROUP definition. At session termination, more granular descriptions of the SSL status are available and the SECURE session's status will be updated to reflect the session's status. The valid values are: v 0 = NON_SSL v 1 = SERVER_AUTH v 2 = NO_SAF v 3 = SAF v v 9 = Unknown 128 = SECURE. This is an interim state that can be displayed while a session or connection is active. The session termination record updates the row with more granular security information when the session or connection ends. The following attributes were added. The existing versions of these attributes were displayed as bytes in Tivoli Enterprise Portal. The new versions are displayed as in the most significant unit to better accommodate the column width in the enhanced 3270 user interface. Total Bytes The number of bytes sent or received by the server for this session. The format is a long long integer. Total Bytes Received The number of bytes received by the server for this session. The format is a long long integer. Total Bytes Sent The number of bytes sent by the server for this session. The format is a long long integer. These attributes are not currently in the product-provided Tivoli Enterprise Portal workspaces. They can be added to any user-customizable workspace. 32 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

45 Table 5. New attributes and attribute values (continued) Attribute group Table prefix New or changed information TN3270 Server Sess Avail (continued) KN3TNA The following attributes, which express time spans as the seconds, centiseconds, or milliseconds since an event took place, were updated to report time spans in a more 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 Time The average IP response time over the last Response Times Collection Interval. Average SNA Response Time The average SNA response time over the last Response Times Collection Interval. Average Total Response Time The average total response time over the last Response Times Collection Interval. Updates to workspaces v 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 Telnet Connection Count. In the Telnet Pool Usage view, Telnet Session Count in the legend was changed to Telnet Connection Count. 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 renamed to Telnet Connection Count to reflect its actual meaning, which is all connections, including those that 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. The following 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 Telnet Connection Count and the new Telnet Session Count. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 33

46 The existing TN3270 Server Session Summary Table now displays only Telnet connections that are in session with an application, as well as completed TN3270 Server Sessions that meet the TN3270 display 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 the TN3270 Server Session Summary Table to display Telnet connections that are not in session with an application, 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 Count and 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 "the total number of Telnet connections." The new attribute (Telnet Session Count) was added to the Active TN3270 Sessions Table view. The following 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 well as 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 set of Take Action commands. These commands were available from Tivoli Enterprise Portal and were executed with the prefix N3. In V you can now issue these commands from the enhanced 3270 interface with improved security. These commands are: v Drop v Ping v Nslookup v Tracerte 34 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

47 In V5.1.0, the new 3270 and existing Tivoli Enterprise Portal Take Action commands fail unless explicit security definitions are configured that enable these commands to be issued. Security for this monitoring agent Take Action commands is implemented through direct System Authorization Facility (SAF) calls and is based on resource profiles. Both user ID and command are validated. These information sources explain 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 and Configuration Guide for more information v You can configure a common SAF security class name for OMEGAMON enhanced 3270 user interface security controls. See the IBM Tivoli OMEGAMON XE and Tivoli Management Services: Common Parameter Reference 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 is specified for the runtime environment, allowing the use of a separate security class to control command-level security for OMEGAMON XE for Mainframe Networks monitoring agent Take Action commands. See the IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference for information 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 and Response 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 these commands when run in the enhanced 3270 user interface. v See the appendix on product-specific Take Action commands in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User s Guide for more information about the parameters associated 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 the OMEGAMON XE for Mainframe Networks commands, or you can use a separate security class. These commands will fail RACF authorization unless SAF security is configured. See the completing the configuration information in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration 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, see Updates to attribute definitions to address the requirements of the enhanced 3270 user interface Definitions of some attributes were updated to meet the requirements of the enhanced 3270 user interface. 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 long number that was previously displayed in bytes, for example, might now be expressed as gigabytes. The unit 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 enhanced 3270 interface. v Sometimes the date and time, usually displayed as a single value, are displayed in two separate columns: date and time. v Dates are displayed differently. In Tivoli Enterprise Portal, the format is mm/dd/yy hh:mm:ss. In the enhanced 3270 interface, it is yy/mm/dd hh:mm:ss. Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 35

48 v Some attributes use abbreviated names in the enhanced 3270 interface to conserve space. Attributes names are always correct in the help for the environment in which the help appears. Both the long name and the abbreviated names, when used, are shown together in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User Guide. v Attributes with restrictions that are imposed by versions of z/os earlier than v1.11 have had these restrictions removed. v Attributes that described actions that are performed using the Configuration Tool method now also list the 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 the NetView 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 APAR OA New serviceability messages Two serviceability messages were added that make it easy for you to provide build level and dates of the data collection servers when you talk with IBM Software Support. These messages are KN3N015I for the KN3ANMON data collector and KN3CT051 for the KN3ACTCS data collector. See IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting for explanations of these messages. IPv6 considerations These factors should be considered if you are using IPv6. The following IPv6 changes are included in this release of the OMEGAMON XE for Mainframe Networks program: 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, will be displayed in place of ::FFFF: ): Connections workspaces FTP workspaces TN3270 workspaces Enterprise Extender workspaces v All other OMEGAMON XE for Mainframe Networks workspaces that display IP addresses can show IP addresses in IPv4 or IPv6 format. Abbreviations used by the Configuration Tool In the books that discuss configuration and in the Configuration Tool, the abbreviations shown in the following table are used. Table 6. Configuration Tool abbreviations Abbreviation &rtename &midlev &rhilev &rvhilev Meaning The name of the runtime environment (RTE) The mid-level qualifier. Used with &rhilev Runtime high-level qualifier (non-vsam) Runtime high-level qualifier (VSAM) 36 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

49 Table 6. Configuration Tool abbreviations (continued) Abbreviation &shilev &thilev Meaning Installation high-level qualifier of the INST* libraries SMP/E target high-level qualifier Chapter 1. Introducing IBM Tivoli OMEGAMON XE for Mainframe Networks 37

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

51 Chapter 2. Planning for configuration Several variables that affect planning decisions contribute to the amount of CPU, memory, and disk space used by OMEGAMON XE for Mainframe Networks and the Tivoli Management Services components. Collecting, processing, and storing data consumes system and network resources. Several variables contribute to the amount of CPU, memory, and disk space used by OMEGAMON XE for Mainframe Networks and the OMEGAMON XE platform components. The amount of CPU, memory, and disk space used on each monitored system is dependent on the number of resources being monitored, how often performance data is collected and whether you choose to store historical data. This section identifies options to consider while planning the configuration and deployment of this product to meet the needs of your enterprise. This chapter also provides information to consider when creating and modifying situations and workspaces. Additional performance information for OMEGAMON products is available at ibm.com/software/tivoli/features/ccr2/info.html. Additional deployment and environment design recommendations are found in the IBM Tivoli Monitoring: Deployment Guide. This section also provides a high-level description of planning information about security issues and the OMEGAMON II component, if you decide to configure this component. The OMEGAMON II FMID has been merged with the OMEGAMON XE FMID in this release. Additional support for planning decisions can be found in the task-oriented OMEGAMON Integrated Information Center, found at CPU usage for monitoring networks on z/os systems Total CPU usage attributed to running the OMEGAMON XE for Mainframe Networks monitoring agent includes the percentage of CPU used by the agent and the additional CPU usage associated with the following 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 subagent is required on systems where OSA channels, LPARs and ports data is to be collected. OSA-Express3 and 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 retrieve route information when the monitoring is running in an address space on z/os 1.10 or later. SNMP was previously used to obtain this data. The change in data retrieval methods was made to reduce CPU utilization when a large number of routes are defined. Note: Remember that the OMEGAMON XE for Mainframe Networks monitoring agent might not be the only application or user querying SNMP. Understanding how real-time data is collected Real-time data collection allows you to monitor performance of your network and system resources in an effort to resolve potential problems before they affect the user. Copyright IBM Corp. 2006,

52 The OMEGAMON XE for Mainframe Networks monitoring agent is designed to collect z/os TCP/IP and VTAM performance data. You must run the monitoring agent on each LPAR being monitored. The agent 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 monitor TCP/IP address spaces, TN3270 server sessions, High Performance Routing connections, Enterprise Extender connections, FTP sessions and transfers, OSA adapters, TCP/IP connections, interfaces, gateways, Communication Storage Manager, VTAM buffer pools, and VTAM environment. Performance data is collected using the z/os Communications Server network management interface (NMI), by querying SNMP MIBs and using the VTAM Performance Monitor Interface. The OMEGAMON XE for Mainframe Networks monitoring agent is designed with performance in mind, providing an efficient mechanism 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 in the 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 Communications Server network management interface (NMI), the z/os Communication Server external I/O control (IOCTL) function data, and Take Action command data. The storage area is reused each time the monitoring agent performs a collection. The actual amount of storage used is determined by the number of resources being monitored. N3TCPIP 2 GB This data space is used to store data collected using the z/os Communications Server network management interface (NMI). A maximum of 225 MB is used for VTAM data. A maximum of 225 MB for each TCP/IP address space is used for TCP/IP data. The storage area is reused each time the monitoring agent performs a collection. The actual amount of storage used is determined by the number of resources that are being monitored. N3FTP 2 GB This data space is used to store data collected for FTP sessions and transfers. A maximum of 256 MB is used for each TCP/IP address space. Over time, all 256 MB is used because each new row of data is added to the existing data. When all 256 MB has been used, the data space wraps and new data is written to the beginning of the storage area. N3TN GB This data space is used to store data collected for TN3270 server sessions. A maximum of 256 MB is used for each TCP/IP address space. The actual amount of storage used is determined by the number of resources being monitored. One record for each active session and one record for each session that closed in the last 24 hours is stored in the data space. The data spaces are created when the monitoring agent initializes and are deleted when the monitoring agent is stopped. The sizes are not configurable. However, the amount of storage used is determined by the number of TCP/IP address spaces and the types of data you configure the monitoring agent to collect. Determining which systems and TCP/IP address spaces to monitor All production LPARS and TCP/IP address spaces should be monitored because they represent the core of your business enterprise. You might choose to collect data less frequently on some systems, especially non-production LPARs, to minimize the cost of monitoring your networks. 40 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

53 Since V4.2.0 and later, you can decide whether to monitor a TCP/IP address space on a per-address-space basis. To learn about this new feature and how to select not to monitor some TCP/IP address spaces, see Figure 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 collect The OMEGAMON XE for Mainframe Networks monitoring agent includes two data collector components: 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 monitoring agent. Data collection for these components or any of the individual data types they include can be stopped and started between recycles using the KN3FCCMD commands. See Appendix C, KN3FCCMD and KONFCCMD command reference, on page 203 for more information about stopping and starting collections of various types of data. By default, the OMEGAMON XE for Mainframe Networks monitoring agent is configured to monitor all resources. The monitoring agent always collects a required minimum amount of real-time data. You may choose to disable one or more of these data types. The following tables show the storage costs for monitoring the required and optional types of resources. These tables are provided to inform you of the relative size of attribute tables and the frequency in which data is collected. You might use this information to determine what to monitor: which types of resources, which systems and at what collection interval. The monitoring agent monitors itself. Configuration and status information for the agent is displayed in the Agent Status workspace. This workspace is part of a special group of workspaces known as the Agent and TCP/IP Subnode workspaces. These workspaces include high-level views accessed from the Agent node in the Navigation tree that display configuration, status, and command execution information about the instance of the OMEGAMON XE for Mainframe Networks monitoring agent represented by the specified node. Data for these workspaces is stored in internal control blocks maintained by the agent. The data is gathered from the control blocks whenever a user navigates to one of these workspaces or refreshes the view for that workspace. There is no collection interval for this data. There is also no memory in a data space for this data. Status data for these workspaces is always available and cannot be disabled through configuration of any kind. Table 8 on page 42 shows the data gathered every time you display or refresh Agent and TCP/IP Subnode workspaces. Chapter 2. Planning for configuration 41

54 Table 8. Data collected every time the Agent or TCP/IP subnode workspaces are displayed or refreshed LPAR name Type of data Real-time data attributes group Row size in bytes Frequency per display/refresh Agent Subnode KN3 Agent Status row KN3 SNA Collector Status row KN3 TCP Collector Status row per monitored TCP/IP stack KN3 Take Action Command 596 A maximum of rows of data KN3 Take Action Command Response 312 Multiple rows of command responses can be associated with a given Take Action command.. A maximum of rows of data. The data shown in Table 9 is collected once every collection interval and stored in memory (in a data space). The memory is reused each collection interval. When a user navigates to a workspace, a query will result in the monitoring agent retrieving the appropriate data from a data space. Use this table to calculate the memory usage by multiplying the row size by the number of resources. Add the numbers in the memory usage column to obtain the total memory used to hold data collected in an interval for a TCP/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 address space name Type of data TCP/IP Stack Layer statistics Real-time data attributes table Row size in bytes Frequency per interval TCPIP Address Space row per TCPIP address space KN3 ICMP Global Counters 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 Counter row per TCP/IP address space Statistics KN3 UDP Counter row per TCPIP Address Space Statistics TCPIP Stack Layer row per TCP/IP address space Memory usage 42 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

55 Table 9. Data collected once every collection interval (continued) LPAR name TCP/IP address space name Type of data Interface statistics collection Data Link Control statistics collection OSA statistics collection TCP/IP and VTAM (required collection) Real-time data attributes table Row size in bytes Frequency per interval TCPIP Devices row per device Interfaces row per TCP/IP interface KN3 Interface Address row per TCP/IP interface address KN3 Interface Statistics row per active strategic TCP/IP interface (max 256) KN3 Interface Status row per TCP/IP interface KN3 Interface Read Queue KN3 Interface Write Queue row per read queue per active OSA Queued Direction I/O (QDIO) or HiperSockets interface row per configured queue priority per OSA-Express Queued Direct I/O (QDIO) or HiperSockets interface OSA Channels row per OSA Channel OSA-Express LPARS rows per OSA Channel per LPAR per local channel subsystem OSA-Express Ports row per OSA channel of channel subtype: gigabitethernet,fastethernet or onethousandbasetethernet per port 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 row per OSA channel of channel subtype: tengigabitethernet per port row per OSA channel of channel subtype: tengigabitethernet per port row per OSA channel of channel subtype: tengigabitethernet per port row per OSA channel of channel subtype: tengigabitethernet per port row per OSA channel of channel subtype: osaexp3gigabitethernet, osaexp3onethousandbasetethernet or osaexp3tengigabitethernet per port row per OSA channel of channel subtype: osaexp3gigabitethernet, osaexp3onethousandbasetethernet or osaexp3tengigabitethernet per port row per OSA channel of channel subtype: osaexp3gigabitethernet, osaexp3onethousandbasetethernet or osaexp3tengigabitethernet per port row per OSA channel of channel subtype: osaexp3gigabitethernet, osaexp3onethousandbasetethernet or osaexp3tengigabitethernet per port TCPIP Memory Statistics row per TCP/IP address space Memory usage Chapter 2. Planning for configuration 43

56 Table 9. Data collected once every collection interval (continued) LPAR name TCP/IP address space name Real-time data attributes table Row size in bytes Type of data Frequency per interval TCP/IP Connection TCPIP Applications row per TCP/IP application and Application Performance statistics TCPIP Connections row per TCPIP connection collection TCPIP Details row per TCP connection TCP Listener row per TCP listener UDP Connections row per UDP endpoint Routing Table statistics collection IPSec Security Collection TCPIP Gateways row per TCP/IP gateway collected on Routing Table Collection Frequency IPSec Status row per TCP/IP address space Current IP Filters row per IP filter Dynamic IP Tunnels row per dynamic IP tunnel IKE Tunnels row per IKE tunnel Manual IP Tunnels row per manual IP tunnel Memory usage The data shown in Table 10 is collected once every collection interval and stored in memory. This data is collected for each LPAR you monitor. The memory is each collection interval. Use this table to calculate the memory usage by multiplying the row size by the number of resources. Total the memory usage column 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 data TCP/IP and VTAM (required collection) Enterprise Extender (EE) and High Performance Routing (HPR) statistics collection Communications Storage Manager (CSM) buffer reporting Real-time data attribute group VTAM Summary Statistics Row size in bytes 72 1 row Frequency per interval EE Connections row per EE connection EE Connections Details rows per EE connection HPR RTP Connections row per HPR RTP connection CSM Storage row KN3CSM Storage by Owner row per address space that owns CSM storage Memory usage 44 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

57 Table 10. Data collected for each monitored LPAR (continued) LPAR name Type of data Buffer Pool and VTAM Environment data collection Real-time data attribute group Row size in bytes Frequency per interval VTAM Address Space row VTAM I/O 72 1 row for each of 6 resources VTAM Buffer Pools row for each of 14 resources VTAM Buffer Pool Extents 96 1 row per buffer pool extent VTAM Buffer Usage by Address Space VTAM Buffer Usage by Application VTAM Buffer Usage by Category 72 1 row per address space using IO00 or CRPL buffers 80 1 row per application per address space using IO00 buffers 68 1 row for each of 12 resources Memory usage The FTP data shown in Table 11 is collected when a new session or transfer is opened or when an existing session or transfer is closed. This data is collected when z/os Communications Server notifies the monitoring agent that data is available and therefore does not adhere to a collection interval. As explained previously, new records are appended to the previously collected data until the table in the data space is full, at which time the table wraps. Therefore, over time 256 MB per TCP/IP address space will 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 space name Type of data Real-time data attribute group Row size in bytes Frequency Maximum rows stored FTP Data Collection FTP Sessions rows per FTP session 25,000 TCPIP FTP rows per FTP transfer 100,000 The TN3270 session workspaces display information about open, closed and active TN3270 sessions for a TCP/IP address space. Data for open and closed sessions is provided when z/os Communications Server notifies the monitoring agent that data is available and therefore is not driven by a collection interval. 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 for the data collected when the session is closed. Approximately 24 hours after a session is closed, the memory 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 of resources. Total the memory usage column to obtain the total memory used to hold TN3270 data collected for a TCP/IP address space. Perform these calculations for each TCP/IP address space you are monitoring. Note: The TN3270 Response Time Buckets table is not collected or stored as a separate table. Instead, it is a different view into the TN3270 Server Sess Avail table. When a query is issued to retrieve TN3270 Chapter 2. Planning for configuration 45

58 Response Time Buckets data, the appropriate TN3270 Response Time Buckets rows (one row for each of the five response time buckets) are created from the corresponding row in the TN3270 Server Sess Avail table. Table 12. TN3270 data collected LPAR name TCP/IP address space name Type of data TN3270 Server Statistics Collection Real-time data attribute table TN3270 Server Sess Avail TN3270 Response Time Buckets Row size in bytes Frequency row per TN3270 server session that is active or was closed in the last 24 hours rows 0 Maximum rows stored Use the Configuration Tool or the z/os MODIFY command to enable or disable data collection for specific types of data. See Appendix C, KN3FCCMD and KONFCCMD command reference, on page 203 for more 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 more extensive coverage of TCP/IP and its resources and provides a more efficient monitoring solution. Be aware that enabling both OMEGAMON II for Mainframe Networks and OMEGAMON XE for Mainframe Networks to monitor TCP/IP generates unnecessary processing activities. To enable the best performance of your system, use only OMEGAMON XE for Mainframe Networks to monitor TCP/IP resources in your enterprise. Defining data collection intervals The collection intervals control how often real-time data is collected. Each time you collect data, the monitoring agent incurs a certain amount of CPU usage. How much processing is incurred depends on the 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 a collection interval is 5 minutes. This default value satisfies the monitoring needs of many customers who require near 'real time' access to data. The collection intervals are specified in the Configuration Tool or the PARMGEN method, or you can modify 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 the MODIFY 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/VTAM Environment Data Collection when you configure the monitoring agent in the Configuration Tool. The z/os Communications Server network management interface (NMI) and Performance Monitoring Interfaces maintain performance information between collection intervals. For example, spikes are identified in such attributes as Maximum Authorized Private Storage Allocated. Over- and under-utilization values are identified in such attributes as Total Bytes Sent. 46 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

59 The network performance data displayed in the Tivoli Enterprise Portal is the latest collection interval; a user request to view data does not initiate a new data collection. Therefore, increasing the frequency of data collection (that is, decreasing the collection interval) by the monitoring agent generally results in your network operators viewing more recent data but results in higher CPU consumption by the monitoring agent. By decreasing the frequency of data collection (for example, from 5 to 15 minutes), you reduce the number of times per hour that the monitoring agent collects data (from 12 to 4 times per hour), 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 the Configuration Tool or on a KN3FCCMD START ROUTE command. See Appendix C, KN3FCCMD and KONFCCMD command reference, on page 203 for information about this command. The Routing Table Collection Frequency controls how often the Routing Table Statistics (Gateway table) are collected. By default, this data is collected once every 10 collection intervals (once every 50 minutes when the default collection interval is used). The frequency does not affect the amount of storage used; it affects only CPU consumption. Set the collection intervals and routing table frequency to meet your monitoring needs, ensuring that you are promptly alerted to problems so they can be resolved quickly. But, also be aware that each data collection comes with a cost in CPU usage. Run OMEGAMON XE for Mainframe Networks and use Tivoli OMEGAMON XE on z/os or the Resource Measurement Facility (RMF ) to measure CPU usage. Adjust the collection intervals until you have achieved the desired balance between currency of data and CPU usage. Defining display intervals A display interval determines how long a session or transfer will be available for display at the Tivoli Enterprise Portal. During configuration of the monitoring agent, specify values for FTP and TN3270 display intervals. The value is specified as a number of hours (1 to 24 are valid values). FTP and TN3270 workspaces display session and transfer information that was collected during the specified display interval. Note that some workspaces 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 monitoring agent when retrieving data for display at the Tivoli Enterprise Portal. Similarly, setting a display interval to a higher value might increase the amount of CPU usage. Balance your need to view data for sessions or 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 and viewing historical data instead of real-time data in the Tivoli Enterprise Portal. See the Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide for more information about the display intervals used for FTP and TN3270 workspaces. Defining and running situations Situations are used to identify monitored resources that meet certain performance criteria, raising an alert when 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 of all the active situations has implications on performance. OMEGAMON XE for Mainframe Networks provides 100 predefined situations (none of which are autostarted) to detect some of the most common mainframe network problems. Autostarted situations run automatically when the OMEGAMON XE for Mainframe Networks monitoring agent is started. See Chapter 2. Planning for configuration 47

60 the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide for a list and description of the product-provided situations. If you are upgrading from a previous version of this monitoring agent, then whatever customization and autostart settings you have on current situations are retained after upgrading. A situation can include a Take Action command that runs when the situation is triggered. By using a Take Action command, you can automate a response to a specific system condition. In addition, each situation can include text describing the probable cause and expert advice that helps you to address and resolve problems quickly. Any triggered situation raised by IBM Tivoli Monitoring or any of the OMEGAMON XE V4.2 or later monitoring 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 to warnings or detect critical situations when they occur. Those alerts or situation events can be forwarded by means of the Event Integration Facility, (EIF). The Netcool OMNIbus Event List and the Tivoli Event Console 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 thresholds were exceeded or which parts of the network are affected is available with Event Integration. If the Netcool 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 sampling frequency. All situations that query a specific attribute table should be defined with the same sampling frequency to enable the OMEGAMON XE platform to group situations and thereby optimize performance. 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 attribute table. Verify that the conditions evaluated by each situation are appropriate for your environment. Check both the set of conditions and individual conditions. The predefined situations attempt to use the most efficient means to identify problems. There might be alternative conditions that identify the same problems but are less expensive to evaluate in your environment. Ensure that the values being checked are correct for your environment. After you modify situations that are auto-started, stop and start the hub Tivoli Enterprise Monitoring Server. The process of combining situations occurs only during initialization of the hub Tivoli Enterprise Monitoring Server. Understanding how historical data is collected Before you can configuration historical data collection, understand the difference between short-term and long-term historical data and how both are collected. Historical data collection is an optional feature that is enabled using the Tivoli Enterprise Portal. The OMEGAMON 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 monitoring agent, meaning that you will have a persistent data store on each z/os system you are monitoring. 48 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

61 Short-term historical data typically refers to data that is stored for 24 hours or less. However, the amount and age of the short-term data that is retained depends on the number of resources being monitored 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 can retain data collected by OMEGAMON XE for Mainframe Networks monitoring agents for as long as you like (days, weeks, months or years). Short-term historical data is best used for analysis during problem determination. Additional prerequisite software is not required for short-term historical data collection, however the data sets used by the persistent 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 the chapter 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) and configuration of an Open Database Connectivity (ODBC) connection. Use the warehouse proxy installation 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-term historical data collection. After historical data collection is enabled, an icon is displayed in qualifying views in Tivoli Enterprise Portal workspaces. Allow time for historical data to be stored, to produce meaningful reports. You can click this icon to extend any existing Tivoli Enterprise Portal view (also called a report) to include historical data. Tivoli Enterprise Portal reports automatically pull data from short-term and long-term history, 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 for real-time data. To avoid excessive processing activities and decrease storage consumption, historical data collection is typically performed less frequently than real-time data collection. You can configure a short-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 you configure long-term history, use a warehousing interval of 1 hour to avoid transferring 24 hours worth of historical data at one time. This shorter interval reduces the duration of CPU usage associated with writing data to the warehouse by spreading the writing across 24 periods. The following example illustrates the rate of accumulation of historical records, assuming the following intervals have been specified: v Real-time data collection interval: 5 minutes v Short-term historical data collection interval: 15 minutes v Long-term warehousing interval: 1 hour 1. 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 therefore does not initiate another data collection. The row stored at 2:00 would use the 1:57 collection. The row stored 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 per hour. All measurements are stored for future use. Chapter 2. Planning for configuration 49

62 6. After one hour, all (4) rows of short-term historical data are transferred by the warehouse proxy to the long-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 collect When 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 following additional workspaces: v Active TN3270 Server Sessions for Selected Port v EE Connection Summary v FTP Transfers for Session The queries for these workspaces contain clauses that are not supported by Tivoli Data Warehouse. You can view long-term history for the same attribute groups from workspaces accessed from the physical navigator. Writing data to short-term history is cost effective and typically much less costly than writing to long-term history. Retrieving short-term history data to display historical reports increases CPU usage at the hub Tivoli Enterprise Monitoring Server (monitoring server) and at the monitoring agent, when short-term history data is stored at the monitoring agent. Short-term historical data is written to disk, typically performed at the monitoring agent, consuming CPU cycles on the z/os monitoring agent system. Additional CPU cycles are used when the Warehouse Proxy extracts data from short-term history and transfers it to the Data Warehouse. If you have collected a large amount of data in short-term history, the extraction process will significantly increase the monitoring agent s CPU usage. Similarly, when a table contains thousands of rows, the retrieval process for a Tivoli Enterprise 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 attribute tables. Using only a subset of attribute tables is an effective means for limiting storage and CPU consumption, particularly if you choose not to perform historical data collection for high volume attribute tables such as TCP connections or attribute tables with many bytes per row (many attributes), such as FTP transfers. Collect only data that you will use in historical reports. Collect those tables only as frequently as your enterprise needs. Selecting a less frequent historical collection interval (30 minutes instead 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 to calculate storage consumption based on real-time data collection. The information you gather for these tables 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 of real-time data storage, per row of data, plus 28 bytes. The additional storage cost for long-term historical data collection, in the Tivoli Data Warehouse, is the same number of bytes. To calculate storage associated with historical data, add 28 bytes to each row of real-time data. See Appendix D, Disk space requirements 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 historical collection. You can select individual attribute tables for historical collection, including specifying different historical collection intervals and warehouse intervals. Here is a list of attribute tables that are likely to have a large number of resources and therefore require higher amounts of storage and CPU consumption when enabled for historical collection v TCPIP Connections 50 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

63 v TCPIP Details v TN3270 Server Sess Avail v TCPIP Devices v Interfaces v EE Connections v EE Connections Details v HPR Connections v VTAM Buffer Pool Extents If you choose to not collect all attribute tables, TCPIP Connections is a logical choice to omit. All of the data in TCPIP Connections is also available in TCPIP Details, TCP Listener and UDP Connections. This choice 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 persistent data 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. You may also want to change the default in order to retrieve less data from short-term history and more data from long-term history in order to reduce the CPU consumed by the monitoring agent to process queries for historical data. See Tuning OMEGAMON XE components on page 53 for information about how to change 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 be maintained. You can also run a KPDXTRA job to write short-term history to flat files, for backup, or for analysis in a statistical or graphing package. See the IBM Tivoli Monitoring: Administrator's Guide for details on KPDXTRA. Long-term history, in the Tivoli Data Warehouse, does not automatically prune old records. You must determine how much data to retain, and either use the database manager tools to manually delete old records or configure the IBM Tivoli Monitoring Summarization and Pruning agent to run automatically to delete old records. For detailed instruction about setting up historical data collection, see the section on configuring your system 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 Tivoli Monitoring: Administrator's Guide. For information about reporting, see IBM Tivoli Monitoring: User's Guide. Designing workspaces When a user navigates to a workspace, one or more queries are processed by the OMEGAMON XE components in order to display the requested workspace. Those same queries are processed again when the user requests a refresh or periodically in the cases where the workspace is configured to refresh automatically. The workspaces and queries provided in the OMEGAMON XE for Mainframe Networks product have been designed with performance in mind. However, your environment and the resources you monitor might require customization of the product-provided workspaces and queries. The following are tips to improve the performance for users viewing workspaces. See IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide to see the default filters provided for each workspace. The query assigned to a chart or table view requests data from a particular attribute table. It runs when you open or refresh the workspace. The Tivoli Enterprise Portal Server sends the query to the hub Tivoli Chapter 2. Planning for configuration 51

64 Enterprise Monitoring Server. The hub Tivoli Enterprise Monitoring Server distributes the query to the appropriate monitoring agent or agents and aggregates the resulting rows. The Tivoli Enterprise Portal Server retrieves the results and holds the entire result set in memory. The Tivoli Enterprise Portal retrieves 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 retrieved v Applying the same query to multiple views in a workspace v Adjusting the auto-refresh rate v 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. You might want to change the existing filter values of a query or add filters to the query. For example, the Applications workspace contains a table view that displays all applications that have TCP/IP connections. You might be interested in only those applications that have active connections. You could customize the query by adding a filter in the Query Editor for Active Connections greater than 0. See IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide to see the default filters provided for each workspace. Do not confuse custom queries with view filters, which can also be invoked from the TEP properties dialog. View filters have no effect on reducing the CPU and storage consumption by the monitoring agent 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 is returned by the query, only a subset of the data is viewed on each page. Increasing the page size is an option available in Tivoli Enterprise Portal. Increasing the page size typically provides more filtered data on each page, but increases the client s memory requirements because now the two pages per query 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 25 attributes reduces Tivoli Enterprise Portal Server and client processing and memory requirements. For example, the OMEGAMON XE for Mainframe Networks applications attribute table contains 54 attributes. If you are creating a workspace that displays information about TCP applications, you are not required to select the 14 UDP attributes of the attribute table. Historical workspaces retrieve much more data than real-time workspaces. Accordingly, all of the queries used for predefined historical workspaces request only the most valuable subset of attributes on the source table. The queries used by predefined historical workspaces are good starting places for building better performing workspace views. See the IBM Tivoli OMEGAMON XE for Mainframe Networks: 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 if you 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 a single 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 workspace is displayed, the entire results set for each query is stored on the Tivoli Enterprise Portal Server. The 100 rows (default page size) from each query currently being viewed and the previous page of any pane 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 time the workspace is refreshed, the data is retrieved from the data spaces that reside on the system where the monitoring agent is running. The happens only for the currently displayed workspace. Retrieving 52 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

65 data from the agent consumes CPU so it is important to specify a refresh rate that meets your monitoring 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 defined for the workspace will continue to be used. The current auto-refresh rate can result in significant CPU consumption by the monitoring agent because the workspace is automatically refreshed (as frequently as once every 30 seconds). Consider changing the default auto-refresh rate to "On Demand" for workspaces that your users frequently use to display historical data. For the enhanced 3270 user interface, you can edit the product-provided workspaces by copying an existing workspace and updating the attributes and the queries associated with it. See the "Customizing workspaces" 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 the enhanced 3270 user interface. You will also need to know COLUMN value for the attribute you want to code. This is found by locating the Object Definition Interchange (ODI) file for this monitoring agent. The KANDATV DD card points to the location of the KN3DOC file in your installation or you can look in the Candle_Home\TEPS directory for the dockn3 file. You need to search first on the name of the attribute group. See the mapping appendix of the IBM Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User s Guide for the names of attribute groups. The same design principles discussed in this section apply to the design of 3270 workspaces. Tuning OMEGAMON XE components Once 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 Tivoli Data Warehouse. This section includes some tuning information about the components of the OMEGAMON XE for Mainframe Networks monitoring agent that you might want to implement once the monitoring agent is installed. v Changing data collection options While an OMEGAMON XE for Mainframe Networks monitoring agent is running, you can change the data that is being collected by using z/os MODIFY commands to temporarily change how often data collection is performed. Using z/os MODIFY commands, you can reduce the z/os system resources used to monitor your networks while a larger than normal workload is being performed. You can also monitor more of your network resources while you are investigating a problem. Changes made using the z/os MODIFY command are temporary. The next time that the monitoring agent is started, the agent reverts to the definitions made in the Configuration Tool. In other words, the changes made using the z/os MODIFY command are not retained when the monitoring agent is stopped. Changes associated with the tolerate TCP/IP recycle option reimplement the configured monitoring options whenever the state of a network monitoring interface (NMI) AF-UNIX socket changes, which may 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 and connections 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 Chapter 2. Planning for configuration 53

66 Note: After you have issued this command, you might experience a delay (the default is up to 30 minutes) before this output is written to RKLVLOG. To see the output immediately, enter the following z/os operator command: MODIFY proc_name,flush To reset to the data collection you specified during configuration of the monitoring agent, you can either stop and start the started task procedure or issue the following z/os operator commands to stop all data collection and start the data collection as configured in the Configuration Tool: MODIFY proc_name,kn3fccmd STOP TCPC MODIFY proc_name KN3FCCMD START TCPC See Appendix C, KN3FCCMD and KONFCCMD command reference, on page 203 for detailed information 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 Tivoli Enterprise Monitoring Server and for OMEGAMON XE for Mainframe Networks Monitoring. It has startup parameters that are defined with appropriate defaults for many customer environments, and these parameters are defined in the data set pointed to by the RKLVIN DD statement in the started task 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 the table variable and failed. The most common cause of this error is a query that returns a large number of 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 and MINIMUM values in &rhilev..&midlev.rkanparu. The current recommendation for the OMEGAMON XE for Mainframe Networks Agent is MINIMUM(768000,X) and LIMIT(24,X) as specified in member (KN3SYSIN). The current recommendation 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 storage that can be allocated. The syntax for setting the largest block of extended storage is shown in the example (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 be allocated is 4 MB. If the LIMIT value is too small and a process in ITMS:Engine attempts to allocate a block of storage larger allowed by LIMIT, a program interruption U0100 or U0200 results When managing 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 display at the Tivoli Enterprise Portal. Historical data from earlier time periods is retrieved from the Tivoli Data Warehouse. You can alter this default by modifying the KFW_REPORT_TERM_BREAK_POINT environment variable in the kfwenv file on the Tivoli Enterprise Portal Server. Information about the environment variable is found in IBM Tivoli Monitoring: Administrator's Guide. This variable is specified in seconds. The default is (= 60 seconds * 60 minutes * 24 hours). Increasing this value will result in historical 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 for more recent time periods. You might want to increase the value of this environment variable if you have not implemented Tivoli Data Warehouse. By increasing the value, you can view more historical data, assuming the persistent data stores are allocated large enough to contain more than 24 hours of data. 54 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

67 You might want to decrease the value of this environment variable if you configured the warehouse interval to be one hour. By decreasing the value, you can view all historical data with smaller persistent data stores. v Tuning considerations for the Tivoli Data Warehouse The default database manager settings provided by DB2 may not be sufficient to support warehousing of large amounts of monitor data from OMEGAMON XE for Mainframe Networks. Review the appendix Relational database design and performance tuning for DB2 database servers appendix in the IBM Tivoli Monitoring: Administrator's Guide to learn about DB2 tuning considerations. Planning security As 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 Tivoli Management 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 portal server. 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 is authorized to see and use, the monitored applications the user is authorized to see, and the Navigator views (and the highest level within a view) the user can access. An initial sysadmin user ID with full administrator authority is provided at installation so you can log in to the Tivoli Enterprise Portal and add more user accounts. No password is required to log on to the Tivoli Enterprise Portal unless user authentication is enabled. Authentication of user IDs can be enabled through the hub Tivoli Enterprise Monitoring Server or through the Tivoli Enterprise Portal Server. User IDs authenticated through the hub monitoring server can 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 an external LDAP-enabled registry. User IDs that are required to make SOAP Server requests (including user IDs that issue CLI commands that invoke SOAP server methods) must be authenticated through the hub monitoring server. User IDs that require single sign-on (SSO) capability for launching into other IBM products must be authenticated through the portal server. LDAP authentication must be enabled through the portal server before SSO can be configured. See the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration 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's Guide 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 explicit security definitions are configured that enable these commands to be issued. Security for this monitoring agent s Take Action commands is implemented through direct SAF (System Authorization Facility) calls and is based on resource profiles. Both user ID and command are validated. See the "Take Action commands issued from the enhanced 3270 interface with SAF security" topic in New function added since Version Fix Pack 3 on page 23 for help locating the SAF configuration information for this monitoring agent. At the end of the configuration process for the OMEGAMON XE for Mainframe Networks monitoring agent, two additional agent-specific security tasks must be performed: v Define monitoring agent access to the network management interfaces and commands on page 128 v Give users authorization and resource access to run the VARY TCPIP DROP command on page 130 Chapter 2. Planning for configuration 55

68 Planning for OMEGAMON II for Mainframe Networks Starting with V4.2, delivery and installation of the OMEGAMON II monitoring agent (sometimes called the CUA interface) for this OMEGAMON XE product has changed. The OMEGAMON II FMID has been merged with the OMEGAMON XE FMID. The OMEGAMON II FMID has been eliminated. This change should shorten the required installation time and simplify configuration. The configuration guide for OMEGAMON II has been merged into the planning and configuration guide for OMEGAMON XE. The remaining OMEGAMON II manuals continue to be provided with the current version of Tivoli OMEGAMON XE for Mainframe Networks. No enhancements have been made to these documents since version of the OMEGAMON II interface. See the OMEGAMON II for Mainframe Networks Version 520 User's Guide for information about the performance attributes displayed in the OMEGAMON II for Mainframe Networks component. The OMEGAMON II for Mainframe Networks component provides a 3270 CUA interface for monitoring SNA, NCP, VTAM, and TCP/IP performance. NetView Performance Monitor (NPM) provides performance monitoring similar to that provided by OMEGAMON II for Mainframe Networks and is included in the OMEGAMON XE for Mainframe Networks packaging for use by existing NPM customers. The OMEGAMON XE for Mainframe Networks component provides a graphical interface for monitoring VTAM, High Performance Routing, Enterprise Extender, FTP, TN3270, OSA, IPSEC and TCP/IP performance data. The OMEGAMON XE graphical interface (Tivoli Enterprise Portal) can run in desktop mode and is also accessible from your internet browser. OMEGAMON II and NPM are considered older technologies. For optimum performance, use the OMEGAMON XE for Mainframe Networks monitoring agent and Tivoli Enterprise Portal instead of OMEGAMON II for Mainframe Networks or NPM. If your primary goal is to monitor TCP/IP and VTAM resources, you should install and configure the OMEGAMON XE for Mainframe Networks monitoring agent. The OMEGAMON XE for Mainframe Networks monitoring agent provides a richer set of capabilities for monitoring TCP/IP and VTAM and their associated resources and it uses a much more efficient method of collecting TCP/IP data. The OMEGAMON XE for Mainframe Networks monitoring agent uses the z/os Communications Server network monitoring interfaces (NMIs) to collect most of the TCP/IP data. The OMEGAMON II for Mainframe Networks monitoring agent uses SNMP as it primary means of data collection, which is less efficient 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 that included %INCLUDE statements, the OMEGAMON II agent will not process those statements, so it is possible that OMEGAMON II might fail to calculate metrics correctly. Collecting TCP/IP data using both OMEGAMON II for Mainframe Networks and OMEGAMON XE for Mainframe Networks is not recommended. Using both products to collect TCP/IP data causes redundant data, an increase CPU overhead, and ultimately has a negative impact on performance. If you are currently monitoring your TCP/IP environment with the OMEGAMON II monitoring agent, consider using the OMEGAMON XE for Mainframe Networks monitoring agent instead. If you must run both monitoring agents, you should disable TCP/IP monitoring in the OMEGAMON II monitoring agent to avoid additional resource use. See Figure 39 on page 162 for information about the field in the Configuration Tool where you set this value. See the KON_TCP_CONFIGURE_FLAG parameter used to set this value 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 agent does not use the ETE facility and does not collect SNA response time data. 56 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

69 v If you want to monitor channel data for older VTAM transport protocols and virtual routes, this data is provided by the OMEGAMON II monitoring agent or NPM. Additionally, the VTAM trace facility in OMEGAMON II enables you not just to start, run and view traces. If you have a need to browse MIBs OMEGAMON II provides this function. The OMEGAMON XE for Mainframe Networks monitoring agent provides support to monitor VTAM address space, I/O, Storage, Buffer Pools, HPR and EE but does not provide support for monitoring older VTAM transport protocols and virtual routes and does not provide access to the VTAM trace facility. v If you want to monitor NCP performance, you may use the OMEGAMON II for Mainframe Networks agent or NPM. The OMEGAMON XE for Mainframe Networks monitoring agent does not provide a function for monitoring NCP. v If your enterprise requires SMF records to generate historical reports, OMEGAMON II and NPM generate SMF records to produce reports and graphs. OMEGAMON XE stores historical data in the Tivoli Data Warehouse and uses Tivoli Enterprise Portal or Tivoli Common Reporting to produce reports. Appendix A, Configuring the OMEGAMON II for Mainframe Networks component, on page 155 provides information about the components of OMEGAMON II for Mainframe Networks and the tasks for 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. For more information about using OMEGAMON II for Mainframe Networks, see OMEGAMON II for Mainframe Networks: User's Guide, OMEGAMON II for Mainframe Networks: Historical Reporting Guide, and OMEGAMON II for Mainframe Networks: NCP Monitoring Guide in the IBM Tivoli Monitoring and OMEGAMON Information Center. If you are upgrading from a previous version of OMEGAMON II for Mainframe Networks within the same 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 can use 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 2. Planning for configuration 57

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

71 Chapter 3. Preparing your z/os environment These z/os environment setup tasks must be completed on z/os system or LPAR where this monitoring agent is running. To make the OMEGAMON XE for Mainframe Networks environment fully operational, you must perform some z/os environment setup. The following setup operations must be performed on each z/os system on which the OMEGAMON XE for Mainframe Networks monitoring agent will run. Enabling the z/os Communications Server network management interface One of the configuration steps you must perform on every z/os system where the monitoring agent will be 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 allow network management applications to programmatically obtain data in real time. To enable these interfaces to 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 configuration options for FTP and TN3270 monitoring: NETMONitor SMFService See the IBM z/os Communications Server: IP Configuration Reference (SC ) for more information about 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 SMF information service. See the IBM z/os Communications Server: IP System Administrator's Commands (SC ) for information on how to use this command. If you wish to collect TN3270 response time data, ensure that the BEGINVTAM block of your Telnet profile, which is part of the BEGINVTAM block, includes a MONITORGROUP statement that applies the monitoring characteristics required by the OMEGAMON XE for Mainframe Networks monitoring agent to the set of resources in your organization that requires Telnet support. The MONITORGROUP statement 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 sliding averages should be calculated) and BUCKETS (indicates whether time buckets are being used), as in this example: MONITORGROUP MONGRP1 AVERAGE BUCKETS ENDMONITORGROUP MONITORMAP MONGRP1 Client_Identifier where Client_Identifier is one of the client identifier types supported by z/os Communications Server. For more information about supported client identifiers, see the "Client identifier types and definitions" topic in the IBM z/os Communications Server: IP Configuration Reference ( SC ). Copyright IBM Corp. 2006,

72 Note: Ensure that you specify Client_Identifier in a way that enables you to collect TN3270 response time data for the desired sessions. See also the "No data in FTP and TN3270 workspaces" topic in the IBM Tivoli 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 : ENDIPGROUP MONITORGROUP MONGRP1 AVERAGE BUCKETS ENDMONITORGROUP MONITORMAP MONGRP1 IPALL Enabling SNA monitoring Update your VTAM start list (ATCSTRxx, if LIST=xx entered) to activate Communications Storage Manager (CSM), Enterprise Extender (EE), and High Performance Routing (HPR) monitoring. Include the following 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 was accepted: IST097I MODIFY ACCEPTED IST223I MODIFY COMMAND COMPLETED IST1925I SOCKET OPENED BY SNAMGMT SERVER SUBTASK The MODIFY statement is in effect until you either restart VTAM or issue another MODIFY command to change this setting. Enabling IPSec monitoring IPSec is enabled in the TCP profile data set. If your organization is using IP Security, then this update to the 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 Policy Agent daemon must be started. The NMI for IP filters and IPSec tunnels is available for monitoring agents without updating the TCP/IP profile. Enabling SNMP manager functions The SNMP manager agent and subagent must be active on every system where the monitoring agent is running. The OMEGAMON XE for Mainframe Networks monitoring agent uses the Simple Network Management Protocol (SNMP) Management Information Base (MIB) to obtain TCPIP performance data. Both the OMEGAMON XE for Mainframe Networks monitoring agents and its OMEGAMON II component require that the SNMP manager agent and subagent be active. The chapter about SNMP in the IBM z/os Communications Server: Configuration Guide (SC ) explains the configuration procedure for running the TCP/IP SNMP agent and subagent. The chapter also explains how to automatically start the SNMP agent when TCP/IP starts. 60 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

73 The SNMP subagent, a task in the TCP/IP address space, is a z/os UNIX system services application that communicates with the SNMP agent using an AF_UNIX socket. Consequently, the AF_UNIX domain must be configured in your BPXPRMxx member of SYS1.PARMLIB. Consult the BPXPRMxx chapter in the 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 the IBM z/os Communications Server: Configuration Guide to configure them. Steps 3 and 4 under Verifying the 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 the monitoring agent is installed. The Configuration Tool creates sample SNMP system definition files and stores them in &hilev.&midlev.&rtename.rkansamu. These sample files are named KN3SNMP (for OMEGAMON XE for Mainframe Networks) and KONSNMP (for the OMEGAMON II for Mainframe Networks component), though you can use the same file for both agents by modifying the OMEGAMON II PROC to point to the KN3SNMP file. Edit the SNMP system definition file or files to add a configuration 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 and collect 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 configuration file. v See Configuring the OMEGAMON XE for Mainframe Networks SNMP manager functions on page 136 for more information about SNMP validation in the "Complete the configuration" process for the OMEGAMON XE for Mainframe Networks monitoring agent. v See Authorize the OMEGAMON XE for Mainframe Networks started tasks for TCP/IP privileges on page 137 for more information about SNMP validation in the "Complete the configuration" process for the OMEGAMON II for Mainframe Networks component. Starting the OSA adapter SNMP subagent Follow 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 adapters in 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 SNMP subagent and the OSA/SF application, must be configured and running. You should use the OSA-Express Direct SNMP subagent because it provides additional attributes not available from the TCP/IP SNMP subagent, and does not require the OSA/SF applications. To enable the OSA data support, perform the following steps: Procedure 1. 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 cataloged procedure, IOBSNMP. A sample IOBSNMP procedure can be found in z/os Communications Server 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

74 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/SF target 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 PORT statement. 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 (SA ). v Open Systems Adapter-Express Customer's Guide and Reference (SA ). v OSA-Express MIB support is described at After logging in, select Library. Under Library shortcuts, select Open System Adapter (OSA) Library. v The OSA Redbook OSA-Express Implementation Guide (SG ) is available at Verifying the z/os environment setup Several short commands can verify that you have your environment set up correctly. About this task Issue the following commands to confirm the environment setup: Procedure 1. 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 receive the response shown in the preceding example, then TCP/IP was configured successfully for the network management interfaces (NMIs) used by OMEGAMON XE for Mainframe Networks. If you plan to use NetView for z/os packet trace feature, then the values for the PKTTRCSRV TCP/IP parameters 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. 62 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

75 Note: If you have specified that OSA data should be collected using the Configuration Tool or the PARMGEN method, then perform this step. Ifyou have specified that OSA data should not be collected, then skip to Step 6 on page 64. Issue the z/os UNIX snmp command from the UNIX System Services command line with the following 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 the z/os system where you will be running the OMEGAMON XE for Mainframe Networks monitoring agent. If OSNMPD is configured correctly, the sysuptime value is displayed. This value is the time in seconds that OSNMPD has been active. If the command times out, OSNMPD is not configured correctly. For the TCP/IP SNMP subagent, issue the z/os UNIX snmp command from the UNIX System Services 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 for the z/os system where you will be running the OMEGAMON XE for Mainframe Networks monitoring agent. If the TCP/IP subagent is configured correctly, the name of the TCP/IP stack under which the subagent is running is displayed. If the command times out, or you receive a value of nosuchname or nosuchobject, 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: 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 not started, 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 the TCP/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. If they 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 the following syntax: snmp c <community_name> h <host_name_name> -v walk If you receive a No valid PDUs returned message, then the OSA-Express Direct SNMP subagent is not configured correctly. v TCP/IP SNMP subagent Issue the z/os UNIX snmp command from the UNIX System Services command line with the following syntax: snmp c <community_name> h <host_name_name> -v walk ibmmvsosaexpchannelnumber Chapter 3. Preparing your z/os environment 63

76 If you receive a No valid PDUs returned message, then the TCP/IP SNMP subagent is not configured correctly. 6. On each z/os system where you plan to monitor IP filters and IPSec tunnels, confirm that the IKE daemon and Policy Agent daemon have started. For each stack that you plan to monitor IP filters and IPSec 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 and validate that the procedure names for the IKE daemon (IKED) and the Policy Agent (PAGENT) are listed. The output of this command will be similar to this: IEE114I ACTIVITY 312 JOBS M/S TS USERS SYSAS INITS ACTIVE/MAX VTAM OAS / LLA LLA LLA NSW S VLF VLF VLF NSW S JES2 JES2 IEFPROC NSW S VTAM VTAM VTAM NSW SO RACF RACF RACF NSW S TSO TSO STEP OWT S TCPIP TCPIP TCPIP NSW SO TN3270 TN3270 TN3270 NSW SO INETD4 STEP1 OMVSKERN OWT AO SYSLOGD8 STEP1 OMVSKERN NSW AO RXSERVE RXSERVE RXSERVE OWT SO OSNMPD OSNMPD OSNMPD OWT SO FTPD1 STEP1 OMVSKERN OWT AO TCPCS2 TCPCS2 TCPCS2 NSW SO OSNMPD2 OSNMPD2 OSNMPD OWT SO TCPCS4 TCPCS4 TCPCS4 NSW SO TRMD1 STEP1 TRMD IN AO OSNMPD4 OSNMPD4 OSNMPD OWT SO TRMD1 STEP1 TRMD OWT AO IKED IKED IKED NSW SO PAGENT PAGENT PAGENT OWT SO IOBSNMP IOBSNMP IOBSNMP OWT SO CANSN3 CANSN3 AGENT NSW SO CANSDSST CANSDSST TEMS NSW SO Note the highlighted lines. You can also search the log for the following messages HASP373 PAGENT STARTED IEF403I PAGENT - STARTED - TIME= EZZ8431I PAGENT STARTING EZZ8432I PAGENT INITIALIZATION COMPLETE EZZ8771I PAGENT CONFIG POLICY PROCESSING COMPLETE FOR image : type EZD1059I IKE CONNECTED TO PAGENT EZD1058I IKE STATUS FOR STACK stack_name IS UP EZD1068I IKE POLICY UPDATED FOR STACK stack_name EZD1133I IKE STATUS FOR STACK stack_name IS ACTIVE WITHOUT IPSECURITY SUPPORT EZD1128I IKE STATUS FOR STACK stack_name IS ACTIVE WITHOUT POLICY EZZ8771I PAGENT CONFIG POLICY PROCESSING COMPLETE FOR stack_name : IPSEC EZD1046I IKE INITIALIZATION COMPLETE EZD1058I IKE STATUS FOR STACK stack_name IS UP EZD1068I IKE POLICY UPDATED FOR STACK stack_name If the daemons have not started, start them. See the IBM z/os Communications Server: IP Configuration Guide (SC ) for more information about the IKE daemon and Policy Agent daemon. If the stack is up but does not have security enabled, you would see the following message: EZD1133I IKE STATUS FOR STACK stack_name IS ACTIVE WITHOUT IPSECURITY b. Verify that IP security is enabled for a stack by issuing this command D TCPIP,<tcpip_procname>,NETSTAT,CONFIG The response from this command includes information about the IP configuration table and the IPv6 configuration table. Search for IPSECURITY in these sections. A value of YES indicates that IP security is enabled for IPv4, IPv6, or both. Here, for example, is an excerpt from a response that indicates IP security is enabled for IPv4 and not for IPv6: IP CONFIGURATION TABLE: FORWARDING: YES TIMETOLIVE: RSMTIMEOUT: IPSECURITY: YES 64 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

77 ... IPV6 CONFIGURATION TABLE: FORWARDING: YES HOPLIMIT: IGREDIRECT: NO SOURCEVIPA: NO MULTIPATH: NO ICMPERRLIM: IGRTRHOPLIMIT: NO IPSECURITY: NO Defining monitoring agent access to the NMI and commands Edit and run the KN3UAUTH job to give the monitoring agent access to the commands used to collect data and the commands issued on behalf of Tivoli Enterprise Portal user. Some security configuration is required to grant the OMEGAMON XE for Mainframe Networks monitoring 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 or more of these management interfaces depending on the data you want collected: v SNA network monitoring v Local IPSec v Real-time SMF data The monitoring agent must also be given access to commands used to collect data and commands issued on behalf of Tivoli Enterprise Portal users. Give access to the monitoring agent by editing and running the KN3UAUTH job created in Define monitoring agent access to the network management interfaces and commands on page 128. Chapter 3. Preparing your z/os environment 65

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

79 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 upgrade requirements and instructions common to all the OMEGAMON XE products, including: v Required versions of Tivoli Monitoring Server components v Requirements for staged upgrades v Instructions for upgrading in-place and in a new CSI v 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 monitoring agents in your environment. It includes an overview of the upgrade process and information specific to OMEGAMON XE for Mainframe Network upgrades. Upgrade overview Upgrade scenarios include upgrades from versions 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 with APARs OA42339 and OA42422 applied. You can upgrade from OMEGAMON XE for Mainframe Networks V5.1.0 by installing the PTFs and fix pack that are associated with APARs OA42339 and OA42422, or you can upgrade from V4.1.0 or later by ordering and installing OMEGAMON XE for Mainframe Networks V5.1.1 PID: 5698-T03. If you have enabled the self-describing agent feature, and you do not use the Tivoli Enterprise Portal desktop client, you do not need to install the distributed fix pack that goes with the APARs. Refer to the Version Program Directory for pre-requisites and installation instructions. The OMEGAMON XE for Mainframe Networks V5.1.0 monitoring agent requires Tivoli Management Services V6.2.3 Fix Pack 1 with APAR OA39890 or later applied. If you are not currently running at the required level, you must, at a minimum, upgrade the Tivoli Enterprise Portal desktop client, the Tivoli Enterprise Portal Server, and the hub Tivoli Enterprise Monitoring Server to V6.2.3 Fix Pack 1 before you install your first OMEGAMON XE V5.1.0 monitoring agent. Upgrade your monitoring agents and any Tivoli Enterprise Monitoring Server the agents report to. In addition, upgrade the Tivoli Data Warehouse components at the same time you upgrade the Tivoli Enterprise Portal Server. All OMEGAMON XE V5.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 Tivoli Management Services V6.2.3 Fix Pack 1 or higher) to OMEGAMON XE V5.1 products, you can have a combination of V4.1 and V5.1 monitoring agents installed in your environment. For example, you might have an OMEGAMON XE for Mainframe Networks V5.1 monitoring agent on one z/os system (or LPAR) and an OMEGAMON XE for Mainframe Networks V4.1 or V4.2 monitoring agent on another system. You might also have an OMEGAMON XE for Mainframe Networks V5.1 monitoring agent and an 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 XE monitoring agent at the Tivoli Enterprise Portal Server and at the hub Tivoli Enterprise Monitoring Server. 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 Copyright IBM Corp. 2006,

80 Note: You cannot upgrade from V4.1 to V5. Upgrade from V4.1 to V4.2 first, and then upgrade from V4.2 to V5.1. v Path A1: Integrating self-describing OMEGAMON XE agents into an existing Tivoli Monitoring V6.2.3 FP1 (or later) environment v Path B: Upgrading from Tivoli Management Services V6.2.x to OMEGAMON XE without self-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 release In addition to the common upgrade requirements documented in the OMEGAMON XE and Tivoli Management 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 a remote If you intend to enable the self-describing agent (SDA) feature, and you have an agent configured to run in the hub monitoring server address space, configure a high availability (HA) hub on the LPAR and convert 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 to the new HA hub. For instructions on configuring an HA hub, see the IBM Tivoli Monitoring: Configuring Tivoli Enterprise Monitoring 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 the PARMGEN configuration method, see scenario 4 in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference. Enabling new features If you are upgrading from OMEGAMON XE for Mainframe Networks V4.2.0.x to V5.1.0 or later, you do not need to reconfigure the Tivoli Enterprise Monitoring Server or the OMEGAMON XE on z/os monitoring agents. You can simply accept the defaults and build and load the runtime libraries for the runtime 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 68 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

81 v If your monitoring server is running on z/os, specify the UNIX System Services directory from which the SDA packages are to be copied for each runtime environment in which an OMEGAMON XE on z/os monitoring agent is running. v If your monitoring server is running on a distributed platform, see the "Maintaining monitoring agents" topic in the IBM Tivoli Monitoring: Administrators Guide and developerworks/community/wikis/home?lang=en#%21/wiki/tivoli+monitoring/page/ Best+practice+for+ITM SDA+on+Linux+and+Unix for more information. If you want to control access to OMEGAMON XE for Mainframe Networks managed systems from the OMEGAMON 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 this feature, you must enable it on the hub monitoring server and configure each runtime environment in which an OMEGAMON XE for Mainframe Networks monitoring agent is running to support it. To enable SDA on the hub monitoring server, see IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/os. The new Tivoli Enterprise Portal workspaces created during the v5.1.1 release caused the size of the Tivoli Enterprise Portal Server bundle file to grow. SDA fails because the FTP facility cannot process the bundle 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 NONSTANDARD PARAMETERS dialog to specify this update. If you reconfigured after you applied this APAR using PARMGEN, this problem was addressed automatically but you must run the PARMGEN KCIJPCFG job to set up the PARMGEN work environment 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 for more 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 files fails in an IBM Tivoli Monitoring v6.3.0 environment" troubleshooting item. Securing the OMEGAMON XE for Mainframe Networks managed systems and Take Action commands The SAF security class specified for the runtime environment (RTE_SECURITY_CLASS) controls logon access to the OMEGAMON enhanced 3270 user interface. It also controls authorization to view data from managed systems and attribute groups in the interface, and the authority to execute OMEGAMON XE for Mainframe Network Take Action commands from either the OMEGAMON enhanced 3270 user interface or the Tivoli Enterprise Portal interface. For security to be enforced, resource profiles must be defined to the class. If a matching SAF profile does not exist to protect queries (data collection) from a particular OMEGAMON XE for Mainframe Networks managed system or attribute group, all user IDs are allowed to issue the queries. Before you can create resource profiles that restrict access to OMEGAMON XE for Mainframe Networks managed systems, you must 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 to transmit an action to the managed system is denied. To create resource profiles to control OMEGAMON Chapter 4. Upgrading to the new release 69

82 XE for Mainframe Networks Take Action commands, you need to know the resource names of the commands. In addition, if you are using the SAF class name override parameter KN3_SECURITY_ACTION_CLASS to override the SAF security class name for Take Action commands, you must also create resource profiles for the override class. OMEGAMON XE for Mainframe Networks product-provided Take Action commands are not affected by this issue. For more information, see Authorizing users to access OMEGAMON XE for Mainframe Networks managed systems on the enhanced 3270 user interface on page 141 and Prefixed Take Action commands 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 provides remediation measures to help migrate to the enhanced command security. The security compatibility mode 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 policy actions, and so forth) are required to include an encrypted security token. To assist in migration, a security compatibility mode was provided to allow components that do not yet support tokens to issue commands without a token. If compatibility mode is enabled, the monitoring server generates a default security token. Because security tokens are encrypted to prevent tampering as they are passed between components, 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 was enabled. However, starting with Fix Pack 1, if compatibility mode is enabled, commands are allowed to execute 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 and agents for commands to execute properly. If your RTE contains a monitoring server, the synchronization of encryption keys is handled using the value specified for RTE_SECURITY_KAES256_KEY. The common agent configuration has been enhanced to allow an agent-only RTE to customize the TMS:Engine password encryption key (RKANPARU(KAES256)) and provides a standalone KAES256 encryption job (RKANSAMU(KDSDKAES)) for an agent-only RTE. For more information about this security compatibility mode and its implementation in PARMGEN, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os Version FP1 Common Planning and Configuration Guide. Performing a staged upgrade To make product upgrades easier, OMEGAMON XE for Mainframe Networks supports upgrading agents gradually, by allowing a mixture of monitoring agents of the current version and the previous version in the same environment. You can deploy new monitoring agents to your z/os systems along with older monitoring agents of the same 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 V Important: To operate in a mixed environment, monitoring agents must have the correct maintenance applied. Check the OMEGAMON XE for Mainframe Networks V5.1.0 Preventative Services Planning (PSP) bucket for the required PTFs. 70 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

83 Upgrade considerations for the OMEGAMON XE for Mainframe Networks monitoring agent As you upgrade your OMEGAMON XE for Mainframe Networks monitoring agents from an earlier version 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 store When you upgrade your Tivoli Enterprise Monitoring Server, the data set allocation values that were defined in a previous release will likely need to be changed. Determine your persistent data store allocation values by using the information in Appendix D, Disk space requirements for historical data tables, on page 257. If persistent data store allocation values need to be modified, delete any existing OMEGAMON XE for Mainframe Networks persistent data store data sets 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 data store automatically adds columns to short-term historical record when CATs, ATRs, and PDICTs are updated. No reformatting of the persistent data store data sets is required. Migrating historical data in the Tivoli Data Warehouse for Tivoli Enterprise Portal When you enable long-term historical collection for a table, the warehouse proxy creates tables in the Tivoli Data Warehouse. The tables are created when long-term historical collection is first enabled for a table. When you upgrade to a new release of OMEGAMON XE for Mainframe Networks, the tables that were created in Tivoli Data Warehouse must be updated to contain columns for all the current attributes or the tables must be dropped 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 configuration The way you configure SNMP has changed recently. You need to set up a configuration file that can be shared by OMEGAMON XE and OMEGAMON II. The Simple Network Management Protocol (SNMP) engine used to collect data was modified in the OMEGAMON XE V4.1 and OMEGAMON II V560 products. An updated sample started task procedure for both of these products will be generated during configuration using the Configuration Tool or PARMGEN. Starting in V4.1 and OMEGAMON II V560, a sample SNMP configuration file is generated during the initial configuration of the monitoring agent. This file must be customized for your environment. The KN3SNMP DD card of your OMEGAMON XE for Mainframe Networks or the KONSNMP DD card of your OMEGAMON II for Mainframe Networks started task procedure must point to the SNMP configuration file. Failure to copy these updated started task procedures to your PROCLIB data set will result in the monitoring agent not collecting any SNMP data. Note: You can share the same SNMP configuration file between OMEGAMON II for Mainframe Networks and OMEGAMON XE for Mainframe Networks. Sharing the same SNMP configuration file Chapter 4. Upgrading to the new release 71

84 could make it easier for an administrator to maintain the list of TCP/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 procedure or the KONSNMP DD card in the OMEGAMON II for Mainframe Networks start procedure to use the same SNMP configuration file. Note that OMEGAMON II for Mainframe Networks has no IPv6 support, so entries with IPv6 addresses are only read and checked for syntax, not used by OMEGAMON II for Mainframe Networks to obtain SNMP agent information. For more information about the format of the SNMP configuration file, see Appendix E, Format of the SNMP configuration file, on page 289. Upgrade issues related to running different product versions Be prepared for some unanticipated behaviors in a mixed environment (not all components at the same level) that might be found during an upgrade. Tivoli Management Services supports running a mixture of V4.1, V4.2, and V5.1 monitoring agents in your environment during an upgrade period. The expectation is that a single Tivoli Enterprise Portal client 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, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal. The version determines the attributes that the monitoring agent can provide. This version identification enables the Tivoli Enterprise Portal to conditionally select version-specific objects for Managed System Lists, Situations, Queries, Policies, and Workspaces. When users of the enhanced 3270 user interface run multiple versions of OMEGAMON agents during a staged upgrade period, they might experience operational limitations. The common upgrade guide summarizes related operational considerations by product. See the "Running the products in a mixed environment" topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide for more information. Upgrading an existing OMEGAMON II for Mainframe Networks environment Migrating OMEGAMON II for Mainframe Networks is aided by a configuration utility. If you are monitoring TCP/IP, consider having TCP/IP collection performed by the OMEGAMON XE for Mainframe 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 more efficient manner. If you are monitoring TCP/IP, consider having TCP/IP collection performed by the OMEGAMON XE for Mainframe Networks monitoring agent. Likewise, V4.1 or later of OMEGAMON XE for Mainframe Networks collects performance metrics for SNA and VTAM that were previously available only in the OMEGAMON II for Mainframe Networks component. 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 Enterprise Portal 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 Networks monitoring agent. OMEGAMON II for Mainframe Networks thresholds can be created as OMEGAMON XE for Mainframe Networks situations, which are more powerful and flexible. 72 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

85 "Prepare User Libraries" configuration utility (migration consideration only) Since V560 of OMEGAMON II for Mainframe Networks, the Configuration Tool supports the allocation of 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 this installation environment with exception of Base RTEs. You can prepare user libraries for the default RTE listing (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 applicable new user libraries for each RTE listed. See the Configuration Services and Utilities online help for more information. 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, and then use your newly updated V4.2.0 RTE and migrate to PARMGEN. See "Scenario PGN06: clone an existing environment to run on a different LPAR" in the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os: PARMGEN Reference for information about performing this task. Chapter 4. Upgrading to the new release 73

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

87 Chapter 5. Configuration Use this information to understand the flow of task for configuring the OMEGAMON XE for Mainframe Networks monitoring agent. If you are deploying and configuring the components of the Tivoli Management Services environment for the first time, or if you are using previous versions of OMEGAMON II for Mainframe Networks or OMEGAMON XE for Mainframe Networks, you will find these sections very useful. The sections that follow walk you through the process of setting up the OMEGAMON XE for Mainframe Networks monitoring agent in the best configuration for running these monitoring agents: in an environment where the monitoring server is running on z/os in a separate address space from the monitoring agent, as shown in Figure 4. Figure 4. Typical configuration for deployment of the OMEGAMON XE for Mainframe Networks monitoring agent Before you begin to configure OMEGAMON XE for Mainframe Networks, ensure that you have completed the tasks listed in Table 13. Table 13. Preconfiguration tasks Task v Complete any preinstallation requirements. v Verify that you have the required software and DASD. v Install the product. Location of information IBM Tivoli OMEGAMON XE Products: Preinstallation Requirements and Instructions IBM Tivoli OMEGAMON XE for Mainframe Networks: Program Directory Copyright IBM Corp. 2006,

88 Table 13. Preconfiguration tasks (continued) Task v Read the planning information and make any necessary planning decisions. v Review information on batch processing and system symbolics, so your first runtime environment is appropriate for replication. v Set up the runtime environment and allocate the runtime libraries. v Configure the Tivoli Enterprise Monitoring Server in the runtime environment. Location of information IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os v Configure your Tivoli Management Services environment and this monitoring agent using the PARMGEN configuration method. v v v IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference to understand PARMGEN scenarios IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide for the PARMGEN procedure IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Parameter Reference for explanations for common parameters v IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference for explanations of configuration parameters for this monitoring agent v Configure the enhanced 3270 user interface. IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide v Configure SAF security for Take Action commands. IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide for general tasks and Authorizing users to issue Take Action commands on page 141 for OMEGAMON XE for Mainframe Networks tasks After completing these tasks, you are ready to configure this monitoring agent. You can configure the OMEGAMON II for Mainframe Networks component (optionally) and OMEGAMON XE for Mainframe Networks (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 monitoring agent using the PARMGEN method (the preferred method). v Chapter 7, Configuring the monitoring agent using the Configuration Tool, on page 87 has instructions for configuring the OMEGAMON XE for Mainframe networks monitoring agent using the Configuration Tool. v Chapter 8, Completing the configuration, on page 127 describes the tasks you must perform outside the 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 monitoring agents on z/os in the Configuration Tool. v Verifying configuration if you configured both Tivoli Enterprise Portal and the enhanced 3270 user interface on page 149 contains instructions for validating the configuration of OMEGAMON XE for Mainframe Networks. 76 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

89 Chapter 6. Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method You configure OMEGAMON XE for Mainframe Networks by accepting or customizing the values of parameters 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-level entities, install product-specific data on the Tivoli Enterprise Monitoring Server, and register the OMEGAMON XE for Mainframe Networks monitoring agent to the Tivoli Enterprise Monitoring Server address space. You also configure the persistent data store for the product historical data and allocate the data sets to store enterprise data. These parameters are specified in the KN3 section of the PARMGEN configuration profile. Default values are provided for all required parameters and some optional ones. If you do not want to customize these parameters, and you do not want to enable optional features, you can complete the configuration by accepting these defaults. Alternatively, you can specify custom values. You can also specify custom values for optional parameters that have no defaults. You must specify values for these parameters in order to activate those features. If you are migrating from OMEGAMON XE for Mainframe Networks version or later, you can use the PARMGEN configuration method. To use PARMGEN with older versions of OMEGAMON XE for Mainframe Networks, you must first use the Configuration Tool to migrate to version or later. For guidance on setting parameter values, see the following sources of information: v Comments in the configuration profiles v Online help for the configuration profile If the supplied KCIRPLBS macro has been copied to your SYSPROC concatenation, you can enter TSO KCIRPLBS at the ISPF command line to run the help macro. Place the cursor anywhere on the line that contains 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 Set up PARMGEN work libraries for the runtime environment. Set up the PARMGEN configuration profile for the runtime environment. Configure a Tivoli Enterprise Monitoring Server on z/os. Location of instructions 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 Planning and Configuration Guide IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os and IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Parameter Reference Copyright IBM Corp. 2006,

90 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 Time collector. IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os and IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Parameter Reference (Optional) Configure the OMEGAMON enhanced 3270 user interface address space. The End-to-End Response Time collector is required for user response time data. IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide Note: You only need to configure one OMEGAMON enhanced 3270 user interface address space. If you have already configured this address space for another version OMEGAMON monitoring agent on z/os, you do not need to repeat this configuration step. Tip: If you are enabling self describing agents, configure a stand-alone high-availability hub monitoring server. Installing a high-availability hub lets you apply maintenance or upgrades without recycling the hub. If you have an existing static hub to which agents report, convert the hub to a remote and configure all 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 to configure) using the runtime environment profile, you must complete several configuration tasks outside of the profile. See Chapter 8, Completing the configuration, on page 127. Configuring the enhanced 3270 user interface using the PARMGEN method You configure the Enhanced 3270 User Interface using the rtename configuration profile for the runtime environment. To configure the interface, you can accept the defaults or specify site-specific values for the started task name, 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 name KOB_TOM_VTAM_NODE CTDOBN * VTAM node KOB_TOM_VTAM_APPL_LOGON CTDOBAP * VTAM logon applid KOB$ END *---- Tivoli OMEGAMON Enhanced 3270 User Interface ----* where: KOB_TOM_STC Is the name of the interface started task. KOB_TOM_VTAM_NODE Is the name of the VTAM major node used by the Enhanced 3270 User Interface. 78 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

91 KOB_TOM_VTAM_APPL_LOGON Is the VTAM logon applid used by the interface. After configuring all the components and agents in the runtime environment, you complete the configuration by submitting the PARMGEN jobs and completing the required "Complete the configuration" steps. If you are configuring other products in this runtime environment, you can perform these 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 is enabled), all the STCs and VTAM major nodes are copied to the system libraries that are specified for the GBL_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 to VARY the node and APF authorize the load libraries. To use ccccapf, uncomment the placeholder INAPF INCLUDE 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 parameters The parameters used by this monitoring agent for the PARMGEN configuration method are grouped logically in the configuration profile. With the PARMGEN configuration method, you edit a comprehensive list of parameters for configuring all installed products and components. You then submit a series of jobs to create a complete runtime environment with the parameter values that you specified. If you are an existing Configuration Tool user and already have a runtime environment, you can convert it to PARMGEN. See the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference for information about migrating to PARMGEN. These parameters are found in the configuration profile, which can be generated from an existing RTE. If you installation is new or if you do not want to base the configuration profile on an existing RTE, a default configuration profile is provided and can be edited. Refer to the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference to understand the other scenarios for using PARMGEN. In the configuration profile, the OMEGAMON XE parameters are organized into the groups found in Table 15 on page 80. The most important two groups of parameters for configuring this monitoring agent are the Agent Parameters that set the global values for all configurable parameters that are unique to this monitoring 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

92 values that override the global parameters. For comprehensive information about these parameters, see the IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference. Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configuration profile PARMGEN classification Parameters in this group Explanation Additional OMEGAMON XE for Mainframe Networks Agent settings Advanced Agent configuration values Agent nonstandard parameters v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v KN3_X_AGT_CONFIRM_SHUTDOWN KN3_X_AGT_KDC_DEBUG KN3_X_AGT_DEBUG_TRACE KN3_X_AGT_LGSA_VERIFY KN3_X_AGT_LSRPOOL_BUFFER_NUM KN3_X_AGT_LSRPOOL_BUFSIZE KN3_X_AGT_SDUMP_SVC_SYS1_DUMP KN3_X_AGT_STORAGE_LIMIT_EXTEND KN3_X_AGT_STORAGE_LIMIT_PRIMARY KN3_X_AGT_STORAGE_RESERVE_EXT KN3_X_AGT_STORAGE_RESERVE_PRI KN3_X_AGT_STORAGE_STGDEBUG KN3_X_AGT_TASKS_ATTACHED_NUM KN3_X_SECURITY_USER_EXIT KN3_X_SECURITY_RESOURCE_CLASS KN3_AGT_FLUSH_LSR_BUFR_INT_HR KN3_AGT_FLUSH_LSR_BUFR_INT_MIN KN3_AGT_ICU_LANGUAGE_LOCALE KN3_AGT_KGL_WTO KN3_AGT_KLX_TCP_TOLERATERECYCLE KN3_AGT_STORAGE_DETAIL_INT_HR KN3_AGT_STORAGE_DETAIL_INT_MIN KN3_AGT_STORAGE_MINIMUM_EXTEND KN3_AGT_VIRTUAL_IP_ADDRESS KN3_AGT_VTAM_APPL_NCS KN3_AGT_WTO_MSG KN3_AGT_NSNEWn_VALUE KN3_AGT_NONSTDn_DSN KN3_AGT_NONSTDn_MBR KN3_AGT_NONSTDn_PARM KN3_AGT_NSOLDn_VALUE Specifies settings for initializing Tivoli Monitoring: Services (TMS: Engine). These values are usually found in the KN3SYSIN member in the rhilev.midlev.rtename. RKANPARU library and are usually updated only with the assistance of IBM Software Support. Specifies a wide range of essential agent configuration parameters, including parameters that define where console messages are displayed, whether TCP/IP can be recycled, language of the interface, virtual addresses, and storage-related values. Nonstandard parameters are customer-defined or hidden options that do not correspond to fields in the Configuration Tool interactive panels. This set of parameters defines the values required to establish a nonstandard parameter. Create these parameters under the guidance of IBM Software Support. 80 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

93 Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configuration profile (continued) PARMGEN classification Parameters in this group Explanation Agent parameters: TCP/IP information v v v v v v v v v v v v v v v v v v v v v KN3_SNA_VTAM_COLLECT_DATA KN3_SNA_VTAM_SNAC_SNACINTV KN3_SNMP_CONFIG_FILE KN3_TCP_ALLHPR KN3_TCP_COLLECT_STACK KN3_TCP_CONN KN3_TCP_CSM KN3_TCP_EEHPR KN3_TCP_FTP KN3_TCP_FTP_DSPINTV KN3_TCP_GLBS KN3_TCP_INTE KN3_TCP_INT KN3_TCP_IPSEC KN3_TCP_OSA KN3_TCP_ROUTE_TBL KN3_TCP_ROUTE_TBL_FREQ KN3_TCP_SAMPLE_INTERVAL KN3_TCP_TN3270 KN3_TCP_TN3270_DSPINTV KN3_TCP_VIO_UNIT Agent's Applids v KN3_AGT_VTAM_APPL_AA v KN3_AGT_VTAM_APPL_KN3INVPO v KN3_AGT_VTAM_APPL_NCS v KN3_AGT_VTAM_APPL_OPERATOR v KN3_AGT_VTAM_APPL_CNM_SPO Agent's local TCP/IP information Agent's local VTAM and logon information Agent's primary TEMS TCP/IP information Agent's Primary TEMS VTAM information: v KN3_AGT_TCP_HOST v KN3_AGT_TCP_STC v 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) v v v KN3_AGT_VTAM_APPL_PREFIX KN3_AGT_VTAM_NODE KN3_TEMS_TCP_HOST Note: KN3_TEMS_TCP_HOST and KN3_AGT_TCP_HOST must be the same value if KN3_TEMS_LOCAL _CONNECT_FLAG=Y (Agent connects to local TEMS). v v v v KN3_TEMS_VTAM_LU62_DLOGMOD KN3_TEMS_VTAM_LU62_MODETAB KN3_TEMS_VTAM_NETID KN3_TEMS_VTAM_APPL_LLB_BROKER Sets the global values for all configurable parameters that are unique to the OMEGAMON XE for Mainframe Networks monitoring agent. Specifies the VTAM application IDs (applids) that the agent uses to define communication with the Tivoli Enterprise Monitoring Server. Applids are used for communication with the monitoring server, except for KN3_AGT_VTAM_ APPL_CNM_SPO, which is used to collect CNM data. These parameters are not used unless you are using SNA (instead of TCP/IP) to communicate with the monitoring server. Provides the TCP/IP information that the Tivoli Enterprise Monitoring Server uses to communicate with the monitoring agent. Specifies the values that are used by the agent for creating VTAM definitions specific to the monitoring agent. Specifies the host name of the Tivoli Enterprise Monitoring Server that is specific to this monitoring agent. This field is required if this server is to communicate with agents using TCP/IP. Specifies the VTAM information that is used by the Tivoli Enterprise Monitoring Server to communicate with the monitoring agent. Chapter 6. Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method 81

94 Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configuration profile (continued) PARMGEN classification Parameters in this group Explanation Audit parameters v KN3_AGT_AUDIT_ITM_DOMAIN v KN3_AGT_AUDIT_MAX_HIST v KN3_AGT_AUDIT_TRACE Define TCP v KN3_TCPX monitoring v KN3_TCPXnn_OVRD_GLBS systems member v KN3_TCPXnn_OVRD_INTE Note: Specify v KN3_TCPXnn_OVRD_INTS KN3_TCPXxx_* v KN3_TCPXnn_OVRD_OSA row for each v KN3_TCPXnn_ROW TCP/IP v KN3_TCPXnn_SYS_NAME monitored stack. v KN3_TCPXnn_TCP_STC Global default is v KN3_TCPXnn_TCPIP_PROFILES_DSN $$$$ (monitor all v KN3_TCPXnn_OVRD_GLOBAL_FLAG TCP/IP stacks). v KN3_TCPXnn_OVRD_COLLECT_STACK v KN3_TCPXnn_OVRD_CONN v KN3_TCPXnn_OVRD_IPSEC v KN3_TCPXnn_OVRD_ROUTE_TBL v KN3_TCPXnn_OVRD_ROUTE_TBL_FREQ v KN3_TCP_ROUTE_TBL v KN3_TCP_ROUTE_TBL_FREQ v KN3_TCPXnn_OVRD_FTP v KN3_TCPXnn_OVRD_FTP_DSPINTV v KN3_TCPXnn_OVRD_TN3270 v KN3_TCPXnn_OVRD_TN3270_DSPINTV v KN3_TCPXnn_TCPIP_PROFILES_MBR Define TN3270 Telnet session link user values Enable self-describing agent processing If the Agent requires address translation support If the Agent requires network interface list support v v KN3_TN3270_DXL_APPLID KN3_TN3270_DXL_USERDATA Specifies the amount of detail, maximum number of entries, and identifier for z/os SAF tracing. Sets the stack-specific values that override the global parameters for all configurable parameters that are unique to the OMEGAMON XE for Mainframe Networks monitoring agent. Specifies the IBM Tivoli NetView for z/os user ID and password that OMEGAMON XE for Mainframe Networks logs onto dynamically. The applid is for the Tivoli NetView on z/os application. The user data is the user ID and password that must be passed to NetView for z/os to complete the login. v KN3_AGT_TEMA_SDA Specifies whether this monitoring agent plans to use the self-describing agent feature. v KN3_AGT_PARTITION_NAME Specifies the partition name that identifies the location of this TEMS (namespace) relative to the firewall(s) used for address translation. v KN3_AGT_TCP_KDEB_INTERFACELIST Specifies a list of network interfaces that the monitoring agent uses. This parameter is required for sites that are running multiple TCP/IP interfaces or network adapters on the same z/os image. 82 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

95 Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configuration profile (continued) PARMGEN classification Parameters in this group Explanation Persistent datastore table space allocation overrides Protocol port numbers for Agent connection to TEMS Secondary TEMS configuration Secondary TEMS TCP/IP information Secondary TEMS VTAM information: Specify communication protocols preference for TEMS connection Take Action commands security settings v v v v v v v v v v v v KN3_PD KN3_PD_CYL KN3_PD_GRP KN3_PD_ROW KN3_X_PD_HISTCOLL_DATA_AGT_STC KN3_X_PD_HISTCOLL_DATA_TEMS_STC KN3_TEMS_TCP_PIPE_PORT_NUM KN3_TEMS_TCP_PIPES_PORT_NUM KN3_TEMS_TCP_PIPE6_PORT_NUM KN3_TEMS_TCP_PIPE6S_PORT_NUM KN3_TEMS_TCP_UDP_PORT_NUM KN3_TEMS_TCP_UDP6_PORT_NUM Specifies the information that is required for this monitoring agent to override the global RTE defaults for space allocation for the persistent data store libraries and for overhead information such as the product dictionary, table records, index records, and buffers to hold overflow data. Specifies the port numbers that are used by the protocols specified under "Specify communication protocols preference for TEMS connection" for communication between the monitoring agent and Tivoli Enterprise Monitoring Server. v KN3_TEMS_BKUP1_NAME_NODEID Specifies the name of the secondary monitoring server if you defined a backup Tivoli Enterprise Monitoring Server. The BKUP1 values are found in the KN3ENV member in the rhilev.midlev.rtename. RKANPARU library to communicate with the backup Tivoli Enterprise Monitoring Server. v KN3_TEMS_BKUP1_TCP_HOST Specifies TCP/IP information for a backup Tivoli Enterprise Monitoring Server if you defined a backup monitoring server. The BKUP1 values are found in the KN3ENV member in the rhilev.midlev.rtename. RKANPARU library to communicate with the backup Tivoli Enterprise Monitoring Server. v v v KN3_TEMS_BKUP1_VTAM_APPL_LLB_BKR KN3_TEMS_BKUP1_VTAM_LU62_DLOGMOD KN3_TEMS_BKUP1_VTAM_NETID Specifies VTAM or SNA information for the backup Tivoli Enterprise Monitoring Server if you defined a backup monitoring server. The BKUP1 values are found in the KN3ENV member in the rhilev.midlev.rtename. RKANPARU library to communicate with the backup Tivoli Enterprise Monitoring Server. v KN3_AGT_COMM_PROTOCOLn Details the protocol possibilities for communication between the monitoring agent and Tivoli Enterprise Monitoring Server in the order in which the protocols will be used. v v v KN3_AGT_PPI_RECEIVER KN3_AGT_PPI_SENDER KN3_SECURITY_ACTION_CLASS Defines the connection between OMEGAMON XE for Mainframe Networks and Tivoli NetView for z/os if you use Tivoli NetView for z/os and specifies whether to override the SAF security value specified for the runtime environment at the agent. Chapter 6. Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method 83

96 Table 15. OMEGAMON XE for Mainframe Networks parameters divided into the groups found in the configuration profile (continued) PARMGEN classification Parameters in this group Explanation Values that describe the address space Values that describe the Primary TEMS the Agent will connect to VTAM Secondary Program Operator (SPO) for Communication Network Management (CNM) interface (optional) v v v v v v KN3_AGT_CONFIGURATION_MODE KN3_AGT_STC KN3_TEMS_LOCAL_CONNECT_FLAG KN3_TEMS_NAME_NODEID KN3_AGT_VTAM_NODE_OMXE KN3_AGT_VTAM_APPL_CNM_SPO Specifies the name of the address space in which you are running and the name of your agent PROC. Defines the information required to connect to the local Tivoli Enterprise Monitoring Server. Defines how the OMEGAMON XE for Mainframe Networks monitoring agent communicates with the VTAM CNM interface to collect monitoring information. Configuring security for Take Action commands You 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 is implemented through direct System Authorization Facility (SAF) calls and is based on profiles and resource names. These commands cannot be run unless security is configured. OMEGAMON XE for Mainframe Networks agent Take Action commands cannot be issued unless a security class is defined to the SAF security manager and the security class name is configured in each runtime environment in which an OMEGAMON XE for Mainframe Networks monitoring agent is configured. 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 Mainframe Networks Take Action commands. After you define each security class, you must create profiles to control access to individual commands and give user IDs UPDATE access to those profiles. See Prefixed Take Action commands on page 141. Finding previous PARMGEN configuration sessions If you configured an RTE by using the PARMGEN method and exit the PARMGEN tool, you might have difficulty 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 are blank, as shown in Figure 5 on page 85 and it seems that the work from your previous session is lost. 84 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

97 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 Date Enter ns (1s-11s) to display detailed status 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 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 this value and press Enter, then configuration information from the previous session is displayed. Also, the Status and Date for each PARMGEN option that you completed is displayed, providing an accurate record of your progress. Ensuring that your runtime environment supports the NetView for z/os packet trace using PARMGEN If you are using the PARMGEN configuration method, you must set values for these three parameters before 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/os packet trace function, the settings for your runtime environment must include the information that is required 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 these three RTE_TN3270 parameters is correct: v RTE_TN3270_DXL_HOSTADDRESS for specifying the Hostname v RTE_TN3270_DXL_TN3270PORT for specifying the Port Number v 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 the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. Chapter 6. Configuring OMEGAMON XE for Mainframe Networks using the PARMGEN method 85

98 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 active Telnet listener, you can specify the network address of a system that does have an active Telnet 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, ) To get this value, issue the TSO HOMETEST command on the system of the Telnet listener. Port number The default port number of the Telnet listener is 23. To override this value, specify the port number of the Telnet listener. LUGROUP The Dynamic XE to 3270 (NetView for z/os) linking feature requires the VTAM Unformatted System Services (USS) screen to accept a LOGON APPLID() DATA() command. If the default Telnet USS screen does not accept this command, supply the name of a Logical Unit (LU) group that does accept it. The TN3270 session is joined to that LU group. Note: 1. Complete this panel only if you are configuring products that support the Dynamic XE to 3270 (NetView for z/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 can be modified for an individual TN3270 session. 86 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

99 Chapter 7. Configuring the monitoring agent using the Configuration Tool These factors should be considered as your begin configuration of the OMEGAMON XE for Mainframe Networks Monitoring agent using the Configuration Tool. After the Tivoli Enterprise Monitoring Server, the next product displayed on the Product Component Selection Menu shown in Figure 9 on page 91 is the Tivoli OMEGAMON Enhanced User Interface. The component 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 related VTAM node definition, and a VTAM applid. This component is installed in its own address space. The configuration process for the interface defines the address space controls and logical VTAM connections required to run it. In addition, a data retrieval agent (DRA) must be enabled on the hub monitoring server. This configuration is covered in the IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/os. You must configure one instance of this interface per sysplex. See Configuring the enhanced 3270 user interface using the Configuration Tool for information about configuring this interface. The next option is to configure OMEGAMON II for Mainframe Networks. The OMEGAMON II for Mainframe Networks component was installed during the SMP/E installation of the product so that its facilities are available. The OMEGAMON II for Mainframe Networks configuration step is optional and should be performed only if you want to use this 3270 component to monitor VTAM, NCP, and SNA resources. If you want to use OMEGAMON II for Mainframe Networks, see Appendix A, Configuring the OMEGAMON II for Mainframe Networks component, on page 155 for information about configuring this component and Appendix B, Customizing the OMEGAMON II components and verifying installation, on page 185 to configure the OMEGAMON II constituent parts, such as NCP collection and the End-to-End Response Time Feature (ETE) and to verify that the product is configured correctly. For information to help you decide whether to install the OMEGAMON II component, see Upgrading an 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 Mainframe Networks V4.2.0 Fix Pack 1, you must update your runtime environment to include the TN3270E Telnet session link support override values. See Updating your runtime environment to support the NetView for z/os packet trace on page 124 for information about how to perform this task, or refer to the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/os: Common Planning and Configuration Guide. If you want additional information about any of the parameters specified by the Configuration Tool, you can search on the Configuration Tool name of the field in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Parameter Reference and learn more about these parameters. Configuring the enhanced 3270 user interface using the Configuration Tool If this is the first V5.1.0 monitoring agent on z/os you have installed, you must configure it. You should configure one instance of the Enhanced 3270 User Interface per sysplex. To configure the interface, perform the following steps: Copyright IBM Corp. 2006,

100 1. If you have not already done so, type B (Build libraries) and press Enter to allocate the new runtime libraries. 2. From the he Product Component Selection panel, select option 2 Tivoli OMEGAMON Enhanced 3270 User Interface PRODUCT COMPONENT SELECTION MENU COMMAND ===> The following list of components requires configuration to make the product operational. Refer to the appropriate configuration documentation if you require additional information to complete the configuration. To configure the desired component, enter the selection number on the command line. 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 Server 2 Tivoli OMEGAMON Enhanced 3270 User Interface 3 OMEGAMON II for Mainframe Networks 4 OMEGAMON XE for Mainframe Networks Figure 6. Product component selection menu panel. Product component selection menu panel 3. The Configure OMEGAMON Enhanced 3270 UI / RTE: rtename panel is displayed: 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) 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 4. Select option 1 Specify configuration values. The Specify Configuration Values panel is displayed: 88 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

101 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 5. Accept the default values or specify your preferences for the following parameters: OMEGAMON Enhanced 3270 UI The started task name for the interface address space. The default is CANSTOM. Node Name The name of the VTAM major node for the address space. The default is CTDOBN. Appl ID The 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 is redisplayed. 7. Select option 2 Create runtime members. The OB#3xxx job is displayed. Review the JCL and then submit 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 you have 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 steps Use this summary of configuration steps to understand the flow of configuration for the OMEGAMON XE 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 Chapter 7. Configuring the monitoring agent using the Configuration Tool 89

102 you have not, see "Setting up and building a runtime environment" in the IBM Tivoli OMEGAMON XE and 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 local Tivoli Enterprise Monitoring Server. The registration process includes installation of product-provided solutions 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 with the Tivoli Enterprise Monitoring Server of your choice. In a shared address space environment, only the 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 the connection 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 the address 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 to create 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 the monitoring agent address space for historical data collection. This step also allocates the persistent data store 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 use OMEGAMON XE for Mainframe Networks. (These procedures are also covered on a panel displayed when you select to complete the configuration using the Configuration Tool.) Before you begin these steps, 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 and new requirements are introduced. Therefore, the screens in the Configuration Guide may not exactly match 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 to determine other acceptable return codes. Where a conflict arises between the JCL job comments and the configuration guide, accept the information in the JCL job, which might have been created later than the information in the book. 3. If you change any of the values defined in the Configuration Tool after initial configuration, you must Run 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 have been updated. Running the JCL Jobs Installation 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 90 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

103 N3#5xx) need to be run to pick up changes made in the Configuration Tool and incorporate them into production. 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 Monitoring Agent Runtime Members that presents the N3#5xx job for your submission, and submit job N3#5xx to incorporate any changes into production. v To run the N3#3xxx job Create runtime members JCL job, return to the Configure OMEGAMON XE for Mainframe Networks panel show in Figure 10 on page 92, choose Step 4: Create Runtime Members that presents job N3#3xxx for your submission, and submit job N3#3xxx to incorporate any changes into production. Accessing OMEGAMON XE configuration steps in the Configuration Tool To configuration the OMEGAMON XE for Mainframe Networks monitoring agent, begin with the Product 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: Procedure 1. 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 is displayed. 2. From the Runtime Environments panel, enter C in the Action column by the name of the SHARING RTE (which in the following screens is HUBN3IRA). The Product Component Selection Menu shown in Figure 9 is displayed PRODUCT COMPONENT SELECTION MENU COMMAND ===> The following list of components requires configuration to make the product operational. Refer to the appropriate configuration documentation if you require additional information to complete the configuration. To configure the desired component, enter the selection number on the command line. 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 Server 2 Tivoli OMEGAMON Enhanced 3270 User Interface 3 OMEGAMON II for Mainframe Networks 4 OMEGAMON XE for Mainframe Networks Figure 9. Product component selection menu panel. Product component selection menu panel The last product displayed on the Product Component Selection Menu shown in Figure 9 is OMEGAMON XE for Mainframe Networks. This section describes the procedures for configuring the monitoring agent and linking it to the hub Tivoli Enterprise Monitoring Server. 3. To start the OMEGAMON XE monitoring agent configuration, from the Product Configuration Selection Menu shown in Figure 9, enter 4 OMEGAMON XE for Mainframe Networks. This action causes the Configure OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page 92 to be displayed. Chapter 7. Configuring the monitoring agent using the Configuration Tool 91

104 ----- CONFIGURE OMEGAMON XE FOR MAINFRAME NETWORKS V5.1.0 / RTE: HUBN3IRA -- - Last selected Perform the appropriate configuration steps in order Date Time If you have defined a TEMS in this RTE that this Agent will 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 Mainframe Networks panel This menu presents the steps needed to configure the OMEGAMON XE for Mainframe Networks monitoring agent if you have defined a Tivoli Enterprise Monitoring Server in this RTE. These steps should be completed in the order shown in the following section. Step 1: Registering with local TEMS Register with the local Tivoli Enterprise Monitoring Server (TEMS) if you are installing this monitoring agent 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 runtime environment (RTE) with the Tivoli Enterprise Monitoring Server, use this step to register the monitoring agent with the local monitoring server. Procedure 1. 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 the OMEGAMON XE for Mainframe Networks monitoring agent with the local Tivoli Enterprise Monitoring Server. 2. Review the JCL and submit the job. Verify that the job completes successfully. If it does not, check the log to diagnose errors and rerun the job. 3. When the JCL for registering with the hub Tivoli Enterprise Monitoring Server completes, press F3 to return to the Configure OMEGAMON XE for Mainframe Networks panel shown in Figure 10. Step 2: Specifying configuration parameters Use 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. 92 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

105 Procedure 1. 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: SPECIFY CONFIGURATION PARAMETERS / RTE: HUBN3IRA OPTION ===> Last selected Perform these configuration steps in order: Date Time 1 Specify component configuration 2 Specify monitored systems information 3 Create monitoring agent runtime members Figure 11. Specify configuration parameters panel. Specify configuration parameters panel This panel presents the steps to configure OMEGAMON XE for Mainframe Networks. These configuration steps must be performed in order. The options are found in Table 17. Table 17. Parameters and explanations for the Specify Configuration Parameters panel Parameter Explanation 1 Specify component configuration 2 Specify monitored systems information 3 Create monitoring agent runtime members This step collects information that applies to the monitoring agent, to monitoring all TCP/IP address spaces on the system, or to monitoring VTAM on the system. This step collects information to define the TCP/IP address spaces that should be monitored and the configuration options for each monitored TCP/IP address space. This step creates the members in the runtime data sets that are read by the monitoring agent. These members determine what information is collected and which TCP/IP address spaces are monitored. The N3#5xxx job is created, which updates selected members of the RKANPARU and RKANCMDU data sets. If any manual edits have been made to these members data sets, they will be overwritten by this job. Selecting this option presents the N3#5xxx job to be created. Review the JCL 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 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 complete successfully. When the jobs complete successfully, the values will have been updated. 2. Select 1 Specify component configuration. This action causes the Specify Component Configuration panel shown in Figure 12 to be displayed: 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 Complete this panel using the information found in Table 18 on page 94. Chapter 7. Configuring the monitoring agent using the Configuration Tool 93

106 Table 18. Parameters and explanations for the Specify Component Configuration panel Parameter Explanation Specify your site's VIO unit name Provide the TCP/IP virtual input/output (VIO) unit name for your site. The VIO unit is used to allocate temporary data sets. The default is VIO. Specify the following TCP/IP information: OMEGAMON XE for Mainframe Networks requires this information about the TCP/IP systems you plan to monitor. TCP/IP data file The dsname of the library which provides parameters for TCP/IP address space configuration. This dsname can be either a sequential data set name or a partitioned data set name and a member name (for example, TCPIP.DATA or SYS1.TCPPARMS(TCPDATA)). Specify the data set used by the TCP/IP address space. See the TCPDATA search order section of the z/os Communications Server IP Configuration Guide. If you are monitoring multiple TCP/IP address spaces, pick the primary address space for the monitoring agent to connect to. TCP/IP sample interval Specify Take Action Security: SAF class name override The frequency with which IBM Tivoli OMEGAMON XE for Mainframe Networks requests performance data about your TCP/IP stack. The value is expressed in minutes from 1 to 60. The default value is 5 minutes. For every sample interval, IBM Tivoli OMEGAMON XE for Mainframe Networks gathers TCP/IP performance data from the z/os Communication Server network management interface (NMI) and the SNMP agent. Specify the security class override that will be used to validate OMEGAMON for Mainframe Networks action commands. Specify the name of the security class override. If the specified class is invalid or is not active in the security manager, the command will not be executed. The value should conform to the definition rules dictated by the security manager. The Configuration Tool generates the KN3_SECURITY_ACTION_CLASS parameter in one of these locations: v v In the xkanparu(kn3env) member, if the KN3 Agent runs in its own Agent address space, that is, if KN3_AGT_CONFIGURATION_MODE = "STANDALONE" In the xkanparu(kdsenv) member, if the KN3 Agent runs in the TEMS address space, that is, if KN3_AGT_CONFIGURATION_MODE = "CMS" Notes : v If you are using ACF2 as your external security resource manager, specify a maximum of three characters. v The SAF class name is applicable to Tivoli Enterprise Portal and OMEGAMON Enhanced 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 complete successfully. 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: 94 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

107 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. This panel 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 Specify monitored systems information on the Specify Configuration Parameters panel shown in Figure 11 on page 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 jobs described in Running the JCL Jobs on page 90 to incorporate this change into production. Verify that these jobs complete successfully. When the jobs complete successfully, the values will have been updated. a. Use the information in Table 19 to complete this panel: Table 19. Parameters and explanations for the Specify Component Configuration (Page 2) panel Parameter OSA Statistics Collection Interface Statistics Collection Interface Data Link Control Statistics Collection TCP/IP Stack Layer Statistics Collection Explanation Determines whether to collect OSA data for the system. This global parameter applies to the entire system. Y (the default) indicates OSA data will be collected on this system. N indicates OSA data will not be collected on this system. Determines whether to collect Interface Statistics data for the system. This global parameter applies to the entire system. Y (the default) indicates that Interface Statistics data will be collected on this system. N indicates Interface Statistics data is not be collected on this system. Specifying N will also disable collection of Devices data. Note: For performance reasons, turn on Interface Statistics collection if Routing Table Collection is active. Determines whether to collect Interface Data Link Control (DLC) Statistics read and write 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 indicates Interface DLC Statistics data will not be collected on this system. 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 that TCP/IP Stack Layer Statistics data will be collected on this system. N indicates that TCP/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 Component Configuration (Page 3) panel. 4. This action causes the continuation of the Specify Component Configuration (Page 3) panel sequence shown in Figure 14 on page 96 to be displayed: Chapter 7. Configuring the monitoring agent using the Configuration Tool 95

108 SPECIFY COMPONENT CONFIGURATION (Page 3) Command ===> Specify the following global information: 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) Figure 14. Specify component configuration (page 3) panel. Specify component configuration (pages 3) panel This configuration panel lets you specify which types of TCP/IP performance data to collect. This panel defines the values that apply globally to all TCP/IP address spaces being monitored. The default is for most categories of data to be collected, with the exception of IP Filters and IPSec Tunnels. Select global values that meet the needs of most of your monitored systems. Then in Step 2 Specify monitored systems information on the Specify Configuration Parameters panel shown in Figure 11 on page 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 jobs described in Running the JCL Jobs on page 90 to incorporate this change into production. Verify that these jobs complete successfully. When the jobs complete successfully, the values will have been updated. a. Use the information in Table 20 to complete this panel: Table 20. Parameters and explanations for the Specify Component Configuration (Page 3) panel Parameter Explanation TCP/IP Connection and Application Performance Statistics Collection IP Filters and IPSec Tunnels Statistics Collection Routing Table Statistics Collection Routing Table Collection Frequency TN3270 Server Statistics Collection Determines whether to collect TCP/IP Connection and Application performance statistics globally. Y (the default) indicates TCP/IP Connection and Application performance statistics will be collected. N indicates TCP/IP Connection and Application performance statistics will not be collected. Determines whether to collect IPSec security data. Y indicates IPSec Security data will be collected. N (the default) indicates IPSec Security data will not be collected. Determines whether to collect routing table data globally. Y (the default) indicates SNMP routing data will be collected. N indicates SNMP routing data will not be collected. Determines how often the routing table information will be collected. A value of 1 means that routing information is collected every collection interval. The global default value of 10 means that routing information is collected once every 10 collection intervals. The value is expressed as a whole number from 1 to 99. Setting a higher value means you collect the data less often, reducing overall CPU consumption while still making the data available. Determines whether to collect TN3270 data for all TN3270 servers running on this system. Y (the default) indicates TN3270 data will be collected. N indicates TN3270 data will not be collected. Only TN3270 connections which started within the display interval will be seen in the real-time data displays. 96 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

109 Table 20. Parameters and explanations for the Specify Component Configuration (Page 3) panel (continued) Parameter TN3270 Data Display Interval FTP Data Collection FTP Data Display Interval SNMP Configuration File Explanation Determines how long TN3270 server statistics will be displayed on the Tivoli Enterprise Portal. This value is expressed as a whole number in hours from 1 to 24. The default is 2 hours 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 indicates FTP data will not be collected. Determines the size of the sliding window that displays all FTP transfers that were completed or became active within the display interval. A value of "1" means the window displays all data from present until 1 hour ago. This value is expressed as a whole number in hours from 1 to 24. The default is 2 hours. The name of the data set containing configuration entries for the SNMP manager functions within TCP/IP data collection. Specify either the name of a sequential data set or the name of a partitioned data set, and the name of the member containing SNMP configuration entries. The data set name will have a format such as USER.PARMLIB (if the data set has physical sequential organization) or USER.PARMLIB(KN3SNMP) (if the data set has partitioned organization and member KN3SNMP contains SNMP configuration entries). For more information about defining the entries in this data set, see the KN3SNMP sample file in RKANSAMU. This field is required. For more information about the format of this file, see Appendix E, Format of the SNMP configuration file, on page 289. b. When all entries on this panel are complete, press Enter to go to the Specify Component Configuration (Page 4) panel. 5. This action causes the Specify Component Configuration (Page 4) panel shown in Figure 15 to be displayed: 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) Figure 15. Specify component configuration (page 4) panel. Specify component configuration (pages 4) panel 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 jobs described in Running the JCL Jobs on page 90 to incorporate this change into production. Verify that these jobs complete successfully. When the jobs complete successfully, the values will have been updated. a. Use the information in Table 21 on page 98 to complete this panel: Chapter 7. Configuring the monitoring agent using the Configuration Tool 97

110 Table 21. Parameters and explanations for the Specify Component Configuration (Page 4) panel Parameter Explanation Enterprise Extender and High Performance Routing Statistics Collection All High Performance Routing Connections CSM Buffer Reporting Buffer Pool/VTAM Environment Data Collection Determines whether to collect Enterprise Extender and High Performance Routing statistics. Y (the default) indicates Enterprise Extender and High Performance Routing statistics will be collected. N indicates Enterprise Extender and High Performance Routing statistics will not be collected. Determines if High Performance routing statistics will be collected for all connections or only Enterprise Extender connections. Y indicates that performance data for all High Performance Routing connections will be collected, regardless of whether this data flows over Enterprise Extender connections. N (the default) indicates that performance data will be collected only for High Performance Routing connections that flow data over Enterprise Extender connections. Determines whether to collect Communications Storage Manager buffer reporting data. Y (the default) indicates Communications Storage Manager buffer reporting data will be collected. N indicates Communications Storage Manager buffer reporting data will not be collected. Determines whether to collect data for VTAM buffer pools, applications, extents, and address spaces. Y (the default) indicates VTAM data will be collected. N indicates VTAM data will not be collected. If you specify Y, you will see an additional configuration panel. You may not start or modify the collection of VTAM buffer pools or VTAM address space data using the KN3FCCMD START SNAC command unless you indicate Y for this parameter. For more information about this command, see Appendix 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 Buffer Pool/VTAM Environment Data Collection, then you see Figure 16. If you specified N, then you are returned to the Specify Configuration Parameters panel shown in Figure 11 on page 93 except that dates and times are now provided for Option If you specified Y as the value for Buffer Pool/VTAM Environment Data Collection, pressing Enter in the previous step causes the Specify VTAM Applid Values (Page 5) panel shown in Figure 16 to be displayed: SPECIFY VTAM APPLID VALUES (Page 5) Specify the following global information: SNA data collection interval: ==> 5 (1-60 minutes) Specify the Mainframe Networks APPLID information on this panel: Major node CNM application ==> CTDN3N ==> CTDN3SP Figure 16. Specify VTAM applid values / RTE (Page 5) panel. Specify VTAM applid values / RTE (Page 5) panel This panel lets you define the collection interval for SNA data and specify the APPLID information required by the monitoring agent. Note: If you change any of these values after initial configuration, you must run the JCL jobs described in Running the JCL Jobs on page 90 to incorporate this change into production. Verify that these jobs complete successfully. When the jobs complete successfully, the values will have been updated. a. Use the information in Table 22 on page 99 to complete this panel: 98 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

111 Table 22. Parameters and explanations for the Specify VTAM APPLID Values (Page 5) panel Parameter Explanation SNA Data Collection Interval Determines how often VTAM buffer pool and VTAM address space performance data will be collected. A value of 1 means that SNA data is collected every minute. This value is expressed as a whole number from 1 to 60, indicating the collection interval in minutes. The default is 5 minutes. Specify the Mainframe Networks APPLID information on this panel: APPLIDs are the names by which logical units are known in a VTAM network. Default APPLIDs are provided by the Configuration Tool. You can keep these default names or change them to match naming conventions at your site. For more information about how the Configuration 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 VTAM APPLID definitions for OMEGAMON XE for Mainframe Networks. This member must be moved to your VTAMLST concatenation. The name of this major node is also 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 Secondary Program Operator, the OMEGAMON XE for Mainframe Networks monitoring agent can issue VTAM commands and receive the VTAM responses. The default is CTDN3SP. Note: Perform all configuration steps found on this panel. 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 complete successfully. When the jobs complete successfully, the values will have been updated. b. When all entries on this panel are complete, press Enter and you are returned to the Specify Configuration Parameters panel shown in Figure 11 on page 93 except that dates and times are now provided for Option Select 2 Specify TCP/IP monitored systems information and press Enter. This action causes the panel shown in Figure 17 to be displayed SPECIFY TCP/IP MONITORED SYSTEMS INFORMATION / RTE: HUBN3IRA The following is a list of TCP/IP systems that will be monitored by this product. The global override settings are determined by the selections on the TCP/IP Monitored Systems Information panel. Actions: A Add, C Copy, D Delete, U Update, V View TCP/IP Address 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 This panel provides a list of TCP/IP address spaces that OMEGAMON XE for Mainframe Networks will monitor when configuration is complete. From this panel, you can verify that the information shown is correct, override global values with system-specific values, or supply additional TCP/IP information by adding a monitored system or cloning another monitored system definition with the Copy function. By default, OMEGAMON XE for Mainframe Networks monitors all address spaces. However, in V4.2 and later, you can specify which stacks are monitored on a per stack basis. Using the Specify TCP/IP Monitored 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 to monitor this system." The value determines whether this stack is monitored. Y indicates this stack is monitored. N indicates this stack is not monitored. The default is Y. You must use this path to explicitly eliminate a discovered TCP/IP stack from being monitored. Chapter 7. Configuring the monitoring agent using the Configuration Tool 99

112 The configuration options provided in the $$$$ entry is used whenever a specific entry in not included in the table for a detected TCP/IP address space. The $$$$ entry is referred to as the global default. You cannot Delete (D) this value, but you can Update (U) it. If you want to apply different monitoring characteristics to each TCP/IP address space, you must Add (A) this address space from this 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 Parameter A Explanation 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, the defaults you specified in the Option 1 Specify Component Configuration path are displayed but all 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 process begins on the Specify TCP/IP Monitored Systems Information panel, shown in Figure 17 on page 99. C Copy the system monitored information. When you copy one monitored system definition to create a new monitored system, the defaults you specified in the Option 1 Specify Component Configuration 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 other panels are displayed. The system definition is removed and no longer visible on the Specify TCP/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, the values you have already specified in the Option 1 Specify Component Configuration path are displayed 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 specified for 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 complete successfully. 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 reserved combination. You may not change the override setting for this reserved combination. To change these global values, return to the Specify Configuration Parameters panel and select Option 1 Specify TCP/IP Component Configuration. See Step 2: Specifying configuration parameters on page If you are using the default global system definitions for a stack or address space, when you edit the N3#5 JCL job, you will not see a specific command for that stack because it is covered by the global definition. Even though you don't see the stack listed in the JCL job, the changes for these stacks are picked up when the N3#5 JCL job is run. Perform one of these operations. At any time, you can return to the panel found in Figure 17 on page 99 and press F3. When you finish configuring address spaces, choose Option 3 Create monitoring agent runtime members shown in Figure 11 on page 93 to create the N3#5xxx job, which will incorporate these changes into production. 8. Review and submit the JCL. You might want to change the jobname to match the member name so that 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 be returned to the Specify Configuration Parameters panel shown in Figure 26. Press F3 again to be returned to the Configure OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page 92. Adding, changing, or updating a monitored system definition You can add, change, or update a monitored system definition using these steps. 100 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

113 About this task When you add, change, or update a monitored system definition, the defaults you specified in the Option 1 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 blank and can be edited. v When you copy one system definition to another, you use the cloned values from another monitored system or LPAR as the starting place for configuring another. All fields in the Copy panel sequence can be updated. v When you update a monitored system definition, all values except the Sys and TCP/IP address space can 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 highlighted in white cannot be changed. This process begins on the Specify TCP/IP Monitored Systems Information panel, shown in Figure 17 on 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. Procedure 1. 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. This action causes the first of two Add TCP/IP Monitored System Info panels shown in Figure 18 is displayed 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 Use the values in Table 24 to complete this panel: Table 24. Parameters and explanations for the Add TCP/IP Monitored Systems Info panel Parameter Explanation 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. Chapter 7. Configuring the monitoring agent using the Configuration Tool 101

114 Table 24. Parameters and explanations for the Add TCP/IP Monitored Systems Info panel (continued) Parameter Explanation 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 using global override specifications. TCP/IP profile data set name Member name (optional) Do you want to monitor this stack? TCP/IP Connection Collection Override IP Filters and IPSec Tunnels Collection Override (optional) Routing Table Collection Override Routing Table Collection Frequency The name of the data set that contains the TCP/IP profiles. This data set can be either a partitioned data set or a sequential data set. The default is TCPIP.PROFILE.TCPIP. If you specify a partitioned data set, then you must supply a member name. This value cannot be altered during View (V) processing. The member name of the TCP/IP profiles in the TCP/IP profile data set. This value is required if you specify a partitioned data set. It is not used if you specify a sequential data set. This value cannot be altered during View (V) processing. Determines whether to monitor this stack. Y (the default) indicates this stack will be monitored. N indicates this stack will not be monitored. This is a required field. Determines whether to collect TCP/IP Connection and Application Performance Statistics for this address space. Y indicates TCP/IP Connection and Application Performance Statistics will be collected for this address space. N indicates TCP/IP Connection and Application Performance Statistics will not be collected. See Note at the end of this table for additional restrictions. Determines whether to collect IP Security and tunnel data for this address space. Y indicates IP Security data will be collected. N indicates IP Security data will not be collected. See the Notes at the end of this table for additional restrictions. 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 indicates SNMP routing data will not be collected for this address space. See Note at the end of this table for additional restrictions. Determines how often the routing table information will be collected for this address space. 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 means you collect the data less often, reducing overall CPU consumption while still making the data 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/IP Monitored Systems Info2 panel. 2. This action causes the second of three Add TCP/IP Monitored Systems Info2 for the specified RTE panel, shown in Figure 19 on page 103, to be displayed. 102 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

115 ADD TCP/IP MONITORED SYSTEMS INFO2 / RTE: HUBN3IRA COMMAND ===> Complete the items on this panel: Sys ==> TCP/IP address space ==> TCP/IP profile dataset name: ==> Member name ==> (Optional) 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 Use the information in Table 25 to complete this panel: Table 25. Parameters and explanations for the Add TCP/IP Monitored Systems Info2 panel Parameter Explanation TN3270 Collection Override (optional) TN3270 Display Interval Override (optional) FTP Collection Override FTP Display Interval Override Determines whether to override the global TN3270 Server Statistics Collection setting for the TN3270 server running on this system. Y indicates TN3270 data will be collected for the TN3270 server running on this system. N indicates TN3270 data will not be collected for the TN3270 server running on this system. See the Note at the end of this table for additional restrictions. Determines how long TN3270 server statistics will be displayed on the Tivoli Enterprise Portal for the TN3270 server running on this system. This value is expressed as a whole number in hours from 1 to 24. The default is 2 hours. See the Note at the end of this table for additional restrictions. Determines whether to override the global FTP Collection setting in this address space. Y indicates FTP data will be collected for this address space. N indicates FTP data will not be collected for this address space. See the Note at the end of this table for additional restrictions. Determines how long FTP data will be displayed on the Tivoli Enterprise Portal for this address space. A value of 1 means that FTP data is displayed for one hour. This value is expressed as a whole number in hours from 1 to 24. The default is 2 hours. See the Note at the end of this table for additional restrictions. 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 to the Add TCP/IP Monitoring Systems Info3 panel shown in Figure 20 on page This action causes the third of three Add TCP/IP Monitored Systems Info3 for the specified RTE panel, shown in Figure 20 on page 104, to be displayed. Chapter 7. Configuring the monitoring agent using the Configuration Tool 103

116 ADD TCP/IP MONITORED SYSTEMS INFO3 / RTE: HUBN3IRA COMMAND ===> Complete the items on this panel: Sys ==> TCP/IP address space ==> TCP/IP profile dataset name: ==> Member name ==> (Optional) 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) Use the information in Table 26 to complete this panel: Table 26. Parameters and explanations for the Add TCP/IP Monitored Systems Info3 panel Parameter Explanation OSA Collection Override (optional) Interface Collection Override (optional) Interface DLC Collection Override (optional) Stack Layer Collection Override (optional) (PF3 to CANCEL or Enter to proceed) Figure 20. Add TCP/IP monitored systems info3 panel. Add TCP/IP monitored systems info3 panel 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 will not be collected for this address space. Determines whether to override the global Interface Collection setting for this address space. Y indicates Interface data will be collected for this address space. N indicates Interface data will not be collected for this address space. Determines whether to override the global Interface Data Link Control (DLC) Collection read and write queue data for interfaces defined to this address space. Y indicates that Interface DLC read and write queue data for this address space will be collected. N indicates Interface DLC read and write queue data for this address space will not be collected. Determines whether to override the global TCP/IP Stack Layer Statistics Collection setting for this address space. Y indicates TCP/IP Stack Layer data will be collected for this address space. N indicates TCP/IP Stack Layer data will not be collected for this address space. 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 return to the Specify TCP/IP Monitoring Systems Information panel shown in Figure 17 on page You may add, update, or copy any of the monitored systems information using the processes described in the previous steps until you have made all configuration override updates to TCP/IP address spaces found in Figure 17 on page 99. When you have finished adding configuration information for the monitored TCP/IP address spaces, you will be returned to the Specify TCP/IP Monitored Systems Information panel shown in Figure 17 on page Press F3 to return to the panel shown in Figure 11 on page 93. Select Option 3 Create monitoring agent runtime members to view the JCL that is generated to create the TCP/IP monitored system member, &rhilev.&midlev.&rtename.rkanparu(kn3tcpmo). Submit JCL job N3#5xx. Upon successful completion of this job, press F3 twice to return to the Configure OMEGAMON XE for Mainframe Networks main menu panel, shown in Figure 10 on page IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

117 Step 3: Specifying agent address space parameters Use this step to create the address space in which the OMEGAMON XE for Mainframe Networks monitoring agent will run and define how this agent will communicate with Tivoli Enterprise Monitoring Server. About this task This step is used to provide information required to create the address space and communicate with the Tivoli Enterprise Monitoring Server of your choice. In a shared address space environment, only the address space owner (agent that created the address space) can change these parameters. Procedure 1. 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 panel shown in Figure 21 is displayed. This panel is used to specify the agent address space parameters and communication protocol priority sequence for the monitoring agent. The values in the second section of the panel are used to specify communication protocols that this agent will use to connect to the Tivoli Enterprise Monitoring Server. You must select a communication protocol that your Tivoli Enterprise Monitoring Server was configured to support in your environment using the Specify Agent Address Space Parameters panel, shown in Figure 21: SPECIFY AGENT ADDRESS SPACE PARAMETERS COMMAND ===> The following information is needed to define the Agent address space. Agent started task ==> CANSN3 Connect 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 Use the information in Table 27 to complete this panel: Table 27. Parameters and explanations for the Specify Agent Address Space Parameters panel Parameter Explanation Agent started task Specify the started task name for the agent. This started task must be copied to your system procedure library. The default is CANSN3. Chapter 7. Configuring the monitoring agent using the Configuration Tool 105

118 Table 27. Parameters and explanations for the Specify Agent Address Space Parameters panel (continued) Parameter Explanation Connect to TEMS in this RTE Specify Y if you want to connect to a Tivoli Enterprise Monitoring Server already configured in the RTE. This is the default when a Tivoli Enterprise Monitoring Server is detected in the RTE. To select a different primary Tivoli Enterprise Monitoring Server to connect to, specify N. Press F10 (the CMS List key) to display a list Tivoli Enterprise Monitoring Servers already configured in this RTE. The initial TEMS List is derived from local and non-local z/os Tivoli Enterprise Monitoring Server configured in this Configuration Tool environment. They are defined in this RTE or another RTE that is accessible to this installation library. The agent can connect to any Tivoli Enterprise Monitoring Server that runs on any platform. Name of primary TEMS 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 CSI environment where the primary monitoring server is installed, if this monitoring agent 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 another Configuration Tool environment or in another platform, then from the Communication Selection Panel, press the F5=Advanced key to navigate to the Specify Agent Primary TEMS Values panel. On this panel, specify the values for the primary Tivoli Enterprise Monitoring Server. When no Tivoli Enterprise Monitoring Server is defined in this RTE, the default is N, and you must select a Tivoli Enterprise Monitoring Server from the list displayed on the Communication Selection panel. Note: If the monitoring agent must switch primary Tivoli Enterprise Monitoring Server connections 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. The same procedure also applies if any of the primary Tivoli Enterprise Monitoring Server values that this agent connects to have changed. The monitoring agent must reconnect to the primary monitoring server to refresh the monitoring server values generated in the monitoring agent gent runtime members. 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 be displayed. Note: If the monitoring agent is connecting to the local monitoring server, and System Variable mode is enabled, then the System Variable monitoring server name is displayed. 106 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

119 Table 27. Parameters and explanations for the Specify Agent Address Space Parameters panel (continued) Parameter Explanation Specify the communication protocols in priority sequence Specify which communication protocols you want the monitoring gent to support when connecting to its primary Tivoli Enterprise Monitoring Server. By default, the first monitoring agent configured in this RTE takes the default protocols set by the monitoring server, if a local monitoring server is configured in this RTE. Otherwise, the default IP.PIPE, IP.UDP and SNA.PIPE protocol ordering is set for the monitoring agent, if both TCP and VTAM values are provided during initial RTE creation. You must specify at least one protocol. The communication protocols are used in the priority sequence that you set by numbering each protocol. They are used in the order in which they appear in the KDE_TRANSPORT environment in the KN3ENV member in the &hilev.&midlev. &rtename.rkanparu library. Environment variable KDE_TRANSPORT configures the transport ID managed by component KDE. Each transport ID consists of an address family and a protocol connected by a period (for example, IP.PIPE or IP.UDP). For compatibility, IP is assumed to 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 and parameters are then listed in preference order. See the Configuration Tool online help for this panel for an example of how to specify these protocols in a mixed IPv4 and IPv6 environment. In the second part of this panel, you specify the priority sequence for communication protocols. The choices are: IP.PIPE - Non-secure NCS RPC Specifies the use of the TCP/IP protocol for underlying communications. This protocol uses non-secure Network Computing System (NCS) that conform to the Network Computing Architecture. NCS includes the Remote Procedure Call (RPC) runtime library, the Location Broker, and the Network Interface Definition Language (NIDL) compiler. Note: IP.PIPE should be used for communication if the z/os system that this monitoring agent runs on supports TCP. In addition, enable only protocols in use by the monitoring agent's Primary monitoring server. IP.UDP - Non-secure NCS RPC Specifies the use of the UDP/IP (User Datagram Protocol), which is the "packet-based," connectionless-oriented protocol. This protocol uses non-secure Network Computing System (NCS) that conform to the Network Computing Architecture. Note: Enable only protocols in use by the monitoring agent's Primary monitoring server. IP6.PIPE - IP.PIPE for IPV6 Specifies the use of the TCP/IP protocol for underlying communications. This protocol uses non-secure Network Computing System (NCS) that conform to the Network Computing Architecture. Note: IPV6 must be installed and operational to use this protocol. Enable only protocols in use by the monitoring agent's Primary monitoring server. Chapter 7. Configuring the monitoring agent using the Configuration Tool 107

120 Table 27. Parameters and explanations for the Specify Agent Address Space Parameters panel (continued) Parameter Specify the communication protocols in priority sequence (continued) Explanation IP6.UDP - IP.UDP for IPV6 Specifies the use of the UDP/IP (User Datagram Protocol), which is the "packet-based," connectionless-oriented protocol. This protocol uses non-secure Network Computing System (NCS) that conform to the Network Computing Architecture. Note: IPV6 must be installed and operational to use this protocol. Enable only protocols in use by the monitoring agent's Primary monitoring server. IP.SPIPE - Secure IP.PIPE Specifies the use of the TCP/IP protocol for underlying communications. This protocol uses secure Network Computing System (NCS) that conform to the Network Computing Architecture. Note: The Transparent Transport Layer Security (TTLS) feature of z/os Communications Server must be available to use this protocol. IP6.SPIPE - Secure IP.PIPE for IPV6 Specifies the use of the TCP/IP protocol for underlying communications. This protocol uses secure Network Computing System (NCS) that conform to the Network Computing Architecture. Note: The Transparent Transport Layer Security (TTLS) feature of z/os Communications Server must be available to use this protocol. SNA.PIPE - Non-secure NCS RPC Specifies the use of Systems Network Architecture (SNA)/Advanced Program-To-Program Communications (APPC). This protocol uses non-secure Network Computing System (NCS) that conform to the Network Computing Architecture. Note: IPV6 must be installed and operational to use this protocol. Enable only protocols 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/os image 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 specify IP.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: 108 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

121 SPECIFY AGENT IP.PIPE CONFIGURATION VALUES COMMAND ===> Specify the IP.PIPE communication values for this Agent. These network address-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 Use the information in Table 28 to complete this panel: Table 28. Parameters and explanations for the Specify Agent IP.PIPE Communication Protocol and Specify Agent IP.UDP Configuration Values panels Parameter Explanation 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 To determine this value, issue the TSO HOMETEST command. If you decide to specify the hostname value for the network address, use the first qualifier of the fully qualified hostname if the z/os domain name resolver configuration specifies a search path that would include the target domain suffix. Started task 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 IPv4 address written in dotted decimal notation. This scheme is numeric and consists of four groups separated by a period (.). Note: IBM managed system names are generally derived from the TCP/IP hostname of the machine that the product runs on. Ensure that this value is different from the name of the Tivoli Enterprise Monitoring Server (TEMS name). You are prompted for a TCP/IP started task name when you create a runtime environment and when you configure a monitoring server or monitoring agent. In a new runtime 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 this system contains a single TCP/IP stack. If the system contains more than one TCP/IP stack, you can specify the started task name 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 to use, either through TCP/IP definitions or through the use of the SYSTCPD DD statement. Chapter 7. Configuring the monitoring agent using the Configuration Tool 109

122 Table 28. Parameters and explanations for the Specify Agent IP.PIPE Communication Protocol and Specify Agent IP.UDP Configuration Values panels (continued) Parameter Explanation Network interface list Specify a list of network interfaces you want the monitoring agent to use. This parameter is required for sites that are running multiple TCP/IP interfaces or network adapters on the same z/os image. Setting this parameter allows you to direct the monitoring agent to connect to a specific TCP/IP local interface. Specify the network adapters as one or more 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 If your site supports DNS, you can enter the short hostname or an IP address. If your site does not support DNS, you must enter the fully qualified hostname. This field is only applicable for networks with multiple interface cards for which a specific output network interface list is required. If an interface address or a list of interface addresses is specified, the Configuration Tool generates 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 Tivoli Enterprise Monitoring Server if one is configured in this IPL16 RTE. Also, separate the entries using a blank space between interface addresses. For example: ==> SYS1 SYS.IBM.COM Address translation Partition name 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 interface list considerations and usage. Specify Y to configure IP.PIPE support for communication across firewalls using address translation. Specify the partition name that identifies the location of this TEMS (namespace) relative to the firewallsi used for address translation. Note: The Tivoli Enterprise Monitoring Server that this monitoring agent connects to must have a corresponding partition reference entry. In this task, the partition table is populated or modified. The partition table contains labels 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 an external network, outside a firewall, during the Tivoli Enterprise Monitoring Server (TEMS) connection establishment phase. The first part of this connection establishment is the lb lookup, which requires that the location brokers to return the socket address of the monitoring server. The partition table is used by the brokers, matching a partition name for a client to the labels in the partition table. On a match, the associated socket address in the partition table is returned to the client outside the firewall. This socket address is used by the IBM products 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 for TCP), and a hostname or dotted-decimal IP address. The well-known port (Hub port) must be authorized by the firewall administrator. v v If UDP is the protocol configured in the partition table, then a range of (UDP) ports must be authorized by the firewall administrator (in addition to the well-known port). If TCP is the protocol, no additional ports other than the well-known TEMS port need be authorized. 110 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

123 After you provide the IP.PIPE configuration values, press Enter and you see the next protocol in the order that you specified. v If you specified IP.UDP, IP6.UDP as one of your protocols, then pressing Enter from the IP.PIPE configuration values panel causes the Specify Agent IP.UDP Configuration Values panel shown in Figure 23 to be displayed SPECIFY AGENT IP.UDP CONFIGURATION VALUES COMMAND ===> Specify the IP.UDP communication values for this Agent. These network address-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 This panel is used to specify the IP.UDP (User Datagram Protocol) values for configuring where the montioring agent address space is to run on your site. These values apply to any IP.UDP-related protocols you have enabled on the Specify Agent Address Space Parameters panel shown in Figure 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 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 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: Chapter 7. Configuring the monitoring agent using the Configuration Tool 111

124 Table 29. Parameters and explanations for the Specify Agent SNA Configuration Values panel Parameter VTAM applid prefix Explanation Specify the applid prefix to create the VTAM node and applids required by the monitoring agent. This field is required for SNA connection. Note: Type README APP on the command line to get more information on how the Configuration Tool processes VTAM applids. Use the F6=Applids key to specify the VTAM major node and applid values. If System Variable support is enabled, the Applid prefix must end with a dot (.) if the symbolic used as part of the Applid prefix is at the end of the value. Type README SYS on the command line to get more information on how the Configuration Tool processes VTAM 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 the IBM Tivoli NetView for z/os product. At a minimum, you will probably want to enable TCP/IP to be recycled. The Tivoli Enterprise Monitoring Server on z/os and the OMEGAMON XE for Mainframe Networks monitoring agent can now automatically reconnect to the TCP/IP address space when TCP/IP is recycled. This capability must be enabled on both the hub monitoring server and the monitoring agent by 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 the monitoring server is recycled, the monitoring server address space reconnects to it without being recycled. If this parameter is set to N (the default), then if the TCP/IP stack which is used by the monitoring server is recycled, the monitoring server address space must also be recycled to re-establish TCP/IP connectivity. See the IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os for more information about this capability. To specify these or other values found on the "Specify Advanced Agent Configuration Values" panel shown in Figure 21 on page 105, press F5=Advanced (or whatever function key is customized on your system to show the Advanced options). This action causes the "Specify Advanced Agent Configuration Values" panel shown in Figure 25 on page 113 to be displayed: 112 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

125 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 ==> K Language 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 ==> ( ) 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 1. Use the information in Table 30 on page 114 to complete this panel: Chapter 7. Configuring the monitoring agent using the Configuration Tool 113

126 Table 30. Parameters and explanations for the Advanced agent configuration values panel Parameter Explanation Enable secondary TEMS Specify Y to this parameter if you want to use a secondary Tivoli Enterprise Monitoring Server (monitoring server). To remove the secondary monitoring server definition, enter N. The currently selected secondary monitoring server is displayed. If a secondary monitoring server is defined, this agent automatically connects to it when the primary monitoring server is unavailable or terminates. The default is N. See the "Sharing address space when enabling secondary TEMS" help topic for additional considerations when enabling this feature. To select a different secondary monitoring server to connect to, specify N. Press F10=CMS List and the Configuration Tool presents the Communication Selection Panel (KCIPCMSS) with a list of monitoring servers. The initial monitoring server list is derived 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 one communication protocol value in common with the primary monitoring server that this agent 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 in this RTE or another RTE that is accessible to this installation library. Name of secondary TEMS Enable startup console messages Enable WTO messages 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 not accessible to this &rhilev.&midlev.instlib installation library. Note: The monitoring agent must also be installed in the non-local INSTLIB or CSI environment where the secondary monitoring server is installed, if this agent will report to this non-local monitoring server. 2. A monitoring server defined in another platform (non-z/os). If the preferred secondary monitoring server is located in another INSTLIB or in another platform, then, from the "Communication Selection Panel," press F5=Advanced to navigate to the "Specify Agent Secondary TEMS Values" (KAG62P8) panel. On the KAG62P8 panel, 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 List to navigate to the KCIPCMSS panel. The same procedure also applies if any of the secondary monitoring server values that this agent connects to has changed. The monitoring agent must reconnect to the secondary monitoring server to refresh the monitoring server values generated in the agent runtime members. If a secondary monitoring server has been selected, it will be listed here. If a secondary monitoring server has not been selected, None will be displayed. Specify Y to this parameter if you want a SYSLOG message on the console to indicate when the monitoring agent finishes initializing. You can use this message in an automation script. See the automation package for your site for further instructions on how 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 messages so the parameter must not be present in the KN3ENV member if you do not want this feature (i.e., if enabled later on, the parameter gets added to KN3ENV).If you wish to turn it back off, regenerate the N3#3Vxxx monitoring agent "Create runtime members" job to refresh KN3ENV, where xxx is the JCL suffix. Specify Y to this parameter if you want the monitoring agent address space to issue WTOs. WTOs write information and exception condition messages to the operator consoles. Alert messages are written to the consoles. The default is N. 114 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

127 Table 30. Parameters and explanations for the Advanced agent configuration values panel (continued) Parameter Explanation Reconnect after TCP/IP recycle Intervals Storage detail logging Flush VSAM buffers Virtual IP Address (VIPA) Type Minimum extended storage Language locale Specify Y to this parameter if you want the monitoring agent address space to reconnect to the z/os Communications Server without having to subsequently recycle the address space. When this field is set to Y, the "TOLERATERECYCLE" keyword is added in the KN3INTCP member of the &rhilev.&midlev.&rtename.rkanparu library. If this field is set to N, then when the z/os Communications Server is recycled, the address space must also be recycled to establish connectivity to TCP/IP. The default is N. Set the interval to monitor storage. The interval values are written as part of the second EVERY command in: &rhilev.&midlev.&rtename.rkancmdu(kn3agst) The default is 0 hours (hh) and 60 minutes (mm). Set the interval to force all deferred VSAM writes to DASD. The interval values are written as part of the third EVERY command in: &rhilev.&midlev. &rtename.rkancmdu(kn3agst) The default is 0 hours (hh) and 30 minutes (mm). Set this parameter to the type of VIPA defined for this z/os system. If the monitoring agent address space is a VIPA-defined application, specify if the VIPA definition is Static or Dynamic. If VIPA is in use, then the VIPA name is resolvable through the Domain Name Server (DNS). Note: The IP.PIPE protocol is required when dynamic VIPA is in use. Specify the amount of virtual storage the monitoring agent must acquire to run at your site. The default is Specify the language and codeset (system's locale) that you would like the monitoring agent to use. The language locale value is used for National Language support.this field requires the numeric value (1-36) representing the Language and Region in the table that follow. As an example, specify 1 for "English - United States". The country and character set that this language represents (for example, country is en_us and character set is ibm-037) make-up the LANG= environmental variable value generated in the KN3ENV member 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 the Language locale field. Important: If the language is not listed in the table that follows, contact IBM Software Support to get the actual LANG= value in country and character set format, and specify this value accordingly. In addition, this value defaults to the language locale setting used by the TEMS if one is configured in this RTE. Otherwise, the default is 1. See the online help for the Table of Languages and Regions from which you obtain these values. Program to Program (PPI) information: Forward Take-Actions commands to NetView for z/os Specify the Program to Program Interface (PPI) values that will enable forwarding of Take Action commands to IBM Tivoli NetView for z/os V5.2, or later. The Tivoli Enterprise Portal (TEP) user ID gets passed to NetView for z/os. Chapter 7. Configuring the monitoring agent using the Configuration Tool 115

128 Table 30. Parameters and explanations for the Advanced agent configuration values panel (continued) Parameter Explanation NetView PPI receiver Specify the name of the PPI receiver on NetView for z/os which will receive Take Action commands. This value is required if you specified Y to the "Forward Take Action commands 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, unique identifier 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" in NetView's DSIPARM initialization member, CNMSTYLE. Agent PPI sender The Configuration Tool generates the KGLHC_PPI_RECEIVER parameter in the KN3ENV member of the &rhilev.&midlev.&rtename.rkanparu library. This value defaults to the NetView 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 command APSERV for more details. Specify the optional name of the PPI sender. The value should be a 1-8 character, unique identifier for the sender 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 name should not conflict with any NetView for z/os domain name, as it is used in logging the command and command response in the NetView for z/os log. If a value is specified on this field, the Configuration Tool generates the KGLHC_PPI_SENDER parameter 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 agent jobname that is the source of the command. z/os Audit collection values Enable/Disable z/os Indicates the trace level to pass messages. Message trace levels (from low to high) are as audit collection follows: v X=Disabled v M=Minimum v B=Basic v D=Detai. Maximum in-memory cache entries Domain ( Audit domain name) Higher levels trace all lower levels. The value you specify generates an AUDIT_TRACE parameter in member &rhilev.&midlev.&rtename). If AUDIT_TRACE is not specified on the panel, AUDIT_TRACE=BASIC internal code default is set. The AUDIT_TRACE parameter is generated as commented out in KN3ENV. Indicates the maximum number of records kept in short-term memory for direct queries. Valid values range from 10 to The value you specify generates an AUDIT_MAX_HIST parameter 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 is generated as commented out in KN3ENV. Specifies an identifier that may be used to associate audit records. It is suited for commonly identifying agents that are associated with each other. An example use may be for sorting records by a particular customer. This field will also be used to create unique namespaces for RBAC. The value you specify generates an ITM_DOMAIN parameter in KN3ENV. 116 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

129 Table 30. Parameters and explanations for the Advanced agent configuration values panel (continued) Parameter Enable Self-Describing Agent processing (TEMA_SDA) Explanation 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 parameter written 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 Common Tivoli Enterprise Monitoring Agent (TEMA) Configuration What's New README entry for 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 yet support Self-Describing Agent processing, the following informational message is generated in the output log: KRAA0016, Ignoring TEMA_SDA Configuration. Agent SDA package not found for 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/IP Monitoring Systems Information panel shown in Figure 17 on page Press F3 to return to the Configure IBM OMEGAMON XE for Mainframe Networks panel shown in Figure 10 on page 92 so you can go on to the next step, Step 4 Specify dynamic terminal integration parameters. Step 4: Specifying dynamic terminal integration parameters Use this step to specify TN3270 Telnet session link parameter values. These parameters define the connection information that the Tivoli Enterprise Portal terminal emulator uses to connect to NetView for z/os. About this task Use this step to specify TN3270 Telnet session link parameter values. These parameters define the connection information that the Tivoli Enterprise Portal terminal emulator uses to connect to NetView for z/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 page 92, select 4 Specify dynamic terminal integration parameters. The panel shown in Figure 26 is displayed SPECIFY DYNAMIC TERMINAL INTEGRATION PARAMETERS OPTION ===> Dynamic link to NetView for z/os values NetView APPLID ==> CNM01 User data ==> Figure 26. Specify Dynamic Terminal Integration Parameters panel. Specify Dynamic Terminal Integration Parameters panel 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. Chapter 7. Configuring the monitoring agent using the Configuration Tool 117

130 Table 31. Parameters and explanations for the Specify dynamic terminal integration parameters panel Parameter Explanation NetView APPLID Specify the NetView for z/os APPLID that the OMEGAMON XE for Mainframe Networks monitoring agent will dynamically log on to. The NetView specified must run on the same system as the OMEGAMON XE for Mainframe Networks monitoring agent. The Configuration Tool generates the KN3_DLX_APPLID parameter in the KN3ENV member of the &rhilev.&midlev.rkanparu library. The default is CNM01. The field is a character string with a maximum length of 8. User data Specify the data to be passed to the NetView for z/os program during logon. The Configuration Tool generates the KN3_DLX_USERDATA parameter in the KN3ENV member of the &rhilev.&midlev.rkanparu library. If no user data is specified, the default value is a null string. This option may be used to specify the NetView OPERATOR ID and PASSWORD in NetView for z/os if the LOGONPW option is enabled in NetView. The field is a character string with a maximum length of 109 in the format userid/password. Attention: This is an optional field. However, if you provide an operator ID in this field, the NetView operator ID you provide should not be configured to be a receiver of unsolicited messages. For more information about the format of this field, see the "Logging on to NetView from a 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 on to the next step, Step 5 Create runtime members. Step 5: Creating runtime members The Create runtime members option in the Configuration Tool generates JCL that should complete with a return code of 0. About this task The Create runtime members step generates a batch job that creates the runtime members required to create or update the address space where the OMEGAMON XE for Mainframe Networks monitoring agent is running. These members are created in the runtime libraries for this RTE. Procedure 1. 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 Mainframe Networks 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 monitoring agent. This step is optional and depends on whether you plan to collect historical data for your system. 118 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

131 About this task Persistent data stores are associated with each Tivoli Enterprise Monitoring Server and each monitoring agent. You have already created one persistent data store for Tivoli Enterprise Monitoring Server. This persistent data store is for the OMEGAMON XE for Mainframe Networks monitoring agent. This step is optional 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 you will 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 monitoring agent address space for historical data collection. This step also allocates the persistent data store data sets 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-term history is configured at the Tivoli Enterprise Portal in the historical collection dialog. If the person who configures collection at the Tivoli Enterprise Portal, chooses to Collect at TEMS, these agent data sets are not used, and you might run out of storage for short-term history, depending on persistent data store collection at the Tivoli Enterprise Monitoring Server. If you implement this step, configure historical collection to be Collect at Agent on the Tivoli Enterprise Portal. Use the historical data store configuration worksheets in Appendix D, Disk space requirements for historical data tables, on page 257 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 Mainframe Networks monitoring agent. Procedure 1. The first panel in the persistent data store configuration flow is shown in Figure SPECIFY PERSISTENT DATASTORE VALUES COMMAND ===> The following values are used to allocate and maintain Persistent Datastore for standalone Agents. For efficiency, use the same maintenance procedure prefix for all your runtime environments (RTEs). Datastore high-level prefix: &rhilv.&midlev.hubn3ira Maintenance procedure prefix ==> KPDPROC Allocation volume ==> &volser Allocation unit ==> &unit Allocation STORCLAS ==> Allocation MGMTCLAS ==> Figure 27. Specify persistent data store values for the monitoring agent. Specify persistent data store values for the monitoring agent This panel is used to specify values for allocating and managing the persistent data store for use by the 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 and explanations for the Specify Persistent Datastore Values panel Parameter Explanation Maintenance procedure prefix Prefix for the names of the procedures that are used to perform persistent data store maintenance when a product data store file is full. Procedure names can be the same for all products in an RTE. Specifying the same procedure name prefix for all products is recommended. The default prefix is KPDPROC. Chapter 7. Configuring the monitoring agent using the Configuration Tool 119

132 Table 32. Parameters and explanations for the Specify Persistent Datastore Values panel (continued). Parameters and explanations for the Specify Persistent Datastore Values panel Parameter Explanation Datastore high-level prefix Allocation volume Allocation unit Allocation STORCLAS Allocation MGMTCLAS High-level qualifier used in the procedure that allocates persistent data store files for this standalone agent. The default is &rhilev.&midlev.&rtename. DASD volume used in the procedure that allocates persistent data store files for this standalone agent. DASD unit used in the procedure that allocates persistent data store files for this standalone agent. Valid unit types are 3380 and SMS storage class to be used in the procedure that allocates persistent data store files for this standalone agent. SMS management class to be used in the procedure that allocates persistent data store files for this standalone agent. Complete this panel and press Enter to save your changes and continue to the Allocate Persistent Datastore Menu panel. 2. The Allocate Persistent Datastore Menu panel shown in Figure 28 is used to configure persistent data store ALLOCATE PERSISTENT DATASTORE MENU OPTION ===> Perform these configuration steps in order: Last selected Date Time 1 Modify and review datastore specifications 2 Create or edit PDS maintenance jobcard 3 Create runtime members 4 Edit and submit datastore allocation job 5 Complete persistent datastore configuration Figure 28. Allocate persistent data store menu for the monitoring agent. Allocate persistent data store menu for the monitoring agent 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 in Figure 29 is displayed PERSISTENT DATASTORE SPECIFICATIONS ---- Row 1 to 1 of 1 COMMAND ===> 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 panel for the monitoring agent The parameters set from this panel control the size, the placement and the number of data sets that comprise the persistent data store. The settings on this panel are only suggestions; follow the guidelines for your site. 120 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

133 Use the information in Table 33 to define these values: Table 33. Parameters and explanations for the Persistent Datastore Specifications panel. Parameters and explanations for the Persistent Datastore Specifications panel Parameter Explanation Group Name The name of the group. Each group contains the number of data sets specified in the Group 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 Group Count value of 3, the following data sets with be allocated: v &rhilev.&midlev.&rtename.rkn3his1 v &rhilev.&midlev.&rtename.rkn3his2 v &rhilev.&midlev.&rtename.rkn3his3 Where RKN3HISn is the low-level qualifier. Group Count Est Cyl Space Backup, Export, and Extract You may use the default values displayed or change them to meet your site requirements. 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 collected short-term history for over 24 hours, but cannot create views at the Tivoli Enterprise Portal for a full 24 hours of data, then you need more data sets (Group Count) or larger data sets (Est Cyl Space). Some OMEGAMON XE agents use a group count of The supported minimum setting for this parameter is 3 for all but a limited number of special purpose data sets. If you specify 1, additional I/O is required to delete records when space is reused. If you specify 2, data becomes unavailable when a data store file fills up. Indicates the total number of cylinders of disk space for the group. The persistent data store processing computes how much space is needed to allocate the group data store files, and how much additional required space is needed to hold additional information. Additional information includes the product dictionary, table records, index records, and spare room for buffers that need to be reserved for when the data set is full. For more information about sizing the persistent data store, see Appendix D, Disk space requirements for historical data tables, on page 257. Note: 1. You might want to increase Group Count or Est Cyl space. If you have collected short-term history for over 24 hours, but cannot create views at the Tivoli Enterprise Portal for a full 24 hours of data, then you need more data sets (Group Count) or larger data sets (Est Cyl Space). Some OMEGAMON XE agents use a group count of If the value has changed from last release, the existing persistent data store data sets must be deleted so that reallocation will occur during this step. You might also want to increase this value if you upgrading from a prior release of the product. These fields are used for data store maintenance functions. Specify Y to turn on one of these maintenance functions for a group. You can use the backup facility if you want to keep old history data. This facility invokes an IEBGENER procedure to make an exact copy of the data set being maintained. It is a simple copy of the data set to either tape or DASD. A backed-up file also has the advantage that nothing has to be done to the file to dynamically make the data available to the persistent data store again. Note: If none of the maintenance options is specified, the data within the data set being maintained will be erased. Chapter 7. Configuring the monitoring agent using the Configuration Tool 121

134 If you update the values on this panel, you must press Enter and then F3 for your new values to take effect. You are returned to the Allocate persistent data store Menu panel. Select 2 Create or edit PDS maintenance jobcard and press Enter. 4. Selecting 2 Create or edit PDS maintenance jobcard causes a jobcard to be displayed. This step specifies the jobcard to be used for the persistent data store maintenance jobs ( KPDPROC1 and KPDPROCC). The KPDPROC1 member is created in the &rhilev.&midlev.&rtename.rkansamu library. The KPDPROCC member is created in the &rhilev.&midlev.&rtename.rkansam library. Press Enter when the jobcard is complete. You are returned to the Allocate Persistent Datastore Menu panel. 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 persistent data store definitions. Review and edit the JCL, and submit the job. 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. During the process of running this JCL job, the information panel about persistent data store maintenance shown in Figure 30 is displayed: Press Enter to advance when you have read this information UPGRADE PERSISTENT DATASTORE MAINTENANCE PROCEDURES OPTION ===> The Configure persistent datastore (PDS) historical data collection facility now supports a more simplified PDS maintenance procedure. It no longer requires the submission of a KPDPROC2 batch job and the PDS jobcard (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 KPDDSCO program must be enabled to execute as an authorized program under TSO. This can be done by adding the KPDDSCO name to the system PARMLIB(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 the monitoring agent When this job completes, press F3 to return to the Allocate Persistent Datastore Menu panel. Select 4 Edit 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 job allocates and initializes all data sets required for this product's persistent data store. Review and edit the JCL, and submit the job. 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. Note: This job is used to define a new persistent data store configuration. If the persistent data store data sets already exist, then delete or rename this product's persistent data store files if you want the Configuration Tool to re-allocate and re-initialize the data sets. If these data sets have not been deleted, then the persistent data store will contain residual data. This job will run with a completion code of 0 but will not re-allocate or re-initialize the data sets. You must delete or renames the data sets and run the job again. When this job completes, press F3 to return to the Allocate Persistent Datastore Menu panel. Select 5 Complete persistent datastore configuration and press Enter. 7. Enter 5 Complete persistent datastore configuration. This option describes steps you need to take outside the Configuration Tool to complete the configuration. This step is deferred until the completion of the configuration of OMEGAMON XE for Mainframe Networks. See Chapter 8, Completing the configuration, on page 127 for more information. 122 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

135 See IBM Tivoli Monitoring: Administrator's Guide for information about maintaining the persistent data store. After reviewing the information displayed in the Complete the persistent datastore configuration step, 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.0 panel shown in Figure 10 on page Enter 7 Complete the configuration. This describes the steps that you need to take to copy the members that you have created to your PROCLIB and VTAMLST libraries. It also identifies other steps you must run outside of the Configuration Tool to finalize installation and configuration of this product. Results Even though configuration of the OMEGAMON XE for Mainframe Networks monitoring agent is complete, do not start the monitoring agent yet. You must first load the runtime libraries and complete the configurations steps performed outside the Configuration Tool. See Chapter 8, Completing the configuration, on page 127 for more information. Step 7: Loading the runtime libraries Load the runtime libraries from the SMP/E target libraries after initial product configuration, after applying 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 Mainframe Networks monitoring agent, you must load the runtime libraries from the SMP/E target libraries. The load job requires shared access to the runtime libraries, and must be performed for each runtime environment (RTE). You must load the runtime libraries based on the following conditions: v After initial product configuration v After applying SMP/E maintenance v 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 be loaded after applying SMP/E maintenance because these RTE types contain copies of the SMP/E target libraries. If the RTE is configured to share the SMP/E target libraries directly, then this load step is not required after applying SMP/E maintenance. For additional information enter README RTE on the Configuration Tool command line. Follow these steps to load the runtime libraries from the SMP/E target libraries. Procedure 1. 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 Runtime Environments (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 code is 04 or less. Chapter 7. Configuring the monitoring agent using the Configuration Tool 123

136 4. When you are finished loading the libraries, exit the Configuration Tool. Considerations when performing the RTE load function Look at the README SYS and README RTE files for additions considerations when performing the RTE load function. After initial configuration of the first product configured in an RTE, you must perform the Load all product libraries after SMP/E step from the Configuration Tool Runtime Environments (RTE) panel. If you have additional products that you plan to configure in this RTE, perform the Load all product libraries after SMP/E step after you have completed the configuration of all products in this RTE. If you intend to start using this product operationally before the additional products are initially configured in this RTE, then you must perform the Load all product libraries after SMP/E step for this product before startup. If you are using system variables, read the information found in the README SYS file that is part of the Configuration Tool help. After all required steps for this product within the Configuration Tool have been performed, then you must perform some steps outside of the Configuration Tool to finalize installation and configuration of this product. Each product lists these steps in the Complete the configuration option from the product main menu. For more information, see the README RTE file by entering README RTE from the Configuration Tool command line. Step 8: Completing the configuration Perform the Complete the Configuration steps outside the Configuration Tool or PARMGEN to enable the monitoring agent to work with the z/os environment. About this task Option 6 Complete the configuration on the Configure OMEGAMON XE for Mainframe Networks menu displays a description of the steps you must take outside of the Configuration Tool or PARMGEN to complete the configuration process and ensure that you have the definitions that have been created in the configuration in your runtime environment. You can complete these steps following the procedures displayed 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 all the 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 Services on z/os: Common Planning and Configuration Guide for more information. Updating your runtime environment to support the NetView for z/os packet trace Use this information if you plan to use the Dynamic XE to 3270 functionality to access the NetView for z/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/os packet trace function, then the settings for your runtime environment must include the information required for 3270 applications to link to NetView for z/os. If you are creating your runtime environment 124 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

137 for the first time, you should ADD this functionality. If you have an existing runtime environment for the OMEGAMON XE for Mainframe Networks monitoring agent, you should update this runtime environment. 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 the Configuration 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 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 Utilities R 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 6. On the Runtime Environments (RTEs) panel, type U (Update RTE) in the Action field adjacent to the name 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: UPDATE RUNTIME ENVIRONMENT (3 of 3) If you require TN3270E Telnet session link support override, complete these values: Hostname ==> Port number ==> LUGROUP ==> Figure 32. Update Runtime Environment (3 of 3) panel. Update Runtime Environment (3 of 3) panel a. Use the information in Table 34 on page 126 to complete this panel: Chapter 7. Configuring the monitoring agent using the Configuration Tool 125

138 Table 34. Parameters and explanations for the Update Runtime Environment (3 of 3) panel Parameter Explanation Hostname If the system where you are defining a runtime environment does not have an active Telnet listener, specify the network address of a system that does have an active Telnet listener. 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, ) To get this value, issue the TSO HOMETEST command on the system of the Telnet listener. Port number The default port number of the Telnet listener is 23. To override this value, specify the port number of the Telnet listener. LUGROUP The Dynamic XE to 3270 (NetView for z/os) linking feature requires the VTAM Unformatted System Services (USS) screen to accept a LOGON APPLID() DATA() command. If the default Telnet USS screen does not accept this command, supply the name of a Logical Unit (LU) group that does accept it. The TN3270 session will be joined to that LU group. Note: 1. Complete this panel only if you are configuring products that support the Dynamic XE to 3270 (NetView for z/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 can be 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 in the 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 and Tivoli Management Services on z/os: Common Planning and Configuration Guide for information about setting up a runtime environment. 126 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

139 Chapter 8. Completing the configuration Use this information to understand the flow of tasks completed outside the Configuration Tool or PARMGEN 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 complete the configuration of OMEGAMON XE on z/os. Some of these steps may not be listed under Option 6 Complete the configuration in the Configure OMEGAMON XE for Mainframe Networks panel, shown in 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 agent are not found in the online help for the Configuration Tool or PARMGEN. To ensure that you perform all the steps required and perform them in the correct order, use this chapter for product configuration, not the 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 128 v 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 all the products. v Add support for the SYSTCPD DDNAME in the started tasks on page 131 v Copy the started task procedures to your procedure library on page 132 v Vary the VTAM major node active and copy it to your VTAMLST library on page 133 v APF authorize your libraries on page 133 v 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 135 v Enabling CSA tracking to display TCP/IP CSA usage on page 136 v Configuring the OMEGAMON XE for Mainframe Networks SNMP manager functions on page 136 v 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 monitoring server 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 139 v Verify the configuration on page 139 v 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 Copyright IBM Corp. 2006,

140 Authorizing users to access OMEGAMON XE for Mainframe Networks managed systems on the enhanced 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 the release level of z/os is other than the release level of the system where the SMP/E installation of the OMEGAMON XE for Mainframe Network monitoring agent was installed, perform this task: v Deploy the configuration on page 146 v Relink the runtime environments on page 147 Perform agent-specific security configuration As part of the configuration done outside the Configuration Tool or PARMGEN, you must perform agent-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 your system authorization facility (SAF) product to authenticate your Tivoli Enterprise Portal users when you set up your Tivoli Enterprise Monitoring Server on z/os. Additional RACF authorization described in the following section is required when you configure the OMEGAMON XE for Mainframe Networks monitoring agent. User IDs were also defined on the UNIX and Windows systems that are part of your distributed components. For more information about security issues in the Tivoli Management Services environment, see IBM Tivoli 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 for Mainframe 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 interfaces and commands As part of the configuration done outside the Configuration Tool or PARMGEN, you must define monitoring agent access to the network management interfaces and commands for the OMEGAMON XE for Mainframe Networks monitoring agent. About this task If your site has the security profiles defined for the z/os Communications Server network management interfaces (NMIs), then the OMEGAMON XE for Mainframe Networks monitoring agent must be authorized to access these interfaces. One or more of the following security profiles may be defined in the SERVAUTH class: v EZB.NETMGMT.systemname.tcpipprocname.* v EZB.NETMGMT.systemname.tcpipprocname.SYSTCPCN v EZB.NETMGMT.systemname.tcpipprocname.SYSTCPSM v EZB.NETMGMT.systemname.tcpipprocname.IPSEC.DISPLAY v IST.NETMGMT.systemname.SNAMGMT If the security profiles are not defined in order to control access to the NMIs, the user ID under which the monitoring agent procedure runs must be a superuser. A superuser is an ID which has a numeric value of 0 and which has been permitted to the BPX.SUPERUSER profile in the FACILITY class. 128 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

141 If your site has security profiles defined for the OPERCMDS class, then the OMEGAMON XE for Mainframe Networks monitoring agent must be authorized to access the following commands: VARY TCPIP,,DROP DISPLAY NET DISPLAY TCPIP DISPLAY A Access to these commands is controlled by the following profiles in the OPERCMDS class: MVS.VARY.TCPIP.DROP MVS.DISPLAY.NET MVS.DISPLAY.TCPIP MVS.DISPLAY.JOB The Configuration Tool placed a sample JCL job in the &rhilev.&midlev.&rtename.rkansamu library called KN3UAUTH that will create a new KN3USER user and grant it access to several security profiles: v IST.NETMGMT.systemname.SNAMGMT in the SERVAUTH class v EZB.NETMGMT.systemname.tcpipprocname.* in the SERVAUTH class v MVS.VARY.TCPIP.DROP in the OPERCMDS class Additionally, the JCL contains commented out sample statements that grant the agent access to the security profiles that control access to the DISPLAY NET, DISPLAY TCPIP, and DISPLAY A commands: v MVS.DISPLAY.NET in the OPERCMDS class v MVS.DISPLAY.TCPIP in the OPERCMDS class v MVS.DISPLAY.JOB in the OPERCMDS class The PARMGEN configuration method copies this sample JCL to your PROCLIB if you ran the JCL to copy 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 job before 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 and MVS.DISPLAY.JOB resources profiles in the OPERCMDS class. To do this you can remove the comment delimiters in front of the statements that define (RDEFINE) these resources and permit (PERMIT) the agent user ID to access them. You do not need to remove the comment delimiters on the statements that 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 your enterprise. 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 to monitor. 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

142 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 of KN3USER in the job. Make these changes and review this job before you provide it to your security department. It should run with a zero return code. Note that a user ID defined with UID(0) authority (SUPERUSER) has automatic access to the NMI resources required by the OMEGAMON XE for Mainframe Networks agent. However, if your installation does not permit the creation of a UID(0) user ID, the KN3UAUTH sample job must still be run in order to establish the proper rules required by the agent task. The KN3UAUTH job contains sample RACF statements that demonstrate how a user ID associated with a non-zero UID can be created. In the JCL example, the value UID(12345) is used, but any valid, non-zero number acceptable by the UID parameter can be used to define the user ID. UID(12345) is not required; it is used here to demonstrate the UID(0) is not 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 attribute in the Agent Status workspace will show a value of ROOT. If the UID is not UID(0), the Agent User ID is displayed as the KN3USER user ID (the default in the sample file) or the user ID that the system administrator coded on the RACF ADDUSER statement. The KN3UAUTH job will be created every time you go through the configuration process in the Configuration 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 for this 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 PROCLIB that you specified. The default location is SYS1.PROCLIB. Give users authorization and resource access to run the VARY TCPIP DROP command As part of the configuration done outside the Configuration Tool or PARMGEN, you give users authorization and resource access to run the VARY TCPIP DROP command for the OMEGAMON XE for Mainframe Networks monitoring agent. About this task z/os Communications Server protects data and other system resources accessed by applications included in the Communications Server z/os component. This protection requires that the identity of the user requesting access be verified (identification and authentication) and that access be limited to only those resources permitted to this user (access control). z/os Communications Server applications use RACF for identification and authentication and for access control, though you may use other supported security access facility (SAF) programs. Users authenticated with 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 VARY TCPIP,tcpip_jobname,CMD=DROP,CONNECTION=connection_number command to function correctly. The permissions granted to a given Tivoli Enterprise Portal user determine the network resources against which the DROP command can be executed. TCP/IP uses SAF profiles in the OPERCMD resource class to determine access to network resources. The MVS.VARY.TCPIP.DROP profile can be used by a SAF product to restrict access to the DROP command. 130 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

143 If the MVS.VARY.TCPIP.DROP profile is defined, the monitoring agent restricts access to the DROP command to only those users who have CONTROL or higher access to the MVS.VARY.TCPIP.DROP profile. 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. The command 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 the user chooses to allow these actions. 2. When a DROP Connection command is issued from the dialog, the OMEGAMON XE for Mainframe Networks agent will check the Tivoli Enterprise Portal User ID to validate that the user issuing the command 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 for Mainframe 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 tasks As part of the configuration done outside the Configuration Tool or PARMGEN, users of other monitoring agents must add support for the SYSTCPD DDNAME in the started tasks. This step is not necessary for OMEGAMON XE for Mainframe Networks users. This step is performed for you as part of a JCL job. About this task Note: This step is not necessary for OMEGAMON XE for Mainframe Networks users. This step is performed for you as part of a JCL job. SYSTCPD explicitly identifies which data set to use to obtain the parameters defined by TCPIP.DATA when no GLOBALTCPIPDATA statement is configured. If a monitoring server is using any of the IP.UDP-related or IP.PIPE-related communication protocols for connection, but the IP domain name resolution is not fully configured on the z/os system, SYSTCPD must 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, note that you might gain a small performance benefit by avoiding multiple dynamic data set allocations if you supply a SYSTCPD DD statement. To support SYSTCPD, uncomment the following statement in the started task members in RKANSAMU and provide the name of the SYSTCPD data set: //*SYSTCPD DD DISP=SHR, //* DSN=TCPIP.SEZAINST(TCPDATA) Chapter 8. Completing the configuration 131

144 The name of the SYSTCPD data set is installation-specific. Get the correct specification from your network administrator. 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 for connection, but the IP domain name resolution is not fully configured on this z/os system, you must specify 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 the procedures, you only need edit them in PROCLIB if you installed the monitoring agent using PARMGEN. Copy the started task procedures to your procedure library As part of the configuration done outside the Configuration Tool or PARMGEN, you must copy the started tasks procedures to the procedure library used by the OMEGAMON XE for Mainframe Networks monitoring agent. About this task The Configuration Tool created started task procedures in &rhilev.&midlev.&rtename.rkansamu that you must 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 the Configuration Tool, on page 87 for more information. 2. If you have configured a persistent data store for the OMEGAMON XE for Mainframe Networks monitoring agent, copy the persistent data store maintenance procedures (KPDPROC1 from &rhilev.&midlev.&rtename.rkansamu and KPDPROC from &rhilev.&midlev.&rtename.rkansam) to your PROCLIB. Note: You might also use the sample system copy JCL to copy the system procedures and the VTAM major node members from the &rhilev.&midlev.&rtename.rkansamu library to the system libraries (if applicable). 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 system procedure copy job (CB#Pxxxx) is displayed. 132 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

145 Vary the VTAM major node active and copy it to your VTAMLST library As part of the configuration done outside the Configuration Tool, you must vary the VTAM major node active and copy it to the VTAMLIST library used by the OMEGAMON XE for Mainframe Networks monitoring 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 your VTAMLST library. (CTDDSN is the default name of the VTAM major node definition for the Tivoli Enterprise Monitoring Server on z/os. CTDN3N is the default name of the VTAM major node definition for 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 in Chapter 7, Configuring the monitoring agent using the Configuration Tool, on page 87, vary the VTAM node (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 to VTAMLST and activated before the OMEGAMON XE for Mainframe Networks monitoring agent is started. Note: You might also use the sample system copy JCL to copy the system procedures and the VTAM major node members from the &rhilev.&midlev.&rtename.rkansamu library to the system libraries (if applicable). 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 system VTAMLST copy job (CB#Nxxxx) is displayed. If you used the PARMGEN configuration method, these statements were added to PROCs. You uncomment these statement to vary the VTAM node active. PARMGEN also copies these statements to the VTAMLST you specified during configuration if you run the KCIJPSYS JCL jobs to do this. APF authorize your libraries As part of the configuration done outside the Configuration Tool or PARMGEN, you must APF authorize the 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-authorized libraries. Chapter 8. Completing the configuration 133

146 &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 the CANSN3 started tasks must be APF-authorized. See the Complete the Configuration information in the Configuration Tool for additional information. The PARMGEN configiruation method updates your PROC with these statements, but you must uncomment them. Enable historical data store maintenance As part of the configuration done outside the Configuration Tool or PARMGEN, you must enable historical 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 the historical 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 the persistent data store files. PARMGEN performs this task automatically and copies this procedure to the 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 data store. Data store files are archived, exported or recycled according to the maintenance strategy that you specified for persistent data store file groups for the product. The persistent data store subsystem automatically submits maintenance jobs whenever a data store file becomes full. The maintenance procedure must be available in a system procedure library for the procedure to operate. The procedure is generic so it may be used by all runtime environments using this version of the persistent data store. 2. Authorize the KPDDSCO module The KPDPROCC REXX procedure runs in a TSO environment and must be enabled to run as an authorized program under TSO. Authorize the KPDDSCO module by adding KPDDSCO to the system PARMLIB(IKJTSOnn) under the AUTHPGM section and refresh the IKJTSOnn member by issuing the set command (T IKJTSO=nn). You might also request that authorized system programmers perform 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 the following 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: 134 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

147 Command: RESUME FILE=DSN:&rhilev.&midlev.&rtename.RKN3HIS1 KPDDSTR: CONNECT processing started for DataStore file DSN:&rhilev.&midlev.&rtename.RKN3HIS1 KPDDSTR: CONNECT processing ended for DataStore file DSN:&rhilev.&midlev.&rtename.RKN3HIS1 e. If these references are not found, view the KPDPROC1 started task in SDSF and look for any obvious errors. If you are upgrading an existing monitoring server or monitoring agent, you must also refresh the KPDPROC1 maintenance procedure in your system procedure library. See IBM Tivoli OMEGAMON XE and 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, and environment configuration. The ITMSUPER Tools are included in the IBM Support Assistant (ISA), a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. To install the ISA software, go to Making the performance monitor interface (PMI) exit available to VTAM As part of the configuration done outside the Configuration Tool or PARMGEN, you must make the performance monitor interface exit available to VTAM for the OMEGAMON XE for Mainframe Networks monitoring agent. You must make the PMI exit accessible to VTAM. Choose one of these two ways to do this task: by modifying 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/E target libraries (that is, SHARING SMP), then you could add the following statement to the VTAMLIB concatenation. See the note in the XE configuration section on this topic if you select this option. Add this library: 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/E target libraries (that is, SHARING SMP), then you could add the following statement to the VTAMLIB concatenation. See the note in the XE configuration section on this topic if you 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 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 page 136. You should not add SMP/E target libraries to the VTAMLIB concatenation because this would be a problem when you apply maintenance in the future. Chapter 8. Completing the configuration 135

148 Copying the PMI Exit to VTAM An alternate approach is to copy the PMI exit module and its ALIASes to an existing library in the VTAMLIB concatenation. The PMI Exit consists of module KN3AMVPX and its five ALIASes KN3AMV The PMI Exit must be found somewhere in the VTAMLIB concatenation in order for the exit to function correctly when the Tivoli OMEGAMON XE for Mainframe Networks program tries to activate 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 picked up when you apply maintenance if you forget to recopy the PMI Exit program and its ALIASes to the library in the VTAMLIB concatenation after the maintenance is applied. Another potential problem occurs if you copy the PMI exit to different libraries in the VTAM concatenation and have multiple copies of the PMI exit in your VTAMLIB concatenation. If you choose this approach, you must put a process in place for ensuring that the OMEGAMON XE for Mainframe Networks PMI exit program is correctly maintained. Enabling CSA tracking to display TCP/IP CSA usage As part of the configuration done outside the Configuration Tool or PARMGEN, you must enable CSA tracking so that TCP/IP CSA usage can be displayed for the OMEGAMON XE for Mainframe Networks monitoring 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 SNMP manager functions As part of the configuration done outside the Configuration Tool or PARMGEN, you configure SNMP manager 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 this file format. Procedure 1. 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. 136 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

149 Results When you start the Tivoli Management Services environment and the OMEGAMON XE for Mainframe Networks monitoring agent, workspaces that use data collection services dependent on SNMP should display data. Related reference: Appendix E, Format of the SNMP configuration file, on page 289 Since V4.2, SNMP data collection in the OMEGAMON XE for Mainframe Networks monitoring agent was enhanced to give you greater flexibility when communicating with the SNMP agents. Authorize the OMEGAMON XE for Mainframe Networks started tasks for TCP/IP privileges Use this information to define a TCP/IP OMVS segment for the user ID associated with units of work requesting these UNIX System Services. About this task The OMEGAMON XE for Mainframe Networks TCP/IP data collector uses TCP/IP service components in z/os Communications Server that exploit z/os UNIX System Services. Using these components requires a UNIX System Services security construct, called an OMVS segment, for the user ID associated with units of work requesting these services. The OMVS segment must be defined with SuperUser authority. Authorize the OMEGAMON XE for Mainframe Networks started task for TCP/IP privileges by creating an OMVS segment for RACF or another SAF product. Identify the OMEGAMON XE for Mainframe Networks started task CANSN3 as a superuser, 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 provide an OMVS segment for the OMEGAMON XE for Mainframe Networks started task. Note: This command makes setting of SuperUser authority more explicit. This action has actually already taken place when you ran the JCL job described in Define monitoring agent access to the network 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 launch the OMEGAMON XE for Mainframe Networks monitoring agent. Be aware that as of z/os V2R1, the ability to use default OMVS segments has been removed. All z/os UNIX users or groups must now have OMVS 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 in system log on z/os v2.1 systems" in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide. Configure historical data collection As part of the configuration done outside the Configuration Tool or PARMGEN, you must configure historical 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). Chapter 8. Completing the configuration 137

150 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 Enterprise Portal. The Tivoli Enterprise Portal History Collection dialog box displays all of the OMEGAMON XE for Mainframe Networks attribute tables that are enabled for historical collection and reporting. To enable historical data collection, you must select and configure each group (attribute table) for which you want to collect data, and then start collection of those groups. If you want to warehouse the data for long-term historical 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's GuideIBM Tivoli Monitoring: User s Guide, and the Tivoli Enterprise Portal online help. Enable Warehouse agents on a z/os hub monitoring server As part of the configuration done outside the Configuration Tool or PARMGEN, you must enable Warehouse agents on a z/os hub monitoring server for the OMEGAMON XE for Mainframe Networks monitoring agent. About this task If you want to store long-term history data and your hub monitoring server is on z/os, you must transfer the catalog and attribute files for the Warehouse Proxy agent and the Summarization and Pruning 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 install application support for OMEGAMON XE for Mainframe Networks, using the IBM Tivoli OMEGAMON Data 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 Manage Tivoli 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 and Attribute 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 Pruning agents, 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 Server v A valid FTP user ID and password v 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. 138 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

151 Install application and language support As part of the configuration done outside the Configuration Tool or PARMGEN, you must install application 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 displayed in the Tivoli Enterprise Portal, support for the agents must be installed and enabled. Application support files 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 called seed 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, and expert 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 Portal Server, and Tivoli Enterprise Portal desktop client, if the desktop client was installed from the installation media. Application support for the monitoring agent is installed on the remote monitoring servers when agents are registered with the local monitoring server. The files required for support are contained in IBM Tivoli OMEGAMON Data Files for z/os DVD included in the product package. You install support on the Tivoli Enterprise Portal Server and any desktop clients on 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 on which it is installed). If your hub is on z/os, you install support from a Windows computer that hosts either a Tivoli Enterprise Portal Server or a Tivoli Enterprise Monitoring Server. The hub monitoring server must be running while you are installing support. Use the procedures documented in the IBM Tivoli Monitoring: Installation and Setup Guide to add support to Tivoli Enterprise Portal or a hub monitoring server on Windows, AIX, or Linux. Use the instructions in IBM Tivoli Monitoring: Configuring the Tivoli Enterprise Monitoring Server on z/os to add support to a z/os hub. If you want application data, online help, and expert advice to be displayed in a language other than English, you must also install language support. You install language support from the IBM Tivoli OMEGAMON XE for Mainframe Networks Language Pack CD on the same system where you install application support. Install the language packs on any system where you have installed the Tivoli Enterprise Portal or where you have installed a desktop client. (If you download and run a desktop client using Web Start, you do not need to install the language packs on the local system. They are downloaded from the portal server.) Before you can install a language pack, you must install the component in English. For additional information about installing application and language support, including the most up-to-date files, see Technote at docview.wss?uid=swg Verify the configuration The verification task must be performed at this juncture during configuration. Chapter 8. Completing the configuration 139

152 About this task Follow the instructions in Verifying configuration if you configured both Tivoli Enterprise Portal and the enhanced 3270 user interface on page 149 to verify that you have correctly configured the products and components. Enable security After your new environment is configured correctly, you can safely enable the required level of security on 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 authorize users to view the monitored data and set up authentication of those accounts by enabling security through the hub monitoring server or through the portal server. For instructions on enabling authentication on a hub monitoring server on Windows, Linux and UNIX operating systems, see the IBM Tivoli Monitoring: Administrator's Guide. For instructions on enabling authentication on a hub monitoring server on z/os systems, see the IBM Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os. If you intend to use autonomous agents on a z/os system, you can enable SNMP V3 passwords if the Integrated 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 enable security by following the steps described in Authorizing users to access OMEGAMON XE for Mainframe 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 explicit security definitions are configured that enable these commands to be issued. Security for this monitoring agent s Take Action commands is implemented through direct SAF (System Authorization Facility) calls and is based on resource profiles. Both user ID and command are validated. See Authorizing users to issue 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 Portal As part of the configuration done outside the Configuration Tool and PARMGEN, you must enable security at Tivoli Enterprise Portal. About this task To enable security for the Tivoli Enterprise Portal through either the hub monitoring server or the Tivoli Enterprise Portal Server, review the planning information in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide and see the appropriate guide for instructions. To enable security for OMEGAMON XE for Mainframe Networks, see Perform agent-specific security configuration on page 128. Enabling SNMP V3 passwords for autonomous agents If you intend to use autonomous agents on a z/os system, you can enable SNMP V3 passwords if the ICSF subsystem is available on the z/os system. 140 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

153 See the Enabling SNMP V3 passwords for autonomous agents topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide for more information about performing this task. Authorizing users to access OMEGAMON XE for Mainframe Networks managed systems on the enhanced 3270 user interface Logons to the OMEGAMON XE for Mainframe Networks enhanced 3270 user interface are controlled through the system authorization facility (SAF) interface. In addition, the OMEGAMON enhanced 3270 user interface performs SAF checks on users authorization to view data for specific managed systems or managed 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 OMEGAMON enhanced 3270 user interface and to view data for any managed system. All Take Action commands are denied. If a security class name is configured, resource profiles must be defined to control logon, data access, and Take Actions, and users must be given access to those profiles. For instructions on configuring security for the OMEGAMON enhanced 3270 user interface, see the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os Common Planning and Configuration Guide. Authorizing users to issue Take Action commands Certain commands, known as Take Action commands, can be issued from the Tivoli Enterprise Portal and OMEGAMON enhanced 3270 user interface. OMEGAMON XE for Mainframe Networks supports two types of Take Action commands: z/os system commands and agent-provided commands. Users must be authorized to issue these commands. z/os commands By default, Take Action commands issued by OMEGAMON XE for Mainframe Networks are issued as z/os system commands. However, a monitoring server or monitoring agent address space can be configured to redirect Take Action commands to NetView through the program to program interface (PPI). Take Action commands that are issued in NetView make full System Authorization Facility (SAF) calls for authorization. NetView uses the Tivoli Enterprise Portal user ID to determine the NetView operator on which the command authorization is performed. If command authorization passes, the command is processed by the NetView operator. Messages are written to the NetView log to provide an audit trail of the commands and the users that issued them. If you enable NetView command authorization on the monitoring server, you must also enable NetView to execute the commands. For more information, see "Configuring NetView authorization of z/os commands" in IBM Tivoli Monitoring: 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: Drop Nslookup Ping Tracerte Chapter 8. Completing the configuration 141

154 These commands, which are prefixed by N3:, are known as agent commands. A subset of these commands, commands that cannot also be run as console commands, can be issued using the Take Action feature on the Tivoli Enterprise Portal. In the OMEGAMON enhanced 3270 user interface, these commands are available in action menus. Security for OMEGAMON XE for Mainframe Networks Take Action commands is based on SAF security classes and resource profile names. During product configuration you specify the name of the SAF security class that is used to validate product specific take action commands. The SAF class that is used to validate take action commands is specified in the RTE_SECURITY_CLASS parameter in your PARMGEN parm deck. You can code the KN3_SECURITY_ACTION_CLASS parameter optionally if you want to have a separate 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 the product-specific take action commands. If no resource profiles are created to control Take Action commands, all commands are denied. The OMEGAMON enhanced 3270 user interface validates the following resource profile to see if users are authorized to issue the Take Action commands directed at z/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 the global security class (RTE_SECURITY_CLASS) and give update access to the profile to all users you want to authorize to issue any Take Action commands from the enhanced 3270 user interface. The enhanced 3270 user interface address space uses SAF validation to determine whether a user is authorized to issue any Take Action commands. SAF validation for product specific commands is performed by the monitoring agent. Create other profiles for more granular access control. For example, to control all OMEGAMON XE for Mainframe Networks 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 Networks monitoring agent that is running on a system with an SMFID of TSTA and stack TCPIP, you would define a profile named: KN3.TCPIP:TSTA.TAKEACTION.* To control access to individual commands, you must define at least one profile with the following format in either the global security class or the override security class (KN3_SECURITY_ACTION_CLASS): KN3.TCPIP:TSTA.TAKEACTION.commandname or KN3.**.TAKEACTION.commandname where commandname is one of the supported OMEGAMON XE for Mainframe Networks Take Action commands. To control access to the DROP command, create a profile in either the global security class or the override security class similar to the following: KN3.**.TAKEACTION.DROP Note: DROP commands also check the TCPIP.MVS.DROP profile of the OPERCMDS class in addition to any SAF checking done for the OMEGAMON for Mainframe Networks DROP command resource profile. 142 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

155 If a user attempts to issue a Take Action command without authorization, a series of messages similar to these messages here is written to the RKLVLOG: :27:37.68 KN3A907I: USER=USER3 CLASS=$KOBSEC RESOURCE=KN3.TCPIPG:SYS.TAKEACTION.PING :27:37.68 KN3A908I: RACROUTE VERIFY REG15= SAFPRRET= SAFPRREA= SAFPSFRC= SAFPSFRS= :27: :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 messages in 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 Networks resource 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 user interface" topic in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. For information on issuing Take Action commands from the enhanced 3270 user interface, see the IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User Interface User s Guide. Restricting access to the Mainframe Networks Command Log and Response workspace The OMEGAMON XE for Mainframe Networks monitoring agent has a unique workspace associated with prefixed Take Action commands: the Command and Response Log workspace. This enhanced 3270 workspace is similar to the Tivoli Enterprise Portal Command Log workspace. Commands in both workspaces are displayed in a last in, first out order. The Tivoli Enterprise Portal workspace displays the commands that are issued by the user ID that logged into Tivoli Enterprise Portal, unless the user is given UPDATE access to the KN3.**.TAKEACTION.ADMIN resource profile, in which case all commands and all responses issued by all users are displayed. A similar mechanism is available in the enhanced 3270 user interface workspace, an enhanced 3270-based Command and Response Log workspace, shown in Figure 33 on page 144. Chapter 8. Completing the configuration 143

156 Figure 33. Command and Response Log workspace (KN3CRTS) To control display of the commands and command output in the command log, create an ADMIN resource 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 and responses for that user and other users. If this resource is not defined and users or groups are not permitted or granted access to this resource, a user is only be allowed to see Take Action commands and responses issued by that user. Users with UPDATE access to KN3.**.TAKEACTION.ADMIN can see commands and command responses issued by all users. For information about setting up this command profile, see the 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 or TEP to an MfN agent instance is verified by checking for access to a SAF resource named in this pattern: KN3.<msn>.TAKEACTION 144 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

157 Where <msn> is a managed system name. A managed system name typically identifies a unique Tivoli Enterprise Monitoring Server agent instance. In this statement, TAKEACTION is a literal. Unless a matching SAF profile exists to control access to a given Take Action command, any request to transmit an action to the managed system name is denied. Typically you define a resource profile that restricts the access to all users (UACC(NONE)) and then PERMIT access to these resources for user IDs or groups. The following examples show resource definitions 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 the enhanced 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 as the 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 Action commands 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 Action commands 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 Action command on any system: Chapter 8. Completing the configuration 145

158 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 Action commands 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 these permissions have taken effect. SETROPTS GENERIC(security_class) REFRESH SETROPTS RACLIST(security_class) REFRESH SETROPTS 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 configuration Using PARMGEN or Configuration Tool Batch mode and other methods for deploying configurations throughout your environment are not part of this product information. The IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide includes scenarios that illustrate various methods for using the Configuration Tool to replicate a configuration of Tivoli Management Services components and monitoring agents across an enterprise. These scenarios assume that you are using system variables (IBM symbolics) and consistent naming 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 method v Scenario 2: Using common RKANPARU and RKANCMDU libraries v Scenario 3: Using batch mode to replicate a runtime environment to another LPAR v Scenario 4: Using batch auto-submit to replicate a runtime environment to another LPAR v Scenario 5: Using batch mode to replicate a runtime environment on the same LPAR v Scenario 6: Using interactive copy to replicate a runtime environment v Scenario 7: Copying configuration values from one instance to another of the Configuration Tool v 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 Management Services environment using PARMGEN. Scenarios are also available for PARMGEN in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference. These implementation scenarios include: v Scenario PGN01: Performing a pristine install of the monitoring server and two OMEGAMON agents v Scenario PGN02: Performing a pristine install using shared libraries v Scenario PGN03: Performing a pristine install of a high-availability hub monitoring server v Scenario PGN04: Cloning an existing environment but converting its hub monitoring server to a remote v Scenario PGN05: Upgrading an existing environment to the current release v Scenario PGN06: Cloning an existing environment to run on a different LPAR v Scenario PGN07: Upgrading an agent-only runtime environment to PARMGEN Phase 2 v Scenario PGN07A: Converting an environment from ICAT to PARMGEN 146 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

159 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 Services on z/os: Upgrade Guide supports the following upgrade scenarios: v Scenario A: Upgrading the z/os monitoring server only v Scenario B: Upgrading the z/os monitoring server and monitoring agents v Scenario C: Adding a monitoring agent and upgrading the z/os monitoring server v Scenario D: Upgrading monitoring agents in an existing runtime environment without a z/os monitoring server v Scenario E: Upgrading additional products in an upgraded environment Relink the runtime environments After all configuration is complete and you have loaded the runtime environment, you must relink the runtime 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 for Mainframe Networks RTE is loaded (as documented in Step 7: Loading the runtime libraries on page 123), a sample linkedit job named KN3LINK is created in &rhilev.&midlev&rtename.rkansamu. Edit and run this job when you run the monitoring agent on a different release of z/os from the SMP/E installed system. The linkedit job is reproduced in the following section. Read the comments in the job and update as directed. //KN3LINK JOB (ACCT), NAME,MSGCLASS=A,NOTIFY=ROOT //* ******************************************************************* //* LICENSED MATERIALS - PROPERTY OF IBM * //* 5698-A35 * //* (C) COPYRIGHT IBM CORPORATION 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 CEESTART SETCODE AC(1) SETSSI D4E3C500 NAME KN3ACTCS(R) /* Chapter 8. Completing the configuration 147

160 //* *********************************************************** //* 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 CEESTART SETCODE AC(1) SETSSI D4E3C500 NAME KN3ANMON(R) /* If you configured this monitoring agent using PARMGEN, this linkedit operation is an option on the Parameter Generator Workflow - Welcome panel. From this menu, select option 11. Submit to display the SUBMIT 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 Tivoli Management Services on z/os: Common Planning and Configuration Guide for more information about performing this task in PARMGEN. 148 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

161 Chapter 9. Verifying the configuration After you configure your products and complete the post-configuration tasks, you are ready to confirm that 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 Portal and the enhanced 3270 user interface Use this verification procedure if you configured both Tivoli Enterprise Portal and the enhanced 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 your monitoring agents. If you see error messages, see IBM Tivoli Monitoring: Messages. See also Support information on page 299. Procedure 1. 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 to start 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 the monitoring 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 task procedure 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 Networks monitoring agent. 4. Verify that the OMEGAMON XE for Mainframe Networks XE Monitoring Agent has started successfully. 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 for Mainframe 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 task procedure name) to start the Enhanced 3270 User Interface. S CANSTOM Copyright IBM Corp. 2006,

162 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 the Manage Tivoli Enterprise Monitoring Services window by selecting Start > All Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. Locate entries for and in the Managing 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 a password has been specified by your security administrator. c. Verify that the Tivoli Enterprise Portal starts and that the Enterprise Status window can be displayed. 8. Verify that the OMEGAMON XE for Mainframe Networks monitoring agent shows a status of ONLINE in the Managed Systems Status view of the Enterprise Status window. 9. Verify that the OMEGAMON XE for Mainframe Networks monitoring agent is configured correctly to 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 for Mainframe Networks monitoring agent are communicating successfully. f. Examine the information displayed in this workspace to ensure that it is consistent with how you configured 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 specified a file that could not be opened or did not specify a file at all. See Appendix E, Format of the SNMP configuration file, on page 289. v Does the SNA Collection Started attribute in the Agent Status table have a value of No? Ifyou configured this instance of the monitoring agent to collect VTAM environment and buffer pool data, the value should be Yes. If it is not, then there is a problem with the VTAM major node or the VTAM PMI exit. See Vary the VTAM major node active and copy it to your VTAMLST library on page 133. v Do the IP address, SNMP Agent Port, and SNMP Version columns in the TCP Collector Status table display correct information for the TCP/IP stacks you want to monitor? If not, you may have a problem with the information specified in the TCP Collector SNMP Parameter Dataset identified in the Agent Status table. See Appendix E, Format of the SNMP configuration file, on page 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. 150 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

163 11. Select the OSA subnode and verify that data is being displayed. If no data is being displayed and the value for the OSA Statistics Collection attribute in the Agent Status workspace is "Yes," ensure that the OSA-Express Direct SNMP subagent (IOBSNMP) started task is running. See Starting the OSA 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 for detailed information about performing this validation. Results For more information about using the OMEGAMON XE for Mainframe Networks data displayed in the Tivoli Enterprise Portal, see Tivoli OMEGAMON XE for Mainframe Networks: Tivoli Enterprise Portal User's Guide. For more information about using the Enhanced 3270 User Interface, see the IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User s Guide and the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Enhanced 3270 User Interface Guide. Verifying configuration if you configured only the enhanced 3270 user interface Use this verification procedure if did not configure Tivoli Enterprise Portal, but configured only the enhanced 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 your monitoring agents. If you see error messages, see IBM Tivoli Monitoring: Messages. See also Support information on page 299. Procedure 1. 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 to start 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 the monitoring 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 task procedure 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 Networks monitoring agent. 4. Verify that the OMEGAMON XE for Mainframe Networks XE Monitoring Agent has started successfully. 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

164 You should also see the following message displayed in the RKLVLOG for the OMEGAMON XE for Mainframe 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 task procedure 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 the configuration, on page 127, especially those tasks under Enable security on page 140. The first screen 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. Each agent 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 they match the system ID of the system on which you configured the OMEGAMON XE for Mainframe Networks monitoring agent and the TCPIP STC entries for the TCP/IP stacks that the OMEGAMON 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 connected to 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 and x.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 in Chapter 3, Preparing your z/os environment, on page 59. See the RKLVLOG for more information. e. Type NETMENU on the command line and press Enter. The Enterprise Networks Workspaces pop-up window is displayed. f. Type M on the command line and press Enter to display the Enterprise Memory and CSM Storage Overview workspace. Validate that you seen information about memory and CSM storage. Validate that the values for the System ID and TCPIP STC Name are correct, that is, that they match the system ID of the system on which you configured the OMEGAMON XE for Mainframe Networks monitoring agent and the TCPIP STC entries for the TCP/IP stacks that the OMEGAMON XE for Mainframe Networks monitoring agent is configured to monitor. 152 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

165 If these values are incorrect, ensure that you performed the system setup tasks described in Chapter 3, Preparing your z/os environment, on page 59. See the RKLVLOG for more information. g. Type NETMENU on the command line and press Enter. The Enterprise Networks Workspaces pop-up window is displayed. h. Type B on the command line and press Enter to display the Enterprise OSA Express Channels Overview 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 on which you configured the OMEGAMON XE for Mainframe Networks monitoring agent. Validate that the channel numbers displayed on this workspace reflect the correct OSA-Express devices connected to this system. If you see no data, verify that the z/os TCP/IP SNMP Subagent (OSNMPD by default) and the OSA Express subagent (IOBSNMP or IOASNMP by default) are started on the TCP/IP stacks that are connected to OSA-Express devices. Ensure that you performed the OSA setup task described in Chapter 3, Preparing your z/os environment, on page 59. See the RKLVLOG for additional information. Note: You can easily determine if the monitoring agent is online using the KOBMSNS Only Managed Systems workspace to determine if the OMEGAMON XE for Mainframe Networks monitoring agent is currently registered with the hub monitoring server. When the OMEGAMON XE for Mainframe Networks agent address space is active but shows the MS Online Status value as N (meaning it is offline), this usually means that a configuration error is preventing the monitoring services components from communicating with each other. It might also be that the OMEGAMON XE for Mainframe Networks agent address space had experienced an abend. More details about using this workspace and other troubleshooting scenarios are found in the IBM Tivoli OMEGAMON XE for Mainframe Networks: Troubleshooting Guide. Results For more information about using the Enhanced 3270 User Interface, see the IBM Tivoli OMEGAMON XE for Mainframe Networks: Enhanced 3270 User s Guide and the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Enhanced 3270 User Interface Guide. Chapter 9. Verifying the configuration 153

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

167 Appendix A. Configuring the OMEGAMON II for Mainframe Networks component The OMEGAMON II for Mainframe Networks component provides a 3270 interface to VTAM performance data. This appendix provides the information about the components of OMEGAMON II for Mainframe Networks and the tasks for configuring this component. This appendix assumes that you have already installed the FMID for OMEGAMON XE for Mainframe Networks, which includes the OMEGAMON II for 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 you configure Before you begin configuration of OMEGAMON II for Mainframe Networks, understand these components and the function that each performs. Table 35 lists the characteristics of OMEGAMON II and the components available when you configure OMEGAMON II for Mainframe Networks, provides a brief description of each, and indicates the impact this characteristic or component has on configuration. Table 35. Product components for OMEGAMON II for Mainframe Networks. Product components for OMEGAMON II for Mainframe Networks Component Description Modes of Function: Specifies whether VTAM needs to be available to OMEGAMON II. operations for 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 terminal without an intermediate online application, such as TSO. You can set automatic update mode so that the screen refreshes automatically. VTAM mode allows all VTAM terminal users to share 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 every few seconds. Dedicated mode allows OMEGAMON II to provide real-time data even when VTAM is not available. Configuring this characteristic: During configuration, you will be asked to select and customize an operating mode. v v If you specify VTAM mode, copy the VTAM major node definition created during the Configuration Tool installation. If you specify Dedicated mode, you will require the availability of a locally attached non-sna terminal. For more information about setting up dedicated mode, see Running in dedicated mode on page 194. Copyright IBM Corp. 2006,

168 Table 35. Product components for OMEGAMON II for Mainframe Networks (continued). Product components for OMEGAMON II for Mainframe Networks Component Description Security Function: Enables OMEGAMON II to run in a secure environment configuration and optional NAM and OMEGAMON II supports the following security interfaces: TABLE database v The TMS: Engine Network Access Manager (NAM) interface. migrations 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 up security, 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 II by migrating your existing NAM and Table database data sets to the current release. If you elect to do so, specify the existing data set name on the Configuration Tool panel. VSAM log file record size The NAM database contains user preferences and user IDs and passwords (optional). The Table database 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. For more information about running the migration utility, see Step 4: Run migration utility on page 169. Function: Determines if the default log size is adequate The log (trend/exception) file contains trend and exception records for display. The default for maximum trend/exception record size is the allowable VSAM maximum. This record size is declared as variable. Ensure that you monitor the usage and free space of your log file carefully, as you monitor any VSAM application file. For information about monitoring the log file, see the OMEGAMON II for Mainframe Networks User's Guide. 156 IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide

169 Table 35. Product components for OMEGAMON II for Mainframe Networks (continued). Product components for OMEGAMON II for Mainframe Networks Component Description TCP/IP data collector (optional) Function: Provides TCP/IP performance measurements An OMEGAMON II for Mainframe Networks address space contains a TCP/IP performance data collector that monitors and collects the performance data for mainframe TCP/IP address spaces and the network resources and applications controlled by these address spaces. For each address 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 use to display TCP/IP data. You can use the TCP/IP console to execute TCP/IP and z/os commands. You can also use the SNMP browser facility to display any data collected in the TCP/IP MIBs. Configuring this component: During the configuration process, you will be asked to specify values for the TCP/IP component. If you do not want to collect TCP/IP performance data, you can specify N (No). The default is No. Note that the TCP/IP data collected with through OMEGAMON II for Mainframe Networks is a small subset of the data collection by OMEGAMON XE for Mainframe Networks. Use OMEGAMON XE to collect TCP/IP data. End-to-End Response Time (optional) For information about configuring the TCP/IP data collector, see Configuring the OMEGAMON II TCP/IP component on page 175. Function: Provides OMEGAMON II for Mainframe Networks with response time data and is required 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 the component to monitor the response time of SNA terminals connected to applications on the host. You can also specify that OMEGAMON II for Mainframe Networks will not use ETE services. 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 the terminal (end-to-end response time) v The time the user request and the application response spend in VTAM and in the application (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 to specify 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

170 Table 35. Product components for OMEGAMON II for Mainframe Networks (continued). Product components for OMEGAMON II for Mainframe Networks Component Description NCP performance data 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 data collector that can connect to and request data from, the NPALUs in your NCPs. An OMEGAMON 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 shown in Figure 34: Figure 34. NCP Collector within the OMEGAMON II address space If you plan to use only one OMEGAMON II address space, and you want to collect NCP performance statistics, specify LOCAL NCP data collection to the Configuration Tool. OMEGAMON II will obtain NCP performance statistics from the LOCAL collector in the OMEGAMON II address space you are configuring. v From the collector in another OMEGAMON II address space (a REMOTE collector), as shown in the diagram that follows: Figure 35. NCP Collector in another OMEGAMON II address space If you plan to use multiple OMEGAMON II address spaces, you can use the Configuration Tool to configure the address spaces so that performance data from all NCPs is available to all the address spaces. To do so, use the Configuration Tool to configure one OMEGAMON II as LOCAL and the rest as REMOTEs. Connect all NPALUs to the LOCAL address space, and configure each of the REMOTE OMEGAMON IIs to obtain their NCP performance statistics from the address space that you configured as 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 to specify whether the OMEGAMON II you are configuring will obtain its NCP performance data using 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 can specify NONE. The default is LOCAL. For information about configuring the NCP data collector, see Customizing NCP on page IBM Tivoli OMEGAMON XE for Mainframe Networks: Planning and Configuration Guide