Alerts are displayed on the Alert Monitor; however, you can also forward them to the following platforms:
You can apply filter criteria to forward different types of alerts to different platforms.
Alert forwarding does not require manual intervention; it occurs automatically when the alert is created.
You implement alert forwarding by using Customizer parameter groups.
Note: TNGTRAP and SERVICEDESK do not have clear alert events. Only alert open and considerations are forwarded.
To implement alert forwarding
The Customizer : Parameter Groups list appears.
The parameter group opens for update.
Specifies the type of alert forwarding to use.
Press Enter.
The fields dynamically change to match the specified destination type.
(Optional) Press F8 (Forward), and repeat Step 3 for each Definition ID.
Note: Press F1 (Help) for information about the fields.
The changes are applied.
The settings are saved.
The MIB definition for alerts forwarded as SNMP traps is provided in member $AMTRAP, supplied in the CC2DSAMP data set. You can download this member to your UNIX system and compile it.
Note: When copying this member to your UNIX system, you can rename it to avoid problems on some UNIX systems where the $ sign has special meaning.
The supplied MIB defines two traps with the following object identifiers:
To receive alerts in a Tivoli NetView region, the CNMCALRT task must be defined and active. The alerts are formatted as Operator Notification generic alerts.
To forward alerts to Tivoli NetView
TASK MOD=CNMCALRT,TSKID=CNMCALRT,PRI=6,INIT=Y
Note: This statement is necessary for the z/OS software alert forwarding function.