## event_wait

### Use

You work in session mode of the Database Manager and fetch messages about the occurrence of an event and the corresponding data. These are then deleted.

The first time you execute one of the DBM commands event_wait, event_receive or event_available an event session is generated within this Database Manager session. Events that are triggered from this time on are collected and can be dealt with within this session.

The events are fetched in the chronological order in which they were triggered, the oldest events are fetched first.

If the data about the event that occurred has been fetched, you evaluate it, enter the command again and wait for the next notification from the Database Manager about the occurrence of an event.

You do not receive a reply to this DBM command until an event occurs.

To finish fetching messages, you need to terminate the event session explicitly (see: event_release)

Use this DBM command preferably via a programming interface of the Database Manager .

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_wait

### 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 are: LOW: low priority MEDIUM: medium priority HIGH: high priority
<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 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.

### Example

1. Call the Database Manager CLI in session mode, log on as operator OLEG with the password MONDAY, connect to the database instance DEMODB:

>dbmcli -u OLEG,MONDAY -d DEMODB

dbmcli on DEMODB>

2. Executing the DBM command for waiting for an event:

dbmcli on DEMODB>event_wait

OK

NAME=DBFILLINGABOVELIMIT

PRIORITY=LOW

DATE=20050615

TIME=150344

VALUE1=6998

VALUE2=70

COUNT=8

TEXT=