How to enable ntspawn debug

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

How do I enable ntspawn debug?

Environment

Release : 9.3x, 9.4x, 9.5x

Component : APPLICATIONS MANAGER

Resolution

**Note that ntspawn debug should only be enabled long enough to gather the necessary debug logs. Enabling long term ntspawn debug is not recommended as log files will continue to grow in size and are not be deleted by Applications Manager's SYSTEM maintenance Process Flow.

On the Windows Agent, ntspawn debug can be enabled by:

1. Edit the %AW_HOME%\site\sosite.bat file.
2. Add the following line to the sosite.bat file and save.
   
   SET so_ntspawndbg=true
   
   
3. Restart the Applications Manager Service (AWW-<MASTER_NAME>) to register sosite.bat changes.
4. Create a debug flag file called BODY (0 byte and no extension) in the %AW_HOME%\debug directory. Create debug directory if it does not exist.

Ntspawn debug can be disabled by:

1. Delete the flag file(s) in %AW_HOME%\debug directory
2. Delete the line "SET so_ntspawndbg=true" from the %AW_HOME%\site\sosite.bat file and save.
3. Restart the Applications Manager Service (AWW-<MASTER_NAME>) to register sosite.bat changes.

 

Once ntspawn debug is enabled and a Job is run, the following will contain debugging information:

1. The standard output or "o file" located in the %AW_HOME\out directory for the Job in question
2. ntspawn debug files are located in the %AW_HOME%\run\LOG directory and have file names listed as ntspawnDebug-<jobid>.