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.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for SAP HANA
  24. PowerExchange for VSAM and Flat Files
  25. PowerExchange ODBC

Release Guide

Release Guide

Back Next

DBMOVER Configuration File Statements

DBMOVER Configuration File Statements

PowerExchange 10.5.2 introduces the following changes in the DBMOVER configuration file:
AS4J CAPI_CONNECTION
Changed
. This statement includes the new optional RTNBUFFSIZE parameter.
CONVERT_CODEPAGES_WITH_ICONV=[
N
|Y]
New
. Determines whether PowerExchange uses the ICONV functions to covert code pages, or ICU. Using ICONV can reduce memory requirements for complex code pages, such as Chinese or Turkish
Valid values are Y or N. Default is N.
FILEMAPPED_MEMORY_DIR
Changed
. Specifies the directory that stores temporary file-mapped memory files for PowerExchange Listener statistics on AIX PPC64, IBM i (i5/OS), and Solaris SP64 systems. This statement is now required for AIX and IBM i systems.
JOB_START_MINIMUM_MEMORY_MB=
megabytes
New
. Prevents PowerExchange Listener from accepting incoming connections or tasks if the available extended memory in the JCL control region is less than the specified value in the statement.
Valid values are 50 through 1520. Default is 50.
RTNBUFFSIZE={
kilobytes
|
960
}
New
. Adjusts the buffer size, in kilobytes, that is used to collect journal entries for CDC as a result of PowerExchange calls to the IBM QjoRetrieveJournalEntries API. You can use this parameter to tune performance based on your environment.
Valid values are 128 through 12288. Default is 960 KB, which is the IBM default size.
If you also specify the RTNBUFFSIZE in the
PWX Overrides
 field of the PowerCenter PWX DB2i5OS CDC application connection, the override takes precedence.
IMSID
Changed
. This statement contains a change to the
dbdlib
 parameter.
dbdlib
 or DD:
XXXXXXXX
Provides PowerExchange access to the IMS DBD which is required for activities such as reading IMS unload files, registering IMS sources for CDC, and running utilities, including DTLURDMO and DTLUCBRG. In this parameter, you can either specify the IMS DBD library dataset name in line or specify a DD name for PowerExchange to search. By specifying DD:
XXXXXXXX
, where
XXXXXXXX
 is the DD name coded in the JCL for the component requiring access, you can have one or more DBD libraries for a system allocated to the specified DD name.
If you use the DD:
XXXXXXXX
, PowerExchange uses the first DBDLIB it finds in the concatenated list and continues processing. Ensure that you place this DD with the one or more DBD libraries in the appropriate JCL or started task.
LISTENER
Changed
. This statement has the new optional
message_queue
 parameter for IBM i.
IBM i can run multiple PowerExchange Listeners from the same PowerExchange environment by specifying a different message queue for each Listener. For example: 
/* Listener using default message queue (LISTENER)
LISTENER=(node1,TCPIP,2480,262144,262144,262144,262144)             
/* Listener using user defined message queue (LISTENER2)
LISTENER=(node2,TCPIP,12480,262144,262144,262144,262144,,,,LISTENER2)
PG CAPI_CONNECTION
Changed
. This statement can includes the new optional CAPTUREALL parameter.
CAPTUREALL={
N
|Y}
New
. Controls whether PowerExchange captures and stores change data for all tables in the source database or only for the tables registered for CDC. Use this parameter to limit the amount of data that is stored in the replication store table to only the data from registered source tables.
Options are:
  • N
    . Capture DML changes and store the changes in the replication store table, only for registered source tables. This option limits the amount of data that is collected and stored in the store table.
  • Y
    . Capture DML changes and store the changes in the replication store table, for all tables in the source database, including unregistered tables. This setting is not recommended because it can cause more data than is needed for CDC processing to be stored in the replication store table.
Default is N.
UNLOGGED_ERROR_MESSAGES_DEST=[STDERR,STDOUT,ERRFILE,NONE]
New
. Specifies a location to write error messages that might not be logged to the detail.log file because of limits on the file.
Options are:
  • STDERR. Enter this value to write the messages to the standard error file. Informatica recommends you use STDERR for z/OS and Windows systems.
  • STDOUT. Enter this value to write the messages to the standard output file.
  • ERRFILE. Enter this value to write the messages to an error file. PowerExchange creates the error file with the prefix
    errorfile
    . Informatica recommends you use ERRFILE for IBM i, Linux, and UNIX systems, in conjunction with the FILEMAPPED_MEMORY_DIR.
  • NONE. Enter this value if you do not want to record unlogged error messages.
  • On IBM i systems, the STDERR and STDOUT options write the messages to QPRINT spools. Using the ERRFILE option with the FILEMAPPED_MEMORY_DIR statement makes the messages easier to locate.
  • You can specify multiple options, separated by commas. If you specify NONE with any other option, NONE takes precedence, and no unlogged errors are recorded.
For more information, see the "DBMOVER Configuration File" chapter in the
PowerExchange Reference Manual
.
0 COMMENTS
We’d like to hear from you!