Upon injection, each monitor’s initial instance runs in the main context. You must explicitly create additional contexts. Conceptually, a context is like a correlator, however, a correlator has a few special properties:

All contexts share the same namespace, and thus share all monitor and event definitions that have been injected. A monitor instance must have a context reference to pass an event to that context.

There is one queue of enqueued events for all contexts. When you specify the enqueue command (not the enqueue...to command), the enqueued event goes to the special queue for enqueued events. The correlator then places the event on the input queue of each public context. The correlator ensures that an enqueued event always arrives on the appropriate input queue(s). An enqueue operation never blocks. However, if the input queue of a context is full and the enqueued events queue gets very large, the result can be an unbounded memory usage error.

The engine_receive utility receives events from all contexts.

The engine_send utility sends events to all contexts that have been set to receive external events, that is, all public contexts.