Monitoring Applications
System Automation for z/OS provides different ways to monitor your applications:
- Using observed status monitoring routines, SA z/OS can determine whether your applications and several other automated resources are active, inactive, or in the process of being started. It is recommended to always enable observed status monitoring routines and to use the product-provided routines where possible. See Observed Status Monitoring for further details.
- With monitor resources you can optionally monitor the health of your applications and recover them on health status changes. SA z/OS distinguishes between active health monitoring and passive event-based health monitoring. See Health Monitoring for further details.
Active and passive health monitoring is supported by SA z/OS in the following areas:
- Health monitoring of JES3, based on console messages
- Health monitoring of z/OS, DB2®, CICS®, IMS and other components, based on IBM® OMEGAMON® classic monitor exceptions or IBM Tivoli OMEGAMON XE situations
- Health monitoring of CICS, based on CICSPlex® SM
- Health monitoring of IMS, based on console messages