The command sends from a dynamic agent or domain manager the custom events defined with the evtdef command to the event processor server currently active in the production plan. As the events are received by the event processor, they trigger the event rules in which they were specified.
Note: On Windows 2012, the command is not supported on Windows PowerShell.

Users can override the default destination server (defined by global options) by specifying the hostname and the port of a new server.


sendevent -V | ? | -help | -u | -usage

sendevent [-hostname hostname]
          [-port port]


Displays the command version and exits.
? | -help | -u | -usage
Displays command usage information and exits.
-hostname hostname
Specifies the host name of an alternate event processor server other than the currently active one.
-port port
Specifies the port number of an alternate event processor server other than the currently active one.
One of the custom event types defined with the evtdef command in the generic event provider and specified as the triggering event in an event rule definition.
The name of the event provider that you customized with evtdef. This is also the name you must specify as the argument for the eventProvider keyword in the definition of the event rules triggered by these custom events.

The default name is GenericEventPlugIn.

One or more of the attributes qualifying the custom event type that are specified as the triggering event attributes for the event rule.


The command in this form applies to the dynamic environment only. To send events from non-dynamic agents, see sendevent.


In this example an application running on a dynamic agent sends the BusProcCompleted custom event type to the default event processor. The event is that file calcweek finished processing.
sendevent BusProcCompleted GenericEventPlugIn TransacName=calcweek 
The file name and the associated workstation are the two BusProcCompleted event attributes that were specified as triggering event attributes in an associated event rule.