Using HP Data Protector Debug Log Collector Tool "Best Practices"

In this scenario you will get debug files on every of these 5 systems. With the help of the omnidlc
command you are able to collect all debug files and additional needed information with the execution
of only one command. No need to travel around with ftp.
Figure 3: Scenario – omnidlc collects debug data from 5 systems (incl. CM)
omnidlc Command Syntax
The Debug Log Collector tool is a command line tool. The command omnidlc has several options
which are described in detail in this chapter.
C:\>omnidlc -help
Usage: omnidlc -version | -help
Usage: omnidlc {-session sessionID | -did debugID
| -postfix string | -no_filter}
[-hosts list]
[-pack filename | -depot directory | -space | -delete_dbg]
[-no_logs] [-no_getinfo] [-no_compress] [-no_config]
[-no_debugs | -debug_loc Dir1 [Dir2 ...]] [-verbose]
[-add_info [-any | host] path]
Usage: omnidlc -localpack [filename]
Usage: omnidlc -unpack [filename]
Usage: omnidlc -uncompress filename
Usage: omnidlc [-hosts list] -del_ctracelog
6