IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os Version Fix Pack1. Upgrade Guide SC

Transcription

1 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os Version Fix Pack1 Upgrade Guide SC

2

3 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os Version Fix Pack1 Upgrade Guide SC

4 Note Before using this information and the product it supports, read the information in Notices on page 83. This edition applies to version 5, release 1, modification 1 of the IBM Tivoli OMEGAMON XE products and to version 6, release 3, Fix Pack 1 of IBM Tivoli Management Services on z/os (product number 5698-A79) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2005, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Tables v Chapter 1. Overview Version requirements Tivoli Management Services on z/os Basic upgrade requirements Before you begin Completing the upgrade Products in a mixed environment Autonomous agent support Tivoli Management Services V6.3.x component interoperability New in the Tivoli Management Services V6.3.0 Fix Pack 1 release New in configuration software New in the enhanced 3270 user interface New in Tivoli Management Services New in the previous release (Tivoli Management Services V6.3.0) New in PARMGEN New in Tivoli Management Services New in the previous release New feature enablement using the PARMGEN method SOAP server for a remote monitoring server 29 Monitoring server self-describing agent support Monitoring server audit support Chapter 2. Upgrade paths Path A: Upgrading from Tivoli Management Services V6.2.x and OMEGAMON XE with self-describing agent feature enabled Path A1: Integrating self-describing OMEGAMON XE agents into an existing Tivoli Monitoring V6.2.3 FP1 (or later) environment Path B: Upgrading from Tivoli Management Services V6.2.x to OMEGAMON XE without self-describing agent capability Chapter 3. SMP/E installation Planning your installation Scenario A: Cloned SMP/E environment for a staged upgrade of existing runtime environments. 39 Installing into a cloned environment using JOBGEN Installing into a cloned environment SMP/E using the Configuration Tool method Scenario B: New SMP/E environment for a staged upgrade of new or existing runtime environments. 43 Installing into a new environment, configuring in PARMGEN Installing into a new environment, configuring in interactive mode Installing into a new environment, configuring in batch mode Scenario C: Existing SMP/E environment Installing into an existing environment with PARMGEN Installing into an existing environment using the Configuration Tool Chapter 4. PARMGEN upgrade scenarios Scenario A: Upgrading the z/os monitoring server only Scenario B: Upgrading the z/os monitoring server and monitoring agents Scenario C: Adding a monitoring agent and upgrading the z/os monitoring server Scenario D: Upgrading monitoring agents in an existing runtime environment without a z/os monitoring server Scenario E: Upgrading additional products in an upgraded environment Chapter 5. Interactive upgrade scenarios using the Configuration Tool. 51 Scenario A: Upgrading the z/os monitoring server only Step 1. Creating and submitting the upgrade batch job Step 2. (Optional) Reconfiguring the monitoring server Step 3. Reloading the runtime environment Step 4. Completing the configuration Migrating customized objects to a cloned runtime environment Restarting the monitoring server Scenario B: Upgrading the z/os monitoring server and monitoring agents Step 1. Creating and submitting the upgrade batch job Step 2. Reloading the runtime environment Step 3. Completing the configuration Scenario C: Adding a monitoring agent and upgrading the z/os monitoring server Step 1. Creating and submitting the upgrade batch job Step 2. Configuring the monitoring server (optional) and OMEGAMON XE components.. 64 Step 3. Reloading the runtime environment Step 4. Completing the configuration Scenario D: Upgrading monitoring agents in an existing runtime environment without a monitoring server Step 1. Upgrade the monitoring agents Step 2. If required, update the persistent data store maintenance procedure Copyright IBM Corp. 2005, 2013 iii

6 Step 3. Complete the configuration Chapter 6. Batch upgrade scenario using the Configuration Tool Sample upgrade environment Batch upgrade procedure Step 1. Clone and upgrade the installation environment Step 2. Create the CICATB batch mode job Step 3. Update runtime environments Step 4. Upgrade products and recreate the runtime environment IBM Tivoli Monitoring library Documentation for the base agents Other sources of documentation Support information Notices Trademarks Privacy policy considerations Index Documentation library Shared OMEGAMON XE publications iv IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

7 Tables 1. Current versions of OMEGAMON XE monitoring agents and minimum required level of Tivoli Management Services and common components Supported OMEGAMON XE 510 family features Support for staged upgrades with SDA Operation issues for the enhanced 3270 user interface during a staged upgrade New runtime libraries and started task DDNAMEs The tivoli enterprise monitoring server audit parameters for the PARMGEN configuration method Sample upgrade environment Batch upgrade product tag indicators Copyright IBM Corp. 2005, 2013 v

8 vi IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

