Each of the logical destinations that are specified in your criteria statements must be defined in the destination statement file. The statements in this file define the logical destinations and optionally explain how Event Management Utilities exchange messages when communicating with this destination.
A destination statement has the following format:
destination_name: driver(driver) [lang(language)] [drvrdata(data1)] [drvropts(data2)] [mlwto]
Defines a logical identifier for use by the criteria control statement file.
Limits: 64 characters
Specifies the name of a program that is to be the driver for this destination. The different Event Management Utilities drivers are available to communicate with Event Management using various communication techniques.
(Optional) Specifies the character-encoding scheme of the message. It represents a locale or code page name acceptable to the IBM iconv() function.
Default: Messages are routed to the destination unchanged.
Limits: 16 characters
In some cases, translation is not possible between the specified code page and the code page that Event Management uses. For example, if you specify multibyte messages (such as UCS-2 or IBM-939) and Event Management runs with a code page that lacks translation for certain input values.
(Optional) Passes information to the driver program. For example, the SNMP driver uses this parameter to let you specify the object identifier (OID) used in generating SNMP traps.
(Optional) Passes information to the driver program. The Event Management driver allows you to pass a remote node name in the format (-n XYZNODE) to forward a message directly to another node without having to define a message action. The SNMP driver allows you to pass a port number in the format ( -p nnnn ) to specify the port where the trap is sent.
(Optional) Enables the processing of multiline WTO messages. This parameter is mlwto (case-sensitive).
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|