Special Events of the Event
Dispatcher 
Use
The special events of the event dispatcher provide information about the state of the even dispatchers.
They are always active and you do not have to activate them with the Database Manager CLI.
See also:
Overview of the special events of the event dispatcher
Name |
When is it triggered by the database instance? |
DISPINFO:DISPSTART |
When a user starts the event dispatcher. |
DISPINFO:DISPSTOP |
When a user stops the event dispatcher. |
DISPWARN:SHUTDOWN |
When the database instance has been set to the OFFLINE operational state. |
DISPERR:DBCRASH |
When the database system crashes (system breakdown). |
DISPERR:CONNLOST |
When the event dispatcher loses the connection to the DBM server. If you have started the event dispatcher on the same computer as the database application, this event can also be used to inform you of a breakdown in the network connection between the database application and the database instance. |
DISPWARN:MISSEDEVT |
When the database system kernel has triggered an event and the event dispatcher has not reacted to it. |
DISPERR:NOEVENTTASK |
When it was not possible to start the event dispatcher because there were no more event tasks free. To configure the
number of event tasks, use the database parameter _MAXEVENTTASKS, see Concepts of the Database System, |
SupportSee also:
Overview of Event Dispatcher Commands