Packaging the log files
You package log files to provide assistance to IBM® Support.
About this task
- Preserves the information that is required to perform detailed problem determination
- Prevents you from having to scan through messages that were recorded after the problem occurred.
The log package is saved as a JAR (Oracle Java™ Archive) file. The default location of the log package for distributed systems is path_prefix/liberty/wlp/usr/servers/csmServer/diagnostics. For z/OS, the default location is path_prefix/opt/IBM/CSM/wlp/usr/servers/csmServer/diagnostics.
On z/OS, the install_CSM.log and install_CSM_err.log files are not picked up by the log package. If you have any issues that are related to installation or upgrade, or if you have runtime issues and you recently installed or upgraded, send the install_CSM.log and install_CSM_err.log files to IBM Software Support.
Use these steps to package log files with the Copy Services Manager graphical user interface (GUI):
Procedure
- In the Copy Services Manager menu bar, click .
- On the Advanced Tools page, click Create to
create a .jar package file that contains all
log files. When the log package is created, the package file name
and location on the management server is displayed as a link. You
can click the link to download the log package to the server on which
the web browser is running. You can also click Display PE Packages to download the current and previous log packages.
What to do next
If the Copy Services Manager server is not running, you can package the logs manually by gathering all files. For distributed systems, the files are in the directory path_prefix/liberty/wlp/usr/servers/csmServer/logs/. For z/OS, the files are in the directory path_prefix/opt/IBM/CSM/wlp/usr/servers/csmServer/logs. Collect the files into a single .zip or .jar file.