## stop

### Use

You stop an event dispatcher.

### Prerequisites

● The event dispatcher has been started and has received a numerical ID <instance_ID> (see start).

● If the –remoteaccess option was not specified on starting the event dispatcher, it can only be stopped from the database computer or the computer used to start it.

● To enable the event dispatcher to log on to the database instance, you require the name and password of a DBM operator with the following properties:

○ DBM operators with the server authorization EvtDispAdmin can stop all event dispatchers

○ DBM operators with the server authorization EvtDispUse can only stop those event dispatchers started under their user name.

### Procedure

dbmevtdisp stop <instance_ID> <database_authentication>

<database_authentication> :: = -d <database_name> <user_authentication> [-n <database_computer>] [-e SSL]

<user_authentication> :: = -u <user_data> |-U <user_key>

<user_data> :: = <dbm_operator>,<dbm_operator_password>

Option | Description
<instance_ID> | ID of event dispatcher you want to stop
<database_name> | Name of the database instance to be monitored
<database_computer> | Name of the database computer
SSL | Encryption method See Database Manager CLI, -e: Activate Encryption
<user_key> | XUSER key See Utilities, XUSER
<dbm_operator>,<dbm_operator_password> | DBM user data that is used by the event dispatcher to log on to the database instance to be monitored See Database Manager CLI, user_logon

### Result

OK

See also:

Overview of Event Dispatcher Commands