Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Specifying an Alternative Configuration File or License Key File

Specifying an Alternative Configuration File or License Key File

When you start the PowerExchange Listener on an i5/OS, Linux, UNIX, or Windows system, you can include the CONFIG and LICENSE statements in the start command. These statements point to alternative configuration and license key files that you want to use for the PowerExchange Listener execution instead of the default DBMOVER configuration and license.key files. Usually, you create the alternative files by copying the default files to a different location or under a different file name and then customizing the copies. This practice prevents your customized configuration and license key files from being overwritten when you upgrade or reinstall PowerExchange.
On a Linux, UNIX, or Windows system, you can also specify alternative configuration and license key files in the PWX_CONFIG and PWX_LICENSE environment variables. If you do so, the alternative files identified in the CONFIG and LICENSE statements override the alternative files identified in the environment variables for the current PowerExchange Listener execution.

0 COMMENTS

We’d like to hear from you!