34 IBM Tivoli System Automation for z/OS Enterprise Automation
3.1 IBM Tivoli OMEGAMON integration
The OMEGAMON real-time monitor components alert you to application
degradation and overall system problems through color-coded status bars or
through user-defined status words. This includes a wide range of detailed
analysis and exception reporting for every aspect of your enterprise. The
valuable information that IBM Tivoli OMEGAMON suite of products convey to
operations and support staff quickly becomes relied upon for the day to day
running of a data center, making the availability of the Tivoli monitors themselves
almost as important as the applications they monitor. The best way to achieve
this is to entrust their availability to System Automation for z/OS and its excellent
recovery, scheduling, and automation features.
A programmer-less integration with Monitor Resources is achieved by providing
an interface tailored specifically for exception monitoring. The automation
administrator uses this interface as a monitor command and specifies the
exceptions of interest. In addition to the monitor command, the administrator also
specifies the health state associated with the exception and commands that
System Automation for z/OS should issue to recover from the exception. There
are facilities that allow the administrator to escalate commands in case a
previously scheduled recovery action was unsuccessful or to insulate from
subsequent exceptions for a certain time while a recovery action is in progress.
Integrating OMEGAMON products into System Automation for z/OS gives the
benefits of System Automation for z/OS's resource management and scheduling
facilities:
OMEGAMON error conditions and restart/recovery processing are handled
by System Automation for z/OS, thus minimizing your application downtime.
Having your OMEGAMONs integrated into System Automation for z/OS
allows you to include the monitors in a fully-automated initial program load
(IPL) for maximum efficiency.
A combination of System Automation for z/OS high availability functionality and
the ability of IBM Tivoli OMEGAMON to move its Tivoli Enterprise Monitoring
Server hub ensures the highest possible levels of application availability. For
more discussion on moveable Tivoli Enterprise Monitoring Server hub, see IBM
Tivoli OMEGAMON XE V3.1.0 Deep Dive on z/OS, SG24-7155.
Exception analysis is an OMEGAMON feature that monitors predefined
thresholds in a system. Each time exception analysis is invoked, an exception is
displayed on the OMEGAMON console if a threshold is exceeded. Using System
Automation for z/OS, you can then act on these exception alerts by running
programs or issuing commands back to the OMEGAMON system that has the
problem. This feature is called Monitor Resources.
Chapter 3. Working with IBM Tivoli OMEGAMON classic interface 35
You can set up Monitor Resources to:
Monitor sets of exceptions that may be of interest
Set an application’s health state based on the existence of such exceptions
React to and resolve conditions that cause those exceptions
This chapter shows you how to define the sessions and the monitor resource
definitions to set the System Automation for z/OS health status.
Various topologies are possible for System Automation for z/OS integration with
IBM Tivoli OMEGAMON:
There can be one or more systems.
There can be one or more OMEGAMON monitors per system.
Connectivity is through VTAM and the NetView Terminal Access Facility
(TAF).
System Automation for z/OS can act as a focal point either:
Globally, monitoring data from OMEGAMON monitors running on different
systems
Locally, monitoring data from OMEGAMON monitors running on the local
system
The following assumptions are made about the topologies that we implement in
this chapter. For background informtion about IBM Tivoli OMEGAMON
implementation, refer to IBM Tivoli OMEGAMON XE V3.1.0 Deep Dive on z/OS,
SG24-7155.
IBM Tivoli OMEGAMON product is installed on each system.
IBM Tivoli OMEGAMON classic monitors are installed and configured already
to support multiple VTAM-based connections to it. For interoperability with
System Automation for z/OS, support for 3270 model 2 (screen size 24x80) is
required.
IBM Tivoli OMEGAMON monitors are set up to interact with an external
security product, such as RACF®, to validate access.
IBM Tivoli OMEGAMON exceptions are reported when the threshold that is
defined in OMEGAMON is exceeded. That threshold must be agreed within
an installation because it must cater for the least severe condition that there
might be an alert for.

Get IBM Tivoli System Automation for z/OS Enterprise Automation now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.