9 Chapter 1. Overview Before upgrading the components of Tivoli Management Services and the OMEGAMON XE monitoring agent products, consider the basic requirements for an upgrade and the effects of a mixed-version environment on globalization and data presentation. You can find product-specific upgrade information in the following locations: v Publications in the IBM Tivoli Monitoring and OMEGAMON XE Information Center at (versions and earlier) and (versions and later). v Technotes for each product on the IBM Software Support website at support. The instructions in this document are based on the following assumptions: v You have already installed V4.1.0 or later of the OMEGAMON XE monitoring agents that you want to upgrade. v You are already at Tivoli Management Services v6.2.x or higher. v You are upgrading the Tivoli Management Services components to the V6.3.0 Fix Pack 1 or higher. If you are upgrading your monitoring agents but keeping your Tivoli Management Services components at the V6.2.3 Fix Pack 1 level, see the previous edition of the Upgrade Guide ( infocenter/tivihelp/v15r1/topic/com.ibm.omegamon_share.doc_623fp1_1/source/upgrade/ tmsz_upgrade.htm). You can use the ShopzSeries website to order mainframe products and maintenance (also known as program temporary fixes or PTFs). The primary product fulfillment mechanism is physical media, but electronic CBPDOs (Custom-Built Product Delivery Offerings) are available. Maintenance is available on physical tape or electronically on the ShopzSeries website. For information about ordering products and maintenance through the ShopzSeries website, see the Ordering Products and Maintenance Through Shop zseries Technote. You can find this Technote by selecting one of your OMEGAMON XE products on the Software Support website at and searching for shop zseries. Version requirements IBM Tivoli OMEGAMON XE monitoring agents require that IBM Tivoli Management Services and common components be at a certain minimum version. The minimum level required depends on the version of the monitoring agent that you are installing. A family is a group of products that have the same minimal FMID requirements. The OMEGAMON XE 510 product family comprises the following products: OMEGAMON XE for CICS on z/os V5.1.0 OMEGAMON XE for DB2 Performance Expert on z/os V5.2.0 OMEGAMON XE for DB2 Performance Monitor on z/os V5.2.0 OMEGAMON XE for IMS on z/os V5.1.0 OMEGAMON XE for Mainframe Networks V5.1.0 and V5.1.1 OMEGAMON XE for Messaging V7.1.0 OMEGAMON XE for Storage on z/os V5.2.0 Copyright IBM Corp. 2005,

10 OMEGAMON XE on z/os V5.1.0 and V5.1.1 OMEGAMON Dashboard Edition on z/os V5.1.0 All members of the 510 family require that Tivoli Management Services be at a minimum of version Fix Pack 1. However, version Fix Pack 3 is suggested. If you are installing application support for OMEGAMON XE for DB2 on Windows from the LCD (or later) DVD image, V6.2.3 Fix Pack 3 is required. If you are running JRE 1.7 or Java 7 (1.7), Tivoli Management ServicesV6.3.0 is required. If you upgrade to version 6.3.0, install Fix Pack 1. The required minimum version for common components are listed in Table 1. Table 1. Current versions of OMEGAMON XE monitoring agents and minimum required level of Tivoli Management Services and common components Current monitoring agent release OMEGAMON XE for CICS on z/os V5.1.0 OMEGAMON XE for DB2 Performance Expert on z/os V5.2.0 OMEGAMON XE for DB2 Performance Monitor on z/os V5.2.0 OMEGAMON XE for IMS on z/os V5.1.0 OMEGAMON XE for Mainframe Networks V5.1.0 and V5.1.1 OMEGAMON XE for Messaging V7.1.0 OMEGAMON XE for Storage on z/os V5.2.0 OMEGAMON XE on z/os V5.1.0 and V5.1.1 OMEGAMON Dashboard Edition on z/os V Interim Feature 1 is suggested. OMNIMON (Enhanced 3270UI - KOB) End-to-End (KET) Shared probes (KSB) V V6.2.0 n/a V7.0.0 Interim Feature 1 n/a n/a V7.0.0 Interim Feature 1 n/a n/a V V6.2.0 n/a V7.0.0 Interim Feature 1 V6.2.0 n/a V n/a n/a V7.0.0 Interim Feature 1 n/a V7.2.0 V7.0.0 Interim Feature 1 V6.2.0 V6.2.0 n/a n/a n/a Table 2 lists the OMEGAMON XE 510 family features supported by each product. Table 2. Supported OMEGAMON XE 510 family features Current Monitoring Agent Release Enhanced 3270 user interface Self-describing agents Configuration method OMEGAMON XE for CICS on z/os V5.1.0 Yes Yes PARMGEN preferred, ICAT optional OMEGAMON XE for DB2 Performance Expert on z/os Yes Yes PARMGEN only V5.2.0 OMEGAMON XE for DB2 Performance Monitor on Yes Yes PARMGEN only z/os V5.2.0 OMEGAMON XE for IMS on z/os V5.1.0 Yes Yes PARMGEN preferred, ICAT optional 2 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

11 Table 2. Supported OMEGAMON XE 510 family features (continued) Current Monitoring Agent Release OMEGAMON XE for Mainframe Networks V5.1.0 and V5.1.1 Enhanced 3270 user interface Self-describing agents Configuration method Yes Yes PARMGEN preferred, ICAT optional OMEGAMON XE for Messaging V7.1.0 Yes Yes PARMGEN preferred, ICAT optional OMEGAMON XE for Storage on z/os V5.2.0 Yes Yes PARMGEN preferred, ICAT optional OMEGAMON XE on z/os V5.1.0 and V5.1.1 Yes Yes PARMGEN preferred, ICAT optional OMEGAMON Dashboard Edition on z/os V5.1.0 No No PARMGEN preferred, ICAT optional Table 3 shows the support by agent for staged upgrades from GA-1 and GA-2 to the GA version using either self-describing agents or the application support DVD to install application support. Table 3. Support for staged upgrades with SDA Current Monitoring Agent Release GA-1 product version (no SDA configuration except for V5.1.1) OMEGAMON XE for CICS on z/os V OMEGAMON XE for DB2 Performance Expert on z/os V OMEGAMON XE for DB2 Performance Monitor on z/os V OMEGAMON XE for IMS on z/os V OMEGAMON XE for Mainframe Networks V5.1.0 and V OMEGAMON XE for Messaging V OMEGAMON XE for Storage on z/os V OMEGAMON XE on z/os V5.1.0 and V OMEGAMON Dashboard Edition on z/os V V4.1.0 is end-of-service as of September, GA-2 product version (no SDA configuration) 1 Tivoli Management Services on z/os All the OMEGAMON XE monitoring agents use a commonly shared technology called Tivoli Management Services on z/os. Tivoli Management Services comprises a set of components and services shared by monitoring agents in an agent-server-client architecture. Tivoli Management Services consists of the following components: Distributed Tivoli Enterprise Portal clients Tivoli Enterprise Portal Server Chapter 1. Overview 3

