Configure the PowerExchange Listener by defining statements in the DBMOVER configuration file. You can accept default settings or you can customize configuration statements for your environment.

Configure the TCP/IP port number if the default port number of 2480 is not available or if you use multiple PowerExchange Listeners and need to define additional ports for them.

Configure alternative logging for message and trace information. PowerExchange provides a single log file by default. Because logging data to a single file is inefficient and can result in the log file becoming full, use the PowerExchange alternative logging strategies that are described in the

PowerExchange Reference Manual

. To implement alternative logging, you must specify the TRACING parameter in the DBMOVER configuration file.

On z/OS systems, the default DBMOVER configuration file that is shipped with PowerExchange includes the TRACING statement. Also, the JCL that is provided for PowerExchange jobs, such as netport jobs, contains the following statement for allocating log data sets:

Often, this default logging setup is sufficient. However, multiple other logging strategies are available.

On Linux, UNIX, or Windows, place an exact or modified copy of the dbmover.cfg and license.key files in a location other than the default location. This practice preserves the original files if you upgrade to a new release. To define the alternative files to the PowerExchange Listener, you can enter the full path and file name of each file in the CONFIG and LICENSE statements on the dtllst command when you start the PowerExchange Listener. Alternatively, you can specify the alternative files in the PWX_CONFIG and PWX_LICENSE environment variables.

On z/OS, configure the PowerExchange Listener JCL.

On z/OS, if you use CA TCPAcess instead of IBM z/OS TCP/IP, set up TCP/IP sockets to use TCPAccess.