OMEGAMON (3270) and OMEGAMON II (CUA) interfaces

The older 3270 interfaces require the least amount of product-specific architecture to support. These interfaces perform well and are user-friendly to systems programmers and administrators that are familiar with an ISPF-based 3270 interface. Standard and custom PF Key settings, menu options, and command-line interface options allow for short cuts to commonly viewed screens. While basic customization options allow for highlights and other eye-catcher techniques to be added to the interface, the customization options are limited. The 3270 interfaces use dedicated connection features and avoid disk I/O. Documentation may be out-of-date or difficult to find.

The OMEGAMON® (3270) and OMEGAMON II interfaces do not provide plex data, cross-LPAR monitoring, or cross-product views. However, you can get limited multisystem monitoring and cross-system views using OMEGAMON DE. The following OMEGAMON products provide older 3270 interfaces:
  • IBM® OMEGAMON for z/OS®
  • IBM Z® OMEGAMON for CICS
  • IBM OMEGAMON for Db2® on z/OS
  • IBM OMEGAMON for CICS® on z/OS
  • IBM OMEGAMON for Messaging on z/OS
  • IBM OMEGAMON for Storage on z/OS
  • IBM OMEGAMON for Networks on z/OS
OMEGAMON on z/OS and OMEGAMON for Storage require more infrastructure than the other agents: a Tivoli Enterprise Monitoring Server must be installed in the same runtime environment as each monitoring agent and the OMEGAMON component to be configured. (While the OMEGAMON on z/OS agent can be configured to run as a stand-alone system, that is, outside of a monitoring server, such a configuration does not support plex data.)

The other agents do not require either a portal server or a monitoring server, and require only configuration of the OMEGAMON II component.