Running the collect_logs command to collect and package log files

You can run the collect_logs command to automatically collect and package log files to send to IBM® Support (or to use for your own analysis).

The following files are collected:
  • Platform problem determination files
  • Platform provisioning files
  • System configuration files
  • System log and trace files
  • Java™ dump files
  • Problem determination framework internal log files

Output from the collect_logs command

The collect_logs command creates the following files in the $COLLATION_HOME/log/support directory:
  • A compressed file that is the package of log files
  • collect_logs.log. If the collection and packaging of the log files is unsuccessful, review this log file to determine the problem.

collect_logs command details

From the $COLLATION_HOME/bin directory, run one of the following commands, with the parameters of your choice, depending on the operating system:
On Windows systems
collect_logs.bat -i | -g | -h [-f prefix]
On UNIX systems
collect_logs.jy -i | -g | -h [-f prefix]
The parameters in the command represent the following items:
-i
Collects log files and relevant information for troubleshooting an installation problem.
-g
Collects log files and relevant information for troubleshooting a general problem.
-h
Prints the log files and relevant information.
Optional:
-f prefix
Specifies the prefix that you want to add to the name of the compressed file that is the package of log files.

By default, a compressed file named TADDM_ISA_Collection.problem_type.timestamp.zip is created in the $COLLATION_HOME/log/support directory. TADDM_ISA_Collection is the default prefix. To override this default prefix, specify the prefix of your choice.

If you are gathering support information to attach to a problem management record (PMR), include the IBM Support naming convention ppppp.bbb.ccc in your prefix, where:

  • ppppp is the Problem Management Record (PMR) number
  • bbb is the branch number
  • ccc is the country code