## event_receive

### Use

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.

This 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.

See also:

Utilities, Event Dispatcher

### Prerequisites

● You have the DBInfoRead server authorization.

● The database parameter _MAXEVENTTASK has been configured sufficiently large (see: Concepts of the Database System, Support Database Parameter).

### Syntax

event_receive

### Reply

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: LOW | MEDIUM | HIGH
<value1> | Numerical value 1, the meaning of which depends on the event With events of category DBFILLINGABOVELIMIT, DBFILLINGBELOWLIMIT and LOGABOVELIMIT: -Number of full pages
<value2> | Numerical value 2, the meaning of which depends on the event With events of category DBFILLINGABOVELIMIT, DBFILLINGBELOWLIMIT and LOGABOVELIMIT: -Percentage rate of full pages
<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> | 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.