By default, PowerExchange writes log messages and trace information to a single log file. Although you can easily search for error messages in a single file, the log file can become full, especially if you have long-running jobs such as the PowerExchange Listener. To resolve an out-of-space condition, you usually need to stop PowerExchange.

To avoid PowerExchange outages that result from an out-of-space log file and to make logging more efficient, you can use PowerExchange alternative logging. To implement alternative logging, you must include the TRACING statement in the DBMOVER configuration file. This statement enables PowerExchange to write message and trace information to a series of reusable log files that have a generated numeric suffix. When a reusable log file becomes full, PowerExchange begins writing information to the next log file in the sequence based on the numeric suffix.

On z/OS systems, PowerExchange includes the TRACING statement in the default DBMOVER configuration member. Also, the default JCL for PowerExchange jobs contains the following statement for allocating log data sets:

If this default logging setup is not sufficient, you can use any of the multiple logging strategies that are available for z/OS.

To configure multiple log files: