Introduction of Alert Notification by SA z/OS

SA z/OS alert notification is triggered by the invocation of the INGALERT command.

It can be used to perform one ore more of the following tasks:
  • Start notification escalation by IBM® Tivoli® System Automation for Integrated Operations Management (SA IOM)
  • Display an event on a centralized operator console such as IBM Tivoli Enterprise Console (TEC) or IBM Tivoli Netcool/OMNIbus (OMNIbus)
  • Create a trouble ticket in a service desk application such as IBM Tivoli Service Request Manager® (TSRM)
  • Perform an arbitrary task in a user-defined alert handler
The following communication methods are available for alert notification:
  • Use the peer-to-peer protocol of SA IOM to start a REXX script on the SA IOM server
  • Send a Tivoli Event Integration Facility (EIF) event
  • Send XML data the to IBM Tivoli Directory Integrator (TDI) and from there trigger the creation of the trouble ticket
  • Pass parameters to the user-defined alert handler that is called as a NetView command
Note: EIF events and the TDI interface can be used to perform a variety of tasks or to integrate other operator consoles or service desk applications. The ones listed above are provided by SA z/OS as samples.

The behavior of INGALERT is controlled with the INGCNTL command at the system level, by a resource's Inform List at the resource level and even more granularly by CODE entries for the INGALERT entry in the MESSAGES/USER DATA policy item.

For details about the INGALERT and INGCNTL commands, see IBM Z® System Automation Programmer's Reference.