Diagnostic pause length (-diagPause)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Diagnostic pause length (-diagPause) to specify the
number of seconds to pause after recording data for a diagnostic event before processing the
event.
| Operating system and syntax | UNIX / Windows |
-diagPause
n
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Database Server | 1920 (30 minutes) | 0 | — | 0 |
- n
- The number of seconds to pause.
Two conditions can cause the pause to terminate before the specified time
elapses:
- DiagComplete file — If you want the pause to terminate, create a file named diagComplete in the event-specific directory. This indicates that the DBA is ready to have the event process.
- DiagProc terminates — If you have specified a process to be spawned when a diagnostic event triggers, the pause will terminate when the spawned process terminates.
Note: If you trigger data collection
from PROMON, or by setting the VST field
_DbStatus._DbStatus-InitiateDiag=TRUE, the pause time is ignored.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.