Troubleshooting and support

Obtaining necessary diagnostic documents

General product log files

Developer for z/OS® logs all information, warning, and severe error messages in a file called workspace/.metadata/.log. A new .log file is created for each session of the workbench. If a .log file exists, it is backed up as .bak_x.log, where x is a sequential number. You can also see the contents of the log file in the Remote Error Log view. All messages are logged always. You do not have to do anything to set logging levels or enable logging. The messages in the log file are intended for user consumption.

For more information about collecting log files, see Collecting log files.

Trace messages

If you set the tracing level for components that support tracing, the product places these messages in a file called workspace/.metadata/.trace. Trace messages consist of the detailed path of execution for a product component and are intended for use by Developer for z/OS developers and support staff, not for user consumption. The trace files are usually requested by the support team. If trace is enabled, a new .trace file is created for each session of the workbench. If a .trace file exists, it is backed up as .bak_x.trace.

For more information about setting the trace level for a component that is enabled for tracing, see Tracing.

Db2® for z/OS Development tooling logs

The Db2 for z/OS Development tooling component of the product logs trace messages in the metadata/.plugins/com.ibm.systemz.db2/logs folder of the Eclipse workspace.

IBM Support portal

The support page can be found here at IBM® Support.