Performing a staged upgrade

To make product upgrades easier, OMEGAMON AI for CICS 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.

OMEGAMON AI for CICS monitoring agent can only monitor CICS® regions where the level of OMEGAMON® initialized within the CICS region is that of the same level or less. For example, an OMEGAMON AI for CICS V5.5.0 agent will monitor a CICS region initialized with V4.2.0, V5.1.0 or V5.3.0, but a V5.1.0 agent will not monitor a CICS region with OMEGAMON AI for CICS V5.5.0 initialized in it. The OMEGAMON AI for CICS V5.5.0 agent only supports a connection to Tivoli® Enterprise Monitoring Server running with IBM Tivoli Monitoring, V6.2.3 or higher level.

If you are upgrading a monitoring agent and Tivoli Management Services, refer to OMEGAMON shared documentation Version 6.3.0 Fix Pack 2: Upgrading.

IMPORTANT: Only CICS regions monitored by OMEGAMON AI for CICS V5.1.0 and later can be viewed in the OMEGAMON enhanced 3270 user interface.

Migration considerations

When upgrading the OMEGAMON for CICS (3270) address space all CICS regions that it monitors should be upgraded to the matching release. It is possible to have two different releases of OMEGAMON for CICS (3270) monitoring the same CICS region, however, Response Time Analysis, and Task History will only function in the address space that matches the release that is installed in the CICS region. OMEGAMON will not initialize in a CICS region if no OMEGAMON for CICS (3270) address space is located at the same release level; this means that Resource Limiting and SMF data would not be produced.

How to avoid a CICS region recycle when upgrading to OMEGAMON AI for CICS V5.5.0

If you want to avoid recycling your CICS regions during the upgrade to OMEGAMON AI for CICS, the following upgrade scenario is suggested:
  1. Complete your first runtime environment upgrade (see OMEGAMON shared documentation Version 6.3.0 Fix Pack 2: Upgrading for additional information regarding staged upgrade requirements).
  2. As part of the runtime environment upgrade, after you load the runtime environment, your RKANMOD and RKANMODR libraries will contain the V5.5.0 modules. Your CICS region should have the same RKANMOD and RKANMODR libraries allocated.
  3. Recycle your upgraded OMEGAMON for CICS (3270) V5.5.0 address space, leaving your CICS regions running.
    Note: After the recycle is complete, your response time analysis, task history and interval recorder features will not be restarted until after the next step (4) is completed.
  4. For each CICS region that you want to upgrade to OMEGAMON AI for CICS V5.5.0, enter the OMEG RECYCLE command or the OMEG REMOVE command, followed by the OMEG INIT command. This will remove the previous version of OMEGAMON for CICS (3270) and restart the monitoring by loading the V5.5.0 version of OMEGAMON for CICS (3270) that exists in your upgraded runtime environment RKANMOD and RKANMODR libraries.