Tracing

Tracing can be switched on when the daemon is started.

1. If running the Global daemon as a service, add a line to the startup batch file singleds.bat to set the environment variable DEBUG_ADMIND as follows:

   DEBUG_ADMIND=1023

2. If the Global daemon in not being used as a service, set DEBUG_ADMIND from the command line.

   The value of the DEBUG_ADMIND variable determines the type of activities that are traced:

   0	=	Not used
   1	=	Not used
   2	=	Trace
   4	=	Remote Procedure Calls
   8	=	Thread Library
   16	=	Systems DB Access
   32	=	Dabacon Thread
   64	=	Event Loop Thread
   128	=	Operation Thread
   256	=	Trans DB I/O
   512	=	Not used
   1024	=	Not used
   2048	=	Dabacon Detail

3. These values are bit settings, so to trace a combination of activities, add the above values together.

   For example, to trace Systems DB access and the Event Loop thread only, set DEBUG_ADMIND as follows:

   DEBUG_ADMIND=80

4. To enable tracing for all activities, set the DEBUG_ADMIND value to 3071.

   A useful level of tracing for tracking commands is 896.

   Full tracing can be verbose and fill disk space rapidly, the recommended value of 896 allows the administrator to gain an idea of the current number of commands running through the system.

   This may help when bringing down a daemon at a particular location. Further tracing may be required when investigating a particular problem.