Step 15: Configure Alert Notification for SA z/OS

SysOps ProcOps
*  

This section describes the configuration steps that are required for alert notification by SA z/OS.

In order to use alert notification the following must apply to the affected resource in your automation policy:
  1. The inform list of the resource must contain at least one of the following communication methods (it can also be defaulted or inherited):
    • IOM: via the IBM® Tivoli® System Automation for Integrated Operations Management (SA IOM) peer-to-peer protocol
    • EIF: via a Tivoli Event Integration Facility (EIF) event
    • TTT: via XML
    • USR: via a user-defined alert handler
  2. Codes must be present on the reserved message ID, INGALERT, that are suitable for the chosen communication methods.
For full details about the installation of related workstation components, refer to Configuring SA z/OS Workstation Components. Additionally for further information, see IBM Z® System Automation Defining Automation Policy and IBM Z System Automation Customizing and Programming.
Furthermore, for each system that is able to trigger an alert (that is, to issue an INGALERT command), the ALERTMODE parameter must be set to the chosen communication methods with the INGCNTL command, for example: 
INGCNTL SET ALERTMODE=’IOM EIF TTT USR’
You can also use the following command to set alerting for all available communication methods: 
INGCNTL SET ALERTMODE=ON
The available communication methods are:
  • IOM: via the SA IOM peer-to-peer protocol
  • EIF: via EIF events
  • TTT: via XML
  • USR: via a user-defined alert handler

Depending on the chosen communication methods, additional customization is required. This is described in the following sections. Note that you can combine the INGCNTL calls shown in this section in one single invocation.

For more details about INGCNTL, see IBM Z System Automation Programmer's Reference.