Creates the Event Dispatcher module.  For more information about
    this entity and its subentities, refer to
    HELP ENTITY EVENT_DISPATCHER.

    create [node node-id] event dispatcher

    Select outbound_stream for information on creating event dispatcher
    outbound stream subentities.  Select relay for information on
    creating the event dispatcher relay subentity.  Select sink for
    information on creating event dispatcher sink subentities.

1  –  Exception Messages

 o  entity class not supported (OpenVMS)

    The Event Dispatcher has not registered with EMAA.  The NET$EVD
    process is probably not running.  For instructions on restarting
    the process, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER.

2  –  outbound_stream

    Creates an instance of an event dispatcher outbound stream entity.

    create [node node-id] event dispatcher -
        outbound stream stream-name [maximum buffer size integer]

    An event dispatcher outbound stream entity represents an outgoing
    connection to a sink on a local or remote node.  Stream-name is the
    simplename which identifies this event dispatcher outbound stream
    instance.  Maximum buffer size is an optional argument.

    Example:

    create event dispatcher outbound stream local_stream

2.1  –  maximum_buffer_size

    Maximum buffer size is an optional argument that specifies the
    maximum number of octets to be used for event processing of this
    stream. The current value is displayed in the buffer size status
    attribute. You can specify a size smaller than the
    implementation's default, provided it is still sufficient to hold
    the events lost event. It is recommended that you use the default
    buffer size, which is 16384.

    Example:

    create event dispatcher outbound stream local_stream -
        maximum buffer size 16384

2.2  –  Exception Messages

 o  entity class not supported (OpenVMS)

    The Event Dispatcher has not registered with EMAA.  The NET$EVD
    process is probably not running.  For instructions on restarting
    the process, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER.

3  –  relay

    Creates an event dispatcher replay entity which processes events
    from Phase IV systems.  It receives Phase IV format events and
    posts them into the DECnet-Plus logging system.

    create  [node node-id] event dispatcher relay

3.1  –  Exception Messages

 o  process failure

    The event dispatcher relay entity probably already exists.

 o  entity class not supported (OpenVMS)

    The Event Dispatcher has not registered with EMAA.  The NET$EVD
    process is probably not running.  For instructions on restarting
    the process, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER.

4  –  sink

    Creates an instance of an event dispatcher sink entity.

    create [node node-id] event dispatcher -
       sink sink-name [maximum buffer size integer]

    A sink manages incoming connections and filters incoming events.
    Each sink maintains a filter that is applied to all streams that
    are assigned to that sink.  Sink-name is a simplename that
    identifies this particular event dispatcher sink instance.
    Maximum buffer size is an optional argument.

    Example:

    create event dispatcher sink local_sink

4.1  –  maximum_buffer_size

    Maximum buffer size is an optional argument that specifies the
    maximum number of octets to be used for event processing of this
    sink.  The current value is displayed in the buffer size status
    attribute. You can specify a size smaller than the
    implementation's default, provided it is still sufficient to hold
    the events lost event. If the value specified is inadequate for
    the events lost event, an "insufficient resources" exception is
    returned.  It is recommended that you use the default buffer size,
    which is 16384.

    Example:

    create event dispatcher sink local_sink -
         maximum buffer size 16384

4.2  –  Exception Messages

 o  entity class not supported (OpenVMS)

    The Event Dispatcher has not registered with EMAA.  The NET$EVD
    process is probably not running.  For instructions on restarting
    the process, refer to HELP NETWORK_MANAGEMENT EVENT_DISPATCHER.