Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. DTLDESCRIBE Metadata
  12. PowerExchange Globalization
  13. Using the PowerExchange ODBC Drivers
  14. PowerExchange Datatypes and Conversion Matrix
  15. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  16. Appendix B: PowerExchange Glossary

PowerExchange Message Logs

PowerExchange Message Logs

PowerExchange stores informational, warning, and error messages about bulk data movement and change data capture (CDC) operations in PowerExchange message log files. PowerExchange also writes some message output to standard output (stdout). On z/OS and i5/OS systems, PowerExchange writes WTO messages to the system operator console.
The text for the majority of PowerExchange messages is stored in the DTLMSG file, which is created during installation.
You can use the following types of message log files as the primary location for writing messages:
  • PowerExchange message log file
    . PowerExchange writes all runtime messages to the PowerExchange message log file by default. PowerExchange creates this log file if it does not exist. PowerExchange writes each message, as it occurs, to this single log file. If the message log file becomes full, you must clear it.
    If you enable alternative logging of messages, this primary message log file contains only the DBMOVER statements and any trace information.
  • PowerExchange alternative log files
    . If you enable alternative logging by defining the TRACING statement in the DBMOVER configuration file, PowerExchange writes runtime messages from PowerExchange components, programs, and commands to a set of alternative message log files that are used on a rotating basis. PowerExchange dynamically allocates these alternative log files if they do not exist. When an alternative log file becomes full, PowerExchange switches to another alternative log file and begins overwriting any data in that file. Informatica recommends that you use alternative logging to prevent out-of-space conditions on log files, to improve logging performance, and to control the amount of data that is logged for long-running jobs. Also, with alternative logging, PowerExchange buffers messages and writes them to disk files based on a customized flush interval, thereby reducing I/O activity on these files.
The names of the primary message log file and the alternative log files vary by platform.
To redirect specific messages to destinations other than the default message log file, you can define a message destination override file, called DTLMSGO. The override destinations include the PowerExchange message log file or alternative log file, standard output (stdout), and i5/OS or z/OS system operator console.


We’d like to hear from you!