NetView Operations Facility › What Happens When You Generate an Alert › How the NOF Responds to NetView Alerts

How the NOF Responds to NetView Alerts

In much the same way that CA OPS/MVS can send alerts into NetView, other system components (both hardware and software) also send alerts into NetView. This gives NetView access to an important systems management data stream that CA OPS/MVS can also tap into. Depending on your configuration, the alert stream can include DASD information, messages from NetView/6000, or even AS/400 messages. The next few sections explain how the NOF sees NetView alerts.

The NOF sees NetView alerts and responds:

• A function in NetView Version 2.2 and above allows the NetView automation table to see network alerts and drive automation based on those alerts.
• CA OPS/MVS supplies the entries in this automation table and the programs that do the automation. This enables CA OPS/MVS to capture all NetView alerts and forward those alerts to the CA OPS/MVS internal rules processor for resolution.
• The ALRTMLWTO and ALRTOPSGLBV parameters you specified when calling the OPNOF REXX program determine what the NOF does when it encounters an alert.
• Before sending the alerts to CA OPS/MVS, a REXX program called OPNFMSUR formats the information in the alert so that an automation procedure can make sense of it:
  • The OPNFMSUR program first translates the code points into English
  • Then places the result in a single global variable.

  You can then write a CA OPS/MVS global variable rule to process the alert.