event_receive 
You can use this DBM command to fetch an event that has been triggered.
Repeat this DBM command to fetch additional events. The events are fetched in the chronological order in which they were triggered, the oldest events are fetched first.
The first time you execute one of the DBM commands event_wait, event_receive or event_available, an event session is generated within the Database Manager session. Events that are triggered from this time on are collected and can be dealt with within the event session.
If no event was triggered, you get an error message for DBM command event_receive.
Prerequisites
You have the DBInfoRead server authorization.
The FloatingServiceTasks and PreservedEventTasks database parameters are configured large enough (see: Database Administration, Support Database Parameters).
Structure
event_receive
Result
OK
NAME=<event_category>
PRIORITY=<priority>
VALUE1=<value1>
VALUE2=<value2>
DATE=<yyyymmdd>
TIME=<HHmmss>
COUNT=<count>
TEXT=[<text>]
Value |
Description |
|---|---|
<event_category> |
Event Category |
<priority> |
Priority of an event Possible values are: LOW | MEDIUM | HIGH |
<value1> |
Numerical value 1, the meaning of which depends on the event For events of the categories DBFILLINGABOVELIMIT, DBFILLINGBELOWLIMIT and LOGABOVELIMIT: number of pages used |
<value2> |
Numerical value 2, the meaning of which depends on the event For events of the categories DBFILLINGABOVELIMIT, DBFILLINGBELOWLIMIT and LOGABOVELIMIT: percentage of pages used |
<date> |
Day on which event was triggered Time format: <yyyymmdd> (year month day) |
<time> |
Time at which event was triggered Time format: <HHMMSS> (hours minutes seconds) |
<count> |
Sequence number of the event The system starts numbering at the moment in which the database instance is transferred to the ONLINE operational state. |
<text> |
Text, the meaning of which depends on the event |
In the event of errors, see Reply Format.
More Information
Glossary, Event, Event Dispatcher