If events were triggered, they can be fetched with this DBM command. You receive a notification from the Database Manager about the occurrence of an event and the data associated with it.
Repeat this DBM command to fetch additional events. The events are fetched in the chronological order of their creation, 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 task is generated for this Database Manager session. Events that are triggered from this time on are collected and can be dealt with within this session.
If no event was triggered, you get an error message for DBM command event_receive.
· You have the DBInfoRead server authorization.
· The database parameter _MAXEVENTTASK has been configured sufficiently large (see Concepts of the Database System, Support Database Parameter).
event_receive
OK
NAME=<event_category>
PRIORITY=<priority>
VALUE1=<value1>
VALUE2=<value2>
DATE=<yyyymmdd>
TIME=<HHmmss>
COUNT=<count>
TEXT=[<text>]
Values for the Reply Fields
Value |
Description |
<event_category> |
Event category |
<priority> |
Priority of the event; possible values are: LOW: low priority MEDIUM: medium priority HIGH: high priority |
<value1> |
Numerical value 1, the meaning of which depends on the event |
<value2> |
Numerical value 2, the meaning of which depends on the event |
<date> |
Day on which the event was triggered Time format: <yyyymmdd> (year month day) |
<time> |
Time at which the event was triggered Time format: <HHMMSS> (hours minutes seconds) |
<count> |
Current number of the event The system starts numbering with transferring the database instance into the operational state ONLINE. |
<text> |
Text, the meaning of which depends on the event |
In the event of errors, see Reply Format.