Triggering events can be specified in server startup parameters, and can be modified at runtime with PROMON or by editing the _dbParams VST.

To specify the triggering event at startup, use the -diagEvent parameter. The -diagEvent accepts a character string of comma-separated keywords and a data collection level that identify the triggering event(s) to capture data for and the amount of data.

The accepted keywords for -diagEvent, are:
  • locktable
  • bithold
  • syserr

You specify the level of data collection by adding :n to the event. Valid values for n range from -15 to 15, where a negative value triggers an event only if an error is fatal, bringing the database down. For a description of event levels, see Event Levels. For more information about the -diagEvent parameter, see Diagnostic events value (-diagEvent).

The following example demonstrates specifying the locktable and syserr triggering events:
-diagEvent locktable:3,syserr:-15
This example sets -diagEvent to bithold:3,locktable:4,syserr:2 using the _DbParams VST:
find _DBparams where _DbParams._DbParams-Name = "-diagEvent".
assign _DbParams._DbParams-Value = "bithold:3,locktable:4,syserr:2".

If you do not specify an event, it is set with the value specified by -diagEvtLevel. By default, -diagEvtLevel is 0, meaning that data collection for that event is off.