Diagnostic events value (-diagEvent)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Diagnostic events value (-diagEvent) to
specify the database events to collect diagnostic data for.
| Operating system and syntax | UNIX / Windows |
-diagEvent
event-string
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Database Server | — | — | — | — |
- event-string
- A character string of comma-separated keywords, specifying triggering
events and levels.
Valid triggering events are:
locktable-
bithold syserr
You must also specify the level of data collection by adding
:nto the event. Valid values fornrange from -15 to 15. See the table in Diagnostic event level (-diagEvtLevel) for a description of the levels.
In the following example, the lock table overflow event is specified with -15, and the bithold event is specified with 4, and syserror is set to 8.
|
If you do not specify an event, it is set to the value specified by the -diagEvtLevel startup parameter. The -diagEvtLevel default is 0, if not specified; 0 indicates that data is not
collected for the event.
To change this parameter while the database is running, use PROMON or the _DbParams VST.
You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.