Start/notes.ini Parameters/Debug_AMgr

Debug_AMgr

Parameter: Debug_AMgr
Short description: Enables detailed Agent Manager tracing — fine-grained per subsystem (scheduling, loading, memory, performance, run-time, verbose) — the main diagnostic tool for Agent Manager problems.

Profile

Parameter
Debug_AMgr
Category
Logging / Debug (Agent Manager)
Component
Server
Available since
At least 9.0.1 (HCL Designer documentation 9.0.1 – 14.0)
Supported versions
9.0.1, 10.0, 11.0, 12.0, 14.0, 14.5, 14.5.1
GUI equivalent
notes.ini only (no GUI) — changeable at runtime via tell amgr debug <options>
Possible values
Single letters or combinations: c e l m p r s v *
Default
not set (no tracing)

Description

Debug_AMgr is the primary tracing tool of the Domino Agent Manager. Using one or more option letters, you can selectively control which aspects of AMgr behavior are written to the server log or to the debug outfile:
Option
Meaning
c
Control — Agent Manager control logic (start/stop, transitions between worker threads)
e
Events — internal AMgr events (trigger evaluation, queue movements)
l
Loading — loading and preparing agents (signer resolution, database access)
m
Memory warnings — warnings about memory/resource usage of the AMgr
p
Performance — runtime/performance data per agent
r
Run-time reports — detailed run-time report per agent execution
s
Scheduling — schedule calculations, on-schedule triggers, weekend/day logic
v
Verbose — additional detail level for all other options
*
All options — maximum tracing, significant performance impact
Multiple options can be combined (e.g. Debug_AMgr=lps for Loading + Performance + Scheduling). Output goes by default to the server console and to log.nsf. With Debug_Outfile=<file>, output can be redirected to a central text file — the approach explicitly recommended in the HCL Designer help for longer tracing sessions.
Special feature: via the Tell command
tell amgr debug <options>
Debug_AMgr can be changed at runtime without restarting the Agent Manager. This makes Debug_AMgr one of the few tracing settings that is practical for live diagnostics on production systems without restarting the AMgr.
For operational continuous logging (which agents start when), Log_AgentManager=1 or =2 is the better switch — Debug_AMgr is clearly designed as a short-lived, targeted diagnostic tool.

Example configuration

Targeted combination — Loading + Performance + Scheduling, output to dedicated file:
Debug_AMgr=lps
Debug_Outfile=C:\Domino\Logs\amgr_debug.txt
Only run-time reports per agent — lean performance audit:
Debug_AMgr=r
Debug_Outfile=/local/notesdata/IBM_TECHNICAL_SUPPORT/amgr_runtime.txt
Maximum tracing for short reproduction (not permanent!):
Debug_AMgr=*
Debug_Outfile=C:\Domino\Logs\amgr_full_trace.txt
Runtime activation without server restart — takes effect immediately:
tell amgr debug lps
Runtime deactivation:
tell amgr debug

Notes & pitfalls

  • Performance impact: Even individual options (in particular p, r, v) generate measurable load — Debug_AMgr=* is suitable only for short reproduction windows.
  • Output control: Without Debug_Outfile, output goes directly to the server console / log.nsf — with extensive tracing, older console entries are quickly lost.
  • Live toggle via Tell command: tell amgr debug <options> is the HCL-recommended way to switch Debug_AMgr on and off for live diagnostics; a set config Debug_AMgr=… alone only takes effect after an AMgr restart.
  • Interaction with Log_AgentManager: Both switches can be set in parallel. Debug_AMgr provides more detailed tracing, Log_AgentManager is the permanently operational logger. They complement each other when needed.
  • Option letters are case-insensitive, but in HCL documentation are consistently written in lowercase — when maintaining the configuration settings document, pay attention to consistent casing.
  • * is not for permanent operation: It noticeably slows down the AMgr and on heavily loaded servers can cause timeouts and schedule shifts.
  • Diagnostic classic together with Log_AgentManager=1 and AMgr_DisableMailLookup=1 (KB0032179 bundle) for mail-triggered agent issues.

Sources (HCL Product Documentation)