|
|
|
Depending on your configuration, different driver programs are available to enable integration with Event Management. The following drivers are available:
Invokes Event Management directly on z/OS. It routes events directly to Event Management on the local system.
If you use the optional parameter drvropts(data2) you can forward a message directly to a remote node specified by data2 without defining a message action. For example:
CON11: driver(/cai/nsmem/bin/casyfem1) drvropts(-n XYZNODE) [mlwto]
If you use the optional parameter mlwto, you enable the processing of all lines of multi-line WTO messages. For more details, see Processing Multi-line WTO Messages.
Integrates with Event Management using UNIX style syslogd calls. syslogd must be configured to route messages to Event Management, either locally or on another platform.
Generates SNMP traps that can be processed on other CA platforms through integration with Event Management. To specify the OID that the SNMP trap will produce, you must code the OID value using the drvdata parameter in the destination statement. A listening port number may be specified in the drvropts parameter in the destination statement. The default port is 162. For more information, see the catrap discussion in the Event Management chapter of the Reference Guide.
Example
The following statement creates a destination called SNMP with a specific OID value:
SNMP: driver(/cai/nsmem/bin/casyfem5) + drvrdata(1.3.6.1.4.1.791.2.9.2.2 6 12 1.3.6.1.4.1.791.2.2.3.1)
The sample drvrdata value is as follows:
The trap will be sent to port 162 since the parameter drvropts was not used to specify a different port.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |