Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5.8
  • All Products

Table of Contents

Search

  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

Reference Manual

Reference Manual

Back Next

Direct Logging and Delayed Logging

Direct Logging and Delayed Logging

PowerExchange writes messages in one of two ways: direct logging of informational and warning messages or delayed logging by adding error messages to a message block.

Direct Logging

In direct logging, the calling application, such as a PowerExchange Listener, determines the destination for the informational and warning messages. Most informational and warning messages are directed to the log. Some messages are duplicated to standard output (stdout) and a small number of messages are sent to the operator's console on IBM i and z/OS. Processing continues.
Messages are written to the log file where PowerExchange runs. For example on z/OS, messages might be written to an alternative log file or to DD DTLLOG, depending on how logging is configured.
  • It is possible to generate a large quantity of messages from NRDB processing where a map specifies to continue processing after mapping or after data cleansing errors.
  • If an application such as PowerCenter was configured to retrieve messages, messages written to the logs are sent to the client and appear in the session log on the client machine.

Delayed Logging

When an application detects a fatal error, it adds messages to a message block and processing fails. The block contains message numbers and a maximum of 1000 bytes of substitution data to be used inside the messages.
If a PowerExchange Listener task fails, the block of messages is written to the following places:
  • The PowerExchange Listener log file
  • The client log file
  • The session log of the calling application, such as PowerCenter
Messages written to logs on IBM i and z/OS are in English.
Messages written to logs on Linux, UNIX, and Windows might be localized into languages such as Chinese, Japanese, Korean, Portuguese, or Brazilian.
Messages in the block only become visible in the client process after a failure. Otherwise, messages in the block are discarded.
0 COMMENTS
We’d like to hear from you!