Previous Topic: Example: Configuration StatementsNext Topic: Run the Utilities as an OMVS Process

Event Management › Event Management Utilities › Event Management Utilities Drivers

Event Management Utilities Drivers

Depending on your configuration, different driver programs are available to enable integration with Event Management. The following drivers are available:

CASYFEM1

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 multiline WTO messages. For more details, see Processing Multiline WTO Messages.

CASYFEM4

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.

CASYFEM5

Generates the SNMP traps that can be processed on other CA Technologies platforms through integration with Event Management. To specify the OID that the SNMP trap produce, code the OID value using the drvdata parameter in the destination statement. Specify a listening port number in the drvropts parameter in the destination statement. The default port is 162.

Example

The following statement creates a destination, 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 is sent to port 162 because the parameter drvropts was not used to specify a different port.