OMEGAMON AI for CICS considerations

This section contains the upgrade considerations you must review before you begin to configure and customize OMEGAMON AI for CICS.

Hot Standby considerations for distributed hub configurations

If your OMEGAMON AI for CICS agent is reporting to a hub server on a distributed platform and you have configured Hot Standby with your distributed hub server, you will need to keep the RKCPDEFW.db/idx files defined at the hub in sync with the Standby Hub copy of the RKCPDEFW.db/idxfiles. If you customize your CICS® SLA definitions or your OMEGAMON® CICS CICSplex definitions, you will need to copy the RKCPDEFW.db/idx files from your active or primary hub tables directory to your standby hub tables directory, then recycle the Hot Standby hub. This will ensure that whenever a failover to the Hot Standby hub is performed, that your customized CICS SLA and CICSPlex® definitions are available after the failover switch has been completed. For more information, see IBM® Tivoli Monitoring High Availability Guide for Distributed Systems Version 6.3.0.

Removal of INTERVAL= override parameter for WLM startup command

In previous releases of OMEGAMON AI for CICS, you were able to override the collection interval value as part of the monitoring agent's WLM startup command to allow a collection interval of 1 minute. To provide an accurate Service Level Analysis across all your defined CICSplexes, the collection interval setting must be defined consistently at the runtime environment level rather than at the individual monitoring agent level. For this reason, the INTERVAL= agent startup parameter has been deprecated and is ignored if you specify it.

If you specify this startup parameter, the following message appears in the monitoring agent RKLVLOG output:
KCP0233W: THE 'INTERVAL=' PARAMETER IS NO LONGER USED AND WILL BE IGNORED

The service level analysis collection interval defined either through the CICS SLA view in the Tivoli® Enterprise Portal or the SLA Batch command line utility is always used.

If you have used the INTERVAL= parameter in the past to enable a collection interval of 1 minute, you will need to make the following changes as part of your upgrade to ensure you continue to collect data at the required interval:
  1. Prior to bringing any upgraded agents online, install the latest OMEGAMON AI for CICS application support onto a distributed machine which has a Tivoli Enterprise Portal Server installed.
  2. Either log on to a connected Tivoli Enterprise Portal client and switch to the CICS SLA view or use the SLA Batch utility, to update the collection interval to 1 minute (0001, if using the SLA Batch utility). See Configuring Service Level Analysis definitions using the Tivoli Enterprise Portal and Configuring Service Level Analysis definitions using the batch utility for more configuration information.
  3. Bring your new or upgraded agents online. Any agents running at a previous version will continue to use the override parameter while the new agents will use the updated collection interval value applied across the entire runtime environment.
    Note: No agent running at a previous release will contribute any data to CICSplex based workspaces, including the CICSplex SLA Summary.

Runtime environment load processing consideration

Prior to running the runtime environment load job (KCIJPLOD for PARMGEN), the OMEGAMON AI for CICS monitoring agent and the Tivoli Enterprise Monitoring Server started tasks associated with the runtime environment that are being loaded must be shutdown. Runtime environment load processing must be allowed to delete the KC5ATR file in RKANDATV before the agent and Tivoli Enterprise Monitoring Server are restarted. Otherwise, the new KCPATR file might not be correctly loaded during the agent restart process.

New feature upgrade consideration introduced with this release

If you are upgrading an existing runtime environment from a previous release of OMEGAMON AI for CICS, CICSplex reporting through the OMEGAMON enhanced 3270 user interface, does not start until after the load runtime environment processing and product configuration has been completed and the product address spaces have been recycled. This reconfiguration is not required for a general upgrade, but needs to be done before you can use CICSplex reporting and the OMEGAMON enhanced 3270 user interface.

Using the PARMGEN configuration method for your runtime environment configuration, load the runtime environment, and run &hilev.&rtename.WKANSAMU(KCIJPLOD).

Preparing customized OMEGAMON WLM definitions and CICSplex classification rules for an upgrade

The OMEGAMON AI for CICS CICS service level analysis OMEGAMON WLM definitions and CICSplex classification rules (in V5.1.0 or later) are stored in the RKCPDEFW file allocated to the hub Tivoli Enterprise Monitoring Server.

If you are upgrading to OMEGAMON AI for CICS V5.5.0 or performing a maintenance upgrade only, save a back up copy of the RKCPDEFW file prior to starting your upgrade. You should use a standard system file backup utility to back up your RKCPDEFW file. If you are upgrading to V5.5.0, you can also use the SLA batch utility (kcp_slabatch) to back up your RKCPDEFW file. The SLA batch utility does not include support for backing up the CICSplex classification rules, so it can not be used for RKCPDEFW file backup when performing a maintenance upgrade.