12 Tivoli Data Warehouse Warehouse Proxy Agent Summarization and Pruning Agent Event synchronization component Tivoli Enterprise Portal extended services (includes Apache Derby database) IBM DB2 database z/os Tivoli Management Services: Engine Installation and configuration software Distributed and z/os Tivoli Enterprise Monitoring Server If you order a Tivoli Serverpac for your upgrade, the latest level of Tivoli Management Services is automatically included, at the latest maintenance level. If you order CBPDOs instead of a Tivoli Serverpac, be sure to order the Tivoli Management Services package in addition to your agents if the currently installed version is earlier than V The minimum required version for the OMEGAMON XE 510 family is V6.2.3 Fix Pack 1. The suggested minimum requirement is version Fix Pack 3. Important: Tivoli Management Services V6.3.0 is required If you are using Java Runtime Environment (JRE) 1.7 or Java 7 (version 1.7). For complete information about the Tivoli Management Services components and instructions for installing them, see the publications in the IBM Tivoli Monitoring and OMEGAMON XE Information Center at Tip: The OMEGAMON XE product license agreement allows you to install the Tivoli Management Services components but does not include permission to install the IBM Tivoli Monitoring distributed operating system monitoring agents. If you want to use those monitoring agents, you must purchase the IBM Tivoli Monitoring product. For additional details, see the license agreements for the OMEGAMON XE products that you purchased. Basic upgrade requirements Before you begin to upgrade your OMEGAMON products, any Tivoli Enterprise Monitoring Server (hub, remote, backup, and Hot Standby) a monitoring agent reports to must be running at the prerequisite level. All products in a runtime environment must use the same configuration method. v PARMGEN is the preferred configuration method for the OMEGAMON XE V5.1.0 product family. However, for OMEGAMON XE for DB2 Performance Expert V5.2.0 and OMEGAMON XE for DB2 Performance Monitor V5.2.0 or higher, PARMGEN is the required configuration method. You can upgrade OMEGAMON XE for DB2 agents to V5.2.0 in a runtime environment (RTE) created using the Configuration Tool (ICAT) by using the Load option to run with upgraded modules, but you cannot configure the new version to take advantage of any new configuration features that require new runtime members or new parameters in existing members. You will be running with the runtime members for the previous version (toleration mode). You can continue to make configuration changes to any other products in the RTE that support ICAT mode (see Table 2 on page 2). If you want to exploit the new features and parameters, you must convert the runtime environment to PARMGEN and modify the LPAR configuration and the $GBL$USR profiles. Complete the configuration as you would any other PARMGEN configuration. See scenario PGN05 in the IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: PARMGEN Reference for instructions on converting a runtime environment to PARMGEN and upgrading a product. See the OMEGAMON XE for DB2 Performance Expert and Performance Monitor Planning and Configuration Guide for more information on new features that can be exploited and new post-configuration software steps. 4 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

