event_set 
With this command you can specify that the database system should trigger an event as soon as a defined situation occurs. You can execute this DBM command in any operational 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 specify additional property definitions that trigger an event of the corresponding category. For that purpose, use the event_set command.
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, create an event definition in Event Dispatcher. In the event definition specify that the triggered event is to be handled by the database system and how this should be done.
Prerequisites
You have the DBInfoRead server permission.
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 the fill levels of 90%, 95%, 96%, 97%, 98% and 99% (HIGH priority), with the fill levels of 80%, 85% (MEDIUM priority) and with the fill level of 70% (LOW priority) ThrowDBFillingBelowLimitEvent: The system triggers events of this category when the fill level of the data area falls below the predefined value. Default system values are events with the fill levels of 70%, 80%, 85%, 90% and 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 the fill levels of 96%, 97%, 99% and 99% (HIGH priority), with the fill levels of 90% and 95% (MEDIUM priority) and with the fill levels of 50% and 75% (LOW priority) |
<priority> |
Priority of an event Possible values are: LOW | MEDIUM | HIGH For 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: For any fill level between 0% and 99% exceeding the defined value, you can define an event (value range 0 ≤ n ≤ 99) as well as a priority for that event. DBFILLINGBELOWLIMIT: For any fill level between 0% and 100% falling short behind the defined value, you can define an event (value range 1 ≤ n ≤ 100) as well as a priority for that event. LOGABOVELIMIT For any fill level between 0% and 100% exceeding the defined value, you can define an event (value range 0 ≤ n ≤ 100) as well as a priority for that event. |
Example
Call Database Manager CLI, log on as the operator OLEG with the password MONDAY, connect to the DEMODB database, define an event of category ThrowDBFillingAboveLimitEvent with priority LOW and value 50.
>dbmcli -u OLEG,MONDAY -d DEMODB event_set ThrowDBFillingAboveLimitEvent LOW 50
OK