NCLHELP.HLB  —  enable  event_dispatcher
    enable  [node node-id] event dispatcher

1  –  Exception Messages

 o  children in wrong state  (Tru64 UNIX)

    Another Event Dispatcher module entity is still enabled. Retry
    the command after you have disabled all of these entities:
    event dispatcher outbound stream, event dispatcher relay, event
    dispatcher relay logging, event dispatcher sink, and event
    dispatcher sink inbound strea.

 o  entity class not supported (OpenVMS)

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

2  –  outbound_stream

    Transitions an event dispatcher outbound stream instance into the
    on state.  An event dispatcher outbound stream entity represents an
    outgoing connection to a sink on a local or remote node.

    enable  [node node-id] event dispatcher -
          outbound stream simple-name

    Example:

    enable event dispatcher outbound stream local_stream

3  –  relay

    Transitions the event dispatcher relay entity into the "on" state
    and automatically causes three event dispatcher relay logging
    subentities (console, file, and monitor) to be created and enabled.

    enable  [node node-id] event dispatcher relay

3.1  –  logging

    enable  [node node-id] event dispatcher -
          relay logging logging-entity

    Three event dispatcher relay logging entities are created
    and enabled automatically whenever an event dispatcher
    relay entity is enabled.  The logging entities (console,
    file, and monitor) control the destination of Phase IV
    events.  Each logging entity can be disabled and reenabled
    individually.  All three logging entities are deleted
    automatically when the Phase IV relay entity is disabled.

    Examples:

    enable event dispatcher relay logging console

    enable event dispatcher relay logging file

    enable event dispatcher relay logging monitor

4  –  sink

    Transitions the specified instance of an event dispatcher sink to
    the "on" state.  The 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.

    enable  [node node-id] event dispatcher sink simple-name

    Example:

    enable event dispatcher sink local_sink

4.1  –  Exception Messages

 o  invalid name

    Invalid name for DNA session.
Close Help