Adding IBM Z OMEGAMON Monitor for z/OS 5.6 or IBM Z OMEGAMON Network Monitor 5.6 to existing installations

If you are installing IBM Z OMEGAMON Monitor for z/OS or IBM Z OMEGAMON Network Monitor 5.6 with existing installations of OMEGAMON XE for z/OS 5.3 or 5.5, or OMEGAMON XE for Mainframe Networks 5.3 o5 5.5, there are some coexistence considerations to plan for.

IBM Z OMEGAMON Monitor for z/OS 5.6 supports a staged installation. This means as you are installing IBM Z OMEGAMON Monitor for z/OS 5.6 PTF UJ05167 APAR OA60576 or IBM Z OMEGAMON Network Monitor PTFs UJ05168, UJ05169 APARs OA60577, OA61024, you may have a combination of 5.3, 5.4, and 5.6 monitoring agents installed in your environment. For example, you may have a 5.3 monitoring agent and a 5.6 monitoring agent running in the same hub environment during the migration period. However, the hub and TOM must be 5.6. Support of a mixed environment is provided as a compatibility help.

You can deploy new monitoring agents to your z/OS systems along with older monitoring agents of the same product, during a transition period.

Requirements:
  • Hub Tivoli Enterprise Monitoring Server must have 5.6
  • TOM must be 5.6
  • Agents can be 5.3, 5.5, 5.6, or a mix
  • The z/OS SYSPLEX proxy must be running on a 5.6 LPAR
If you want to preserve customized data (situations, workspaces and queries) or historical data, you must first upgrade any distributed components (Tivoli Enterprise Portal Server, hub Tivoli Enterprise Monitoring Server if it is on a distributed platform, and Tivoli Data Warehouse) and then upgrade the agents.
Important: It is recommended to use the new 5.6 tables. If you are upgrading from base IBM Z OMEGAMON Monitor for z/OS or IBM Z OMEGAMON Network Monitor and you have customized data (situations, workspaces and queries) or historical data, you will need to recreate your situations using the new tables provided. If you are migrating with no custom workspaces or situations, you can upgrade normally. See Reference: 5.6 base tables that have been replaced in PTFs UJ05168, UJ05169, and UJ05167 for more information.

Best practices

It is recommended to use Configuration Manager, though PARMGEN is also supported.

It is recommended to use a "clean" installation in a new CSI, though a mixed installation is also supported.

Limitations when using a mixed environment with 5.3 agents

If you have an LPAR running a 5.3 agent connected to a 5.6 Hub, those 5.3 LPARs will not be able to report data for the new 5.6 workspaces. The e3270ui workspace tabs that are new in 5.6 will display blank data. This is because the underlying support is not available on 5.3. These workspaces include:
  • Service Classes Ext Tab of WLM Class Resources workspace
  • Report Classes Tab of WLM Class Resources workspace
  • JES Spool Workspace
  • SCM Cards Tab of Flash Memory Activity Details workspace
  • Summary of PCIE Activity workspace
  • Warning Track Interrupt Details workspace
  • Current/High Usage Tab of UNIX BPXPRMxx Values workspace
  • VTAM Application Address Space Summary workspace (on IBM Z OMEGAMON Network Monitor)