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 Upgrade checklist, review 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. 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.
  • Tivoli Enterprise Monitoring Server (FMID HKDS630)
  • z/OS configuration tools, which are Parameter Generator (PARMGEN) Workflow user interface and Configuration Manager (FMID HKCI310)
  • Tivoli Management Services:Engine (TMS:Engine) (FMID HKLV630)
To find the current release levels of the components running on distributed systems, issue one of the following commands:
  • On Windows
    \ibm\ITM\KinCInfo -i
  • On Linux® or UNIX:
    opt/ibm/ITM/BIN/cinfo -i
Shared components
The shared components should be upgrade to the following levels:
  • OMNIMON Base (including framework support for OMEGAMON enhanced 3270 user interface and OMEGAMON Subsystem): HKOB730
  • Shared probes: HKSB730
  • End-to-End Response Time Feature: HKET620
Self-describing agent feature (SDA)
If you are running a Tivoli Enterprise Monitoring Server on z/OS and you are planning to enable SDA:
  • Create HFS or zFS file system on z/OS UNIX System Services. The file system must be mounted before you upgrade. You will need to provide the path to this directory during configuration. The file system must be large enough to support all the jar files delivered by the z/OS agents:
    • Hub monitoring server: approximately 3.25 MB per agent
    • Remote monitoring server: approximately 2 MB per agent
  • The UNIX System Services system where you create these files system must have access to a Java™ Runtime Environment running under IBM's 31-bit or 64-bit Java SDK Version 6 (or later) and an HFS or zFS file system.
  • Ensure proper authorization has been set for the person who will run the jobs that add the subdirectories for the application support files.

To use SDA to upgrade your monitoring agents, SDA must be enabled and successfully started on the hub monitoring server, any remote monitoring server the monitoring agent reports, and the Tivoli Enterprise Portal, if used. You can check the status of SDA by using tacmd or looking in your monitoring server JESS message log for the following messaged: KFASD009 Self-Describing Agent feature enabled on local TEMS.

See Configure a Tivoli Enterprise Monitoring Server for more details on these requirements. For more information on enabling the self-describing agent capability, see Self-describing agent feature and the IBM Tivoli Monitoring: Administrator's Guide.

The following components do not support SDA. Application support for these components must be installed manually using the application support DVD.
  • OMEGAVIEW for the Enterprise agents
  • Language Packs
  • Tivoli Enterprise Portal desktop client
OMEGAMON enhanced 3270 user interface
If you will be configuring the OMEGAMON enhanced 3270 user interface, define an OMVS segment for the started task (IBMTOM 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.
If you want to enable the Memory Display/Zap feature in the OMEGAMON enhanced 3270 user interface with the OMEGAMON on z/OS product, you must assign a RACF ID to the enhanced 3270 user interface and authorize the ID to be able to generate PassTickets. See the section Security in the OMEGAMON enhanced 3270 user interface reference guide. Additional security definitions are also required for the OMEGAMON on z/OS product to enable the Memory List/Zap feature. See the OMEGAMON for z/OS Planning and Configuration Guide for more information.
SDA and enhanced 3270 user interface

Before you begin an upgrade, if your RKANDATV library was not already converted to a PDSE, you must reallocate it 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. To reallocate the library as a PDSE, delete it, then run the PARMGEN allocation job as part of the upgrade configuration.

If SDA support is enabled and you are configuring a high-availability hub, do not configure the OMEGAMON enhanced 3270 user interface in the same runtime environment as the hub. Configure the OMEGAMON enhanced 3270 user interface in its own runtime environment or in a runtime environment that has a remote monitoring server and monitoring agents configuring in it.

If the OMEGAMON enhanced 3270 user interface is not installed in the same SMP/E CSI as the other OMEGAMON products, you will have to maintain your environment manually by copying the updated application support files from the agent, monitoring server, and portal server libraries into the OMEGAMON enhanced 3270 user interface environment. You must then recycle the OMEGAMON enhanced 3270 user interface started task to include the updates.

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:
  • Components will use password encryption.
  • The SOAP server will be enabled on a remote monitoring server
  • Granular control of command requests will be enabled (KMS_SECURITY_COMPATIBILITY_MODE=N)
  • The zAware feature will be configured for OMEGAMON for z/OS.
Persistent data store
If your persistent data store has not been reconfigured from 3 files to 6, delete your persistent data store files and your RppSGRP* files prior to the upgrade so that they can be reallocated as part of the upgrade configuration process by rerunning the $PARSE and KCIJPALO jobs.
Variables
If the runtime environment is enabled for 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.