13 v If you are upgrading to OMEGAMON XE for DB2 Performance Expert V5.2.0 or OMEGAMON XE for DB2 Performance Monitor V5.2.0 in an existing PARMGEN runtime environment, to enable support for DB2 V11, you must manually add the following two parameters to the &rte_plib_hilev. &rte_name.wconfig($gbl$usr) profile: GBL_DSN_DB2_LOADLIB_V11 GBL_DSN_DB2_RUNLIB_V11 (If you are converting the runtime environment from ICAT, these two parameters are added automatically when you upgrade the agents.) v OMEGAMON XE for CICS TG on zos V4.2.0 and V4.1.0 can be upgraded only by upgrading to OMEGAMON XE for CICS on z/os V Starting with V4.2.0, CICS TG can no longer be ordered as a separate product. It is included in the OMEGAMON XE for CICS on z/os product package. v 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. Note that there is no change in the HKN3510 FMID between V5.1.0 and V v You can upgrade from OMEGAMON XE on z/os V5.1.0 by installing the PTFs and fix packs that are associated with IBM APARs OA42127 and OA42128, or you can upgrade from V4.1.0 or later by ordering and installing OMEGAMON XE on z/os V5.1.1 PID: 5698-T01. There is no change in the HKM5510 FMID between V5.1.0 and V Tip: You can run more than one version of an OMEGAMON XE monitoring agent on the same z/os system, provided that the different versions of the monitoring agent report to different monitoring servers or have different started task names. Note: Distributed fix packs are available through the IBM Support Fix Central at ( support/fixcentral/). You need an IBM registered ID to download fixes from this site and to enable IBM to update you about critical issues that are associated with fixes that you download. z/os fixes continue to be available through IBMLINK or Shop zseries. Before you begin You can eliminate roadblocks and ensure a smoother upgrade if you make sure that all requirements are met before you begin. In addition to reviewing the Preinstallation Requirements and Instructions Technote ( you should address the following requirements. Tivoli Management Services components Before you upgrade an OMEGAMON XE monitoring agent, determine the current release levels of the Tivoli Management Services components. To determine the required level, see Version requirements on page 1. To determine the current level of components on z/os, compare the FMIDs associated with the following components to the FMIDs listed in the product program directory and the FMIDs listed in the SMP/E CSI whose agents you intend to upgrade. This information will help you determine which components must be updated. v Tivoli Enterprise Monitoring Server (FMID HKDS623 or HKDS630) v z/os configuration tools (Parameter Generator (PARMGEN) Workflow user interface and Configuration Tool (ICAT)) (FMID HKCI310) v Tivoli Management Services:Engine (TMS:Engine) (FMID HKLV623 or HKLV630) v OMNIMON Base (including framework support for OMEGAMON enhanced 3270 user interface and OMEGAMON Subsystem) (FMID HKOB700) To find the current release levels of the components running on distributed systems, issue one of the following commands: v On Windows Chapter 1. Overview 5

14 \ibm\itm\kincinfo -i v On Linux or UNIX: opt/ibm/itm/bin/cinfo -i Self-describing agent feature (SDA) If you are running a Tivoli Enterprise Monitoring Server on z/os and you are planning to enable SDA, v Create HFS or zfs directories on z/os UNIX System Services. You will need to provide the path to this directory during configuration. The directories must be large enough to support all the jar files delivered by the z/os agents: Hub monitoring server ~ 3.25 MB per agent Remote monitoring server ~ 2MBperagent v The UNIX System Services system where you create these directories must have access to a Java Runtime Environment running under IBM's 31-bit or 64-bit Java SDK Version 5 (or later) and an HFS or zfs file system. v Ensure proper authorization has been set for the person who will run the jobs that add the subdirectories for the application support files. See IBM OMEGAMON Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Configuring the Tivoli Enterprise Monitoring Server on z/os for more details on these requirements. For more information on enabling the self-describing agent capability, see the IBM Tivoli Monitoring: Administrator's Guide and the IBM OMEGAMON Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Common Planning and Configuration Guide. OMEGAMON enhanced 3270 user interface If you will be configuring the OMEGAMON enhanced 3270 user interface, define an OMVS segment for the started task (CANSTOM by default). Note: 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). One solution is the use of RACF support to automatically generate unique UIDs and GIDs on demand for users and groups that do not have OMVS segments defined. Support for automatic unique UID and GID generation has been available since z/os V1R11. SDA and enhanced 3270 user interface If you are upgrading to either IBM Tivoli Monitoring V6.2.3 or higher or OMEGAMON XE V5.1.0 or higher and the SDA feature or the enhanced 3270 user interface functions will be exploited, reallocate the existing RKANDATV library of existing runtime environments as a PDSE. This change accommodates product features that allow the product started tasks to dynamically create or write multiple members into RKANDATV at product startup, and to ensure that the started tasks are allowed to write into RKANDATV. High-availability hub monitoring server If you will be configuring a high-availability (HA) hub monitoring server, set up a dedicated dynamic virtual IP address (DVIPA). Allow enough time to reconfigure existing static hub to a remote and reconfigure all remotes to connect to the HA hub. Integrated Cryptographic Security Facility If any of the following conditions are in effect, the Integrated Cryptographic Security Facility started task must be running: v Components will use password encryption. v The SOAP server will be enabled on a remote monitoring server v Granular control of command requests will be enabled (KMS_SECURITY_COMPATIBILITY_MODE=N) v The zaware feature will be configured for OMEGAMON XE on z/os. 6 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

15 System variables If the runtime environment is enabled for system variables, started tasks generate a required symbolic substitution step that allocates temporary data sets to perform the variables resolution processing. If you are enabling variables, ensure that enough space is allocated to your temporary space volume to accommodate the TMP* DD processing. Some or all OMEGAMON XE monitoring products also require the following additional components, which might be upgraded with this installation: v End-to-End Response Time collector v OMNIMON Base (which includes the OMEGAMON enhanced 3270 user interface and the OMEGAMON Subsystem) v Shared probes See the program directory for the products and components you are installing or upgrading for product-specific requirements. To obtain the latest information about maintenance that has become available since the products shipped, see the Recommended Maintenance Service Levels for OMEGAMON XE products on ITM V6.x Technote: docview.wss?uid=swg Best practice: Always compare $CFG$IBM to your LPAR profile and $GBL$IBM to $GBL$USR in WCONFIG library after running the KCIJPUP1 job to see what updates have been made. Completing the upgrade After you have completed the configuration steps for the appropriate upgrade scenario, there are additional steps you may need to complete. OMEGAMON enhanced 3270 user interface If you are enabling the enhanced 3270 user interface for the first time, the following steps must be completed: 1. Define the new started task user IDs to your STC table. The default name is CANSTOM. 2. Define the new VTAM APPLID for the enhanced user interface. The default name is CTDOBAP. 3. APF-authorize &rte_hilev.&rte_name.rkanmodp library, as this load library is included in the STEPLIB DDNAME of all started tasks. 4. Customize the KOB* parameters as desired. 5. Add the new address space to the system PROCLIB and add its VTAM major node to the system VTAMLST. If you are using a global VTAM major node, refresh the global VTAM major node with the user interface's VTAM LOGON APPLID. In PARMGEN, the KCIJPSYS job is available to perform these steps. In ICAT, copying the STC from RKANSAMU to system procedure library and system VTAMLST library is a post-configuration step. In a PARMGEN upgrade, steps 1-3 are done automatically (and step 5 if the KCIJPSYS job is run). In a Configuration Tool upgrade, these steps must be performed manually. Self describing agent feature (SDA) enabled at the hub monitoring server If you are enabling the self describing agent feature (SDA), refresh the started tasks in the system PROCLIB. At V6.2.3 a new VSAM library was introduced that is required for SDA exploitation. The upgrade process will ensure that the z/os monitoring server started task is regenerated with a new QA1DAPPL DDNAME that points to the new VSAM library (&rvhilev.&rte.rkdsappl). This change requires started task changes in the system PROCLIB. In a PARMGEN upgrade, the Chapter 1. Overview 7

