Background documentationevent_wait Locate this document in the navigation structure

 

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 the 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)

Recommendation Recommendation

Use this DBM command via a database manager programming interface.

End of the recommendation.

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_wait

Result

OK

NAME=<event_category>

PRIORITY=<priority>

VALUE1=<value1>

VALUE2=<value2>

DATE=<yyyymmdd>

TIME=<HHmmss>

COUNT=<count>

TEXT=[<text>]

Values for the Reply Fields

Values for the Reply Fields

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.

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=

More Information

Glossary, Event, Event Dispatcher