event_set 
You specify that the database system is to trigger an event as soon as a defined situation occurs. You can execute this DBM command in any operating state of the database and the event is active immediately. To set an event inactive, execute the event_release command. An event also becomes inactive when you stop the relevant DBM server process.
For all available event categories, there are one or more property definitions (default values) that trigger an event of that category. For event categories ThrowDBFillingAboveLimitEvent, ThrowDBFillingBelowLimitEvent and ThrowLogAboveLimitEvent, you can define additional property definitions that trigger an event of the corresponding category. Use the command event_set.
Using the Event Dispatcher, you can handle the events triggered by the database system and thus, for example, automate periodic administration tasks. To do this, you afterwards create an event definition in Event Dispatcher in which you specify that the triggered event is to be handled by the database system and how this is to be done.
Prerequisites
You have the DBInfoRead server authorization.
Structure
event_set <event_category> <priority> <value>
<priority> :: = LOW | MEDIUM | HIGH
Option |
Description |
|---|---|
<event_category> |
Event category; possible values are: ThrowDBFillingAboveLimitEvent | ThrowDBFillingBelowLimitEvent | ThrowLogAboveLimitEvent ThrowDBFillingAboveLimitEvent: The system triggers events of this category when the fill level of the data area exceeds the predefined value. Default system values are events with fill levels 90%, 95%, 96%, 97%, 98%, 99% (HIGH priority), fill levels 80%, 85% (MEDIUM priority) and fill level 70% (LOW priority) ThrowDBFillingBelowLimitEvent: The system sends events in this event category when the fill level of the data area goes below the predefined value. Default system values are events with fill levels 70%, 80%, 85%, 90%, 95% (LOW priority) ThrowDBFillingAboveLimitEvent: The system triggers events of this category when the fill level of the data area exceeds the predefined values. Default system values are events with fill levels 96%, 97%, 99%, 99% (HIGH priority), with fill levels 90%, 95% (MEDIUM priority) and fill levels 50%, 75% (LOW priority) |
<priority> |
Priority of an event Possible values are: LOW | MEDIUM | HIGH With events that belong to a category that is changeable, you can override the default values in the database system. |
<value> |
Numerical value whose meaning depends on the event DBFILLINGABOVELIMIT: Each time a fill level is exceeded by between 0% and 99%, you can define a separate event with a certain priority (value range 0 ≤ n ≤ 99). DBFILLINGBELOWLIMIT: Each time a fill level is fallen short of by between 1% and 100%, you can define a separate event with a certain priority (value range 1 ≤ n ≤ 100). LOGABOVELIMIT Each time a fill level is exceeded by between 0% and 100%, you can define a separate event with its own priority (value range 0 ≤ n ≤ 100). |
Example
Call the Database Manager CLI, log on as operator OLEG with password MONDAY, connect to the DEMODB database instance, define an event of category ThrowDBFillingAboveLimitEvent with priority LOW and value 50.
>dbmcli -u OLEG,MONDAY -d DEMODB event_set ThrowDBFillingAboveLimitEvent LOW 50
OK