16 started task is automatically copied to the PROCLIB if you choose to use the WKANSAMU(KCIJPSYS) system setup job. In a Configuration Tool upgrade, the new started task must be copied to the PROCLIB manually. MINIMUM() and LIMIT() settings A number of OMEGAMON XE agents have increased their configuration defaults for TMS:Engine storage-type settings (MINIMUM(), LIMIT()) in support of new agent functions or SDA enablement support. The previous values are preserved during upgrade. To avoid potential TMS:Engine quiesce ABEND in the monitoring server and agent started tasks after the upgrade, adjust the values for these parameters. To take advantage of the new values, refresh the KCIJPCFG job: 1. From the PARMGEN Workflow main menu, select option 1 (Set up PARMGEN work environment for an RTE). 2. Step through the KCIP@PGn panels. 3. On the KCIP@PG5 panel, if you are not changing the product mix, exclude all products not already configured in the runtime environment, then confirm the selection. The KCIP@BAK (Refresh the LPAR RTE User And IBM Profiles" panel is presented. 4. On the KCIP@BAK panel, specify a backup name for the profile member name, then press Enter to regenerate the KCIJPCFG job. 5. Resubmit the KCIJPCFG job. The KCIJPCFG job submits the KCIJPPRF profile refresh job, which creates a new profile with new values, then merges the values from the backed up profile. Verify that both jobs completed successfully. Note that if APAR OA41710 has been installed, the higher value is automatically used. For a Configuration Tool upgrade, determine the new values from the agent's Planning and Configuration Guide, then: v For MINIMUM (): Adjust the values accordingly on the Agent s Specify Advanced Agent Configuration Values panel. Recreate the pp#3xxxx (Create runtime members) job for each agent. v For LIMIT(): If there are slots remaining in the agent s Specify Nonstandard Parameters panels, use this facility to adjust the storage settings. Otherwise, manually edit the LIMIT() parameter in the RKANPARU(KppSYSIN). Repeat for each agent affected. After you have completed configuration, run the appropriate load job and recycle started tasks in the upgraded runtime environment. Products in a mixed environment Support for multiple versions of an agent that run in the same environment is provided to support a staged upgrade. However, you should be aware of certain issues while you are working with a mixed environment. Note: OMEGAMON XE monitoring agents at V3.1.0 are not supported in a mixed environment with OMEGAMON XE monitoring agents at V5.1.0 and later, nor are upgrades from V3.1.0 to V5.1.0 supported. See the IBM support lifecycle page ( support/lifecycle/) for a list of supported products. 8 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

17 Tivoli Enterprise Portal user interface Product information in the Tivoli Enterprise Portal reflects the level of support for applications that are installed on the portal server, not the version of the monitoring agent. After you install support on the portal for V4.2.0 or V5.1.0 monitoring agents, you will see accurate workspace and attribute information for the monitoring agent. However, for V4.1 monitoring agents, you might see potentially misleading information in flyovers, full-text help, and information that is provided in the situation editor. You can use the predefined dynamic workspace links provided by V4.2.0 and V5.1.0 agents to link from an OMEGAMON XE V4.2.0 or V5.1.0 workspace to the workspace of another OMEGAMON XE V4.1.0 product if the target workspace exists in the V4.1.0 product. If the target workspace does not exist, you receive the KFWITM081E message. In cases where the V4.1.0 (or later) target workspace has been modified (for example, to accept link parameters to limit the data that is displayed) you might notice different behavior when you upgrade the target product from V4.1.0 to V4.2.0 or V To view data in two new Managed System Status workspaces (Historical Export Statistics and Audit Log), the selected managed system must have at a minimum an IBM Tivoli Monitoring framework. For example, to view the workspace data for a monitoring server, the monitoring server must be an IBM Tivoli Monitoring V6.3.0 monitoring server. To view the workspace data for a monitoring agent, the agent framework that is used by the agent must be IBM Tivoli Monitoring V (If collection is set to store at the agent, the collection is displayed in the Historical Export Statistics workspace for the monitoring agent. If the collection location is set to store at the monitoring server, the collection is displayed in the Historical Export Statistics workspace for the monitoring server to which the agent reports. OMEGAMON enhanced 3270 user interface The current release of the enhanced 3270 user interface does not support SDA processing. If the enhanced 3270 user interface is configured in the same runtime environment as the hub address space and you plan to upgrade with an OMEGAMON agent that is not configured in this same runtime environment, you must run the configuration load processing for both the runtime environment that contains the agent and the runtime environment that contains both the interface and the hub monitoring server and recycle the interface address space. The OMEGAMON enhanced 3270 user interface does not support releases of OMEGAMON XE earlier than V5.1. Although some of the OMEGAMON XE V4.2 and V4.1 agents return data that is viewable in the new 3270 user interface, only the displayed data that is returned by the OMEGAMON XE V5.1 monitoring agents is supported. Users of the enhanced 3270 user interface can experience operational limitations when they are running configurations that run multiple versions of OMEGAMON agents during a staged upgrade period. Table 4 summarizes related operational considerations by product. For more information about limitations, consult the product configuration and upgrade documentation. Table 4. Operation issues for the enhanced 3270 user interface during a staged upgrade Product version that provides enhanced 3270 interface support OMEGAMON XE for CICS on z/os V5.1.0 Operational considerations with multiple agent versions running Only data that is returned from the V5.1.0 OMEGAMON XE for CICS agents is displayed in the enhanced 3270 user interface. Data that is returned from the V4.2.0 and V4.1.0 agents can be viewed from one of the other available interfaces: Tivoli Enterprise Portal, OMEGAMON for CICS, or OMEGAMON II for CICS. Chapter 1. Overview 9

18 Table 4. Operation issues for the enhanced 3270 user interface during a staged upgrade (continued) Product version that provides enhanced 3270 interface support OMEGAMON XE for DB2 Performance Expert on z/os V5.1.1 and V5.2.0 OMEGAMON XE for DB2 Performance Monitor on z/os V5.1.1 and V5.2.0 OMEGAMON XE for IMS on z/os V5.1.0 OMEGAMON XE for Mainframe Networks V5.1.0 and V5.1.1 OMEGAMON XE for Messaging on z/os V7.1.0 OMEGAMON XE for Storage on z/os V5.1.0 and V5.2.0 OMEGAMON XE on z/os V5.1.0 and V5.1.1 Operational considerations with multiple agent versions running Only data that is returned from the V5.1.1 and V5.2.0 OMEGAMON DB2 agents is displayed in the enhanced 3270 user interface. Data that is returned from V5.1.0 and V4.2.0 agents can be viewed from one of the other available interfaces. If both V5.1.0 and V4.2.0 agents report data through the enhanced 3270 user interface, PTF UA66653 must be installed on the interface. Without this PTF, several workspaces for IMS systems still being monitored by V4.2.0 agents display No Data because column names are not found. Even with PTF UA66653 applied, there are some limitations with displaying data from IMS systems being monitored by V4.2.0 agents. Refer to the technote at the following link for the most up-to-date information about using the enhanced 3270 user interface with pre-v5.1.0 agents: docview.wss?uid=swg The enhanced 3270 user interface for OMEGAMON XE for Mainframe Networks is designed for V5.1.0 and later monitoring agents. Some workspaces display data from previous release agents, but some attributes and tables are provided only by V5.1.0 and V5.1.1 agents. Continue to use the Tivoli Enterprise Portal to view data from V4.2.0 and V4.1.0 agents. The enhanced 3270 user interface for WebSphere MQ monitoring is designed for V7.1.0 and later monitoring agents. The WebSphere MQ Health Overview will not contain Queue Manager Status rows for queue managers that are monitored by previous release agents. Some workspaces function with previous release agents, but you will not be able to navigate to them using health overview options for queue managers. Use the Tivoli Enterprise Portal interface or the old 3270 interface to view data that is produced by previous release agents. The enhanced 3270 user interface displays only data from V5.1.0 and V5.2.0 Storage agents. Data from prior versions is ignored in the interface. The product must be configured so that only V5.1.0 or V5.1.1 agents are eligible to assume the sysplex proxy role. Otherwise, sysplex data is not available in the enhanced 3270 user interface until all OMEGAMON XE on z/os monitoring agents are upgraded to version Incompatibility of V4.1.0 and V4.2.0 agents and native 64-bit monitoring servers Tivoli Management Services on z/os V6.3.0 supports monitoring servers on native 64-bit Windows and xlinux systems. The IBM Tivoli OMEGAMON V5.1.0 (or higher) family (including OMEGAMON XE for DB2 PE/PM V5.1.1 and OMEGAMON XE for Messaging V7.1.0) supports the native 64-bit monitoring server. The OMEGAMON V4.2.0 family (including OMEGAMON XE for DB2 PE/PM V5.1.0 and OMEGAMON XE for Messaging V7.0.1) supports only monitoring servers that run on 64-bit Windows and 64-bit Linux platforms that use 32-bit compatibility mode with IBM Tivoli Monitoring V IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

19 If you are installing or upgrading a hub monitoring server on native 64-bit Windows and xlinux systems, the metaprobes that collect plex data for the following V4.20 family products are disabled until the products are upgraded to the V5.1.0 family versions: v OMEGAMON XE for IMS on z/os, V4.1.0, v OMEGAMON XE for DB2 Performance Expert, V4.1.0, V4.2.0, V5.1.0 v OMEGAMON XE for DB2 Performance Monitoring, V4.1.0, V4.2.0, V5.1.0 v OMEGAMON XE on z/os, V4.1.0, V4.2.0 v OMEGAMON XE for Messaging on z/os V6.0.x and V7.0.x Globalization of interfaces User interfaces for OMEGAMON XE V4.2.0 and later monitoring agents are globalized, with the following exceptions: v z/os configuration tools (Parameter Generator (PARMGEN) Workflow user interface and Configuration Tool (ICAT)) v Installation program v OMEGAMON enhanced 3270 user interface v OMEGAMON II (CUA) interface v OMEGAMON (3270) interface OMEGAMON XE V4.1.0 (or later) workspaces in the Tivoli Enterprise Portal are displayed in the specified language (for example, Spanish or Chinese). Autonomous agent support Tivoli Management Services V6.2.3 (and higher) allows stand-alone monitoring agents (those that are configured in their own address spaces) to run in autonomous mode (without communicating directly with a monitoring server). An autonomous agent can emit Simple Network Management Protocol (SNMP) traps and Event Integration Facility (EIF) events directly to an event server for agent-specific situations (but not for enterprise situations). Autonomous agents can be advantageous in environments where disk space or transmission bandwidth is in short supply. An autonomous agent requires the DSEVT DDNAME in the monitoring agent started task in rhilev.rte.rkansamu. This DDNAME points to the rvhilev.rte.rkdsevt data set. The IBM Tivoli Monitoring: Installation and Setup Guide provides instructions for configuring IBM Tivoli 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 detailed information about managing autonomous agents, see Agent autonomy in the IBM Tivoli Monitoring: Administrator's Guide. Tivoli Management Services V6.3.x component interoperability The following statements specify the level of interoperability for IBM Tivoli Monitoring V6.3.x in support of existing agents and staged upgrade scenarios. Tivoli Enterprise Monitoring Server v If your site uses IP.SPIPE for Tivoli Enterprise Monitoring Server communication: A V6.2 or V6.2.1 remote monitoring server can connect to a V6.2.2 or V6.2.3 or later hub not running in FIPS mode. Connectivity will default to the Triple DES standard. To enable AES encryption, set parameter GSK_V3_CIPHER_SPECS="352F0A" on the remote monitoring systems. Chapter 1. Overview 11

20 Agents using pre-v6.2.2 monitoring agent framework can select IP.SPIPE to connect to a V6.2.2 or V6.2.3 or later monitoring server defined with FIPS=N. Agents using pre-v6.2.2 monitoring agent framework cannot select IP.SPIPE to connect to a V6.2.2 or V6.2.3 or later monitoring server defined with FIPS=Y. Agents using V6.2.2 or later monitoring agent framework defined with either FIPS=N or FIPS=Y can select IP.SPIPE to connect to a V6.2.2 or later monitoring server defined with either FIPS=N or FIPS=Y. v A V6.2, V6.2.1, V6.2.2 or V6.2.3 or later remote monitoring server can connect to a V6.2, V6.2.1, V6.2.2 or V6.2.3 or later hub monitoring server. v If you are running a hub monitoring server at release 6.2 or earlier, the tacmd CLI commands for situation groups, situation long names, and adaptive monitoring cannot be used. v If you are running a monitoring server at release Fix Pack 1 or earlier, you cannot use the tacmd CLI commands, getfile, putfile, and executecommand. v If you are running a monitoring server at a release prior to V6.2.3, you cannot use the tacmd CLI commands for prerequisite information and tacmd setagentconnection. v If you are running a hub monitoring server at a release prior to V6.2.3, you cannot use the self-describing agent function and associated tacmd CLI commands. If you are running a remote monitoring server at a release prior to V6.2.3, the agents connected to that monitoring server cannot be self-describing. Tivoli Enterprise Portal Server v A V6.3.0 Tivoli Enterprise Portal Server can interoperate with an older hub monitoring server at any supported level. If any monitoring agents use features introduced in V6.2.1 or later (for example, dynamic affinities and 64-bit integer data support), all Tivoli Management Services components must be upgraded to at least V For details, see the documentation for your monitoring agents. v A Tivoli Enterprise Portal Server upgrade to a new platform is accomplished with database export and import. For information about migrating the database, see the description of the migrate-export and migrate-import scripts in the IBM Tivoli Monitoring: Administrator's Guide. v To upgrade from a prior portal server to the current version, your temporary directory must have sufficient space to accommodate the download of the ewas server code and the Eclipse server code. See the memory and disk space requirements for V6.3.0 documented in the IBM Tivoli Monitoring: Installation and Setup Guide. Tivoli Data Warehouse v All Warehouse Proxy and Summarization and Pruning agents must be at the same level and must be at the same level as the Tivoli Enterprise Portal Server to avoid inconsistencies in presentation. v Upgrade the Warehouse Proxy and Summarization and Pruning agents to be at the same release level as the most recent agent monitoring framework release level used by your agents. For example, if you intend to use IBM Tivoli Monitoring V6.3.0 operating system agents, then upgrade the Warehouse Proxy and Summarization and Pruning agents to V6.3.0 as well; this ensures the warehouse agents support all of the history collection functions used by your agents: The V6.2.1 or later Warehouse Proxy agent and Summarization and Pruning agent are required for correct functioning of any agent requiring 64-bit integer data support. The V6.2.2 or later Warehouse Proxy agent and Summarization and Pruning agent are required if you configure granular history collection for any of your agents using the V6.2.2 or later agent monitoring framework. The V or later Warehouse Proxy agent and Summarization and Pruning agent are required if you configure historical data compression before upload to the warehouse database for any of your agents using V6.2.3 or later agent monitoring framework. 12 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide

21 Tivoli Event Synchronization component If you have already installed a previous version of Tivoli Event Synchronization, you must upgrade to V The upgrade is required for the event server to parse events coming from the V6.2.x or later hub monitoring server. For additional information, see the IBM Tivoli Monitoring: Installation and Setup Guide. New in the Tivoli Management Services V6.3.0 Fix Pack 1 release Changes to the shared framework or the configuration software that supports it (FMID HKCI310) can affect upgrade. In addition, you might need to reconfigure your runtime environments to take advantage of new features. If you are upgrading your environment to V6.3.0 Fix Pack 1, review these changes. New in configuration software APAR OA41710 (PTF UA69076) for FMID HKCI310 brings changes to the PARMGEN Workflow interface and introduces new and modifed parameters, embed files, and batch jobs. These enhancements affect all products. For product-specific enhancements, see the Planning and Configuration Guide for each product. Note that APAR OA41710 applies to all product versions. You do not have to upgrade to V6.3.0 FP1 on z/os to take advantage of these features. Workflow user interface changes Two parameters that were previously available only in the LPAR profile have been added to the third "Set up PARMGEN Work Environment for an RTE panel" (KCIP@PG3): v RTE_LOAD_SHARED_LIBS This parameter controls whether or not the base libraries for a sharing-with-base RTE are loaded in the WKANSAMU(KCIJPLOD) load job. Best practice: If you have multiple runtime environments sharing the same base libraries, to avoid loading the base libraries multiple times designate one environment as the master by leaving its flag set to Y, and disable loading of base libraries in all the other RTEs. v RTE_TCP_PORT_NUM IP-related port number used for monitoring server and agent connections New PARMGEN LPAR profile parameters To support the requirement that encrypted tokens be issued with command requests (such as Take Action commands), support for Integrated Cryptographic Service Facility (ICSF) encryption has been extended to agent-only runtime environments. Now the ICSF load library can be concatenated in the started task of stand-alone agents, as well as monitoring servers, and stand-alone agents can also customize the password encryption key. RTE_SECURITY_KAES256_KEY This parameter allows stand-alone agents as well as monitoring servers to customize the TMS:Engine password encryption key. In addition, the existing GBL_DSN_CSF_SCSFMOD0 parameter in the WCONFIG($GBL$USR) profile, which supports ICSF load library concatenation in the RKANMODL DDNAME of started tasks, is now extended to all agent configuration. KDS_KMS_SECURITY_COMPATMD This parameter allows customization of the KMS_SECURITY_COMPATIBILITY_MODE parameter in a runtime environment's RKANPARU(KDSENV) member. RTE_USS_MKDIR_MODE This parameter allows the access mode used in the PARMGEN composite UNIX System Services related jobs to be customized to a site's security audit requirements. Chapter 1. Overview 13

22 The PARMGEN KCIJcUSS job creates the UNIX System Services directories and subdirectories required for WebSphere Message Broker, IBM Tivoli Composite Application Manager for SOA, and IBM Tivoli Composite Application Manager for Application Diagnostics. By default, the directories are created with 7/7/7 access mode. This default mode may not suite a site's security audit requirements. By default, any new parameters introduced by a PARMGEN maintenance are automatically generated in the WCONFIG($CFG$IBM) IBM-supplied default profile by rerunning the KCIJPUP1 job. To preserve user customizations, the KCIJPUP1 job does not refresh the WCONFIG(%RTE_NAME%) LPAR profile for existing runtime environments. If you want to take advantage of the new profile parameters in an existing LPAR profile, you must refresh the LPAR and global profiles. Resubmitting the KCIJPCFG job and renaming the LPAR profile, will automatically rerun the KCIJPUP1 job and merge any customizations from the backup profile into a newly generated one which contains the new parameters. Renamed PARMGEN parameter The KDS_TEMS_SECURITY_KAES256_ENCKEY parameter has been renamed. Customizations to the KAES256 encryption key must now be made through the global RTE_SECURITY_KAES256_KEY parameter, which is applicable to all components, including the agents. PARMGEN provides automatic migration of the customized value (if configured) from the original KDS_TEMS_SECURITY_KAES256_ENCKEY parameter to the new global runtime environment parameter. Changed PARMGEN parameters KDS_TEMS_KDC_DEBUG and all common Agent Kpp_X_AGT_KDC_DEBUG By default, the TMS:Engine communications trace configuration is KDC_DEBUG=N. The PARMGEN profile parameter itself does not change but the environmental variable KDC_DEBUG parameter generated in the xkanparu(kppenv) is changing from the original KDC_DEBUG communications trace parameter to KBS_DEBUG for a more diagnostic debug tracing output. KDS_TEMS_STORAGE_LIMIT_EXTEND The default has been changed from 23 to 24. This parameter is used in the monitoring server xkanparu(kdssysin) LIMIT( %KDS_TEMS_STORAGE_LIMIT_EXTEND%,X) parameter. New runtime environments will be created using these defaults. If you want to refresh values in existing runtime environments, resubmit the KCIJPCFG job, backing up the existing profile, and resubmit the $PARSE* and KCIJcW2R jobs. New WK* jobs WKANSAMU(KCIJcW1R) This deployment job empties the current production libraries and copies the WK* work libraries to the RK* production libraries. The original KCIJcW2R deployment job has been re-architected to exclude the EMPT* steps. Moving the EMPT* steps out of the standard KCIJcW2R allow the IEBCOPY jobs to run without requiring started tasks to be recycled. You can choose to run either job. WKANSAMU(KCIJcMTY) Empties out the runtime members created in the RK* product execution user libraries. Emptying the libraries ensures that there are no obsolete members in the RK* user libraries if runtime members are no longer used (for example, if a product is no longer configured in the RTE, or the runtime member is obsolete, or if a configuration option changed and the runtime member name is dependent upon the configuration option). WKANSAMU(KCIJcSPC) Compares (SUPERC) the runtime members from the PARMGEN WK* (WKANCMDU, WKANPARU, WKANSAMU, WKD2PAR, WKD2PRF, WKD2SAM) work libraries with the product execution RK* user libraries (RKANCMDU, RKANPARU, RKANSAMU, RKD2PAR, 14 IBM Tivoli OMEGAMON XE and Tivoli Management Services on z/os: Upgrade Guide