Running Debug Logging

Occasionally, SirsiDynix Customer Support staff may ask you to run the Debug program to help them troubleshoot problems. Debug is a diagnostic and reporting tool used to report problems with individual processes. While you run the Debug program, Horizon tracks everything that happens in Horizon until you stop the program. This detailed information is stored in a separate file in your Horizon directory.

You are strongly discouraged from running Debug logging for extended periods of time. On workstations with heavy Horizon activity and limited free disk space, the log generated by Debug can use up the free space if it is left to run unattended for a long period of time. This is primarily a concern on workstations where Horizon is never, or rarely, shut down.

There are two ways you can run Debug logging: you can run it from within Horizon, or you can run it from a command-line window.

If you want to capture the login process as part of your Debug output, you must start Debug from a command line.

Unlike an earlier Debug program (which used system variables), when you close Horizon, the Debug program stops, and will not automatically restart when you restart Horizon.

This section explains these topics:

Running Debug Logging from the Horizon Launcher
Running Debug Logging from the Command Line

 


© 1998-2017 Sirsi Corporation