Parameter:
Debug_OutfileShort description: Redirects debug/console output to a specified file (for troubleshooting and HCL Support).
Profile
Parameter | Debug_Outfile |
Category | Logging / Debug |
Component | Server, Client |
Available since | R6 |
Supported versions | 9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5 |
GUI equivalent | notes.ini only (no GUI) |
Possible values | Absolute file path, e.g. D:\Domino\Data\IBM_TECHNICAL_SUPPORT\debug.log |
Description
Debug_Outfile instructs Domino or Notes to additionally write all internal debug output – the combination of console text and output from enabled debug switches (DEBUG_*, Console_Log additions, NSD excerpts, etc.) – to a freely chosen file.This parameter is primarily intended for in-depth error analysis and for providing logs to HCL Support. In normal operation it should not be active.
Example configuration
Debug_Outfile=D:\Domino\Data\IBM_TECHNICAL_SUPPORT\debug.log DEBUG_THREADID=1
Notes & pitfalls
- The file grows extremely fast depending on the enabled debug switches – monitor disk space.
- Use only temporarily; remove again after analysis.
- The path must be writable (Domino service account!).
- With
DEBUG_THREADIDactive, lines are enriched with PID/thread ID – practically required for multi-thread analysis.
- HCL Support often provides precise instructions on which switches to set – do not enable everything "blindly".